Hey Xen devel team, I’ve never mailed a developer list before, but I’m worried I may have stumbled across a bad Xen/Debian packaging bug. My confidence is somewhere above “just mail -user” and below “open a bug in xen-system-amd64”. Apologies if this is the wrong usage of the list. I’ve updated to Buster, and my Xen kernel no longer boots. I believe it’s because Xen only offers versions 4.11 and 4.8, while Debian’s kernel images only offer 4.19 and 4.9. I’ve tried various matches between linux image and Xen version, and none of them will make it past loading initrd. (Booting non-Xen works fine) I’ll admit this is a cross-post of https://lists.debian.org/debian-user/2020/02/msg00890.html; I sent that email earlier when I was less convinced that this was a bug. As I’ve continued to poke at the problem, I’m more convinced it’s not user error. And again, sorry if this is the wrong reporting mechanism; I wanted to alert to what seems to (to me) to be a critical bug. - Garrett
Alexander Dahl
2020-Feb-25 06:48 UTC
[Pkg-xen-devel] Possible critical Xen issue on Buster
Hello Garrett, On Mon, Feb 24, 2020 at 07:46:27PM -0800, Garrett Reid wrote:> I’ve updated to Buster, and my Xen kernel no longer boots. I believe > it’s because Xen only offers versions 4.11 and 4.8, while Debian’s > kernel images only offer 4.19 and 4.9. I’ve tried various matches > between linux image and Xen version, and none of them will make it > past loading initrd. (Booting non-Xen works fine)I'm pretty sure you mixed up Linux Kernel versions (4.19 and 4.9) with Xen versions (4.11 and 4.8) here. Those don't need to match, because the Xen hypervisor is a different project than the Linux kernel. The versions happened to be quite similar by chance. For example my Xen host runs Debian bullseye with Xen hypervisor 4.11 and Linux Kernel 5.4, no problem. So your problem is probably somewhere else. You need to give more information on what exactly goes wrong to get help. Greets Alex -- /"\ ASCII RIBBON | »With the first link, the chain is forged. The first \ / CAMPAIGN | speech censured, the first thought forbidden, the X AGAINST | first freedom denied, chains us all irrevocably.« / \ HTML MAIL | (Jean-Luc Picard, quoting Judge Aaron Satie) -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: not available URL: <http://alioth-lists.debian.net/pipermail/pkg-xen-devel/attachments/20200225/b50eebbf/attachment.sig>
That’s a relief! Back to -user I go with my questions. Thanks for the clarification! - Garrett> On Feb 24, 2020, at 10:48 PM, Alexander Dahl <post at lespocky.de> wrote: > > Hello Garrett, > > On Mon, Feb 24, 2020 at 07:46:27PM -0800, Garrett Reid wrote: >> I’ve updated to Buster, and my Xen kernel no longer boots. I believe >> it’s because Xen only offers versions 4.11 and 4.8, while Debian’s >> kernel images only offer 4.19 and 4.9. I’ve tried various matches >> between linux image and Xen version, and none of them will make it >> past loading initrd. (Booting non-Xen works fine) > > I'm pretty sure you mixed up Linux Kernel versions (4.19 and 4.9) with > Xen versions (4.11 and 4.8) here. Those don't need to match, because > the Xen hypervisor is a different project than the Linux kernel. The > versions happened to be quite similar by chance. > > For example my Xen host runs Debian bullseye with Xen hypervisor 4.11 > and Linux Kernel 5.4, no problem. > > So your problem is probably somewhere else. You need to give more > information on what exactly goes wrong to get help. > > Greets > Alex > > -- > /"\ ASCII RIBBON | »With the first link, the chain is forged. The first > \ / CAMPAIGN | speech censured, the first thought forbidden, the > X AGAINST | first freedom denied, chains us all irrevocably.« > / \ HTML MAIL | (Jean-Luc Picard, quoting Judge Aaron Satie)