Pkg xen devel - Jan 2017 - Bug#852069: DomU guests with pygrub as bootloader do not start after, upgrade from Xen 4.1 (wheezy) to Xen 4.4 (jessie)

Package: xen-utils-4.4
Version: 4.4.1-9+deb8u8
Severity: normal

Under Xen 4.1 in Debian 7 (wheezy), the following works when included in a
DomU configuration in "/etc/xen/cfg/" --

	bootloader   = '/usr/lib/xen-default/bin/pygrub'

After upgrading to Xen 4.4 as part of an upgrade to Debian 8 (jessie), the
DomU silently fails to start. Examination of the log files shows that the
cause is that the old path for "bootloader" no longer exists.
Correcting the
DomU configuration manually to the new path works --

	bootloader   = '/usr/lib/xen-4.4/bin/pygrub'

I would assume that creating a symlink would work also, and perhaps the
package installer should do it (in "/usr/lib", "ln -s xen-4.4
xen-default").


-- System Information:
Debian Release: 8.7
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 3.16.0-4-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages xen-utils-4.4 depends on:
ii  e2fslibs          1.42.12-2+b1
ii  libc6             2.19-18+deb8u7
ii  libncurses5       5.9+20140913-1+b1
ii  libtinfo5         5.9+20140913-1+b1
ii  libxen-4.4        4.4.1-9+deb8u8
ii  libxenstore3.0    4.4.1-9+deb8u8
ii  libyajl2          2.1.0-2
ii  python2.7         2.7.9-2+deb8u1
pn  python:any        <none>
ii  xen-utils-common  4.4.1-9+deb8u8

Versions of packages xen-utils-4.4 recommends:
ii  bridge-utils                                   1.5-9
ii  grub-xen-host                                  2.02~beta2-22+deb8u1
pn  qemu-system-x86                                <none>
ii  xen-hypervisor-4.4-amd64 [xen-hypervisor-4.4]  4.4.1-9+deb8u8

xen-utils-4.4 suggests no packages.

-- no debconf information

Michael Bilow writes ("Bug#852069: DomU guests with pygrub as bootloader do
not start after, upgrade from Xen 4.1 (wheezy) to Xen 4.4
(jessie)"):
> Under Xen 4.1 in Debian 7 (wheezy), the following works when included in a
> DomU configuration in "/etc/xen/cfg/" --
> 
> 	bootloader   = '/usr/lib/xen-default/bin/pygrub'
> 
> After upgrading to Xen 4.4 as part of an upgrade to Debian 8 (jessie), the
> DomU silently fails to start. Examination of the log files shows that the
> cause is that the old path for "bootloader" no longer exists.
Correcting the
> DomU configuration manually to the new path works --
> 
> 	bootloader   = '/usr/lib/xen-4.4/bin/pygrub'
> 
> I would assume that creating a symlink would work also, and perhaps the
> package installer should do it (in "/usr/lib", "ln -s
xen-4.4 xen-default").
Thanks for the report.

Nowadays the right way to configure this is to say just

  bootloader = "pygrub"

This will work with the packages I have prepared for Debian stretch
(aka testing).  But TBH I'm not sure that will work with the packages
in jessie.

Can you try that and let me know if it works ?

Thanks,
Ian.

On 23 Jan 2017, at 16:14, Ian Jackson <ian.jackson at eu.citrix.com>
wrote:
> 
> Michael Bilow writes ("Bug#852069: DomU guests with pygrub as
bootloader do not start after, upgrade from Xen 4.1 (wheezy) to Xen 4.4
(jessie)"):
>> Under Xen 4.1 in Debian 7 (wheezy), the following works when included
in a
>> DomU configuration in "/etc/xen/cfg/" --
>> 
>> 	bootloader   = '/usr/lib/xen-default/bin/pygrub'
>> 
>> After upgrading to Xen 4.4 as part of an upgrade to Debian 8 (jessie),
the
>> DomU silently fails to start. Examination of the log files shows that
the
>> cause is that the old path for "bootloader" no longer exists.
Correcting the
>> DomU configuration manually to the new path works --
>> 
>> 	bootloader   = '/usr/lib/xen-4.4/bin/pygrub'
>> 
>> I would assume that creating a symlink would work also, and perhaps the
>> package installer should do it (in "/usr/lib", "ln -s
xen-4.4 xen-default").
> 
> Thanks for the report.
> 
> Nowadays the right way to configure this is to say just
> 
>  bootloader = "pygrub"
> 
> This will work with the packages I have prepared for Debian stretch
> (aka testing).  But TBH I'm not sure that will work with the packages
> in jessie.
> 
> Can you try that and let me know if it works ?
> 
> Thanks,
> Ian.
> 
> _______________________________________________
> Pkg-xen-devel mailing list
> Pkg-xen-devel at lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-xen-devel
That works on Jessie as well using 4.4.1-9+deb8u7.

John