提交 35e4c153 编写于 作者: A Andrea Bolognani

tests: Refresh capabilities for QEMU on ppc64

Now that we're probing machine type properties using the
latest machine type rather than the "spapr-machine" parent,
we can finally discover properties that are not available
on all machine types.

This commit refreshes replies for QEMU 4.0.0 as well as
3.1.0 to show not only that we're actually discovering new
machine type properties this way, but also that the number
of available machine type properties increases with each
subsequent QEMU release.

If qom-list-properties had been available in QEMU 2.10.0,
we could now drop the explicit version number checks for
the QEMU_CAPS_MACHINE_PSERIES_MAX_CPU_COMPAT and
QEMU_CAPS_MACHINE_PSERIES_RESIZE_HPT capabilities, but
unfortunately it wasn't, so we have to keep them around
still.
Signed-off-by: NAndrea Bolognani <abologna@redhat.com>
Reviewed-by: NPavel Hrdina <phrdina@redhat.com>
上级 d22c6221
......@@ -5841,6 +5841,35 @@
"name": "cap-nested-hv",
"description": "Allow Nested KVM-HV",
"type": "bool"
},
{
"name": "resize-hpt",
"description": "Resizing of the Hash Page Table (enabled, disabled, required)",
"type": "string"
},
{
"name": "max-cpu-compat",
"description": "Maximum permitted CPU compatibility mode. Valid values are power6, power7, power7+, power8, power9.",
"type": "string"
},
{
"name": "modern-hotplug-events",
"description": "Use dedicated hotplug event mechanism in place of standard EPOW events when possible (required for memory hot-unplug support)",
"type": "bool"
},
{
"name": "vsmt",
"description": "Virtual SMT: KVM behaves as if this were the host's SMT mode",
"type": "uint32"
},
{
"name": "kvm-type",
"description": "Specifies the KVM virtualization mode (HV, PR)",
"type": "string"
},
{
"name": "vfio-no-msix-emulation",
"type": "bool"
}
],
"id": "libvirt-33"
......
......@@ -6234,6 +6234,50 @@
"name": "cap-nested-hv",
"description": "Allow Nested KVM-HV",
"type": "bool"
},
{
"name": "vfio-no-msix-emulation",
"type": "bool"
},
{
"name": "ic-mode",
"description": "Specifies the interrupt controller mode (xics, xive, dual)",
"type": "string"
},
{
"name": "kvm-type",
"description": "Specifies the KVM virtualization mode (HV, PR)",
"type": "string"
},
{
"name": "host-model",
"description": "Host model to advertise in guest device tree",
"type": "string"
},
{
"name": "max-cpu-compat",
"description": "Maximum permitted CPU compatibility mode. Valid values are power6, power7, power7+, power8, power9.",
"type": "string"
},
{
"name": "modern-hotplug-events",
"description": "Use dedicated hotplug event mechanism in place of standard EPOW events when possible (required for memory hot-unplug support)",
"type": "bool"
},
{
"name": "vsmt",
"description": "Virtual SMT: KVM behaves as if this were the host's SMT mode",
"type": "uint32"
},
{
"name": "host-serial",
"description": "Host serial number to advertise in guest device tree",
"type": "string"
},
{
"name": "resize-hpt",
"description": "Resizing of the Hash Page Table (enabled, disabled, required)",
"type": "string"
}
],
"id": "libvirt-34"
......
Markdown is supported
0% .
You are about to add 0 people to the discussion. Proceed with caution.
先完成此消息的编辑!
想要评论请 注册