libvirt/tests/qemuxml2argvdata/qemuxml2argv-cpu-kvmclock.xml

<domain type='kvm'>
  <name>QEMUGuest1</name>
  <uuid>c7a5fdbd-edaf-9455-926a-d65c16db1809</uuid>
  <memory>219100</memory>
  <currentMemory>219100</currentMemory>
  <vcpu>6</vcpu>
  <os>
    <type arch='i686' machine='pc'>hvm</type>
    <boot dev='network'/>
  </os>
  <cpu mode='custom' match='exact'>
    <model fallback='allow'>core2duo</model>
  </cpu>
  <clock offset='utc'>
    <timer name='kvmclock' present='no'/>
  </clock>
  <on_poweroff>destroy</on_poweroff>
  <on_reboot>restart</on_reboot>
  <on_crash>destroy</on_crash>
  <devices>
    <emulator>/./qemu.sh</emulator>
    <controller type='usb' index='0'/>
    <memballoon model='virtio'/>
  </devices>
</domain>
qemu: parse and create -cpu ...,-kvmclock QEMU supports a bunch of CPUID features that are tied to the kvm CPUID nodes rather than the processor's. They are "kvmclock", "kvm_nopiodelay", "kvm_mmu", "kvm_asyncpf". These are not known to libvirt and their CPUID leaf might move if (for example) the Hyper-V extensions are enabled. Hence their handling would anyway require some special-casing. However, among these the most useful is kvmclock; an additional "property" of this feature is that a <timer> element is a better model than a CPUID feature. Although, creating part of the -cpu command-line from something other than the <cpu> XML element introduces some ugliness. Reviewed-by: Jiri Denemark <jdenemar@redhat.com> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com> 2012-01-27 13:49:52 +00:00			`<domain type='kvm'>`
			`<name>QEMUGuest1</name>`
			`<uuid>c7a5fdbd-edaf-9455-926a-d65c16db1809</uuid>`
			`<memory>219100</memory>`
			`<currentMemory>219100</currentMemory>`
			`<vcpu>6</vcpu>`
			`<os>`
			`<type arch='i686' machine='pc'>hvm</type>`
			`<boot dev='network'/>`
			`</os>`
			`<cpu mode='custom' match='exact'>`
			`<model fallback='allow'>core2duo</model>`
			`</cpu>`
			`<clock offset='utc'>`
			`<timer name='kvmclock' present='no'/>`
			`</clock>`
			`<on_poweroff>destroy</on_poweroff>`
			`<on_reboot>restart</on_reboot>`
			`<on_crash>destroy</on_crash>`
			`<devices>`
			`<emulator>/./qemu.sh</emulator>`
domain: add implicit USB controller Some tools, such as virt-manager, prefers having the default USB controller explicit in the XML document. This patch makes sure there is one. With this patch, it is now possible to switch from USB1 to USB2 from the release 0.9.1 of virt-manager. Fix tests to pass with this change. 2012-02-08 00:48:25 +00:00			`<controller type='usb' index='0'/>`
qemu: parse and create -cpu ...,-kvmclock QEMU supports a bunch of CPUID features that are tied to the kvm CPUID nodes rather than the processor's. They are "kvmclock", "kvm_nopiodelay", "kvm_mmu", "kvm_asyncpf". These are not known to libvirt and their CPUID leaf might move if (for example) the Hyper-V extensions are enabled. Hence their handling would anyway require some special-casing. However, among these the most useful is kvmclock; an additional "property" of this feature is that a <timer> element is a better model than a CPUID feature. Although, creating part of the -cpu command-line from something other than the <cpu> XML element introduces some ugliness. Reviewed-by: Jiri Denemark <jdenemar@redhat.com> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com> 2012-01-27 13:49:52 +00:00			`<memballoon model='virtio'/>`
			`</devices>`
			`</domain>`