Pkg xen devel - Oct 2018 - Bug#912381: xen-utils-4.11: /usr/lib/xen-4.11/bin/pygrub is missing after upgrade from xen-utils-4.8

Package: src:xen
Version: 4.11.1~pre.20180911.5acdd26fdc+dfsg-5
Severity: critical
Justification: breaks the whole system



-- System Information:
Debian Release: buster/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 4.18.0-2-amd64 (SMP w/40 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages xen-utils-4.11 depends on:
ii  libc6             2.27-6
ii  libncurses6       6.1+20181013-1
ii  libtinfo6         6.1+20181013-1
ii  libxenevtchn1     4.11.1~pre.20180911.5acdd26fdc+dfsg-5
ii  libxengnttab1     4.11.1~pre.20180911.5acdd26fdc+dfsg-5
ii  libxenmisc4.11    4.11.1~pre.20180911.5acdd26fdc+dfsg-5
ii  libxenstore3.0    4.11.1~pre.20180911.5acdd26fdc+dfsg-5
ii  libxentoolcore1   4.11.1~pre.20180911.5acdd26fdc+dfsg-5
ii  libxentoollog1    4.11.1~pre.20180911.5acdd26fdc+dfsg-5
ii  libyajl2          2.1.0-3
ii  python            2.7.15-3
ii  xen-utils-common  4.11.1~pre.20180911.5acdd26fdc+dfsg-5

Versions of packages xen-utils-4.11 recommends:
ii  bridge-utils                          1.5-16
ii  grub-xen-host                         2.02+dfsg1-6
ii  qemu-system-x86                       1:2.12+dfsg-3+b1
ii  xen-hypervisor-4.11-amd64 [xen-hyper  4.11.1~pre.20180911.5acdd26fdc+dfsg-5

Versions of packages xen-utils-4.11 suggests:
pn  ovmf        <none>
ii  qemu-utils  1:2.12+dfsg-3+b1
ii  seabios     1.11.1-1

-- no debconf information

Hi,

On 10/31/2018 12:05 AM, Dimitar Angelov wrote:
> Package: src:xen
> Version: 4.11.1~pre.20180911.5acdd26fdc+dfsg-5
> Severity: critical
> Justification: breaks the whole system
I'm using 4.11.1~pre.20180911.5acdd26fdc+dfsg-5 on a whole lot of
servers, and it does not break the whole system. It doesn't eat my
lunch, it does not kill my cat and does not set all servers and the data
center on fire.

I see that there's no /usr/lib/xen-4.11/bin/pygrub indeed, and that's
something that sounds wrong. Apparently, noone involved in helping
getting Xen 4.11 into Debian so far has been a pygrub user.

So... thanks for reporting, and thanks for trying out the new packages.

I suspect it's rather obvious there's a problem, since there's no
pygrub
file at all, so we have to find out why and how it can be fixed.

Also, whoever is working on the xen packaging will need to set up a test
environment which is actually using pygrub to confirm any fix will
actually work, so your help in all of this would really be appreciated.

Apologies for the inconvenience.

Hans

On Wed, 31 Oct 2018 00:47:46 +0100 Hans van Kranenburg 
<hans at knorrie.org> wrote:
> Hi,
> 
> I see that there's no /usr/lib/xen-4.11/bin/pygrub indeed, and
that's
> something that sounds wrong. Apparently, noone involved in helping
> getting Xen 4.11 into Debian so far has been a pygrub user.
> 
> So... thanks for reporting, and thanks for trying out the new packages.
> 
> I suspect it's rather obvious there's a problem, since there's
no pygrub
> file at all, so we have to find out why and how it can be fixed.
> 
Missing pygrub stops booting paravirtualized Debian guests with grub-legacy.
Can you suggest how to workaround?

Regards,

Dimitar Angelov

On 10/31/2018 08:49 AM, Dimitar Angelov wrote:
> On Wed, 31 Oct 2018 00:47:46 +0100 Hans van Kranenburg
> <hans at knorrie.org> wrote:
>> Hi,
>>
>> I see that there's no /usr/lib/xen-4.11/bin/pygrub indeed, and
that's
>> something that sounds wrong. Apparently, noone involved in helping
>> getting Xen 4.11 into Debian so far has been a pygrub user.
>>
>> So... thanks for reporting, and thanks for trying out the new packages.
>>
>> I suspect it's rather obvious there's a problem, since
there's no pygrub
>> file at all, so we have to find out why and how it can be fixed.
>>
> 
> Missing pygrub stops booting paravirtualized Debian guests with
> grub-legacy.
> Can you suggest how to workaround?
The quickest way, for now, would be to get it from the source package,
and put the pygrub file from it in /usr/lib/xen-4.11/bin:

https://sources.debian.org/data/main/x/xen/4.11.1~pre.20180911.5acdd26fdc+dfsg-5/tools/pygrub/src/pygrub

Hans

Hi,

On 10/31/2018 05:13 PM, Hans van Kranenburg wrote:
> On 10/31/2018 08:49 AM, Dimitar Angelov wrote:
>> On Wed, 31 Oct 2018 00:47:46 +0100 Hans van Kranenburg
>> <hans at knorrie.org> wrote:
>>> Hi,
>>>
>>> I see that there's no /usr/lib/xen-4.11/bin/pygrub indeed, and
that's
>>> something that sounds wrong. Apparently, noone involved in helping
>>> getting Xen 4.11 into Debian so far has been a pygrub user.
>>>
>>> So... thanks for reporting, and thanks for trying out the new
packages.
>>>
>>> I suspect it's rather obvious there's a problem, since
there's no pygrub
>>> file at all, so we have to find out why and how it can be fixed.
>>>
>>
>> Missing pygrub stops booting paravirtualized Debian guests with
>> grub-legacy.
>> Can you suggest how to workaround?
> 
> The quickest way, for now, would be to get it from the source package,
> and put the pygrub file from it in /usr/lib/xen-4.11/bin:
> 
>
https://sources.debian.org/data/main/x/xen/4.11.1~pre.20180911.5acdd26fdc+dfsg-5/tools/pygrub/src/pygrub
The problem has been found, and the fix will be in the next package
upload. There was a too broad exclude in debian/rules, which caused the
file to be ignored:

https://salsa.debian.org/xen-team/debian-xen/commit/d4b0d104f158217036c779e2c7f608d659e01f59

Hans

On Wed, 31 Oct 2018 17:13:10 +0100 Hans van Kranenburg 
<hans at knorrie.org> wrote:
> On 10/31/2018 08:49 AM, Dimitar Angelov wrote:
> > On Wed, 31 Oct 2018 00:47:46 +0100 Hans van Kranenburg
> > <hans at knorrie.org> wrote:
> >> Hi,
> >>
> >> I see that there's no /usr/lib/xen-4.11/bin/pygrub indeed, and
that's
> >> something that sounds wrong. Apparently, noone involved in helping
> >> getting Xen 4.11 into Debian so far has been a pygrub user.
> >>
> >> So... thanks for reporting, and thanks for trying out the new
packages.
> >>
> >> I suspect it's rather obvious there's a problem, since
there's no pygrub
> >> file at all, so we have to find out why and how it can be fixed.
> >>
> > 
> > Missing pygrub stops booting paravirtualized Debian guests with
> > grub-legacy.
> > Can you suggest how to workaround?
> 
> The quickest way, for now, would be to get it from the source package,
> and put the pygrub file from it in /usr/lib/xen-4.11/bin:
> 
>
https://sources.debian.org/data/main/x/xen/4.11.1~pre.20180911.5acdd26fdc+dfsg-5/tools/pygrub/src/pygrub
> 
> Hans
> 
> 
> 
Thank you for reply.
I've copied pygrub from source package to /usr/lib/xen-4.11/bin, but now 
receive following error:

Traceback (most recent call last):
   File "/usr/lib/xen-4.11/bin/pygrub", line 23, in <module>
     import fsimage
ImportError: No module named fsimage

I also can mention something other, when creating PV VM using 
xen-create-image it reports:
warning: something called deprecated script 
/usr/lib/xen-common/bin/xen-toolstack


The command is:
xen-create-image \
    --hostname=test2 --memory=1gb -vcpus=1 \
    --lvm=vg0 --size=10gb --noswap \
    --pygrub \
    --fs=ext4 \
    --dist=stretch \
    --role=udev \
    --gateway=10.10.10.1 --ip=10.10.10.12 --netmask=255.255.254.0 \
    --bridge=xenbr0 \


Regards,

Dimitar Angelov

Hi,

On 10/31/2018 05:51 PM, Dimitar Angelov wrote:
> On Wed, 31 Oct 2018 17:13:10 +0100 Hans van Kranenburg
> <hans at knorrie.org> wrote:
>> On 10/31/2018 08:49 AM, Dimitar Angelov wrote:
>> > On Wed, 31 Oct 2018 00:47:46 +0100 Hans van Kranenburg
>> > <hans at knorrie.org> wrote:
>> >> Hi,
>> >>
>> >> I see that there's no /usr/lib/xen-4.11/bin/pygrub indeed,
and that's
>> >> something that sounds wrong. Apparently, noone involved in
helping
>> >> getting Xen 4.11 into Debian so far has been a pygrub user.
>> >>
>> >> So... thanks for reporting, and thanks for trying out the new
>> packages.
>> >>
>> >> I suspect it's rather obvious there's a problem, since
there's no
>> pygrub
>> >> file at all, so we have to find out why and how it can be
fixed.
>> >>
>> > > Missing pygrub stops booting paravirtualized Debian guests
with
>> > grub-legacy.
>> > Can you suggest how to workaround?
>>
>> The quickest way, for now, would be to get it from the source package,
>> and put the pygrub file from it in /usr/lib/xen-4.11/bin:
>>
>>
https://sources.debian.org/data/main/x/xen/4.11.1~pre.20180911.5acdd26fdc+dfsg-5/tools/pygrub/src/pygrub
> 
> Thank you for reply.
> I've copied pygrub from source package to /usr/lib/xen-4.11/bin, but
now
> receive following error:
> 
> Traceback (most recent call last):
>   File "/usr/lib/xen-4.11/bin/pygrub", line 23, in <module>
>     import fsimage
> ImportError: No module named fsimage
Ah, more regressions... The script is missing a patch to set the lib
directory in the path

In 4.8, it has a line...
  sys.path.insert(1, sys.path[0] + '/../lib/python')
...which is missing now. That patch was lost somewhere apparently.

But even then, it fails:

dom0:/usr/lib/xen-4.11/bin -# python
Python 2.7.15+ (default, Aug 31 2018, 11:56:52)
[GCC 8.2.0] on linux2
Type "help", "copyright", "credits" or
"license" for more information.
>>> import fsimage
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
ImportError: No module named fsimage
>>> import sys
>>> sys.path
['', '/usr/lib/python2.7',
'/usr/lib/python2.7/plat-x86_64-linux-gnu',
'/usr/lib/python2.7/lib-tk', '/usr/lib/python2.7/lib-old',
'/usr/lib/python2.7/lib-dynload',
'/usr/local/lib/python2.7/dist-packages',
'/usr/lib/python2.7/dist-packages']
>>> sys.path.insert(1, '/usr/lib/xen-4.11/lib/python')
>>> import fsimage
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
ImportError: libfsimage.so: cannot open shared object file: No such file
or directory

I guess this is because of renaming of fsimage -> libfsimage that has
been going on? Ian?

---- >8 ----

An alternative that might help you now might be to switch to pvgrub2?

https://blog.xenproject.org/2015/01/07/using-grub-2-as-a-bootloader-for-xen-pv-guests/

Search for "Debian" in that page to find pointers to the grub-xen
packages.
> I also can mention something other, when creating PV VM using
> xen-create-image it reports:
> warning: something called deprecated script
> /usr/lib/xen-common/bin/xen-toolstack
> 
> 
> The command is:
> xen-create-image \
>    --hostname=test2 --memory=1gb -vcpus=1 \
>    --lvm=vg0 --size=10gb --noswap \
>    --pygrub \
>    --fs=ext4 \
>    --dist=stretch \
>    --role=udev \
>    --gateway=10.10.10.1 --ip=10.10.10.12 --netmask=255.255.254.0 \
>    --bridge=xenbr0 \
/usr/lib/xen-common/bin/xen-toolstack is a helper script that returned
either 'xm' or 'xl' in the past. The xm toolstack is long gone
now, and
xl is the only choice. That message is harmless, and it points out that
xen-create-image needs to be changed to just use xl.

This should be in a separate bug against the xen-tools package. I'll
file it, thanks for reporting.

Hans

> >> >> I see that there's no /usr/lib/xen-4.11/bin/pygrub
indeed, and that's
> >> >> something that sounds wrong. Apparently, noone involved
in helping
> >> >> getting Xen 4.11 into Debian so far has been a pygrub
user.
I swear I tested pygrub aftr making my renaming changes, but maybe
only with the upstream tree.

I don't understand why it's not being built by the upstream build
system.  That would be the first thing to look at.

Sorry for the lossage, but I can't conveniently invstigate now.
> > Traceback (most recent call last):
> >   File "/usr/lib/xen-4.11/bin/pygrub", line 23, in
<module>
> >     import fsimage
> > ImportError: No module named fsimage
> 
> Ah, more regressions... The script is missing a patch to set the lib
> directory in the path
No, this is simply because the library is renamed now to
libxenfsimage.  The pygrub from 4.8 isn't compatible with the new
library name.

Ian.

On 10/31/2018 07:16 PM, Hans van Kranenburg wrote:
> Hi,
> 
> On 10/31/2018 05:51 PM, Dimitar Angelov wrote:
>> On Wed, 31 Oct 2018 17:13:10 +0100 Hans van Kranenburg
>> <hans at knorrie.org> wrote:
>>> On 10/31/2018 08:49 AM, Dimitar Angelov wrote:
>>>> On Wed, 31 Oct 2018 00:47:46 +0100 Hans van Kranenburg
>>>> <hans at knorrie.org> wrote:
>>>>> Hi,
>>>>>
>>>>> I see that there's no /usr/lib/xen-4.11/bin/pygrub
indeed, and that's
>>>>> something that sounds wrong. Apparently, noone involved in
helping
>>>>> getting Xen 4.11 into Debian so far has been a pygrub user.
>>>>>
>>>>> So... thanks for reporting, and thanks for trying out the
new
>>> packages.
>>>>>
>>>>> I suspect it's rather obvious there's a problem,
since there's no
>>> pygrub
>>>>> file at all, so we have to find out why and how it can be
fixed.
>>>>>
>>>>> Missing pygrub stops booting paravirtualized Debian guests
with
>>>> grub-legacy.
>>>> Can you suggest how to workaround?
>>>
>>> The quickest way, for now, would be to get it from the source
package,
>>> and put the pygrub file from it in /usr/lib/xen-4.11/bin:
>>>
>>>
https://sources.debian.org/data/main/x/xen/4.11.1~pre.20180911.5acdd26fdc+dfsg-5/tools/pygrub/src/pygrub
>>
>> Thank you for reply.
>> I've copied pygrub from source package to /usr/lib/xen-4.11/bin,
but now
>> receive following error:
>>
>> Traceback (most recent call last):
>>   File "/usr/lib/xen-4.11/bin/pygrub", line 23, in
<module>
>>     import fsimage
>> ImportError: No module named fsimage
> 
> Ah, more regressions... The script is missing a patch to set the lib
> directory in the path
> 
> In 4.8, it has a line...
>   sys.path.insert(1, sys.path[0] + '/../lib/python')
> ...which is missing now. That patch was lost somewhere apparently.
Oh no, duh, it's not in the file in the source package, obviously, heh.

Still, it's missing in the packaging it seems.

It was at the end of
  debian/patches/prefix-abiname/tools-pygrub-prefix.diff
before.

That file got removed in commit 0a18352eb, and the sys.path line didn't
return in any other place in a patch.

I just added a patch back for it.
> But even then, it fails:
> 
> dom0:/usr/lib/xen-4.11/bin -# python
> Python 2.7.15+ (default, Aug 31 2018, 11:56:52)
> [GCC 8.2.0] on linux2
> Type "help", "copyright", "credits" or
"license" for more information.
>>>> import fsimage
> Traceback (most recent call last):
>   File "<stdin>", line 1, in <module>
> ImportError: No module named fsimage
>>>> import sys
>>>> sys.path
> ['', '/usr/lib/python2.7',
'/usr/lib/python2.7/plat-x86_64-linux-gnu',
> '/usr/lib/python2.7/lib-tk', '/usr/lib/python2.7/lib-old',
> '/usr/lib/python2.7/lib-dynload',
> '/usr/local/lib/python2.7/dist-packages',
> '/usr/lib/python2.7/dist-packages']
>>>> sys.path.insert(1, '/usr/lib/xen-4.11/lib/python')
>>>> import fsimage
> Traceback (most recent call last):
>   File "<stdin>", line 1, in <module>
> ImportError: libfsimage.so: cannot open shared object file: No such file
> or directory
> 
> I guess this is because of renaming of fsimage -> libfsimage that has
> been going on? Ian?
> 
> ---- >8 ----
> 
> An alternative that might help you now might be to switch to pvgrub2?
> 
>
https://blog.xenproject.org/2015/01/07/using-grub-2-as-a-bootloader-for-xen-pv-guests/
> 
> Search for "Debian" in that page to find pointers to the grub-xen
packages.
> 
>> I also can mention something other, when creating PV VM using
>> xen-create-image it reports:
>> warning: something called deprecated script
>> /usr/lib/xen-common/bin/xen-toolstack
>>
>>
>> The command is:
>> xen-create-image \
>>    --hostname=test2 --memory=1gb -vcpus=1 \
>>    --lvm=vg0 --size=10gb --noswap \
>>    --pygrub \
>>    --fs=ext4 \
>>    --dist=stretch \
>>    --role=udev \
>>    --gateway=10.10.10.1 --ip=10.10.10.12 --netmask=255.255.254.0 \
>>    --bridge=xenbr0 \
> 
> /usr/lib/xen-common/bin/xen-toolstack is a helper script that returned
> either 'xm' or 'xl' in the past. The xm toolstack is long
gone now, and
> xl is the only choice. That message is harmless, and it points out that
> xen-create-image needs to be changed to just use xl.
> 
> This should be in a separate bug against the xen-tools package. I'll
> file it, thanks for reporting.
> 
> Hans
>

On 10/31/2018 07:23 PM, Ian Jackson wrote:
>>>>>> I see that there's no /usr/lib/xen-4.11/bin/pygrub
indeed, and that's
>>>>>> something that sounds wrong. Apparently, noone involved
in helping
>>>>>> getting Xen 4.11 into Debian so far has been a pygrub
user.
> 
> I swear I tested pygrub aftr making my renaming changes, but maybe
> only with the upstream tree.
> 
> I don't understand why it's not being built by the upstream build
> system.  That would be the first thing to look at.
> 
> Sorry for the lossage, but I can't conveniently invstigate now.
> 
>>> Traceback (most recent call last):
>>>   File "/usr/lib/xen-4.11/bin/pygrub", line 23, in
<module>
>>>     import fsimage
>>> ImportError: No module named fsimage
>>
>> Ah, more regressions... The script is missing a patch to set the lib
>> directory in the path
> 
> No, this is simply because the library is renamed now to
> libxenfsimage.  The pygrub from 4.8 isn't compatible with the new
> library name.
xen-utils-4.11 has:

/usr/lib/xen-4.11/lib/python/fsimage.so

libxenmisc4.11 has:

/usr/lib/xen-4.11/lib/x86_64-linux-gnu/fs/ext2fs-lib/fsimage.so
/usr/lib/xen-4.11/lib/x86_64-linux-gnu/fs/fat/fsimage.so
/usr/lib/xen-4.11/lib/x86_64-linux-gnu/fs/iso9660/fsimage.so
/usr/lib/xen-4.11/lib/x86_64-linux-gnu/fs/reiserfs/fsimage.so
/usr/lib/xen-4.11/lib/x86_64-linux-gnu/fs/ufs/fsimage.so
/usr/lib/xen-4.11/lib/x86_64-linux-gnu/fs/xfs/fsimage.so
/usr/lib/xen-4.11/lib/x86_64-linux-gnu/fs/zfs/fsimage.so
/usr/lib/xen-4.11/lib/x86_64-linux-gnu/libfsimage.so

There is nothing called libxenfsimage in our packages?

But, I'll leave it alone for now, since I apparently don't fully know
what I'm talking about. :)

Hans

On Wed, 31 Oct 2018 19:16:11 +0100 Hans van Kranenburg 
<hans at knorrie.org> wrote:
> An alternative that might help you now might be to switch to pvgrub2?
>
https://blog.xenproject.org/2015/01/07/using-grub-2-as-a-bootloader-for-xen-pv-guests/
> Search for "Debian" in that page to find pointers to the grub-xen
packages.
Thank you for suggestion using pvgrub2 PV VM is booting properly.
Only for information what I was done:
1. Booted Gust OS (Debian stretch) with kernel from DOM0 guest.cfg.
kernel      = '/boot/vmlinuz-4.18.0-2-amd64'
extra       = 'elevator=noop'
ramdisk     = '/boot/initrd.img-4.18.0-2-amd64'

2. Installed grub-pc which replace grub-legacy
apt-get install grub-pc

3. Shutdown guest and modify guest.cfg
kernel      = '/usr/lib/grub-xen/grub-x86_64-xen.bin'
extra       = '(xen/xvda2)/boot/grub/grub.cfg'

DOM0 have installed grub-xen-bin and grub-xen-host.

Create guest and is booted properly via GRUB2.

Regards,

Dimitar Angelov

Hi,

On 10/31/2018 09:10 PM, Dimitar Angelov wrote:
> On Wed, 31 Oct 2018 19:16:11 +0100 Hans van Kranenburg
> <hans at knorrie.org> wrote:
>> An alternative that might help you now might be to switch to pvgrub2?
>>
https://blog.xenproject.org/2015/01/07/using-grub-2-as-a-bootloader-for-xen-pv-guests/
>>
>> Search for "Debian" in that page to find pointers to the
grub-xen
>> packages.
> 
> Thank you for suggestion using pvgrub2 PV VM is booting properly.
> Only for information what I was done:
> 1. Booted Gust OS (Debian stretch) with kernel from DOM0 guest.cfg.
> kernel      = '/boot/vmlinuz-4.18.0-2-amd64'
> extra       = 'elevator=noop'
> ramdisk     = '/boot/initrd.img-4.18.0-2-amd64'
> 
> 2. Installed grub-pc which replace grub-legacy
> apt-get install grub-pc
> 
> 3. Shutdown guest and modify guest.cfg
> kernel      = '/usr/lib/grub-xen/grub-x86_64-xen.bin'
> extra       = '(xen/xvda2)/boot/grub/grub.cfg'
> 
> DOM0 have installed grub-xen-bin and grub-xen-host.
> 
> Create guest and is booted properly via GRUB2.
Great! pvgrub2 is a newer, safer and more robust solution, recommended.
The only downside can be that you already have to choose to boot the 32
or 64 bit image, but in many cases that's not a problem.

Thanks for also sharing the steps, since it might help someone else who
runs into the same or a similar problem.

Hans

For info, I had same problem upgrading Xen 4.8 to Xen 4.11 on Debian Testing.

All my DOMU servers was setup with grub-legacy and required pygrub to boot.
Lucky me Xen 4.8 was not automatic removed during upgrade to 4.11, so
after first reboot DOMU could all reboot as they linked to pygrub from
4.8.
Now looking into changing DOMU boot to new method before I remove 4.8.

But in case someone upgrade to Xen 4.11 and remove Xen 4.8 at same time,
you can end with DOMU servers that can't boot, and no way to get into them
to replace grub package.

/Torben Schou Jensen

NB: My server setup is based on Xen from Debian Testing, years back it was
recommended as Xen on Debian Stable was a little behind. Sometimes a
little risky due to many updates on Debian Testing, but when I upgrade
every 2-3 months it all go as planned without long stop.

Hi,

We aim to have a working pygrub in Buster, regardless of the fact that
using grub2-based boot images is the prefered upgrade path.

This issue is on our Buster TODO list:
https://salsa.debian.org/xen-team/debian-xen/issues/24

Hans

Your message dated Fri, 22 Feb 2019 16:37:31 +0000
with message-id <E1gxDpL-000AIs-O6 at fasolo.debian.org>
and subject line Bug#912381: fixed in xen 4.11.1+26-g87f51bf366-2
has caused the Debian Bug report #912381,
regarding xen-utils-4.11: /usr/lib/xen-4.11/bin/pygrub is missing after upgrade
from xen-utils-4.8
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 at bugs.debian.org
immediately.)


-- 
912381: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912381
Debian Bug Tracking System
Contact owner at bugs.debian.org with problems
-------------- next part --------------
An embedded message was scrubbed...
From: Dimitar Angelov <mitko at edabg.com>
Subject: xen-utils-4.11: /usr/lib/xen-4.11/bin/pygrub is missing after upgrade
from xen-utils-4.8
Date: Wed, 31 Oct 2018 01:05:47 +0200
Size: 3895
URL:
<http://alioth-lists.debian.net/pipermail/pkg-xen-devel/attachments/20190222/5be2efa5/attachment.mht>
-------------- next part --------------
An embedded message was scrubbed...
From: Ian Jackson <ijackson at chiark.greenend.org.uk>
Subject: Bug#912381: fixed in xen 4.11.1+26-g87f51bf366-2
Date: Fri, 22 Feb 2019 16:37:31 +0000
Size: 19114
URL:
<http://alioth-lists.debian.net/pipermail/pkg-xen-devel/attachments/20190222/5be2efa5/attachment-0001.mht>

Hei hei,

On Wed, 31 Oct 2018 19:16:11 +0100 Hans van Kranenburg 
<hans at knorrie.org> wrote:
 > An alternative that might help you now might be to switch to pvgrub2?

This is an alternative for Debian virtual machines. At least I use 
pygrub to boot other distributions, which don't have pvgrub.

So thanks for fixing pygrub! :-)

Greets
Alex