Re: [bitfolk] "Boot loader didn't return any data!" starting…

Top Page

Reply to this message
Author: John Winters
Date:  
To: users
Subject: Re: [bitfolk] "Boot loader didn't return any data!" starting Xen VM
On 02/03/13 10:15, Andy Smith wrote:
> Hi John,
>
> On Sat, Mar 02, 2013 at 10:01:21AM +0000, John Winters wrote:
>> hydra:/etc/xen# xm create pragma.cfg
>> Using config file "./pragma.cfg".
>> Error: Boot loader didn't return any data!
>> hydra:/etc/xen#
>
> Run pygrub manually against the block device / image file to see if
> it can successfully extract a kernel and initramfs. If it can't,
> that's your problem.
>
> $ sudo /usr/lib/xen-default/bin/pygrub -q /dev/vg00/domu_ns2lug_xvda
> linux (kernel /var/run/xend/boot/boot_kernel.kvQ_NA)(ramdisk /var/run/xend/boot/boot_ramdisk.PSOZc1)(args "root=LABEL=root ro")


Interesting. That yields:

hydra:~# /usr/lib/xen-default/bin/pygrub -q /dev/lvmdata/pragma-disk
Using <class 'grub.GrubConf.GrubConfigFile'> to parse /boot/grub/menu.lst
Traceback (most recent call last):
   File "/usr/lib/xen-default/bin/pygrub", line 705, in <module>
     output_directory, not_really)
NameError: name 'output_directory' is not defined
hydra:~#


which if I read it correctly suggests that it's pygrub which is slightly
broken. I will start reading the pygrub source to see if I can see what
is going on. It doesn't seem to have a man page.

The menu.lst which it is trying to parse reads:

default         0
timeout         2


title           Debian GNU/Linux 6.0
root            (hd0,0)
kernel          /boot/vmlinuz-2.6.32-5-xen-amd64 root=/dev/xvda2 ro
initrd          /boot/initrd.img-2.6.32-5-xen-amd64


title           Debian GNU/Linux 6.0 (Single-User)
root            (hd0,0)
kernel          /boot/vmlinuz-2.6.32-5-xen-amd64 root=/dev/xvda2 ro single
initrd          /boot/initrd.img-2.6.32-5-xen-amd64



Thanks for your help.

John