libvirt/tests/qemuxml2argvdata/qemuxml2argv-net-virtio-ccw.args

LC_ALL=C \
PATH=/bin \
HOME=/home/test \
USER=test \
LOGNAME=test \
QEMU_AUDIO_DRV=none \
/usr/bin/qemu \
-S \
-M s390-ccw \
-m 214 \
-smp 1 \
-nographic \
-nodefaults \
-monitor unix:/tmp/test-monitor,server,nowait \
-no-acpi \
-boot c \
-device virtio-net-ccw,vlan=0,id=net0,mac=00:11:22:33:44:55,devno=fe.0.0001 \
-net user,vlan=0,name=hostnet0 \
-device virtio-net-ccw,vlan=1,id=net1,mac=00:11:22:33:44:54,devno=fe.0.0000 \
-net user,vlan=1,name=hostnet1 \
-device virtio-balloon-ccw,id=balloon0,devno=fe.0.000a
tests: redo test argv file line wrapping Back in commit bd6c46fa0cfe275c24debc1152cfc5206c04b59b Author: Juerg Haefliger <juerg.haefliger@hp.com> Date: Mon Jan 31 06:42:57 2011 -0500 tests: handle backspace-newline pairs in test input files all the test argv files were line wrapped so that the args were less than 80 characters. The way the line wrapping was done turns out to be quite undesirable, because it often leaves multiple parameters on the same line. If we later need to add or remove individual parameters, then it leaves us having to redo line wrapping. This commit changes the line wrapping so that every single "-param value" is one its own new line. If the "value" is still too long, then we break on ',' or ':' or ' ' as needed. This means that when we come to add / remove parameters from the test files line, the patch diffs will only ever show a single line added/removed which will greatly simplify review work. Signed-off-by: Daniel P. Berrange <berrange@redhat.com> 2015-11-06 13:20:06 +00:00			`LC_ALL=C \`
			`PATH=/bin \`
			`HOME=/home/test \`
			`USER=test \`
			`LOGNAME=test \`
			`QEMU_AUDIO_DRV=none \`
			`/usr/bin/qemu \`
			`-S \`
			`-M s390-ccw \`
			`-m 214 \`
			`-smp 1 \`
			`-nographic \`
			`-nodefaults \`
			`-monitor unix:/tmp/test-monitor,server,nowait \`
			`-no-acpi \`
			`-boot c \`
S390: Do not generate a default USB controller For s390 we don't want to have a default USB device generated even if QEMU is silently tolerating -usb on the command line. This may change in the future. Another reason to avoid the USB controller is that it implies a PCI bus which might cause a regression at some later point in time. The following change will set the USB controller model to 'none' unless a model or address has been specified, which can be the case if a legacy definition is loaded or the XML writer knows what she/he's doing. Requiring the user to explicitly disable USB on systems not supporting it seems cumbersome. Signed-off-by: Viktor Mihajlovski <mihajlov@linux.vnet.ibm.com> 2013-04-29 16:11:29 +00:00			`-device virtio-net-ccw,vlan=0,id=net0,mac=00:11:22:33:44:55,devno=fe.0.0001 \`
S390: Testcases for virtio-ccw machines This adds and corrects testcases for virtio devices on s390 guests. Signed-off-by: Viktor Mihajlovski <mihajlov@linux.vnet.ibm.com> 2013-03-05 15:44:23 +00:00			`-net user,vlan=0,name=hostnet0 \`
			`-device virtio-net-ccw,vlan=1,id=net1,mac=00:11:22:33:44:54,devno=fe.0.0000 \`
			`-net user,vlan=1,name=hostnet1 \`
			`-device virtio-balloon-ccw,id=balloon0,devno=fe.0.000a`