Red Hat Bugzilla – Bug 890112
'info qtree' outputs are different between "rhel6.3 host" and "rhel6.4 host with -M rhel6.3.0" (default parameters)
Last modified: 2013-01-03 23:42:06 EST
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):
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:
3. Start a command line on rhel6.4 host:
# /usr/libexec/qemu-kvm -M rhel6.3.0 -monitor stdio
4. On rhel6.4 host:
5. Compare the output in step 2 and step 4.
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.
The "info qtree" output should be the same on the two hosts.
(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
Created attachment 668777 [details]
'info qtree' output on rhel6.3 host with default paramters
Created attachment 668778 [details]
'info qtree' output on rhel6.4 host (-M rhel6.3.0) with default paramters
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.
Unifying bugs. See bug 889995 comment #8.
*** This bug has been marked as a duplicate of bug 889995 ***