提交 · b1c81567c7172bc9dcd701cf46ea3f87725d62c7 · openeuler / libvirt

03 8月, 2017 2 次提交

docs: switch to using HTML5 doctype declaration · b1c81567

由 Daniel P. Berrange 提交于 7月 26, 2017

The HTML5 doctype is simply

  <!DOCTYPE html>

no DTD is present because HTML5 is no longer defined as an
extension of SGML.

XSL has no way to natively output a doctype without a public
or system identifier, so we have to use an <xsl:text> hack
instead.

See also

  https://dev.w3.org/html5/html-author/#doctype-declarationSigned-off-by: NDaniel P. Berrange <berrange@redhat.com>

b1c81567

docs: switch to using 'id' attribute instead of 'name' for links · 4e42ff6b

由 Daniel P. Berrange 提交于 7月 26, 2017

The 'name' attribute on <a...> elements is deprecated in favour
of the 'id' attribute which is allowed on any element. HTML5
drops 'name' support entirely.
Signed-off-by: NDaniel P. Berrange <berrange@redhat.com>

4e42ff6b

22 3月, 2017 1 次提交

domain_capabilities: Don't report machine type for bhyve · df769041

由 Michal Privoznik 提交于 3月 21, 2017

For some drivers the domain's machine type makes no sense. They
just don't use it. A great example is bhyve driver. Therefore it
makes very less sense to report machine in domain capabilities
XML.
Signed-off-by: NMichal Privoznik <mprivozn@redhat.com>

df769041

22 9月, 2016 3 次提交

Show host model in domain capabilities · 14319c81

由 Jiri Denemark 提交于 6月 15, 2016

The domain capabilities XML is capable of showing whether each guest CPU
mode is supported or not with a possibility to provide additional
details. This patch enhances host-model capability to advertise the
exact CPU model which will be used as a host-model:

    <cpu>
        ...
        <mode name='host-model' supported='yes'>
            <model fallback='allow'>Broadwell</model>
            <vendor>Intel</vendor>
            <feature policy='disable' name='aes'/>
            <feature policy='require' name='vmx'/>
        </mode>
        ...
    </cpu>
Signed-off-by: NJiri Denemark <jdenemar@redhat.com>

14319c81

domcaps: Add CPU usable flag · d4c007e6

由 Jiri Denemark 提交于 6月 15, 2016

In case a hypervisor is able to tell us a list of supported CPU models
and whether each CPU models can be used on the current host, we can
propagate this to domain capabilities. This is a better alternative
to calling virConnectCompareCPU for each supported CPU model.
Signed-off-by: NJiri Denemark <jdenemar@redhat.com>

d4c007e6

domcaps: Add support for listing supported CPU models · 167280e7

由 Jiri Denemark 提交于 4月 22, 2016

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: NJiri Denemark <jdenemar@redhat.com>

167280e7

10 5月, 2016 2 次提交

domaincaps: Report video modelType · 5ed235c6

由 Cole Robinson 提交于 5月 08, 2016

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

5ed235c6

C
domaincaps: Report graphics type enum · 6da27ad1
由 Cole Robinson 提交于 5月 08, 2016
```
Requires adding the plumbing for <device><graphics>
Wire it up for qemu too
```
6da27ad1

22 4月, 2016 1 次提交

docs: Use <code> inside <dt> for symbols · 61b070cf

由 Andrea Bolognani 提交于 4月 21, 2016

Most of the time, the <dt> tag is used when providing
documentation for a symbol; enclose symbols in <code> tags to
style them appropriately.

61b070cf

20 4月, 2016 1 次提交
- A
  
  docs: Document the new XML elements · eab0fda2
  由 Andrea Bolognani 提交于 4月 18, 2016
  
  eab0fda2
13 1月, 2015 1 次提交

formatdomaincaps: Correctly format API reference · 2b8090b7

由 Michal Privoznik 提交于 1月 13, 2015

Well, since the link to the virConnectGetDomainCapabilities API is in
<pre/> section we must take special care about the spaces around the
link.
Signed-off-by: NMichal Privoznik <mprivozn@redhat.com>
Acked-by: NLaszlo Ersek <lersek@redhat.com>

2b8090b7

02 12月, 2014 1 次提交

docs: Correct invalid hyperlinks · af1b89d1

由 Martin Kletzander 提交于 12月 01, 2014

Since libvirt.h was split into multiple files and similarly
docs/libvirt-libvirt.html, docs/hvsupport.html have bad hyperlinks. The
same happens for all the html.in files that used <code class='docref'>
tag, because page.xsl has no idea where to point the link that's found.
Signed-off-by: NMartin Kletzander <mkletzan@redhat.com>

af1b89d1

17 9月, 2014 2 次提交

domaincaps: Expose UEFI binary path, if it exists · f05b6a91

由 Michal Privoznik 提交于 9月 16, 2014

Check to see if the UEFI binary mentioned in qemu.conf actually
exists, and if so expose it in domcapabilities like

<loader ...>
  <value>/path/to/ovmf</value>
</loader>

We introduce some generic domcaps infrastructure for handling
a dynamic list of string values, it may be of use for future bits.
Signed-off-by: NMichal Privoznik <mprivozn@redhat.com>

f05b6a91

domaincaps: Expose UEFI capability · 4f76621c

由 Michal Privoznik 提交于 9月 16, 2014

As of 54289916 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: NMichal Privoznik <mprivozn@redhat.com>

4f76621c

03 7月, 2014 1 次提交

Introduce domain_capabilities · 614581f3

由 Michal Privoznik 提交于 6月 25, 2014

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: NMichal Privoznik <mprivozn@redhat.com>

614581f3