On a Tuesday in 2022, Michal Privoznik wrote:
Introduced in QEMU's commit of v3.0.0-rc0~124^2~1 the
set-numa-node command is always available for all QEMU versions
we support (4.2.0, currently). Therefore, we can assume the
capability is always set and thus doesn't need to be checked for.
Signed-off-by: Michal Privoznik <mprivozn(a)redhat.com>
---
src/qemu/qemu_domain.c | 10 +++------
src/qemu/qemu_validate.c | 21 -------------------
tests/qemuxml2argvdata/cpu-numa-disjoint.err | 1 -
.../fd-memory-numa-topology2.args | 2 +-
.../fd-memory-numa-topology2.xml | 2 +-
.../fd-memory-numa-topology3.args | 2 +-
.../fd-memory-numa-topology3.xml | 2 +-
tests/qemuxml2argvdata/numatune-memnode.err | 1 -
tests/qemuxml2argvtest.c | 21 +++++++------------
tests/qemuxml2xmltest.c | 12 +++++------
10 files changed, 21 insertions(+), 53 deletions(-)
delete mode 100644 tests/qemuxml2argvdata/cpu-numa-disjoint.err
delete mode 100644 tests/qemuxml2argvdata/numatune-memnode.err
Reviewed-by: Ján Tomko <jtomko(a)redhat.com>
Jano