similar to: Successfully running VM, subsequently startup gives this error -- VmError: Boot loader didn''t return any data!

I''m newbie Xen-4.1.1 I''m trying to boot DomU with the following configuration. Sometime DomU boot, but sometime boot failed I''m not sure what is the problem. I can attach that image with tap-ctl on Dom0. Does anybody advice me about this problem?? Sincerely * Environment OS : Scientific Linux 6.1 x86_64 Kernel : 2.6.32.43

Hi all, after upgrading from xen 3.0 to xen 3.2 I cannot start my domUs: I get: VmError: Boot loader didn''t return any data! Suggestions? This is the log [2008-06-25 11:24:53 2755] DEBUG (XendDomainInfo:84) XendDomainInfo.create([''vm'', [''name'', ''engtest3.infolan''], [''memory'', ''2048''],

Package: xen-utils-4.0 Version: 4.0.1-2 Severity: normal File: pygrub pygrub error when trying to run a image created by xen-create-image with partitions option. ---------------------------------------------------------------------------------------------------------------------------------------- [2011-10-02 21:36:08 1512] DEBUG (XendDomainInfo:101) XendDomainInfo.create(['vm',

Hardware: 2x Intel Xeon Quad-Core 2.33GHz 24GB FBDIMM RAM 2x 2TB HDD in RAID-1 Intel Server Board S5400SF Setup: Arch Linux x86_64 Xen 4.1.2 Grub2 Multiboot Synopsis: I set up a new VM for Debian Squeeze following instructions here: http://www.howtoforge.com/installing-debian-squeeze-6.0-domu-on-centos-5.5-x86_64-dom0. Partitioning & installation completed correctly. When I tried to run the

If list is searched and item not found, then don''t attempt to delete the item. I''ve seen this bug manifest as xen81:~/bin # xm li Name ID Mem VCPUs State Time(s) Domain-0 0 3151 16 r----- 1240.8 pxe 3 256 1 -b---- 26.4 xen81:~/bin

Package: xen-utils-4.0 Version: 4.0.1-2 If you reboot with the DomU disk DRBD domain destroy. pygrub error when trying to run a image on DRBD device My config DomU ------------------------------------------------------ bootloader = '/usr/lib/xen-default/bin/pygrub' vcpus = '1' memory = '256' cpus="8-15" root = '/dev/xvda2 ro' #disk

After changeset 18030 and 18064 were checked in, I found some issues when creating HVM domains with devices assigned: In XendDomainInfo.py, we have the call trace: the global function create() => vm.start() => _constructDomain(). In _constructDomain(), we invoke xc.test_assign_device() and when the function fails (maybe because iommu=1 is not specified in grub entry since iommu is 0 by

Hello, I would like to use the kernel in the domU, so that a user can install it's own kernel. While starting the domU with pygrub I get the following error: "Error: Boot loader didn't return any data!" This is the configfile of the domU: -------------- # # Configuration file for the Xen instance lenny.vandervlis.nl, created # by xen-tools 3.9 on Sun Oct 19 15:46:03 2008. # #

Hello I''m trying to convert a HVM to PV dom0. The domU is a 10SP2 SLED ( Kernel 2.6.16.60-0.21 i386) and is a SLES11SP2 dom0 (Kernel 3.0.13-0.27-xen 64bit). The truth is that every tutorial I see it differently and I do not know where this error. When I start the domU, pvgrub shows the options but when I select the kenel-xen, returns the error "Boot loader did not return any

Package: xen-hypervisor-4.1-amd64 Version: 4.1.1-3 Severity: important Whenever I try to start a domU, xm create failed for 'Boot loader didn't return any data!'. % sudo xm create -c squeeze.cfg Using config file "/etc/xen/squeeze.cfg". Error: Boot loader didn't return any data! It seems related to the following error in dmesg [1440.163935] pygrub[3654] trap invalid

Hi, I''m trying to install a FC 16 PV guest. After installation the guest doesn''t load with: Error: Boot loader didn''t return any data! xend.log: [2011-11-14 18:57:32 32321] ERROR (XendBootloader:214) Boot loader didn''t return any data! [2011-11-14 18:57:32 32321] ERROR (XendDomainInfo:483) VM start failed Traceback (most recent call last): File

I have pulled a recent (today''s) clone of staging/xen-unstable.hg and I get a failure when trying to create a domain with xend/xm. The failure I get is: Error: (''<domain GUID>'', ''VM_metrics'') I have traced the problem down to where the pci = [ ''02:00.0'' ] parameter (which is the value in my case) from my configuration

hi all, why we implement VM_metrics.VCPUs_utilisation as the proportion of all cpu time? Then XenAPI client (xm) can not get the accumulated cpu_time of each vcpu. I recommend we make VM_metrics.VCPUs_utilisation just the cpu_time which is maintained by hypervisor. Then XenAPI client (xm) not only can get the accumulated cpu_time of each vcpu, but also can calculate the proportion by getting

I have an installation of 32bit SLES 10.1 on 2 servers in my lab that I just rebuilt. I applied the files from xen-3.1.0-install-x86_32.tgz and broke all the virtman functions. The errors I got indicate some missing python classes, specifically xen.install. I''m not sure why. This is what I get when I try to run virtman from the command line. If I try to run it from yast i get nothing.

Hello , everyone I am a newcomer to xen , which i study in recent months . I have deploy the xen-4.1.2 on dell server , centos as dom0 , now , i use the vhd format to be the virtual hard disk , after i execute " xm new ***.cfg" , this vm generate the vm in "xm list" , but when i execute " xm start *** ", "Error: Boot loader didn''t return any data

I keep on getting the following entries in the xend.log file and it''s drowning out the important messages: [2007-07-23 14:58:28 2931] ERROR (XendConfig:909) dumping sxp from device controllers Traceback (most recent call last): File "/usr/lib64/python2.5/site-packages/xen/xend/XendConfig.py", line 895, in to_sxp configs = controller.configurations(txn) File

Hi, I tested xm block-attach command with a wrong parameter(file:). Naturally a command error occurred. Then I retested xm block-attach command with a correct parameter(phy:). But a command error occurred again. The second command error occurred because Xend did not remove device information from self.info when the first command error occurred. # xm block-attach vm1 file:/dev/hda4 hdb1 w

Hello List, i am trying to get xen 3.3.1+ linux kernel 2.6.18 +drbd 8.3.0 working. Here is my config: ---------------------------------------------- kernel = ''/boot/vmlinuz-2.6.18.8-xenU'' memory = ''128'' root = ''/dev/sda2 ro'' disk = [ ''drbd:pgone-disk,sda2,w'' ] name

Hello Xen refuses to create domU VM. I have posted some info about my system. Please suggest a solution. gate xen # xm info host : gate release : 2.6.25.5-1.1dom0 version : #24 SMP Sun Aug 31 16:55:27 EEST 2008 machine : x86_64 nr_cpus : 2 nr_nodes : 1 cores_per_socket : 2 threads_per_core : 1 cpu_mhz : 1999 hw_caps : 178bf3ff:e3d3fbff:00000000:00000010:00000001:00000000:00000003:00000000

Dear Users, Debian Etch 2.6.18.8-xen from xensource.com with Xen 3.3.0 on AMD64: After i want to start the HVM i get: VmError: fail to assign device(1:0.0): maybe it has already been assigned to other domain, or maybe it doesn''t exist. [2008-10-25 19:59:30 2460] DEBUG (__init__:1072) XendDomainInfo.destroy: domid=5 [2008-10-25 19:59:30 2460] DEBUG (__init__:1072)