Hello,
after upgrading to Xen 3.4.1 on one of my hosts I have problems starting
my PV domUs that are configured to use pygrub.
When issuing "xm create <domU>" I get the following error message:
Boot loader didn't return any data!
Strange enough it worked before and it even still works when invoking xm
create with "-c" (attached console)...
And yes, the kernel is present on the *first* phy-device.
Here the logs from a xm create (without "-c")
[2009-08-08 13:42:08 9846] DEBUG (XendDomainInfo:92)
XendDomainInfo.create(['vm', ['name', 'test01'], ['memory', 1536],
['vcpus', 1], ['on_xend_start', 'ignore'], ['on_xend_stop', 'ignore'],
['uuid', '6f1ff1af-bff3-4fff-8ff7-1bfffffff0'], ['cpus', '1'],
['bootloader', '/usr/bin/pygrub'], ['bootloader_args', '-q'], ['image',
['linux', ['videoram', 4]]], ['s3_integrity', 1], ['device', ['vbd',
['uname', 'phy:vg00/test_sys'], ['dev', 'xvda1'], ['mode', 'w']]],
['device', ['vbd', ['uname', 'phy:vg00/test_swap'], ['dev', 'xvda2'],
['mode', 'w']]], ['device', ['vbd', ['uname', 'phy:vg01/test_transfer'],
['dev', 'xvdb1'], ['mode', 'w']]], ['device', ['vif', ['bridge',
'xenbr0'], ['mac', '00:16:3e:af:13:ef']]], ['device', ['vif', ['bridge',
'xenbr1'], ['mac', '00:16:3e:af:13:f0']]]])
[2009-08-08 13:42:08 9846] DEBUG (XendDomainInfo:2296)
XendDomainInfo.constructDomain
[2009-08-08 13:42:08 9846] DEBUG (balloon:166) Balloon: 10837396 KiB
free; need 4096; done.
[2009-08-08 13:42:08 9846] DEBUG (XendDomain:452) Adding Domain: 15
[2009-08-08 13:42:08 9846] DEBUG (XendDomainInfo:2497)
XendDomainInfo.initDomain: 15 256
[2009-08-08 13:42:08 26472] DEBUG (XendBootloader:113) Launching
bootloader as ['/usr/bin/pygrub',
'--output=/var/run/xend/boot/xenbl.857', '-q', '/dev/vg00/test_sys'].
[2009-08-08 13:42:09 9846] ERROR (XendBootloader:214) Boot loader didn't
return any data!
[2009-08-08 13:42:09 9846] ERROR (XendDomainInfo:476) VM start failed
Traceback (most recent call last):
File "/usr/lib64/python2.6/site-packages/xen/xend/XendDomainInfo.py",
line 456, in start
XendTask.log_progress(31, 60, self._initDomain)
File "/usr/lib64/python2.6/site-packages/xen/xend/XendTask.py", line
209, in log_progress
retval = func(*args, **kwds)
File "/usr/lib64/python2.6/site-packages/xen/xend/XendDomainInfo.py",
line 2499, in _initDomain
self._configureBootloader()
File "/usr/lib64/python2.6/site-packages/xen/xend/XendDomainInfo.py",
line 2919, in _configureBootloader
bootloader_args, kernel, ramdisk, args)
File "/usr/lib64/python2.6/site-packages/xen/xend/XendBootloader.py",
line 215, in bootloader
raise VmError, msg
VmError: Boot loader didn't return any data!
[2009-08-08 13:42:09 9846] DEBUG (XendDomainInfo:2724)
XendDomainInfo.destroy: domid=15
[2009-08-08 13:42:09 9846] DEBUG (XendDomainInfo:2204) No device model
[2009-08-08 13:42:09 9846] DEBUG (XendDomainInfo:2206) Releasing devices
[2009-08-08 13:42:09 9846] ERROR (XendDomainInfo:97) Domain construction
failed
Traceback (most recent call last):
File "/usr/lib64/python2.6/site-packages/xen/xend/XendDomainInfo.py",
line 95, in create
vm.start()
File "/usr/lib64/python2.6/site-packages/xen/xend/XendDomainInfo.py",
line 456, in start
XendTask.log_progress(31, 60, self._initDomain)
File "/usr/lib64/python2.6/site-packages/xen/xend/XendTask.py", line
209, in log_progress
retval = func(*args, **kwds)
File "/usr/lib64/python2.6/site-packages/xen/xend/XendDomainInfo.py",
line 2499, in _initDomain
self._configureBootloader()
File "/usr/lib64/python2.6/site-packages/xen/xend/XendDomainInfo.py",
line 2919, in _configureBootloader
bootloader_args, kernel, ramdisk, args)
File "/usr/lib64/python2.6/site-packages/xen/xend/XendBootloader.py",
line 215, in bootloader
raise VmError, msg
VmError: Boot loader didn't return any data!
And here the same domain just invoked with "-c":
[2009-08-08 13:52:00 9846] DEBUG (XendDomainInfo:92)
XendDomainInfo.create(['vm', ['name', 'test01'], ['memory', 1536],
['vcpus', 1], ['on_xend_start', 'ignore'], ['on_xend_stop',
'ignore'], ['uuid', '6f1ff1af-bff3-4fff-8ff7-1bfffffff0'], ['cpus',
'1'], ['bootloader', '/usr/bin/pygrub'], ['bootloader_args', ''],
['image', ['linux', ['videoram', 4]]], ['s3_int
egrity', 1], ['device', ['vbd', ['uname', 'phy:vg00/test_sys'], ['dev',
'xvda1'], ['mode', 'w']]], ['device', ['vbd', ['uname',
'phy:vg00/test_swap'], ['dev', 'xvda2'], ['mode',
'w']]], ['device', ['vbd', ['uname', 'phy:vg01/test_transfer'],
['dev', 'xvdb1'], ['mode', 'w']]], ['device', ['vif', ['bridge',
'xenbr0'], ['mac', '00:16:3e:af:13:ef']]], ['devic
e', ['vif', ['bridge', 'xenbr1'], ['mac', '00:16:3e:af:13:f0']]]])
[2009-08-08 13:52:00 9846] DEBUG (XendDomainInfo:2296)
XendDomainInfo.constructDomain
[2009-08-08 13:52:00 9846] DEBUG (balloon:166) Balloon: 10837512 KiB
free; need 4096; done.
[2009-08-08 13:52:00 9846] DEBUG (XendDomain:452) Adding Domain: 16
[2009-08-08 13:52:00 9846] DEBUG (XendDomainInfo:2497)
XendDomainInfo.initDomain: 16 256
[2009-08-08 13:52:00 26498] DEBUG (XendBootloader:113) Launching
bootloader as ['/usr/bin/pygrub',
'--output=/var/run/xend/boot/xenbl.30588', '/dev/vg00/test_sys'].
[2009-08-08 13:52:02 9846] DEBUG (XendDomainInfo:2521)
_initDomain:shadow_memory=0x0, memory_static_max=0x60000000,
memory_static_min=0x0.
[2009-08-08 13:52:02 9846] DEBUG (balloon:166) Balloon: 10837396 KiB
free; need 1579008; done.
[2009-08-08 13:52:02 9846] INFO (image:173) buildDomain os=linux dom=16
vcpus=1
[2009-08-08 13:52:02 9846] DEBUG (image:659) domid = 16
[2009-08-08 13:52:02 9846] DEBUG (image:660) memsize = 1536
[2009-08-08 13:52:02 9846] DEBUG (image:661) image =
/var/run/xend/boot/boot_kernel.O4SUz_
[2009-08-08 13:52:02 9846] DEBUG (image:662) store_evtchn = 1
[2009-08-08 13:52:02 9846] DEBUG (image:663) console_evtchn = 2
[2009-08-08 13:52:02 9846] DEBUG (image:664) cmdline =
root=/dev/xvda1 ro console=hvc0
[2009-08-08 13:52:02 9846] DEBUG (image:665) ramdisk =
[2009-08-08 13:52:02 9846] DEBUG (image:666) vcpus = 1
[2009-08-08 13:52:02 9846] DEBUG (image:667) features =
[2009-08-08 13:52:02 9846] DEBUG (image:668) flags = 0
and so on...
This is on a gentoo x64 system, running Xen 3.4.1-release (own ebuild).
Thanks,
Christian
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
Home