]> xenbits.xensource.com Git - libvirt.git/commitdiff
tests: Refresh capabilities for QEMU on ppc64
authorAndrea Bolognani <abologna@redhat.com>
Thu, 16 May 2019 14:29:53 +0000 (16:29 +0200)
committerAndrea Bolognani <abologna@redhat.com>
Fri, 17 May 2019 12:59:37 +0000 (14:59 +0200)
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: Andrea Bolognani <abologna@redhat.com>
Reviewed-by: Pavel Hrdina <phrdina@redhat.com>
tests/qemucapabilitiesdata/caps_3.1.0.ppc64.replies
tests/qemucapabilitiesdata/caps_4.0.0.ppc64.replies

index c23f67e86936550483df3f84c5c31fd889a1e992..33666a43db33a4568954c014a1422f0be6db49ea 100644 (file)
       "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"
index 38e4c254a44c29e0996d944a48eabd06b1f5cb3e..baa8f8963d6222840f858ebc8aa2d733a9db9ced 100644 (file)
       "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"