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: