Bug#912381: [Pkg-xen-devel] Bug#912381: xen-utils-4.11: /usr/lib/xen-4.11/bin/pygrub is missing after upgrade from xen-utils-4.8
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.
Bug#912381: [Pkg-xen-devel] Bug#912381: xen-utils-4.11: /usr/lib/xen-4.11/bin/pygrub is missing after upgrade from xen-utils-4.8
Hi, On 10/31/2018 09:10 PM, Dimitar Angelov wrote: > On Wed, 31 Oct 2018 19:16:11 +0100 Hans van Kranenburg > 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
Bug#912381: [Pkg-xen-devel] Bug#912381: xen-utils-4.11: /usr/lib/xen-4.11/bin/pygrub is missing after upgrade from xen-utils-4.8
On Wed, 31 Oct 2018 00:47:46 +0100 Hans van Kranenburg 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
Bug#912381: [Pkg-xen-devel] Bug#912381: xen-utils-4.11: /usr/lib/xen-4.11/bin/pygrub is missing after upgrade from xen-utils-4.8
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
