libvirt/tests/qemuxml2argvdata/qemuxml2argv-intel-iommu.args

LC_ALL=C \
PATH=/bin \
HOME=/home/test \
USER=test \
LOGNAME=test \
QEMU_AUDIO_DRV=none \
/usr/bin/qemu \
-name QEMUGuest1 \
-S \
-M q35 \
-m 214 \
-smp 1,sockets=1,cores=1,threads=1 \
-uuid c7a5fdbd-edaf-9455-926a-d65c16db1809 \
-nographic \
-nodefaults \
-monitor unix:/tmp/lib/domain--1-QEMUGuest1/monitor.sock,server,nowait \
-no-acpi \
-boot c \
-device intel-iommu
qemu: format intel-iommu on the command line <devices> <iommu model='intel'/> </devices> results in: -device intel-iommu https://bugzilla.redhat.com/show_bug.cgi?id=1235580 2016-06-22 17:27:57 +02:00			`LC_ALL=C \`
			`PATH=/bin \`
			`HOME=/home/test \`
			`USER=test \`
			`LOGNAME=test \`
			`QEMU_AUDIO_DRV=none \`
			`/usr/bin/qemu \`
			`-name QEMUGuest1 \`
			`-S \`
			`-M q35 \`
			`-m 214 \`
			`-smp 1,sockets=1,cores=1,threads=1 \`
			`-uuid c7a5fdbd-edaf-9455-926a-d65c16db1809 \`
			`-nographic \`
			`-nodefaults \`
			`-monitor unix:/tmp/lib/domain--1-QEMUGuest1/monitor.sock,server,nowait \`
			`-no-acpi \`
			`-boot c \`
tests: Reduce usage of legacy PCI controllers on PCIe machines Up until a while ago, libvirt would automatically add a legacy PCI controllers combo (dmi-to-pci-bridge + pci-bridge) to any PCIe machine type (x86_64/q35 and aarch64/virt). As a result, a number of input and output files in the test suite ended up containing the legacy PCI controllers, even though they are not needed or in any way relevant to the feature being tested. Get rid of most of the occurrences. Most of the time, this just means removing the controllers from the input file and regenerating the output files; in a few instances, some minor tweaking is performed on the input file, most notably removing the memory balloon: as memory balloon support was not the scope of the test being changed, there is no loss of test coverage from doing so. Several occurrences of the legacy PCI controllers remain in the test suite, both because removing their usage would have required even more tweaking, and because we still want to have coverage of this perfectly valid combination. 2017-02-21 14:30:39 +01:00			`-device intel-iommu`