libvirt/tests/domaincapsschemadata/domaincaps-basic.xml

<domainCapabilities>
  <path>/bin/emulatorbin</path>
  <domain>uml</domain>
  <machine>my-machine-type</machine>
  <arch>x86_64</arch>
  <os supported='no'/>
  <devices>
    <disk supported='no'/>
    <hostdev supported='no'/>
  </devices>
</domainCapabilities>
Introduce domain_capabilities This new module holds and formats capabilities for emulator. If you are about to create a new domain, you may want to know what is the host or hypervisor capable of. To make sure we don't regress on the XML, the formatting is not something left for each driver to implement, rather there's general format function. The domain capabilities is a lockable object (even though the locking is not necessary yet) which uses reference counter. Signed-off-by: Michal Privoznik <mprivozn@redhat.com> 2014-06-25 11:24:53 +00:00			`<domainCapabilities>`
			`<path>/bin/emulatorbin</path>`
			`<domain>uml</domain>`
			`<machine>my-machine-type</machine>`
			`<arch>x86_64</arch>`
domaincaps: Expose UEFI capability As of 542899168c38 we learned libvirt to use UEFI for domains. However, management applications may firstly query if libvirt supports it. And this is where virConnectGetDomainCapabilities() API comes handy. Signed-off-by: Michal Privoznik <mprivozn@redhat.com> 2014-09-16 12:47:47 +00:00			`<os supported='no'/>`
Introduce domain_capabilities This new module holds and formats capabilities for emulator. If you are about to create a new domain, you may want to know what is the host or hypervisor capable of. To make sure we don't regress on the XML, the formatting is not something left for each driver to implement, rather there's general format function. The domain capabilities is a lockable object (even though the locking is not necessary yet) which uses reference counter. Signed-off-by: Michal Privoznik <mprivozn@redhat.com> 2014-06-25 11:24:53 +00:00			`<devices>`
			`<disk supported='no'/>`
			`<hostdev supported='no'/>`
			`</devices>`
			`</domainCapabilities>`