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

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256



On 26/04/15 10:45, Bastian Blank wrote:
> Hi Daniel
> 
> On Sun, Apr 26, 2015 at 10:35:01AM +0200, Daniel Pocock wrote:
>> This should probably be released in an update to wheezy.
> 
> 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?

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQIcBAEBCAAGBQJVPKbIAAoJEOm1uwJp1aqDVbUP/RqiO5fN9CGZPFwxhN/tmpwc
zfsDVH+f4A3h6c7KNc1KzNckOeIlswdJaxzjjNr5GwRbcvzzpsY0kVqSOWvF7JeP
1nFK2IwgfG1jsCaJDr+YLHUCxiqtLL+KpEY50I/t0G4/STxqQIlF/awAPaPZuNlO
6aMBB6Vrl1N9aL0cLIMRLtWC7CMkP7t0gcE4NG3aqSArSD5AkcnixV1AF5yW7VaY
U4hJFXzMHegCRUbXV91jD0iipxpaSWQjXJ0g/P8aG6fy/subStwZc41rheaNJ3Q7
kgdRhSkizNuRTOGVtUiyJ9Re8+TGYhVNRRmtWbP++0SCI6JYNUo+W6Gu8p4YQMIK
dQpov0Wc5hgUObGWO9vU+irJI/lya7O5XLummwT4fzShkTQc6UU8goQ9XmhBVjpa
pdQj5ZcxIQLpviVIaTkc6I2oH125F1w00PyESoTxlEXj0xgcYiNDY9TTeOaVdUuW
ziw/3ni+5wVaVLWRteXKxAz0cF3Sqbho2z/1dsW/Pkm+XfXPxsawJeJOIQAhzAWL
AWXrvzP/Gbbeuujpzf7QFp8uirw3SWxP2oPZNMUB6MJ+4W+XkMv9xP0uydunFdPy
H1DdiiJnEnQZNubo9NT6tj5StmzmgrHJRP67D3/P7C5brjDM6399aJs4g2bH4LbR
0jxkr02w3cjMnT1COj/Z
=1Emv
-----END PGP SIGNATURE-----

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

-- 
We have phasers, I vote we blast 'em!
		-- Bailey, "The Corbomite Maneuver", stardate 1514.2

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>