[Pkg-xen-devel] Bug#783346: Bug#783346: Bug#783346: patch for booting Jessie domU with wheezy dom0

[Dameon Wagner]

On Sun, 26 Apr 2015 11:33:17 +0200 Bastian Blank <waldi at debian.org>
wrote:
> On Sun, Apr 26, 2015 at 10:50:16AM +0200, Daniel Pocock wrote:
> > On 26/04/15 10:45, Bastian Blank wrote:
> > > Well, if you can pursuade the release team.  We have grub2 for
> > > Xen in Jessie now and it can be used on Wheezy as well.
> > Can you be more specific?  If somebody is running a wheezy dom0
> > and they install grub2 in their domU before rebooting it the first
> > time, they will not have this problem?
> 
> You install grub-xen-host on the dom0 and point the domains to grub
> as kernel.  For 64bit guests (kernel wise):
> | kernel = '/usr/lib/grub-xen/grub-x86_64-xen.bin'
> For 32bit guests:
> | kernel = '/usr/lib/grub-xen/grub-i386-xen.bin'
> 
> Bastian

Package: xen-utils-4.1
Version: 4.1.4-3+deb7u8
Tags: patch

Hi,

I've just hit a similar bug with using pygrub to boot jessie VMs on a
wheezy Dom0, and stumbled on this bug after fixing things with a (very
similar to Daniel's) patch backported from xen-utils-4.4, which should
be attached.  I've tested it and it works like a treat.

I appreciate that we could install "grub-xen-host" as suggested, but
I'd rather not install anything additional when it could be fixed
simply with a small backport, especially with "grub-xen-host" not
actually being available in the wheezy repositories.

The issue we're seeing is slightly different to what Daniel originally
reported -- though the fix is basically the same -- so please let me
know if you'd rather I report it as a new bug.  What we're seeing is
the following error:

#---8<-----------------------------------------------------------------
# xm create -c /etc/xen/domains/normal/$VM
Using config file "/etc/xen/domains/normal/$VM".
Error: Boot loader didn't return any data!
#---8<-----------------------------------------------------------------

Manually editing grub.cfg to remove the `if [ "${next_entry}" ]; then`
clause and replacing it with a simple `set default="0"` is a kludgy
workaround, but it falls down as soon as something invokes
`update-grub`.

This is with 4.1.4-3+deb7u8, but please let me know if you need any
additional info, and I'll see what I can dig up.

Cheers.

Dameon.

-- 
><> ><> ><> ><> ><> ><> ooOoo <>< <>< <>< <>< <>< <><
Dr. Dameon Wagner, Systems Development and Support
IT Services, University of Oxford
><> ><> ><> ><> ><> ><> ooOoo <>< <>< <>< <>< <>< <><

-------------- next part --------------
A non-text attachment was scrubbed...
Name: pygrub-jessie-on-wheezy-dom0-fix.patch
Type: text/x-diff
Size: 526 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/pkg-xen-devel/attachments/20150713/96eba1b3/attachment.patch>