On 7/30/20 5:23 PM, Peter Krempa wrote:
Note that 'numa-mem-supported' turned off for certain machine types
which in turn forced us to generate a newer command line in certain
tests.
Signed-off-by: Peter Krempa <pkrempa@xxxxxxxxxx>
---
.../caps_5.1.0.x86_64.replies | 3644 ++++++++++-------
.../caps_5.1.0.x86_64.xml | 176 +-
...y-hotplug-nvdimm-access.x86_64-latest.args | 3 +-
...ry-hotplug-nvdimm-align.x86_64-latest.args | 3 +-
...ry-hotplug-nvdimm-label.x86_64-latest.args | 3 +-
...ory-hotplug-nvdimm-pmem.x86_64-latest.args | 3 +-
...hotplug-nvdimm-readonly.x86_64-latest.args | 3 +-
.../memory-hotplug-nvdimm.x86_64-latest.args | 3 +-
8 files changed, 2364 insertions(+), 1474 deletions(-)
@@ -8028,7 +8149,7 @@
{
"hotpluggable-cpus": true,
"name": "pc-q35-5.1",
- "numa-mem-supported": true,
+ "numa-mem-supported": false,
"default-cpu-type": "qemu64-x86_64-cpu",
"cpu-max": 288,
"deprecated": false,
This is expected. It forces libvirt to use the old -numa mem= (if true)
or newer -numa memdev= (if false) see v6.4.0-rc1~75. Since these two
can't be mixed it was agreed that it will be part of machine type since
one can't migrate between machine types.
Michal
