search for: xenbl

...ugStatusCallback 1. [2012-10-18 12:25:53 3511] DEBUG (DevController:616) frontendStatusCallback /local/domain/0/device/vbd/268441856/state = 4 [2012-10-18 12:25:53 27501] DEBUG (XendBootloader:130) Launching bootloader as [''/usr/bin/pygrub'', ''--output=/var/run/xend/boot/xenbl.3769'', ''/dev/xvdz''] +++ this is where the menu shows pvgrub (/ dev/xvdz1 is mountable and contains the root of linux) +++ [2012-10-18 12:27:31 3511] ERROR (XendBootloader:231) Boot loader didn''t return any data! [2012-10-18 12:27:31 3511] INFO (XendDomainInfo:3...

...) Adding Domain: 3 [2011-11-20 09:01:11 2779] DEBUG (XendDomainInfo:2836) XendDomainInfo.initDomain: 3 256 [2011-11-20 09:01:11 3654] DEBUG (XendBootloader:113) Launching bootloader as ['/usr/lib/xen-default/bin/pygrub', '--args=root=/dev/xvda2 ro ', '--output=/var/run/xend/boot/xenbl.8881', '/home/starch/data/xen/domains/squeeze/disk.img']. [2011-11-20 09:01:11 2779] ERROR (XendBootloader:214) Boot loader didn't return any data! [2011-11-20 09:01:11 2779] ERROR (XendDomainInfo:488) VM start failed Traceback (most recent call last): File "/usr/lib/xen-4.1/...

....3 opensolaris 38 2048 0 --p--- 0.0 The log doesn''t seem to show anything useful, [2010-08-02 00:23:19 6022] DEBUG (XendBootloader:113) Launching bootloader as [''/usr/lib/xen-4.0/bin/pygrub'', ''--output=/var/run/xend/boot/xenbl.26929'', ''/dev/internal/opensolaris'']. If I unpause it, nothing happens. I have to destroy it to get rid of the "stuck" instance. This is my config, and the output of the xm info command: bootloader = ''/usr/lib/xen-4.0/bin/pygrub'' memory...

...8-11-26 13:51:31 2705] DEBUG (XendDomainInfo:1703) XendDomainInfo.initDomain: 15 256 [2008-11-26 13:51:31 2579] DEBUG (XendBootloader:100) Launching bootloader as ['/usr/lib/xen-3.2-1/bin/pygrub', '--args=root=/dev/sda2 ro console=xvc0 xencons=xvc0', '--output=/var/run/xend/boot/xenbl.21780', '-q', '/dev/volume0/lenny.vandervlis.nl-swap']. [2008-11-26 13:51:31 2705] ERROR (XendBootloader:171) Boot loader didn't return any data! [2008-11-26 13:51:31 2705] ERROR (XendDomainInfo:440) VM start failed Traceback (most recent call last): File "/usr/lib/xe...

...:38:45 1918] DEBUG (XendDomain:464) Adding Domain: 7 [2012-03-07 15:38:45 1918] DEBUG (XendDomainInfo:2818) XendDomainInfo.initDomain: 7 256 [2012-03-07 15:38:45 5169] DEBUG (XendBootloader:113) Launching bootloader as [''/usr/bin/pygrub-4.1b'', ''--output=/var/run/xend/boot/xenbl.20421'', ''-q'', ''/vm/leela/leela.img'']. -- Mike Brancato

...m/create.py, making sure that all the needed info is passed > to the bootloader and also stored for reuse on rebooting. Some more remarks: XendBootloader.py misses a timeout and waits for the bootloader to finish forever; I just made a TODO. One of the problems it causes though is that the xenbl FIFO may stay laying around. To avoid clashes, I have added some randomness to the name. Apart from the, the patch does add storing and passing --disks= --root= --entry= to the bootloader call. In the reboot code, I reconstruct the disks list in the form it''s created on initial creation...

