On Wed, Jan 17, 2024 at 10:54:38 +0100, Andrea Bolognani wrote:
Even though virtio-mmio is no longer the default on either
architecture, and likely nobody is using it at this point, we
still provide a way to opt into virtio-mmio usage and want to
keep existing guests working. Add explicit test suite coverage
for this scenario.
Signed-off-by: Andrea Bolognani <abologna(a)redhat.com>
---
...h64-virt-headless-mmio.aarch64-latest.args | 48 +++++++++++++
.../aarch64-virt-headless-mmio.xml | 48 +++++++++++++
...v64-virt-headless-mmio.riscv64-latest.args | 43 +++++++++++
.../riscv64-virt-headless-mmio.xml | 43 +++++++++++
tests/qemuxml2argvtest.c | 2 +
...ch64-virt-headless-mmio.aarch64-latest.xml | 71 +++++++++++++++++++
...cv64-virt-headless-mmio.riscv64-latest.xml | 58 +++++++++++++++
tests/qemuxml2xmltest.c | 2 +
8 files changed, 315 insertions(+)
create mode 100644
tests/qemuxml2argvdata/aarch64-virt-headless-mmio.aarch64-latest.args
create mode 100644 tests/qemuxml2argvdata/aarch64-virt-headless-mmio.xml
create mode 100644
tests/qemuxml2argvdata/riscv64-virt-headless-mmio.riscv64-latest.args
create mode 100644 tests/qemuxml2argvdata/riscv64-virt-headless-mmio.xml
create mode 100644
tests/qemuxml2xmloutdata/aarch64-virt-headless-mmio.aarch64-latest.xml
create mode 100644
tests/qemuxml2xmloutdata/riscv64-virt-headless-mmio.riscv64-latest.xml
Reviewed-by: Peter Krempa <pkrempa(a)redhat.com>