External/libvirt
1
0
Fork 0
mirror of https://gitlab.com/libvirt/libvirt.git synced 2024-11-08 14:29:56 +00:00
Code Issues Packages Projects Releases Wiki Activity
f204cf5103
libvirt/tests/domaincapsschemadata/basic.xml

26 lines
645 B
XML
Raw Normal View History

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>
qemu: Add I/O thread support info into domain capabilities Signed-off-by: Martin Kletzander <mkletzan@redhat.com>
2017-10-19 12:19:38 +00:00
<iothreads supported='no'/>
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'/>
domcaps: Add support for listing supported CPU models The patch adds <cpu> element to domain capabilities XML: <cpu> <mode name='host-passthrough' supported='yes'/> <mode name='host-model' supported='yes'/> <mode name='custom' supported='yes'> <model>Broadwell</model> <model>Broadwell-noTSX</model> ... </mode> </cpu> Applications can use it to inspect what CPU configuration modes are supported for a specific combination of domain type, emulator binary, guest architecture and machine type. Signed-off-by: Jiri Denemark <jdenemar@redhat.com>
2016-04-22 09:08:57 +00:00
<cpu>
<mode name='host-passthrough' supported='no'/>
<mode name='host-model' supported='no'/>
<mode name='custom' supported='no'/>
</cpu>
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'/>
domaincaps: Report graphics type enum Requires adding the plumbing for <device><graphics> Wire it up for qemu too
2016-05-08 15:57:20 +00:00
<graphics supported='no'/>
domaincaps: Report video modelType Requires adding the plumbing for <device><video> The value is <enum name='modelType'> to match the associated domain XML of <video><model type='XXX'/> Wire it up for qemu too
2016-05-08 16:11:39 +00:00
<video 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
<hostdev supported='no'/>
</devices>
conf: Expose GIC capabilities Add information about GIC capabilities to virDomainCaps and update the formatter to include them in the XML output.
2016-03-09 17:28:59 +00:00
<features>
<gic supported='no'/>
domain_capabilities: Report <vmcoreinfo> support Report <features><vmcoreinfo supported='yes'/> if the guest config accepts <features><vmcoreinfo state='on'/> Reviewed-by: John Ferlan <jferlan@redhat.com> Signed-off-by: Cole Robinson <crobinso@redhat.com>
2018-04-17 17:54:28 +00:00
<vmcoreinfo supported='no'/>
domcaps: Add 'genid' to domain capabilities Report domaincaps <features><genid supported='yes'/> if the guest config accepts <genid/> or <genid>$GUID</genid>. Signed-off-by: John Ferlan <jferlan@redhat.com> ACKed-by: Michal Privoznik <mprivozn@redhat.com>
2018-04-27 12:16:40 +00:00
<genid supported='no'/>
conf: Fix formatting of <sev> element in domain capabilities XML We only formatted the <sev> element when QEMU supported the feature when in fact we should always format the element to make clear that libvirt knows about the feature and the fact whether it is or isn't supported depends on QEMU version, in other words if QEMU doesn't support the feature we're going to format the following into the domain capabilities XML: <sev supported='no'/> This patch also adjusts the RNG schema accordingly in order to reflect the proposed change. Signed-off-by: Erik Skultety <eskultet@redhat.com> Reviewed-by: Ján Tomko <jtomko@redhat.com>
2018-06-14 12:18:30 +00:00
<sev supported='no'/>
conf: Expose GIC capabilities Add information about GIC capabilities to virDomainCaps and update the formatter to include them in the XML output.
2016-03-09 17:28:59 +00:00
</features>
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>
Reference in New Issue Copy Permalink