libvirt/tests/qemuxml2argvdata/qemuxml2argv-mlock-on.xml

<domain type='qemu'>
  <name>QEMUGuest1</name>
  <uuid>c7a5fdbd-edaf-9455-926a-d65c16db1809</uuid>
  <memory unit='KiB'>219136</memory>
  <currentMemory unit='KiB'>219136</currentMemory>
  <memtune>
    <hard_limit unit='KiB'>256000</hard_limit>
  </memtune>
  <memoryBacking>
    <locked/>
  </memoryBacking>
  <vcpu placement='static'>1</vcpu>
  <os>
    <type arch='i686' machine='pc'>hvm</type>
    <boot dev='hd'/>
  </os>
  <devices>
    <emulator>/usr/bin/qemu</emulator>
    <memballoon model='none'/>
  </devices>
</domain>
qemu: Implement support for locking domain's memory pages 2013-05-16 20:01:05 +00:00			`<domain type='qemu'>`
			`<name>QEMUGuest1</name>`
			`<uuid>c7a5fdbd-edaf-9455-926a-d65c16db1809</uuid>`
			`<memory unit='KiB'>219136</memory>`
			`<currentMemory unit='KiB'>219136</currentMemory>`
qemu: Forbid <memoryBacking><locked> without <memtune><hard_limit> In order for memory locking to work, the hard limit on memory locking (and usage) has to be set appropriately by the user. The documentation mentions the requirement already: with this patch, it's going to be enforced by runtime checks as well, by forbidding a non-compliant guest from being defined as well as edited and started. Resolves: https://bugzilla.redhat.com/show_bug.cgi?id=1316774 2017-02-06 16:54:49 +00:00			`<memtune>`
			`<hard_limit unit='KiB'>256000</hard_limit>`
			`</memtune>`
qemu: Implement support for locking domain's memory pages 2013-05-16 20:01:05 +00:00			`<memoryBacking>`
			`<locked/>`
			`</memoryBacking>`
			`<vcpu placement='static'>1</vcpu>`
			`<os>`
			`<type arch='i686' machine='pc'>hvm</type>`
			`<boot dev='hd'/>`
			`</os>`
			`<devices>`
			`<emulator>/usr/bin/qemu</emulator>`
			`<memballoon model='none'/>`
			`</devices>`
			`</domain>`