Xen users - Jun 2012 - Error: Boot loader didn't return any data [pygrub boot debian wheezy alpha1 netinst ISO]

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 --kernel=/install.amd/vmlinuz --ramdisk=/install.amd/initrd.gz 
/BACKUP/dumpz/wheezytest/debian-wheezy-DI-a1-amd64-netinst.iso
linux (kernel /var/run/xend/boot/boot_kernel.TjAeCF)(ramdisk 
/var/run/xend/boot/boot_ramdisk.1RMH9A)



pygrub version is 4.0.2-rc1-pre (I want to avoid upgrading xen right now 
as this has been running over a year for sure.  Actually the debian 
wheezy install I create will eventually replace my current ubuntu lucid 
dom0 which will get virtualized)



domU config file:

name = "wheezytest"
memory = 256

disk = [
           
''file:/BACKUP/dumpz/wheezytest/debian-wheezy-DI-a1-amd64-netinst.iso,xvdd:cdrom,r''
         , ''phy:/dev/mainvg/wheezytest-root,xvda,w''
         , ''phy:/dev/mainvg/wheezytest-swap,xvdb,w''
]

vif = ['' '']

bootloader = "pygrub"
bootloader_args = "--kernel=/install.amd/vmlinuz 
--ramdisk=/install.amd/initrd.gz"
extra = "debian-installer/exit/always_halt=true -- console=hvc0"

Hello.

El 28/06/12 14:50, Richie escribió:
> 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.
>
> domU config file:
>
> name = "wheezytest"
> memory = 256
>
> disk = [
>
''file:/BACKUP/dumpz/wheezytest/debian-wheezy-DI-a1-amd64-netinst.iso,xvdd:cdrom,r''
>
>          , ''phy:/dev/mainvg/wheezytest-root,xvda,w''
>          , ''phy:/dev/mainvg/wheezytest-swap,xvdb,w''
> ]
>
> vif = ['' '']
>
> bootloader = "pygrub"
> bootloader_args = "--kernel=/install.amd/vmlinuz
> --ramdisk=/install.amd/initrd.gz"
> extra = "debian-installer/exit/always_halt=true -- console=hvc0"
There is a funny issue with pygrub.
It looks for the first element of "disk =" array form the config file,
and tries to get boot images from there. In you case, it''s CDROM.

Re-order the mention of block device, make /dev/mainvg/wheezytest-root 
to appear first.

-- 
Alexandre Kouznetsov

On 6/28/2012 4:11 PM, Alexandre Kouznetsov wrote:
> Hello.
>
> El 28/06/12 14:50, Richie escribió:
>> 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.
>>
>> domU config file:
>>
>> name = "wheezytest"
>> memory = 256
>>
>> disk = [
>>
''file:/BACKUP/dumpz/wheezytest/debian-wheezy-DI-a1-amd64-netinst.iso,xvdd:cdrom,r''
>>
>>
>>          , ''phy:/dev/mainvg/wheezytest-root,xvda,w''
>>          , ''phy:/dev/mainvg/wheezytest-swap,xvdb,w''
>> ]
>>
>> vif = ['' '']
>>
>> bootloader = "pygrub"
>> bootloader_args = "--kernel=/install.amd/vmlinuz
>> --ramdisk=/install.amd/initrd.gz"
>> extra = "debian-installer/exit/always_halt=true --
console=hvc0"
>
> There is a funny issue with pygrub.
> It looks for the first element of "disk =" array form the config
file,
> and tries to get boot images from there. In you case, it''s CDROM.
>
> Re-order the mention of block device, make /dev/mainvg/wheezytest-root 
> to appear first.
>
Hi thanks for the response.  You have misunderstood me so let me 
clarify.   Here in this case the volume wheezytest-root does not have 
any data yet and this is why I am trying to pygrub boot the installation 
ISO so I can then perform the installation.  So I would want the ISO 
first in this case.

There is claim that this can be done this way (instead of direct booting 
a copy of the kernel and initrd) but my guess is that either my pygrub 
is too old or maybe the wheezy Alpha1 installer is missing some 
important bits?  I can''t be sure because that Error is cryptic and
based
on my searches can happen for different reasons.  What really has me 
miffed though is that my manual pygrub test output looks like it did 
find and extract the kernel and initrd.

