[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#604080: marked as done (Xen domU fails to boot after install)

Your message dated Sat, 20 Jul 2013 12:54:21 +0200
with message-id <201307201254.45120.holger@layer-acht.org>
and subject line dealing with old installation-reports
has caused the Debian Bug report #604080,
regarding Xen domU fails to boot after install
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
604080: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=604080
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: installation-reports

I have an amd64 dom0 with lenny

I successfully run the Debian Installer in a fresh domU
xm create -c xm-squeeze1.cfg install=true install-mirror=http://mirror.positive-internet.com/debian install-installer=http://ftp.nl.debian.org/debian/dists/testing/main/installer-amd64/current/images/ 



I then tried to do the first boot:

xm create -c xm-squeeze1.cfg


I get this error:

Error: Boot loader didn't return any data!

Root causes:
- Squeeze installs grub 2, which doesn't have any /boot/grub/menu.lst
- pygrub can't seem to identify the boot partition in the MBR created by the installer - pygrub on lenny is looking for /boot/grub/menu.lst (actually, /grub/menu.lst on the bootable partition) 

Workaround 1:
- mount the filesystem, possibly using kpartx, manually create /boot/grub/menu.lst - tweak the cfg file to tell pygrub to look in the /boot partition (because it doesn't recognise the grub2 MBR) 

bootargs = '/dev/mapper/vg00-squeeze1_disk0p1'

Workaround 2:
- mount the filesystem, possibly using kpartx
- copy the kernel and initrd to the dom0
- modify the cfg file, tell it to use the kernel and initrd from the dom0 and not use pygrub as bootloader 

Suggestions:
- the MBR should be recognisable by the lenny version of pygrub
- better error needed from pygrub when it doesn't find menu.lst
- maybe grub2 should create menu.lst for backwards compatibility? or maybe some optional tool in the domU can create it? - maybe a support package is needed for lenny dom0 users? and a helpful message to let them know it exists?

--- End Message ---
--- Begin Message --- 
Hi,

thank you for submitting installation reports, much appreciated.

I read through all the bugs mentioned here (and I'm sure they were read by 
several people at the time they were submitted) and am closing them now as/if
- they (finally) indicated success and/or
- I know from first hand experience that the functionality is working in 
Wheezy and/or
- they only contained very little information and/or
- they contained user errors and/or
- they have been from a development phase where things were not stable and/or
- they are very old, more than 2.3 years.

If I've closed a bug incorrectly please do reply (it's easy to reopen and I'll 
do if requested) or just file a new one - thats often better, as the bug log 
will be clearer and shorter and not contain cruft.


cheers,
        Holger

Attachment: signature.asc
Description: This is a digitally signed message part.


--- End Message ---
Reply to: