libvirt/tests/qemumemlockdata/qemumemlock-pc-locked+hostdev.xml

<domain type='kvm'>
  <name>guest</name>
  <memory unit='KiB'>1048576</memory>
  <memoryBacking>
    <locked/>
  </memoryBacking>
  <vcpu placement='static'>1</vcpu>
  <os>
    <type arch='x86_64' machine='pc'>hvm</type>
  </os>
  <devices>
    <emulator>/usr/bin/qemu-system-x86_64</emulator>
    <hostdev mode='subsystem' type='pci' managed='yes'>
      <source>
        <address domain='0x0001' bus='0x01' slot='0x00' function='0x0'/>
      </source>
    </hostdev>
  </devices>
</domain>
tests: Introduce QEMU memory locking limit tests These tests cover a number of scenarios where we care about the memory locking limit being set correctly for the guest to work properly. 2017-03-23 13:06:57 +00:00			`<domain type='kvm'>`
			`<name>guest</name>`
			`<memory unit='KiB'>1048576</memory>`
			`<memoryBacking>`
			`<locked/>`
			`</memoryBacking>`
			`<vcpu placement='static'>1</vcpu>`
			`<os>`
			`<type arch='x86_64' machine='pc'>hvm</type>`
			`</os>`
			`<devices>`
			`<emulator>/usr/bin/qemu-system-x86_64</emulator>`
			`<hostdev mode='subsystem' type='pci' managed='yes'>`
			`<source>`
tests: Update qemumemlock data Use 0001:01:00.0 instead of 0000:04:02.0 as the source address for the host device. This doesn't change anything at the moment, but it will make a difference later on. Signed-off-by: Andrea Bolognani <abologna@redhat.com> Reviewed-by: Laine Stump <laine@laine.org> 2017-06-01 16:51:06 +00:00			`<address domain='0x0001' bus='0x01' slot='0x00' function='0x0'/>`
tests: Introduce QEMU memory locking limit tests These tests cover a number of scenarios where we care about the memory locking limit being set correctly for the guest to work properly. 2017-03-23 13:06:57 +00:00			`</source>`
			`</hostdev>`
			`</devices>`
			`</domain>`