libvirt/tests/qemuxml2argvdata/x86-kvm-32-on-64.xml

<domain type='kvm'>
  <name>kvm</name>
  <uuid>d091ea82-29e6-2e34-3005-f02617b36e87</uuid>
  <memory unit='KiB'>4194304</memory>
  <os>
    <type arch='i686' machine='pc'>hvm</type>
  </os>
  <devices>
    <emulator>/usr/bin/qemu-system-x86_64</emulator>
    <controller type='usb' model='none'/>
    <memballoon model='none'/>
  </devices>
</domain>
tests: add qemu x86 kvm 32-on-64 test There's some specific logic in qemuBuildCpuCommandLine to support auto adding -cpu qemu 32 for arch=i686 with an x86_64 qemu binary. Add a test case for it 2017-07-13 11:32:41 -04:00			`<domain type='kvm'>`
			`<name>kvm</name>`
			`<uuid>d091ea82-29e6-2e34-3005-f02617b36e87</uuid>`
			`<memory unit='KiB'>4194304</memory>`
			`<os>`
qemuxml2(argv\|xml)data: x86-kvm-32-on-64: Add machine type The machine type doesn't change the test result and prevents tests being changed every time we are about to update real capabilities to a new qemu. Signed-off-by: Peter Krempa <pkrempa@redhat.com> Reviewed-by: Ján Tomko <jtomko@redhat.com> 2022-01-13 16:14:42 +01:00			`<type arch='i686' machine='pc'>hvm</type>`
tests: add qemu x86 kvm 32-on-64 test There's some specific logic in qemuBuildCpuCommandLine to support auto adding -cpu qemu 32 for arch=i686 with an x86_64 qemu binary. Add a test case for it 2017-07-13 11:32:41 -04:00			`</os>`
			`<devices>`
			`<emulator>/usr/bin/qemu-system-x86_64</emulator>`
			`<controller type='usb' model='none'/>`
			`<memballoon model='none'/>`
			`</devices>`
			`</domain>`