Red Hat Bugzilla – Bug 1093023
provide RHEL-specific machine types in QEMU
Last modified: 2015-03-05 04:45:45 EST
In addition to adding new machine types, the original bug 895959 tracked everything necessary to make old machine types work. This bug tracks only adding the new machine types for 7.1, like bug 977864 did for 7.0 (blocking bug 895959). I guess we should've cloned bug 977864 instead, but it's not worth cleaning up now.
Fix included in qemu-kvm-rhev-2.1.0-4.el7
Reproduce this bug using the following version: qemu-kvm-rhev-2.1.0-3.el7.x86_64 kernel-3.10.0-163.el7.x86_64 Steps to Reproduce: # /usr/libexec/qemu-kvm -M ? Actual results: No machine type for rhel7.1: # /usr/libexec/qemu-kvm -M ? Supported machines are: rhel6.0.0 RHEL 6.0.0 PC rhel6.5.0 RHEL 6.5.0 PC rhel6.1.0 RHEL 6.1.0 PC rhel6.2.0 RHEL 6.2.0 PC pc RHEL 7.0.0 PC (i440FX + PIIX, 1996) (alias of pc-i440fx-rhel7.0.0) pc-i440fx-rhel7.0.0 RHEL 7.0.0 PC (i440FX + PIIX, 1996) (default) rhel6.3.0 RHEL 6.3.0 PC none empty machine q35 RHEL-7.0.0 PC (Q35 + ICH9, 2009) (alias of pc-q35-rhel7.0.0) pc-q35-rhel7.0.0 RHEL-7.0.0 PC (Q35 + ICH9, 2009) rhel6.4.0 RHEL 6.4.0 PC
Verify this bug using the following version: qemu-kvm-rhev-2.1.0-4.el7.x86_64 kernel-3.10.0-163.el7.x86_64 Steps to Verify: # /usr/libexec/qemu-kvm -M ? Actual results: Machine type for rhel7.1 is added: # /usr/libexec/qemu-kvm -M ? Supported machines are: rhel6.0.0 RHEL 6.0.0 PC rhel6.5.0 RHEL 6.5.0 PC rhel6.1.0 RHEL 6.1.0 PC rhel6.2.0 RHEL 6.2.0 PC pc-i440fx-rhel7.0.0 RHEL 7.0.0 PC (i440FX + PIIX, 1996) q35 RHEL-7.1.0 PC (Q35 + ICH9, 2009) (alias of pc-q35-rhel7.1.0) pc-q35-rhel7.1.0 RHEL-7.1.0 PC (Q35 + ICH9, 2009) rhel6.3.0 RHEL 6.3.0 PC none empty machine pc RHEL 7.1.0 PC (i440FX + PIIX, 1996) (alias of pc-i440fx-rhel7.1.0) pc-i440fx-rhel7.1.0 RHEL 7.1.0 PC (i440FX + PIIX, 1996) (default) pc-q35-rhel7.0.0 RHEL-7.0.0 PC (Q35 + ICH9, 2009) rhel6.4.0 RHEL 6.4.0 PC I think the machine type should be ordered, open a new bz1145042.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHSA-2015-0624.html