RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

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.

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.

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.

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

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.

I opened bug 2080133 as a RFE against Fedora qemu.