Hi,

I tried installing Fedora 9 x86_64 as follows:

    virt-install -n Fedora-9-x86_64-test --nographics -p -f 
/files/guests/Fedora-9-x86_64-test/root.img -r 4096 -l http://<my http 
server IP address>/Fedora-9-x86_64-DVD

The installation went fine but the first and all subsequent boot 
attempts failed with the following message in the console:

    # virsh start Fedora-9-x86_64-test
    libvir: Xen Daemon error : POST operation failed: (xend.err "Boot 
loader didn't return any data!")
    error: Failed to start domain Fedora-9-x86_64-test

and the following messages in /var/log/xen/xend.log:

    [2008-11-14 06:58:22 588] DEBUG (SrvDomain:76) Starting domain 
Fedora-9-x86_64-test False
    [2008-11-14 06:58:22 588] DEBUG (XendDomainInfo:1618) 
XendDomainInfo.constructDomain
    [2008-11-14 06:58:22 588] DEBUG (balloon:116) Balloon: 4201280 KiB 
free; need 2048; done.
    [2008-11-14 06:58:22 588] DEBUG (XendDomain:435) Adding Domain: 50
    [2008-11-14 06:58:22 588] DEBUG (XendDomainInfo:1685) 
XendDomainInfo.initDomain: 50 256
    [2008-11-14 06:58:22 7686] DEBUG (XendBootloader:113) Launching 
bootloader as ['/usr/lib/xen/bin/pygrub', 
'--output=/var/run/xend/boot/xenbl.4419', 
'/files/guests/Fedora-9-x86_64-test/root.img'].
    [2008-11-14 06:58:22 588] ERROR (XendBootloader:212) Boot loader 
didn't return any data!
    [2008-11-14 06:58:22 588] ERROR (XendDomainInfo:441) VM start failed
    Traceback (most recent call last):
      File 
"/usr/lib/python2.4/site-packages/xen/xend/XendDomainInfo.py", line 421, 
in start
      File "/usr/lib/python2.4/site-packages/xen/xend/XendTask.py", line 
209, in log_progress
      File 
"/usr/lib/python2.4/site-packages/xen/xend/XendDomainInfo.py", line 
1687, in _initDomain
      File 
"/usr/lib/python2.4/site-packages/xen/xend/XendDomainInfo.py", line 
2059, in _configureBootloader
      File 
"/usr/lib/python2.4/site-packages/xen/xend/XendBootloader.py", line 213, 
in bootloader
    VmError: Boot loader didn't return any data!
    [2008-11-14 06:58:22 588] DEBUG (XendDomainInfo:1893) 
XendDomainInfo.destroy: domid=50
    [2008-11-14 06:58:22 588] DEBUG (XendDomainInfo:1912) 
XendDomainInfo.destroyDomain(50)
    [2008-11-14 06:58:22 588] ERROR (SrvBase:88) Request start failed.
    Traceback (most recent call last):
      File "/usr/lib/python2.4/site-packages/xen/web/SrvBase.py", line 
85, in perform
      File 
"/usr/lib/python2.4/site-packages/xen/xend/server/SrvDomain.py", line 
77, in op_start
      File "/usr/lib/python2.4/site-packages/xen/xend/XendDomain.py", 
line 1006, in domain_start
      File 
"/usr/lib/python2.4/site-packages/xen/xend/XendDomainInfo.py", line 421, 
in start
      File "/usr/lib/python2.4/site-packages/xen/xend/XendTask.py", line 
209, in log_progress
      File 
"/usr/lib/python2.4/site-packages/xen/xend/XendDomainInfo.py", line 
1687, in _initDomain
      File 
"/usr/lib/python2.4/site-packages/xen/xend/XendDomainInfo.py", line 
2059, in _configureBootloader
      File 
"/usr/lib/python2.4/site-packages/xen/xend/XendBootloader.py", line 213, 
in bootloader
    VmError: Boot loader didn't return any data!

The grub configuration of the guest looks OK. If I boot the guest in 
rescue mode, copy the kernel and ramdisk to dom0, and redefine the guest 
to use the kernel and ramdisk from dom0, the guest boots fine.

Any thoughts? One thought here is that xVM's pygrub cannot deal 
correctly with the inode size used by newest Linux distributions by 
default. I had a similar problem with openSUSE 11.

snv101a 64 bit.

Thank you,
Vasiliy
_______________________________________________
xen-discuss mailing list
[email protected]

Reply via email to