On Mon, Jun 23, 2025 at 21:59:12 +0200, Peter Krempa wrote:
From: Peter Krempa <pkrempa@redhat.com>
The QEMU_CAPS_DEVICE_USB_BOT device can be compiled out but realistically it makes no sense to do it thus also makes no sense to have another variant of input data for it.
Add another invocation of "disk-usb-device" clearing QEMU_CAPS_DEVICE_USB_BOT to show the fallback code paths.
Also add "ABI_UPDATE" version for the two cases above as the ABI of usb-bot cdrom is not migration-compatible and we'll be wanting to update to the fixed configuration.
Signed-off-by: Peter Krempa <pkrempa@redhat.com> --- ...est.QEMU_CAPS_DEVICE_USB_BOT-disabled.args | 59 +++++++++ ...test.QEMU_CAPS_DEVICE_USB_BOT-disabled.xml | 107 +++++++++++++++ ...ate.QEMU_CAPS_DEVICE_USB_BOT-disabled.args | 59 +++++++++ ...date.QEMU_CAPS_DEVICE_USB_BOT-disabled.xml | 125 ++++++++++++++++++ ...k-usb-device.x86_64-latest.abi-update.args | 59 +++++++++ ...sk-usb-device.x86_64-latest.abi-update.xml | 125 ++++++++++++++++++ tests/qemuxmlconftest.c | 12 ++ 7 files changed, 546 insertions(+) create mode 100644 tests/qemuxmlconfdata/disk-usb-device.x86_64-latest.QEMU_CAPS_DEVICE_USB_BOT-disabled.args create mode 100644 tests/qemuxmlconfdata/disk-usb-device.x86_64-latest.QEMU_CAPS_DEVICE_USB_BOT-disabled.xml create mode 100644 tests/qemuxmlconfdata/disk-usb-device.x86_64-latest.abi-update.QEMU_CAPS_DEVICE_USB_BOT-disabled.args create mode 100644 tests/qemuxmlconfdata/disk-usb-device.x86_64-latest.abi-update.QEMU_CAPS_DEVICE_USB_BOT-disabled.xml create mode 100644 tests/qemuxmlconfdata/disk-usb-device.x86_64-latest.abi-update.args create mode 100644 tests/qemuxmlconfdata/disk-usb-device.x86_64-latest.abi-update.xml
Reviewed-by: Jiri Denemark <jdenemar@redhat.com>