libvirt/tests/qemuxml2argvdata/qemuxml2argv-q35-pm-disable.xml

<domain type='qemu'>
  <name>q35</name>
  <uuid>56f5055c-1b8d-490c-844a-ad646a1caaaa</uuid>
  <memory unit='KiB'>1048576</memory>
  <currentMemory unit='KiB'>1048576</currentMemory>
  <vcpu placement='static'>1</vcpu>
  <os>
    <type arch='x86_64' machine='pc-q35-2.5'>hvm</type>
    <boot dev='network'/>
  </os>
  <pm>
    <suspend-to-mem enabled='no'/>
    <suspend-to-disk enabled='no'/>
  </pm>
  <devices>
    <emulator>/usr/bin/qemu-kvm</emulator>
  </devices>
</domain>
qemu: command: wire up usage of q35/ich9 disable s3/s4 If the q35 specific disable s3/s4 setting isn't supported, fallback to specifying the PIIX setting, which is the previous behavior. It doesn't have any effect, but qemu will just warn about it rather than error: qemu-system-x86_64: Warning: global PIIX4_PM.disable_s3=1 not used qemu-system-x86_64: Warning: global PIIX4_PM.disable_s4=1 not used Since it doesn't error, I don't think we should either, since there may be configs in the wild that already have q35 + disable_s3/4 (via virt-manager) 2016-01-09 21:00:01 +00:00			`<domain type='qemu'>`
			`<name>q35</name>`
			`<uuid>56f5055c-1b8d-490c-844a-ad646a1caaaa</uuid>`
			`<memory unit='KiB'>1048576</memory>`
			`<currentMemory unit='KiB'>1048576</currentMemory>`
			`<vcpu placement='static'>1</vcpu>`
			`<os>`
			`<type arch='x86_64' machine='pc-q35-2.5'>hvm</type>`
			`<boot dev='network'/>`
			`</os>`
			`<pm>`
			`<suspend-to-mem enabled='no'/>`
			`<suspend-to-disk enabled='no'/>`
			`</pm>`
			`<devices>`
			`<emulator>/usr/bin/qemu-kvm</emulator>`
			`</devices>`
			`</domain>`