Bug 2079915

Summary: panic: qemu-kvm -m 2048 -boot d -cdrom RHEL-9.0.0-20220424.1-BaseOS-x86_64-boot.iso
Product: Red Hat Enterprise Linux 9 Reporter: Jens Petersen <petersen>
Component: kernelAssignee: Virtualization Maintenance <virt-maint>
kernel sub component: Virtualization QA Contact: Virtualization Bugs <virt-bugs>
Status: CLOSED NOTABUG Docs Contact:
Severity: medium    
Priority: unspecified CC: coli, dhoward, hkrzesin
Version: 9.0Flags: pm-rhel: mirror+
Target Milestone: rc   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-04-28 19:15:05 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
qemu screenshot of panic in console none

Description Jens Petersen 2022-04-28 13:35:04 UTC
Created attachment 1875675 [details]
qemu screenshot of panic in console

Description of problem:
I tried booting RHEL 9.0 boot iso with qemu-kvm from the commandline
and it panics very early

Version-Release number of selected component (if applicable):
RHEL-9.0.0-20220424.1-BaseOS-x86_64-boot.iso

How reproducible:
100%

Steps to Reproduce:
1. qemu-kvm -m 2048 -boot d -cdrom RHEL-9.0.0-20220424.1-BaseOS-x86_64-boot.iso

Actual results:
Kernel panics rather early: see attached screenshot.
"Test this media" also panics.

Expected results:
To boot normally

Additional info:
Boots normally via virt-manager or gnome-boxes.

Two of my team-members can also reproduce this from F35 and F36.

Comment 1 Jens Petersen 2022-04-28 13:40:24 UTC
I can add one small datapoint: RHEL-9.0.0-20220110.3-BaseOS-x86_64-boot.iso boots fine in this case.
Though that is already quite old of course.

Also likely not surprising but qemu-kvm RHEL-9.1.0-20220424.2-BaseOS-x86_64-boot.iso also panics for me.

Comment 2 Jens Petersen 2022-04-28 13:57:57 UTC
Okay testing the current available older nightly images:

"qemu-kvm -m 2048 -boot d -cdrom RHEL-9.0.0-20220117.0-BaseOS-x86_64-boot.iso"  <= boots
"qemu-kvm -m 2048 -boot d -cdrom RHEL-9.0.0-20220223.1-BaseOS-x86_64-boot.iso"  <= panics

So this started happening some time before 20220223.

Comment 3 Herton R. Krzesinski 2022-04-28 17:22:45 UTC
This may be due RHEL 9 switch to build/bump the x86_64 cpu baseline to x86-64-v2.

Please see:
https://developers.redhat.com/blog/2021/01/05/building-red-hat-enterprise-linux-9-for-the-x86-64-v2-microarchitecture-level#

However it seems the default CPU model for qemu isn't compatible with x86-64-v2:
https://www.qemu.org/docs/master/system/i386/cpu.html

So please try boot with "-cpu host" option or any model compatible with v2 as in this table:
https://www.qemu.org/docs/master/system/i386/cpu.html#abi-compatibility-levels-for-cpu-models

Comment 4 Jens Petersen 2022-04-28 19:15:05 UTC
Thank you, Herton, you are exactly right.
I was not exactly aware of this, so thank you
for the explanation and workaround.

I suppose it would be kind of nice if qemu did
the right thing here, but might be tricky dunno.

Comment 5 Jens Petersen 2022-04-29 05:56:17 UTC
I opened bug 2080133 as a RFE against Fedora qemu.