Hi, I''m using a custom block script in my xen setup and when started, it creates a new device node pointing to some network resources. Now I noticed that the script is called twice for the root block, the first time for pygrub most likely, but is only stopped once ... I don''t mind creating two devices node, but then I need to destroy both ... Is this a known issue ? Cheers,

Following a Xen tutorial but can''t get the VM (PV Squeeze) running. After doing: # xm create -c /etc/xen/tutorial-pv-guest.cfg The prompt just sits there. Opening another terminal: # xm list /usr/lib/python2.7/dist-packages Name ID Mem VCPUs State Time(s) Domain-0 0 7199 4 r----- 40.6

...25 11:24:53 2755] DEBUG (XendDomain:443) Adding Domain: 2 [2008-06-25 11:24:53 2755] DEBUG (XendDomainInfo:1692) XendDomainInfo.initDomain: 2 256 [2008-06-25 11:24:53 3421] DEBUG (XendBootloader:100) Launching bootloader as [''/usr/bin/pygrub'', ''--output=/var/run/xend/boot/xenbl.20268'', ''/dev/HYP02VM/ENGTEST3'']. [2008-06-25 11:24:53 2755] ERROR (XendBootloader:171) Boot loader didn''t return any data! [2008-06-25 11:24:53 2755] ERROR (XendDomainInfo:440) VM start failed Traceback (most recent call last): File "/usr/lib/python2.4/si...

...Adding Domain: 3 [2011-10-02 21:36:08 1512] DEBUG (XendDomainInfo:2818) XendDomainInfo.initDomain: 3 256 [2011-10-02 21:36:08 14338] DEBUG (XendBootloader:113) Launching bootloader as ['/usr/lib/xen-default/bin/pygrub', '--args=root=/dev/xvda2 ro ', '--output=/var/run/xend/boot/xenbl.24899', '/dev/data/builder-var ']. [2011-10-02 21:36:08 1512] ERROR (XendBootloader:214) Boot loader didn't return any data! [2011-10-02 21:36:08 1512] ERROR (XendDomainInfo:483) VM start failed Traceback (most recent call last): File "/usr/lib/xen-4.0/lib/python/xen/xend/Xen...

...ing Domain: 42 [2011-10-29 21:03:48 26862] DEBUG (XendDomainInfo:2818) XendDomainInfo.initDomain: 42 256 [2011-10-29 21:03:48 27141] DEBUG (XendBootloader:113) Launching bootloader as ['/usr/lib/xen-default/bin/pygrub', '--args=root=/dev/xvda2 ro ', '--o utput=/var/run/xend/boot/xenbl.19733', '-q', '/dev/drbd0']. [2011-10-29 21:03:48 26862] DEBUG (XendDomainInfo:2845) _initDomain:shadow_memory=0x0, memory_static_max=0x10000000, memory_static_min=0x0. [2011-10-29 21:03:48 26862] INFO (image:182) buildDomain os=linux dom=42 vcpus=1 [2011-10-29 21:03:48 26862] D...

Hi, I''ve prepared a Ubuntu 10.04 LTS server on a Xen 3.2-1 host running Debian Lenny on kernel 2.6.26-2-xen-amd64. The Ubuntu 10.04 domU is running a 2.6.32-24-server kernel from the Ubuntu repositories, which is (must be :-) ) xen-aware. The domU uses pygrub to boot and it works like a charm. Now I''m trying to deploy this domU on a Xen 3.2-1 host running Debian Etch on kernel

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

...0 09:35:17 907] DEBUG (XendDomain:476) Adding Domain: 17 [2012-07-20 09:35:17 907] DEBUG (XendDomainInfo:2836) XendDomainInfo.initDomain: 17 256 [2012-07-20 09:35:17 25157] DEBUG (XendBootloader:113) Launching bootloader as [''/usr/bin/pygrub'', ''--output=/var/run/xend/boot/xenbl.15844'', ''--kernel=/boot/vmlinuz'', ''--ramdisk=/boot/initrd'', ''/dev/VPS/fennec'']. [2012-07-20 09:35:17 907] ERROR (XendBootloader:214) Boot loader didn''t return any data! [2012-07-20 09:35:17 907] ERROR (XendDomainInfo:488) VM st...

...:435) Adding Domain: 2 57:27 3636] DEBUG (XendDomainInfo:1566) XendDomainInfo.initDomain: 2 256 57:27 4423] DEBUG (XendBootloader:101) Launching bootloader as [''/usr/lib/xen/boot/domUloader.py'', ''--args= TERM=xterm'', ''--o utput=/var/run/xend/boot/xenbl.20430'', ''-q'', ''/dev/vg01/domino-sys'']. 59:49 3636] INFO (XendDomain:1141) Domain OSS103.lvm (2) unpaused. 05:57 3636] DEBUG (XendDomainInfo:1758) XendDomainInfo.destroy: domid=2 05:57 3636] DEBUG (XendDomainInfo:1775) XendDomainInfo.destroyDo...

...', ] --- Pygrub gives the error "Error: Boot loader didn't return any data". In the xend.log I see: ---- Launching bootloader as ['/usr/lib/xen-3.2-1/bin/pygrub', '--args=root=/dev/sda2 ro console=xvc0 xencons=xvc0', '--output=/var/run/xend/boot/xenbl.21780', '-q', '/dev/volume0/lenny.vandervlis.nl-swap']. ---- Switching the disk statements helps as a workarround, so this work: ---- disk = [ 'phy:/dev/volume0/lenny.vandervlis.nl-disk,sda2,w', 'phy:/dev/volume0/lenny.vand...

...:00 718] DEBUG (XendDomain:435) Adding Domain: 2 [2008-07-03 14:47:00 718] DEBUG (XendDomainInfo:1612) XendDomainInfo.initDomain: 2 256 [2008-07-03 14:47:00 816] DEBUG (XendBootloader:113) Launching bootloader as [''/usr/lib/xen/bin/pygrub'', ''--output=/var/run/xend/boot/xenbl.4403'', ''/export/home/solarisdvd.iso'']. [2008-07-03 14:47:03 718] DEBUG (XendDomainInfo:1646) _initDomain:shadow_memory=0x0, memory_static_max=0x40000000, memory_static_min=0x0. [2008-07-03 14:47:03 718] DEBUG (balloon:116) Balloon: 1053104 KiB free; need 1048576; done....

...[2013-02-25 13:06:34 5470] DEBUG (XendDomainInfo:2818) XendDomainInfo.initDomain: 39 256 [2013-02-25 13:06:34 5781] DEBUG (XendBootloader:113) Launching bootloader as ['/usr/lib/xen-4.0/bin/pygrub', '--args=root=/dev/xvdb ', '--output=/var/run/xend/boot/xenbl.6040', '/dev/lv/vserv1-boot']. [2013-02-25 13:06:39 5470] DEBUG (XendDomainInfo:2845) _initDomain:shadow_memory=0x0, memory_static_max=0x80000000, memory_static_min=0x0. [2013-02-25 13:06:39 5470] INFO (image:182) buildDomain os=linux dom=39 vcpus=2 [2013-0...

Note: I could simply direct boot the appropriate kernel/initrd to get the alpha1 installation going as always done in the past, but I think this should work. The Debian alpha 1 installer page says it should. Details $ sudo xm create -c wheezytest.cfg Using config file "./wheezytest.cfg". Error: Boot loader didn''t return any data! direct pygrub test run: # pygrub

Package: xen-utils-4.0 Version: 4.0.1-2 Severity: normal This issue is similar to http://lists.alioth.debian.org/pipermail/pkg-xen-devel/2011-March/003217.html but since I was not able to find a bug report I'm reporting this now. Steps to reproduce: 1) cat << EOF > config name = 'squeeze64' vcpus = '4' memory = '512' disk = [