[kernel-bugs] [Bug 1177009] New: Leap 15.2 stopped working in KVM with ovmf-ia32 firmware
http://bugzilla.opensuse.org/show_bug.cgi?id=1177009 Bug ID: 1177009 Summary: Leap 15.2 stopped working in KVM with ovmf-ia32 firmware Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.2 Hardware: x86-64 OS: openSUSE Leap 15.2 Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs@opensuse.org Reporter: nwr10cst-oslnx@yahoo.com QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Firefox/78.0 Build Identifier: I'm reporting as a kernel bug, but it might be a bug elsewhere. And yes, I know that this is not a supported configuration. Situation: I have both Leap 15.2 and Tumbleweed installed side by side in a KVM virtual machine, using 32-bit efi for booting. Both Leap and Tumbleweed are 64-bit. I originally setup this VM under Leap 15.0 (as KVM host machine). Everything had been working well. However, I recently tried to boot the Leap 15.2 system in that VM, and it failed to boot. I see the kernel and initrd being loaded. And then there is a reset and I get back to the boot screen. However, Tumbleweed continues to boot without a problem on that virtual machine. I am booting with "grub2-i386-efi", which is installed for both Tumbleweed and for Leap 15.2. This does not appear to be a grub2 problem, because the kernel and initrd are being loaded. Before today, I most recently booted Leap 15.2 on Sept 22, and I updated it at that time. I then rebooted (successfully) to check after the update. I have not been able to boot since, until my workaround today. The KVM host is also running Leap 15.2, and I did apply some updates since Sept 22. My guess is that one of those updates affected how the virtualization is working. I have a similar install of Leap 15.2 on an external USB drive, and I have that setup so that it can boot with legacy BIOS, with 64-bit efi and with 32-bit efi. Testing with that, it also fails to boot the same virtual machine with 32-bit efi, bit it successfully boots with either legacy BIOS or with 64-bit efi. So it looks as if whatever is going wrong has to do with communication between the kernel and the 32-bit efi firmware. Booting the virtual machine to Tumbleweed, then setting up for rescue/chroot, I have installed kernel 5.8.11-1.gf4bb27a-default from the stable kernels repo. And now Leap 15.2 does boot successfully with that kernel. It does not boot with any of the 5.3.x kernels for Leap 15.2 that I have tested. Reproducible: Always -- You are receiving this mail because: You are the assignee for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1177009
http://bugzilla.opensuse.org/show_bug.cgi?id=1177009#c1
--- Comment #1 from Neil Rickert
http://bugzilla.opensuse.org/show_bug.cgi?id=1177009
http://bugzilla.opensuse.org/show_bug.cgi?id=1177009#c2
--- Comment #2 from Neil Rickert
http://bugzilla.opensuse.org/show_bug.cgi?id=1177009
http://bugzilla.opensuse.org/show_bug.cgi?id=1177009#c4
--- Comment #4 from Neil Rickert
Per your description, the issue happened after kernel upgrade in the VM.
No, that's not quite right. The system booted fine with all kernels, up through Sept 22. This included booting with 5.3.18-lp152.41 However, something changed (I'm not sure what), and now neither 5.3.18-lp152.41 nor 5.3.18-lp152.36 will boot. The kernel from the release iso also will not boot, but it did at one time. I originally installed Leap 15.2 into this VM on Aug 30, 2019 when it was an alpha release. I'm checking that date from the date of "/lost+found". And it has worked well ever since, until a few days ago. To check the possibility that the NVRAM might be corrupt, I recreated the VM (with a different name) using "virt-install". And it still would not boot those kernels. So I don't think it is an NVRAM corruption problem. -- You are receiving this mail because: You are the assignee for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1177009
http://bugzilla.opensuse.org/show_bug.cgi?id=1177009#c6
--- Comment #6 from Neil Rickert
http://bugzilla.opensuse.org/show_bug.cgi?id=1177009
http://bugzilla.opensuse.org/show_bug.cgi?id=1177009#c7
Neil Rickert
http://bugzilla.opensuse.org/show_bug.cgi?id=1177009
http://bugzilla.opensuse.org/show_bug.cgi?id=1177009#c8
Michael Chang
http://bugzilla.opensuse.org/show_bug.cgi?id=1177009
http://bugzilla.opensuse.org/show_bug.cgi?id=1177009#c9
Neil Rickert
http://bugzilla.opensuse.org/show_bug.cgi?id=1177009
http://bugzilla.opensuse.org/show_bug.cgi?id=1177009#c10
--- Comment #10 from Michael Chang
I don't know why the grub code does not recognize this and drop back to using "linux". That seems to work with the 5.8 kernel for Tumbleweed (also 64-bit), but not with the 5.3 kernel for Leap 15.2
Because "Secure Boot", it just cannot provide any vehicle to bypass efistub loader. -- You are receiving this mail because: You are the assignee for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1177009
http://bugzilla.opensuse.org/show_bug.cgi?id=1177009#c11
Michael Chang
http://bugzilla.opensuse.org/show_bug.cgi?id=1177009
http://bugzilla.opensuse.org/show_bug.cgi?id=1177009#c12
Michael Chang
http://bugzilla.opensuse.org/show_bug.cgi?id=1177009
http://bugzilla.opensuse.org/show_bug.cgi?id=1177009#c14
Neil Rickert
http://bugzilla.opensuse.org/show_bug.cgi?id=1177009
http://bugzilla.opensuse.org/show_bug.cgi?id=1177009#c15
--- Comment #15 from Neil Rickert
Michael Chang
http://bugzilla.opensuse.org/show_bug.cgi?id=1177009
http://bugzilla.opensuse.org/show_bug.cgi?id=1177009#c16
Michael Chang
http://bugzilla.opensuse.org/show_bug.cgi?id=1177009
http://bugzilla.opensuse.org/show_bug.cgi?id=1177009#c17
Michael Chang
http://bugzilla.opensuse.org/show_bug.cgi?id=1177009
http://bugzilla.opensuse.org/show_bug.cgi?id=1177009#c18
Neil Rickert
http://bugzilla.opensuse.org/show_bug.cgi?id=1177009
http://bugzilla.opensuse.org/show_bug.cgi?id=1177009#c19
--- Comment #19 from Michael Chang
http://bugzilla.opensuse.org/show_bug.cgi?id=1177009
http://bugzilla.opensuse.org/show_bug.cgi?id=1177009#c20
--- Comment #20 from Neil Rickert
http://bugzilla.opensuse.org/show_bug.cgi?id=1177009
http://bugzilla.opensuse.org/show_bug.cgi?id=1177009#c21
Michael Chang
It turns out that this might be a issue also with x86_64.
[snip]
Yesterday, I connected the external drive to a system with 64-bit efi booting, but with secure-boot disabled. And the Tumbleweed 32-bit system would not boot. It used to boot. So I reverted grub2-x86_64-efi back to version 2.04-16.1 (the version just before the update around Sept 15th). And after going back to the old version, I can now boot it again with 64-bit efi.
I'm confused on why you would have to revert grub2-x86_64-efi in order to have 32-bit efi to boot ? I suppose a typo was in "And the Tumbleweed 32-bit system would not boot" with which the 32-bit should be replaced by 64-bit ? Is the tumbleweed system fully updated ? If the problem is reproducible only with "secure-boot disabled", then is there anything to do with bsc#1165773 ? Thanks. -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1177009
http://bugzilla.opensuse.org/show_bug.cgi?id=1177009#c22
Neil Rickert
http://bugzilla.opensuse.org/show_bug.cgi?id=1177009
http://bugzilla.opensuse.org/show_bug.cgi?id=1177009#c23
--- Comment #23 from Neil Rickert
participants (1)
-
bugzilla_noreply@suse.com