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:
Lots of properties that doesn't exist on rhel6.3 host, appears on rhel6.4 host when boot with -M rhel6.3.0. Details please check the steps.
Version-Release number of selected component (if applicable):
RHEL6.4 host:
kernel2.6.32-348.el6.x86_64
qemu-kvm-0.12.1.2-2.346.el6.x86_64
RHEL6.3-z host:
kernel-2.6.32-279.19.1.el6.x86_64
qemu-kvm-0.12.1.2-2.295.el6_3.10.x86_64
How reproducible:
Always
Steps to Reproduce:
1. Start a command line on rhel6.3-z host.
# /usr/libexec/qemu-kvm -monitor stdio
2. On rhel6.3-z host:
(qemu)info qtree
3. Start a command line on rhel6.4 host:
# /usr/libexec/qemu-kvm -M rhel6.3.0 -monitor stdio
4. On rhel6.4 host:
(qemu)info qtree
5. Compare the output in step 2 and step 4.
Actual results:
Lots of properties that doesn't exist on rhel6.3 host, appears on rhel6.4 host when boot with -M rhel6.3.0. Please check the additional info.
Expected results:
The "info qtree" output should be the same on the two hosts.
Additional info:
(a) "dev: PIIX4_PM", rhel6.4 host with -M rhel6.2.0 has the following properties while rhel6.2 has not.
dev-prop: disable_s3 = 1
dev-prop: disable_s4 = 1
dev-prop: s4_val = 2
(b) "dev: ide-drive" under "dev: piix3-ide", following property are showing up on rhel6.4 host while not exist on rhel6.2 host.
dev-prop: wwn = 0x0
(c) "dev: isa-fdc" under "dev: PIIX3", following property are showing up on rhel6.4 host while not exist on rhel6.2 host.
dev-prop: migrate_dir = 0
Copying comment added to bug 889995:
Having new property exposed on the newer qemu versions is completely expected. What can't change is the guest-visible side: the guest-visible state and guest-visible behavior can't change when using the older machine-types.
Auditing every single property will consume some time and will require help from people with experience in each part of the QEMU code. I don't believe we should make this a blocker bug as this isn't even a real bug, unless we find an actual issue during the audit.