On Thu, 2012-06-28 at 20:50 +0100, Richie wrote:
> 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!
Are there any details in /var/log/xen/*? 
> direct pygrub test run:
> # pygrub --kernel=/install.amd/vmlinuz --ramdisk=/install.amd/initrd.gz 
> /BACKUP/dumpz/wheezytest/debian-wheezy-DI-a1-amd64-netinst.iso
> linux (kernel /var/run/xend/boot/boot_kernel.TjAeCF)(ramdisk 
> /var/run/xend/boot/boot_ramdisk.1RMH9A)
Strictly speaking debian-wheezy-DI-a1-amd64-netinst.iso isn''t an image
which supports Xen (although I''d have thought it would happen to work).

Strictly speaking you should be using
debian-wheezy-DI-a1-amd64-i386-netinst.iso and
"--kernel=/install.amd/xen/vmlinuz
--ramdisk=/install.amd/xen/initrd.gz"
-- this is what I''ve actually tested.

It looks like you''ve probably already seen
http://wiki.xen.org/wiki/Debian_Guest_Installation_Using_Debian_Installer ?
> pygrub version is 4.0.2-rc1-pre (I want to avoid upgrading xen right now 
> as this has been running over a year for sure.  Actually the debian 
> wheezy install I create will eventually replace my current ubuntu lucid 
> dom0 which will get virtualized)
> 
> 
> 
> domU config file:
> 
> name = "wheezytest"
> memory = 256
> 
> disk = [
>            
>
''file:/BACKUP/dumpz/wheezytest/debian-wheezy-DI-a1-amd64-netinst.iso,xvdd:cdrom,r''
>          , ''phy:/dev/mainvg/wheezytest-root,xvda,w''
>          , ''phy:/dev/mainvg/wheezytest-swap,xvdb,w''
> ]
> 
> vif = ['' '']
> 
> bootloader = "pygrub"
> bootloader_args = "--kernel=/install.amd/vmlinuz 
> --ramdisk=/install.amd/initrd.gz"
> extra = "debian-installer/exit/always_halt=true -- console=hvc0"
> 
> 
> 
> 
> 
> _______________________________________________
> Xen-users mailing list
> Xen-users@lists.xen.org
> http://lists.xen.org/xen-users

On Fri, 2012-06-29 at 09:24 +0100, Ian Campbell wrote:
> Strictly speaking you should be using
> debian-wheezy-DI-a1-amd64-i386-netinst.iso and
> "--kernel=/install.amd/xen/vmlinuz
--ramdisk=/install.amd/xen/initrd.gz"
> -- this is what I''ve actually tested.
tested with xl... turns out that xend calls bootloader_args
"boot_args",
does making that change help?
> 
> It looks like you''ve probably already seen
> http://wiki.xen.org/wiki/Debian_Guest_Installation_Using_Debian_Installer ?
> 
> > pygrub version is 4.0.2-rc1-pre (I want to avoid upgrading xen right
now
> > as this has been running over a year for sure.  Actually the debian 
> > wheezy install I create will eventually replace my current ubuntu
lucid
> > dom0 which will get virtualized)
> > 
> > 
> > 
> > domU config file:
> > 
> > name = "wheezytest"
> > memory = 256
> > 
> > disk = [
> >            
> >
''file:/BACKUP/dumpz/wheezytest/debian-wheezy-DI-a1-amd64-netinst.iso,xvdd:cdrom,r''
> >          , ''phy:/dev/mainvg/wheezytest-root,xvda,w''
> >          , ''phy:/dev/mainvg/wheezytest-swap,xvdb,w''
> > ]
> > 
> > vif = ['' '']
> > 
> > bootloader = "pygrub"
> > bootloader_args = "--kernel=/install.amd/vmlinuz 
> > --ramdisk=/install.amd/initrd.gz"
> > extra = "debian-installer/exit/always_halt=true --
console=hvc0"
> > 
> > 
> > 
> > 
> > 
> > _______________________________________________
> > Xen-users mailing list
> > Xen-users@lists.xen.org
> > http://lists.xen.org/xen-users
> 
> 
> 
> _______________________________________________
> Xen-users mailing list
> Xen-users@lists.xen.org
> http://lists.xen.org/xen-users

On 6/29/2012 4:53 AM, Ian Campbell wrote:
> On Fri, 2012-06-29 at 09:24 +0100, Ian Campbell wrote:
>> Strictly speaking you should be using
>> debian-wheezy-DI-a1-amd64-i386-netinst.iso and
>> "--kernel=/install.amd/xen/vmlinuz
--ramdisk=/install.amd/xen/initrd.gz"
Upon mounting the ISO loopback I discovered there is no xen dir 
structure under install.amd (or anywhere for that matter) and that is 
why I removed it.  My hopes were that the lone kernel/initrd worked 
under Xen like the alpha 1 installer release page suggests.
>> -- this is what I''ve actually tested.
> tested with xl... turns out that xend calls bootloader_args
"boot_args",
> does making that change help?
No.

I am going to paste the xend log.  From what I see in that output is 
that it is ignoring all bootloader_args I specified and just passing 
"-q".  Maybe this explains why my manual pygrub test appears to work 
while this does not?  And yes I read the installer link you mentioned as 
that is where I got my base config from.

P.S.  Thanks for the response.


[2012-06-29 16:22:30 1903] DEBUG (XendDomainInfo:101)
XendDomainInfo.create([''vm'', [''name'',
''wheezytest''], [''memory'', 256],
[''on_xend_start'', ''ignore''],
[''on_xend_stop'', ''ignore''],
[''vcpus'', 1], [''oos'', 1],
[''bootloader'', ''/usr/bin/pygrub''],
[''bootloader_args'', ''-q''],
[''image'', [''linux'',
[''videoram'', 4], [''args'',
''debian-installer/exit/always_halt=true -- console=hvc0''],
[''tsc_mode'', 0], [''nomigrate'', 0]]],
[''s3_integrity'', 1], [''device'',
[''vbd'', [''uname'',
''file:/BACKUP/dumpz/wheezytest/debian-wheezy-DI-a1-amd64-netinst.iso''],
[''dev'', ''xvdd:cdrom''],
[''mode'', ''r'']]],
[''device'', [''vbd'',
[''uname'',
''phy:/dev/mainvg/wheezytest-root''], [''dev'',
''xvda''], [''mode'', ''w'']]],
[''device'', [''vbd'',
[''uname'',
''phy:/dev/mainvg/wheezytest-swap''], [''dev'',
''xvdb''], [''mode'', ''w'']]],
[''device'', [''vif'']]])
[2012-06-29 16:22:30 1903] DEBUG (XendDomainInfo:2508)
XendDomainInfo.constructDomain
[2012-06-29 16:22:30 1903] DEBUG (balloon:220) Balloon: 4084428 KiB free; need
16384; done.
[2012-06-29 16:22:30 1903] DEBUG (XendDomain:464) Adding Domain: 22
[2012-06-29 16:22:30 1903] DEBUG (XendDomainInfo:2818)
XendDomainInfo.initDomain: 22 256
[2012-06-29 16:22:30 901] DEBUG (XendBootloader:113) Launching bootloader as
[''/usr/bin/pygrub'',
''--args=debian-installer/exit/always_halt=true --
console=hvc0'',
''--output=/var/run/xend/boot/xenbl.15686'',
''-q'',
''/BACKUP/dumpz/wheezytest/debian-wheezy-DI-a1-amd64-netinst.iso''].
[2012-06-29 16:22:31 1903] ERROR (XendBootloader:214) Boot loader
didn''t return any data!
[2012-06-29 16:22:31 1903] ERROR (XendDomainInfo:483) VM start failed
Traceback (most recent call last):
   File
"/usr/local/lib/python2.6/dist-packages/xen/xend/XendDomainInfo.py",
line 469, in start
     XendTask.log_progress(31, 60, self._initDomain)
   File "/usr/local/lib/python2.6/dist-packages/xen/xend/XendTask.py",
line 209, in log_progress
     retval = func(*args, **kwds)
   File
"/usr/local/lib/python2.6/dist-packages/xen/xend/XendDomainInfo.py",
line 2820, in _initDomain
     self._configureBootloader()
   File
"/usr/local/lib/python2.6/dist-packages/xen/xend/XendDomainInfo.py",
line 3266, in _configureBootloader
     bootloader_args, kernel, ramdisk, args)
   File
"/usr/local/lib/python2.6/dist-packages/xen/xend/XendBootloader.py",
line 215, in bootloader
     raise VmError, msg
VmError: Boot loader didn''t return any data!
[2012-06-29 16:22:31 1903] DEBUG (XendDomainInfo:3053) XendDomainInfo.destroy:
domid=22
[2012-06-29 16:22:31 1903] DEBUG (XendDomainInfo:2416) No device model
[2012-06-29 16:22:31 1903] DEBUG (XendDomainInfo:2418) Releasing devices
[2012-06-29 16:22:31 1903] ERROR (XendDomainInfo:106) Domain construction failed
Traceback (most recent call last):
   File
"/usr/local/lib/python2.6/dist-packages/xen/xend/XendDomainInfo.py",
line 104, in create
     vm.start()
   File
"/usr/local/lib/python2.6/dist-packages/xen/xend/XendDomainInfo.py",
line 469, in start
     XendTask.log_progress(31, 60, self._initDomain)
   File "/usr/local/lib/python2.6/dist-packages/xen/xend/XendTask.py",
line 209, in log_progress
     retval = func(*args, **kwds)
   File
"/usr/local/lib/python2.6/dist-packages/xen/xend/XendDomainInfo.py",
line 2820, in _initDomain
     self._configureBootloader()
   File
"/usr/local/lib/python2.6/dist-packages/xen/xend/XendDomainInfo.py",
line 3266, in _configureBootloader
     bootloader_args, kernel, ramdisk, args)
   File
"/usr/local/lib/python2.6/dist-packages/xen/xend/XendBootloader.py",
line 215, in bootloader
     raise VmError, msg
VmError: Boot loader didn''t return any data!

> On 6/29/2012 4:53 AM, Ian Campbell wrote:
>
>>> -- this is what I''ve actually tested.
>> tested with xl... turns out that xend calls bootloader_args
"boot_args",
>> does making that change help?
>
FYI
ignore my last updates.

I just got it to boot using "bootargs" without the underscore.  I
tried
that based on this random google hit: 
http://www.redhat.com/archives/libvir-list/2010-August/msg00065.html

Thanks for the support.

Op Fri, 29 Jun 2012 09:24:24 +0100
Ian Campbell <Ian.Campbell@citrix.com> schreef:
> > $ sudo xm create -c wheezytest.cfg
> > Using config file "./wheezytest.cfg".
> > Error: Boot loader didn''t return any data!  
> 
> Are there any details in /var/log/xen/*? 
Derailing from the topic a little bit -- Ian, perhaps it is a good idea
to suggest this (i.e. check the logs in /var/log/xen/) together with the
"Boot loader didn''t return any data!" message? We see that
many people
don''t understand the error and think, "if the boot loader
didn''t return
any data then the problem must be the boot loader!"

How about a more descriptive error, for example:

Error: Boot loader didn''t return any data. This probably means the VM
has crashed. Details can usually be found in /var/log/xen/.

Your thoughts on this suggestion? Do share. :-)

Mark

I''m also having the same regression with Wheezy and xen 4.2 in the last
months with pygrub and pv-grub, I can''t understand what is the problem
for
now.
Here are some details on one of my test builds:
http://xen.1045712.n5.nabble.com/Test-result-of-xen-unstable-changeset-25459-td5709334.html

--
View this message in context:
http://xen.1045712.n5.nabble.com/Error-Boot-loader-didn-t-return-any-data-pygrub-boot-debian-wheezy-alpha1-netinst-ISO-tp5709841p5709916.html
Sent from the Xen - User mailing list archive at Nabble.com.

On 7/2/2012 1:29 AM, Mark van Dijk wrote:
> Op Fri, 29 Jun 2012 09:24:24 +0100
> Ian Campbell<Ian.Campbell@citrix.com>  schreef:
>
>>> $ sudo xm create -c wheezytest.cfg
>>> Using config file "./wheezytest.cfg".
>>> Error: Boot loader didn''t return any data!
>> Are there any details in /var/log/xen/*?
> Derailing from the topic a little bit -- Ian, perhaps it is a good idea
> to suggest this (i.e. check the logs in /var/log/xen/) together with the
> "Boot loader didn''t return any data!" message? We see
that many people
> don''t understand the error and think, "if the boot loader
didn''t return
> any data then the problem must be the boot loader!"
>
> How about a more descriptive error, for example:
>
> Error: Boot loader didn''t return any data. This probably means the
VM
> has crashed. Details can usually be found in /var/log/xen/.
>
> Your thoughts on this suggestion? Do share. :-)
>
> Mark
>

I had looked at and discarded /var/log/xen/xend.log (the only log 
written to) several times before I had realized that bootloader_args 
parameters were getting ignored completely.  Is there any level of 
syntax checking for the xm config files in that xm create could have 
complained about the use of "bootloader_args=" earlier in the process 
instead?

Here is the final working test config that I used for the regular amd64 
(non multi-arch) netinst ISO.  DHCP just worked during the install so 
apparently xen-netfront support is already there.

name = "wheezytest"
memory = 256

disk = [
           
''file:/BACKUP/dumpz/wheezytest/debian-wheezy-DI-a1-amd64-netinst.iso,xvdd:cdrom,r''
         , ''phy:/dev/mainvg/wheezytest-root,xvda,w''
         , ''phy:/dev/mainvg/wheezytest-swap,xvdb,w''
]

vif = ['' '']

bootloader = "pygrub"
bootargs = "--kernel=/install.amd/vmlinuz
--ramdisk=/install.amd/initrd.gz"
extra = "debian-installer/exit/always_halt=true -- console=hvc0"