Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
Description of problem:
Version-Release number of selected component (if applicable):
qemu-kvm-1.2.0-20.el7.x86_64
How reproducible:
100%
Steps to Reproduce:
1.#/usr/libexec/qemu-kvm -M ?
2.
3.
Actual results:
Supported machines are:
none empty machine
pc Standard PC (alias of pc-1.2)
pc-1.2 Standard PC (default)
pc-1.1 Standard PC
pc-1.0 Standard PC
pc-0.15 Standard PC
pc-0.14 Standard PC
pc-0.13 Standard PC
pc-0.12 Standard PC
pc-0.11 Standard PC, qemu 0.11
pc-0.10 Standard PC, qemu 0.10
isapc ISA-only PC
Expected results:
/usr/libexec/qemu-kvm -M ?
Supported machines are:
pc RHEL 6.4.0 PC (alias of rhel7.0.0)
rhel7.0.0 RHEL 7.0.0 PC (default)
.......
Additional info:
I tried latest qemu(1.3rc1) upstream, the result is not friendly.
#./qemu-system-x86_64 -M ?
Supported machines are:
none empty machine
pc Standard PC (alias of pc-1.3)
pc-1.3 Standard PC (default)
pc-1.2 Standard PC
pc-1.1 Standard PC
pc-1.0 Standard PC
pc-0.15 Standard PC
pc-0.14 Standard PC
pc-0.13 Standard PC
pc-0.12 Standard PC
pc-0.11 Standard PC, qemu 0.11
pc-0.10 Standard PC, qemu 0.10
isapc ISA-only PC
q35 Q35 chipset PC (alias of q35-next)
q35-next Q35 chipset PC
I believe that the RHEL machine types will only be created when we fork qemu 1.3 for RHEL, which should happen soon.
CC'ing a few folks who are more familiar with the RHEL machine types than me, so that then can chime in if necessary (or even take the bz).
True. We won't create the rhel7.0.0 machine-type until we create a RHEL7-specific tree, after QEMU 1.3 is released. When we do that, it will probably be based on the existing "pc-1.3" machine-type.
Additional note from Markus:
> Enabling/disabling KVM is guest-visible upstream. With KVM disabled,
> you get a flash memory device. With KVM enabled, you get a ROM. Not
> good; KVM should be as transparent as possible to the guest.
>
> Looks like we should set "pc-sysfw" property "rom_only" to 1 for all
> RHEL machine types.
Talked with Eduardo about this BZ and he suggested closing this as a dupe of bug 889670 because we need the missing machine types to support migration to RHEL7.0.
*** This bug has been marked as a duplicate of bug 889670 ***