On 23 Jan 2017, at 16:14, Ian Jackson <ian.jack...@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-de...@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
