Description of problem: XEN will not boot using recent kernels 4.19.5-200 and 4.19.6.300.fc29.x86_64 Version-Release number of selected component (if applicable): How reproducible: Every boot. I have locked my boot to kernel 4.19.4-200 Steps to Reproduce: 1. Just reboot system with saved_entry=Fedora, with Xen hypervisor 2. 3. Actual results: System will reboot continuously because of the failure. The error message is file /grub2/i386-pc/module2.mod not found BUT THAT IS SPURIOUS. I get that error even with the kernels that boot properly. Expected results: Boot into kernel with XEN Additional info:
Are you sure this is a grub issue? There is a known bug in the kernel when booting xen (Dom0 or PV DomU) from 4.19.5 onwards. There is a proposed patch (see https://lore.kernel.org/lkml/20181130202328.65359-2-kirill.shutemov@linux.intel.com/ and https://lists.xenproject.org/archives/html/xen-devel/2018-11/msg03313.html ) but it hasn't made it into the main line kernels yet.
(In reply to Michael Young from comment #1) > Are you sure this is a grub issue? There is a known bug in the kernel when > booting xen (Dom0 or PV DomU) from 4.19.5 onwards. There is a proposed patch > (see > https://lore.kernel.org/lkml/20181130202328.65359-2-kirill.shutemov@linux. > intel.com/ and > https://lists.xenproject.org/archives/html/xen-devel/2018-11/msg03313.html ) > but it hasn't made it into the main line kernels yet. You are correct. I changed it to kernel. I was having difficulty with the user interface when I filed the bug. Thanks for the links.
(In reply to Michael Young from comment #1) > Are you sure this is a grub issue? There is a known bug in the kernel when > booting xen (Dom0 or PV DomU) from 4.19.5 onwards. There is a proposed patch > (see > https://lore.kernel.org/lkml/20181130202328.65359-2-kirill.shutemov@linux. > intel.com/ and > https://lists.xenproject.org/archives/html/xen-devel/2018-11/msg03313.html ) > but it hasn't made it into the main line kernels yet. For me, in a *DomU*, Fedora kernels from 4.19.5 onwards crash at boot, while 4.19.5 (and up) built from upstream sources boot the same VM just fine. Therfore I'm not sure if this is really an upstream issue. To me it seems rather Fedora-specific.
Created attachment 1514334 [details] DomU console output of crashing Fedora kernels 4.19.8 and 4.19.5
The issue still exists in kernels 4.19.10-300 and current 4.19.13-300
(In reply to d_ruetti from comment #5) > The issue still exists in kernels 4.19.10-300 and current 4.19.13-300 Yes, the patch hasn't made it into the upstream 4.19 kernel branch yet. It is in the 4.20 branch so it should work after the F29 rebase to 4.20 which should happen in the next couple of weeks (and a bit longer for F28).
There is now a kernel-4.20.1-200.fc29 build available in koji https://koji.fedoraproject.org/koji/buildinfo?buildID=1178656 which fixes the problem for me under early testing. I still expect it will be a week or so before it (or a later build) reaches the main repositories.
The kernel from comment #7 seems to work. Thank you, Michael!
The native 4.19.15-300 kernel boots again normally. The patch was recently ported to the upstream 4.19 kernel branch.
Thanks for verifying.