Apparently, the similarity in version numbers between Xen and the Linux kernel is more coincidental, and they aren’t required to match. How can I start to debug a boot configuration that’s not working? I’ve tried regenerating with with `update-grub` and `update-initramfs -u`, but no luck.
I’ve also confirmed that the initrd generated by update-initramfs is the one used by the xen boot entry in /boot/grub/grub.cfg. I’ve tried rebooting, changing my boot options to “debug earlyprintk=efi,keep”. It causes torrents of information for the non-xen (successful) boot, but seems to have no impact on the xen option. I still just see: > Loading Xen 4.11-amd64 … > Loading Linux 4.19.0-8-amd64 … > Loading initial ramdisk … How can I begin debugging this? - Garrett > On Feb 24, 2020, at 6:34 PM, Garrett Reid <garrett.r...@gmail.com> wrote: > > Hey, Debian folks! > > After updating to Buster, my system is unable to boot with the Xen > hypervisor. When I try and boot, the screen gets stuck loading the ramdisk: >> Loading Xen 4.11-amd64 … >> Loading Linux 4.19.0.8-amd-64 … >> Loading initial ramdisk … > > I’m immediately suspicious of the version mismatch, especially since booting > “Debian GNU/Linux” instead of “Debian GNU/Linux, with Xen hypervisor” works > just fine. > > I still have the appropriate xen package installed: >> bash# apt install xen-system >> Reading package lists... Done >> Building dependency tree >> Reading state information... Done >> Note, selecting 'xen-system-amd64' instead of 'xen-system' >> xen-system-amd64 is already the newest version >> (4.11.3+24-g14b62ab3e5-1~deb10u1). > > And there doesn’t seem to be a 4.11 hypervisor option: >> bash# apt-cache search xen-hypervisor >> xen-hypervisor-4.11-amd64 - Xen Hypervisor on AMD64 >> xen-hypervisor-common - Xen Hypervisor - common files >> xen-hypervisor-4.8-amd64 - Xen Hypervisor on AMD64 > > Furthermore, there also aren’t any packages for a 4.11 stock kernel to match > the hypervisor: >> bash# apt-cache search linux-image-4. | fgrep 'amd64 ' | egrep -v >> 'headers|cloud|rt' >> linux-image-4.19.0-8-amd64 - Linux 4.19 for 64-bit PCs (signed) >> linux-image-4.19.0-6-amd64 - Linux 4.19 for 64-bit PCs (signed) >> linux-image-4.9.0-11-amd64 - Linux 4.9 for 64-bit PCs >> linux-image-4.9.0-12-amd64 - Linux 4.9 for 64-bit PCs >> linux-image-4.9.0-4-amd64 - Linux 4.9 for 64-bit PCs >> linux-image-4.9.0-8-amd64 - Linux 4.9 for 64-bit PCs >> linux-image-4.9.0-9-amd64 - Linux 4.9 for 64-bit PCs > > > (I also checked what old kernels I had lying around in /boot; only a few > varieties of 4.9.0). > > Am I correctly understanding the issue here? If so, is there a way to get a > newer xen hypervisor from a repo somewhere? (I can’t find it in backports or > proposed-updates). Or, is there a way to find a matching old kernel image? > > And if not, where do I start debugging? > > Thanks for your help, > - Garrett >
