- Devel - libvirt List Archives

[libvirt] [PATCH v2 0/2] Rework reference locking; in QEMU, for starters
by Martin Kletzander 09 Dec '14

09 Dec '14

v2: - qemuDomObjEndAPI now resets the parameter to NULL - Fixes from Peter incorporated - rebased on current master v1: https://www.redhat.com/archives/libvir-list/2014-December/msg00198.html Martin Kletzander (2): conf: Rework virDomainObjListFindByUUID to allow more concurrent APIs qemu: completely rework reference counting src/conf/domain_conf.c | 27 +- src/conf/domain_conf.h | 2 + src/libvirt_private.syms | 1 + src/qemu/THREADS.txt | 40 ++- src/qemu/qemu_domain.c | 29 +- src/qemu/qemu_domain.h | 12 +- src/qemu/qemu_driver.c | 708 ++++++++++++++++------------------------------ src/qemu/qemu_migration.c | 108 +++---- src/qemu/qemu_migration.h | 10 +- src/qemu/qemu_process.c | 87 +++--- 10 files changed, 386 insertions(+), 638 deletions(-) -- 2.2.0

3 8

[libvirt] [PATCH] conf: forbid negative number in address(like controller, bus, slot...)
by Luyao Huang 09 Dec '14

09 Dec '14

https://bugzilla.redhat.com/show_bug.cgi?id=1171582 When we edit a negative controller address number to a device, some of them will auto generate a controller with invalid index number. This will make guest disappear after restart libvirtd. Instead of allow negative number for controller index, I think we should forbid negative number in these place (we did this before, but after f18c02ec, virStrToLong_ui changed to allow negative number). So changed to use virStrToLong_uip in these place. Signed-off-by: Luyao Huang <lhuang(a)redhat.com> --- src/conf/device_conf.c | 4 ++-- src/conf/domain_conf.c | 32 ++++++++++++++++---------------- 2 files changed, 18 insertions(+), 18 deletions(-) diff --git a/src/conf/device_conf.c b/src/conf/device_conf.c index b3b04e1..a7ec8a6 100644 --- a/src/conf/device_conf.c +++ b/src/conf/device_conf.c @@ -71,14 +71,14 @@ virDevicePCIAddressParseXML(xmlNodePtr node, } if (bus && - virStrToLong_ui(bus, NULL, 0, &addr->bus) < 0) { + virStrToLong_uip(bus, NULL, 0, &addr->bus) < 0) { virReportError(VIR_ERR_INTERNAL_ERROR, "%s", _("Cannot parse <address> 'bus' attribute")); goto cleanup; } if (slot && - virStrToLong_ui(slot, NULL, 0, &addr->slot) < 0) { + virStrToLong_uip(slot, NULL, 0, &addr->slot) < 0) { virReportError(VIR_ERR_INTERNAL_ERROR, "%s", _("Cannot parse <address> 'slot' attribute")); goto cleanup; diff --git a/src/conf/domain_conf.c b/src/conf/domain_conf.c index 2d81c37..961ec67 100644 --- a/src/conf/domain_conf.c +++ b/src/conf/domain_conf.c @@ -3453,28 +3453,28 @@ virDomainDeviceDriveAddressParseXML(xmlNodePtr node, unit = virXMLPropString(node, "unit"); if (controller && - virStrToLong_ui(controller, NULL, 10, &addr->controller) < 0) { + virStrToLong_uip(controller, NULL, 10, &addr->controller) < 0) { virReportError(VIR_ERR_INTERNAL_ERROR, "%s", _("Cannot parse <address> 'controller' attribute")); goto cleanup; } if (bus && - virStrToLong_ui(bus, NULL, 10, &addr->bus) < 0) { + virStrToLong_uip(bus, NULL, 10, &addr->bus) < 0) { virReportError(VIR_ERR_INTERNAL_ERROR, "%s", _("Cannot parse <address> 'bus' attribute")); goto cleanup; } if (target && - virStrToLong_ui(target, NULL, 10, &addr->target) < 0) { + virStrToLong_uip(target, NULL, 10, &addr->target) < 0) { virReportError(VIR_ERR_INTERNAL_ERROR, "%s", _("Cannot parse <address> 'target' attribute")); goto cleanup; } if (unit && - virStrToLong_ui(unit, NULL, 10, &addr->unit) < 0) { + virStrToLong_uip(unit, NULL, 10, &addr->unit) < 0) { virReportError(VIR_ERR_INTERNAL_ERROR, "%s", _("Cannot parse <address> 'unit' attribute")); goto cleanup; @@ -3507,21 +3507,21 @@ virDomainDeviceVirtioSerialAddressParseXML( port = virXMLPropString(node, "port"); if (controller && - virStrToLong_ui(controller, NULL, 10, &addr->controller) < 0) { + virStrToLong_uip(controller, NULL, 10, &addr->controller) < 0) { virReportError(VIR_ERR_INTERNAL_ERROR, "%s", _("Cannot parse <address> 'controller' attribute")); goto cleanup; } if (bus && - virStrToLong_ui(bus, NULL, 10, &addr->bus) < 0) { + virStrToLong_uip(bus, NULL, 10, &addr->bus) < 0) { virReportError(VIR_ERR_INTERNAL_ERROR, "%s", _("Cannot parse <address> 'bus' attribute")); goto cleanup; } if (port && - virStrToLong_ui(port, NULL, 10, &addr->port) < 0) { + virStrToLong_uip(port, NULL, 10, &addr->port) < 0) { virReportError(VIR_ERR_INTERNAL_ERROR, "%s", _("Cannot parse <address> 'port' attribute")); goto cleanup; @@ -3553,19 +3553,19 @@ virDomainDeviceCCWAddressParseXML(xmlNodePtr node, if (cssid && ssid && devno) { if (cssid && - virStrToLong_ui(cssid, NULL, 0, &addr->cssid) < 0) { + virStrToLong_uip(cssid, NULL, 0, &addr->cssid) < 0) { virReportError(VIR_ERR_INTERNAL_ERROR, "%s", _("Cannot parse <address> 'cssid' attribute")); goto cleanup; } if (ssid && - virStrToLong_ui(ssid, NULL, 0, &addr->ssid) < 0) { + virStrToLong_uip(ssid, NULL, 0, &addr->ssid) < 0) { virReportError(VIR_ERR_INTERNAL_ERROR, "%s", _("Cannot parse <address> 'ssid' attribute")); goto cleanup; } if (devno && - virStrToLong_ui(devno, NULL, 0, &addr->devno) < 0) { + virStrToLong_uip(devno, NULL, 0, &addr->devno) < 0) { virReportError(VIR_ERR_INTERNAL_ERROR, "%s", _("Cannot parse <address> 'devno' attribute")); goto cleanup; @@ -3607,14 +3607,14 @@ virDomainDeviceCcidAddressParseXML(xmlNodePtr node, slot = virXMLPropString(node, "slot"); if (controller && - virStrToLong_ui(controller, NULL, 10, &addr->controller) < 0) { + virStrToLong_uip(controller, NULL, 10, &addr->controller) < 0) { virReportError(VIR_ERR_INTERNAL_ERROR, "%s", _("Cannot parse <address> 'controller' attribute")); goto cleanup; } if (slot && - virStrToLong_ui(slot, NULL, 10, &addr->slot) < 0) { + virStrToLong_uip(slot, NULL, 10, &addr->slot) < 0) { virReportError(VIR_ERR_INTERNAL_ERROR, "%s", _("Cannot parse <address> 'slot' attribute")); goto cleanup; @@ -3642,7 +3642,7 @@ virDomainDeviceUSBAddressParseXML(xmlNodePtr node, bus = virXMLPropString(node, "bus"); if (port && - ((virStrToLong_ui(port, &tmp, 10, &p) < 0 || (*tmp != '\0' && *tmp != '.')) || + ((virStrToLong_uip(port, &tmp, 10, &p) < 0 || (*tmp != '\0' && *tmp != '.')) || (*tmp == '.' && (virStrToLong_ui(tmp + 1, &tmp, 10, &p) < 0 || (*tmp != '\0' && *tmp != '.'))) || (*tmp == '.' && (virStrToLong_ui(tmp + 1, &tmp, 10, &p) < 0 || (*tmp != '\0' && *tmp != '.'))) || (*tmp == '.' && (virStrToLong_ui(tmp + 1, &tmp, 10, &p) < 0 || (*tmp != '\0'))))) { @@ -3655,7 +3655,7 @@ virDomainDeviceUSBAddressParseXML(xmlNodePtr node, port = NULL; if (bus && - virStrToLong_ui(bus, NULL, 10, &addr->bus) < 0) { + virStrToLong_uip(bus, NULL, 10, &addr->bus) < 0) { virReportError(VIR_ERR_INTERNAL_ERROR, "%s", _("Cannot parse <address> 'bus' attribute")); goto cleanup; @@ -3777,14 +3777,14 @@ virDomainDeviceISAAddressParseXML(xmlNodePtr node, irq = virXMLPropString(node, "irq"); if (iobase && - virStrToLong_ui(iobase, NULL, 16, &addr->iobase) < 0) { + virStrToLong_uip(iobase, NULL, 16, &addr->iobase) < 0) { virReportError(VIR_ERR_XML_ERROR, "%s", _("Cannot parse <address> 'iobase' attribute")); goto cleanup; } if (irq && - virStrToLong_ui(irq, NULL, 16, &addr->irq) < 0) { + virStrToLong_uip(irq, NULL, 16, &addr->irq) < 0) { virReportError(VIR_ERR_XML_ERROR, "%s", _("Cannot parse <address> 'irq' attribute")); goto cleanup; -- 1.8.3.1

2 2

[libvirt] [PATCH] libxl: Set path to console on domain startup
by Anthony PERARD 09 Dec '14

09 Dec '14

Hi, I'm trying to fix an issue when using OpenStack with libvirt+xen (libxenlight). OpenStack cannot access the console output of a Xen PV guest, because the XML generated by libvirt for a domain is missing the path to the pty. The path actually appear in the XML once one call virDomainOpenConsole(). The patch intend to get the path to the pty without having to call virDomainOpenConsole, so I've done the work in libxlDomainStart(). So I have a few question: Is libxlDomainStart will be called on restore/migrate/reboot? I guest the function libxlDomainOpenConsole() would not need to do the same work if the console path is settup properly. There is a bug report about this: https://bugzilla.redhat.com/show_bug.cgi?id=1170743 Regards, Anthony PERARD (1): libxl: Set path to console on domain startup. src/libxl/libxl_domain.c | 17 +++++++++++++++++ 1 file changed, 17 insertions(+) -- Anthony PERARD

5 10

[libvirt] [perl-Sys-Virt][PATCH] Fix memory corruption when calling migrate_to_uri
by Hao Liu 09 Dec '14

09 Dec '14

The variable `nparams` didn't change accordingly when adding a new parameter in commit b2cecf73. This patch fixes https://bugzilla.redhat.com/show_bug.cgi?id=1171938 Signed-off-by: Hao Liu <hliu(a)redhat.com> --- Virt.xs | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Virt.xs b/Virt.xs index 763a117..688b0d7 100644 --- a/Virt.xs +++ b/Virt.xs @@ -4342,7 +4342,7 @@ _migrate_to_uri(dom, desturi, newparams, flags=0) virTypedParameter *params; int nparams; PPCODE: - nparams = 5; + nparams = 6; Newx(params, nparams, virTypedParameter); strncpy(params[0].field, VIR_MIGRATE_PARAM_URI, -- 1.8.3.1

2 1

[libvirt] [PATCH] qemu: migration: Unlock vm if ACL check in Perform phase of protocol v2 fails
by Peter Krempa 09 Dec '14

09 Dec '14

Avoid leaving the domain locked on a failed ACL check. Introduced in commit abf75aea247e (Add ACL checks into the QEMU driver). --- src/qemu/qemu_driver.c | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/src/qemu/qemu_driver.c b/src/qemu/qemu_driver.c index ed8e140..8cec372 100644 --- a/src/qemu/qemu_driver.c +++ b/src/qemu/qemu_driver.c @@ -11393,51 +11393,53 @@ static int qemuDomainMigratePerform(virDomainPtr dom, const char *cookie, int cookielen, const char *uri, unsigned long flags, const char *dname, unsigned long resource) { virQEMUDriverPtr driver = dom->conn->privateData; virDomainObjPtr vm; int ret = -1; const char *dconnuri = NULL; virCheckFlags(QEMU_MIGRATION_FLAGS, -1); if (virLockManagerPluginUsesState(driver->lockManager)) { virReportError(VIR_ERR_INTERNAL_ERROR, _("Cannot use migrate v2 protocol with lock manager %s"), virLockManagerPluginGetName(driver->lockManager)); goto cleanup; } if (!(vm = qemuDomObjFromDomain(dom))) goto cleanup; - if (virDomainMigratePerformEnsureACL(dom->conn, vm->def) < 0) + if (virDomainMigratePerformEnsureACL(dom->conn, vm->def) < 0) { + virObjectUnlock(vm); goto cleanup; + } if (flags & VIR_MIGRATE_PEER2PEER) { dconnuri = uri; uri = NULL; } /* Do not output cookies in v2 protocol, since the cookie * length was not sufficiently large, causing failures * migrating between old & new libvirtd. * * Consume any cookie we were able to decode though */ ret = qemuMigrationPerform(driver, dom->conn, vm, NULL, dconnuri, uri, NULL, NULL, cookie, cookielen, NULL, NULL, /* No output cookies in v2 */ flags, dname, resource, false); cleanup: return ret; } /* Finish is the third and final step, and it runs on the destination host. */ -- 2.1.0

2 2

[libvirt] Heads-up about the next release
by Daniel Veillard 09 Dec '14

09 Dec '14

The plan exposed last month is to push the new release mid month. I will be unavailable mostly on 15-16 so pondering pushing next week, which means entering freeze for example Tuesday morning for a final release toward Fri 12 or Sat 13. We have close to 300 commits already since 1.2.10 so that sounds about time :-) Please raise any issue with going forward with this plan, thanks, Daniel -- Daniel Veillard | Open Source and Standards, Red Hat veillard(a)redhat.com | libxml Gnome XML XSLT toolkit http://xmlsoft.org/ http://veillard.com/ | virtualization library http://libvirt.org/

3 2

[libvirt] [PATCH] docs: Fix simple typo s/ a API/ an API/
by Martin Kletzander 09 Dec '14

09 Dec '14

Signed-off-by: Martin Kletzander <mkletzan(a)redhat.com> --- Notes: Pushed as trivial docs/internals/rpc.html.in | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/internals/rpc.html.in b/docs/internals/rpc.html.in index 627d7aa..f2ed64f 100644 --- a/docs/internals/rpc.html.in +++ b/docs/internals/rpc.html.in @@ -597,7 +597,7 @@ <h4><a name="apiclientdispatchex1">Example with buck passing</a></h4> - In the first example, a second thread issues a API call + In the first example, a second thread issues an API call while the first thread holds the buck. The reply to the first call arrives first, so the buck is passed to the second thread. -- 2.2.0

1 0

[libvirt] [PATCH] build: Move check for XML::XPath into bootstrap
by Martin Kletzander 09 Dec '14

09 Dec '14

The module XML::XPath is needed when building from git only (no need to have it when building from tarball), so this patch moves the check from specfile into bootstrap.conf. Signed-off-by: Martin Kletzander <mkletzan(a)redhat.com> --- This patch needs a gnulib update with this proposed patch in it: https://lists.gnu.org/archive/html/bug-gnulib/2014-12/msg00108.html bootstrap.conf | 3 ++- libvirt.spec.in | 1 - 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/bootstrap.conf b/bootstrap.conf index e7ea9c9..c06ee4c 100644 --- a/bootstrap.conf +++ b/bootstrap.conf @@ -1,6 +1,6 @@ # Bootstrap configuration. -# Copyright (C) 2010-2013 Red Hat, Inc. +# Copyright (C) 2010-2014 Red Hat, Inc. # This library is free software; you can redistribute it and/or # modify it under the terms of the GNU Lesser General Public @@ -210,6 +210,7 @@ gzip - libtool - patch - perl 5.5 +perl::XML::XPath - pkg-config - python-config - rpcgen - diff --git a/libvirt.spec.in b/libvirt.spec.in index bda28e7..a23aa0a 100644 --- a/libvirt.spec.in +++ b/libvirt.spec.in @@ -427,7 +427,6 @@ BuildRequires: /usr/bin/pod2man %endif BuildRequires: git BuildRequires: perl -BuildRequires: perl-XML-XPath BuildRequires: python %if %{with_systemd} BuildRequires: systemd-units -- 2.2.0

2 1

Re: [libvirt] Waiting for review of [PATCH v2 2/21] hyperv: implementation of virConnectGetVersion
by Yves Vinter 09 Dec '14

09 Dec '14

No answer ??? What does it mean : - you don't have a window for the review ? - you are not interested in getting these developments ? - you don't agree with the delivery process I proposed ? - you prefer getting the whole set of the v2 versions before reviewing ? Please, just let me know... Thanks, Yves. De : Yves Vinter Envoyé : mardi 25 novembre 2014 10:10 À : libvir-list(a)redhat.com Objet : Waiting for review of [libvirt] [PATCH v2 2/21] hyperv: implementation of virConnectGetVersion Hi All, As I described the 27th of October in the following thread: https://www.redhat.com/archives/libvir-list/2014-October/msg00840.html [libvirt] [PATCH v2 0/21] hyperv: hyperv: set of new functionalities new functionalities has been implemented in the libvirt hyperv driver as a set of 21 patches. PATCH 01/21: hyperv: avoid query memleaks on failure PATCH 02/21: hyperv: implementation of virConnectGetVersion PATCH 03/21: hyperv: implementation of virConnectGetCapabilities PATCH 04/21: hyperv: implementation of virDomainGetVcpus and virConnectGetMaxVcpus PATCH 05/21: hyperv: implementation of virNodeGetFreeMemory PATCH 06/21: hyperv: implementation of virDomainShutdown and virDomainShutdownFlags PATCH 07/21: hyperv: implementation of virDomainGetSchedulerType and virDomainGetSchedulerParameters PATCH 08/21: hyperv: implementation of virNetworkLookupByName PATCH 09/21: hyperv: implementation of virNetworkGetXMLDesc PATCH 10/21: hyperv: implementation of virConnectNumOfNetworks and virConnectListNetworks PATCH 11/21: hyperv: implementation of virConnectNumOfDefinedNetworks and virConnectListDefinedNetworks PATCH 12/21: hyperv: implementation of hypervInvokeMethod to handle complex parameters PATCH 13/21: hyperv: implementation of virDomainSetAutostart and virDomainGetAutostart PATCH 14/21: hyperv: implementation of virDomainSetMaxMemory PATCH 15/21: hyperv: implementation of virDomainSetMemory and virDomainSetMemoryFlags PATCH 16/21: hyperv: implementation of virDomainSetVcpus and virDomainSetVcpusFlags PATCH 17/21: hyperv: implementation of virDomainUndefine and virDomainUndefineFlags PATCH 18/21: hyperv: implementation of internal function hypervDomainAttachDisk PATCH 19/21: hyperv: implementation of internal function hypervDomainAttachNetwork PATCH 20/21: hyperv: implementation of virDomainAttachDevice and virDomainAttachDeviceFlags PATCH 21/21: hyperv: implementation of virDomainDefineXML and virDomainCreateXML A first version of this set has been submitted the 8th of October. The first 3 patches have been already reviewed by Eric and the first patch has been pushed in the main stream. Based on the remarks after this 3 reviews, I will produce a V2 for the whole set of patches. It will be more convenient for me to submit V2 versions patch after patch, only after the previous one has been approved and pushed in the main branch. The V2 of patch 02/21 has been submitted the 27th of October here: https://www.redhat.com/archives/libvir-list/2014-October/msg00824.html [libvirt] [PATCH v2 2/21] hyperv: implementation of virConnectGetVersion I've not received any feedback since, and it has not been pushed in the main stream. Is there any issue? I'm still waiting for its approval before submitting the next patch... Thanks for you answer, Yves.

2 1

[libvirt] [PATCH] docs: Correct invalid hyperlinks
by Martin Kletzander 09 Dec '14

09 Dec '14

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: Martin Kletzander <mkletzan(a)redhat.com> --- docs/Makefile.am | 4 +- docs/acl.html.in | 2 +- docs/api.html.in | 224 ++++++++++++++++++++++++++++++++++-------- docs/errors.html.in | 4 +- docs/formatdomain.html.in | 15 ++- docs/formatdomaincaps.html.in | 17 ++-- docs/hvsupport.pl | 79 ++++++++++----- docs/java.html.in | 6 +- docs/page.xsl | 5 - docs/python.html.in | 8 +- docs/uri.html.in | 12 ++- 11 files changed, 278 insertions(+), 98 deletions(-) diff --git a/docs/Makefile.am b/docs/Makefile.am index 5485ee9..684687d 100644 --- a/docs/Makefile.am +++ b/docs/Makefile.am @@ -1,6 +1,6 @@ ## Process this file with automake to produce Makefile.in -## Copyright (C) 2005-2013 Red Hat, Inc. +## Copyright (C) 2005-2014 Red Hat, Inc. ## ## This library is free software; you can redistribute it and/or ## modify it under the terms of the GNU Lesser General Public @@ -195,7 +195,7 @@ todo: hvsupport.html:: $(srcdir)/hvsupport.html.in -$(srcdir)/hvsupport.html.in: $(srcdir)/hvsupport.pl \ +$(srcdir)/hvsupport.html.in: $(srcdir)/hvsupport.pl $(api_DATA) \ $(srcdir)/../src/libvirt_public.syms \ $(srcdir)/../src/libvirt_qemu.syms $(srcdir)/../src/libvirt_lxc.syms \ $(srcdir)/../src/driver.h diff --git a/docs/acl.html.in b/docs/acl.html.in index 2d228e2..6d280c1 100644 --- a/docs/acl.html.in +++ b/docs/acl.html.in @@ -90,7 +90,7 @@ types in its API. Each object type, in turn, has a set of permissions defined. To determine what permissions are checked for specific API call, consult the - <a href="html/libvirt-libvirt.html">API reference manual</a> + <a href="html/index.html">API reference manual</a> documentation for the API in question. diff --git a/docs/api.html.in b/docs/api.html.in index 68ffa0b..5c64db1 100644 --- a/docs/api.html.in +++ b/docs/api.html.in @@ -16,7 +16,7 @@ manipulated through the API is the <code>virConnectPtr</code>, which represents the connection to a hypervisor. Any application using libvirt is likely to start using the - API by calling one of <a href="html/libvirt-libvirt.html#virConnectOpen" + API by calling one of <a href="html/libvirt-libvirt-host.html#virConnectOpen" >the virConnectOpen functions</a>. You will note that those functions take a name argument which is actually a <a href="uri.html">connection URI</a> to select the right hypervisor to open. @@ -26,7 +26,10 @@ name will default to a preselected hypervisor, but it's probably not a wise thing to do in most cases. See the <a href="uri.html">connection URI</a> page for a full descriptions of the values allowed. - Once the application obtains a <code class='docref'>virConnectPtr</code> + OnDevice the application obtains a + <a href="/html/libvirt-libvirt-host.html#virConnectPtr"> + <code>virConnectPtr</code> + </a> connection to the hypervisor it can then use it to manage the hypervisor's available domains and related virtualization resources, such as storage and networking. All those are @@ -38,33 +41,61 @@ The figure above shows the five main objects exported by the API: <ul> - <li><code class='docref'>virConnectPtr</code> + <li> + <a href="html/libvirt-libvirt-host.html#virConnectPtr"> + <code>virConnectPtr</code> + </a> Represents the connection to a hypervisor. Use one of the - <a href="html/libvirt-libvirt.html#virConnectOpen">virConnectOpen</a> + <a href="html/libvirt-libvirt-host.html#virConnectOpen">virConnectOpen</a> functions to obtain connection to the hypervisor which is then used as a parameter to other connection API's.</li> - <li><code class='docref'>virDomainPtr</code> + <li> + <a href="html/libvirt-libvirt-domain.html#virDomainPtr"> + <code>virDomainPtr</code> + </a> Represents one domain either active or defined (i.e. existing as permanent config file and storage but not currently running on that - node). The function <code class='docref'>virConnectListAllDomains</code> + node). The function + <a href="html/libvirt-libvirt-domain.html#virConnectListAllDomains"> + <code>virConnectListAllDomains</code> + </a> lists all the domains for the hypervisor.</li> - <li><code class='docref'>virNetworkPtr</code> + <li> + <a href="html/libvirt-libvirt-network.html#virNetworkPtr"> + <code>virNetworkPtr</code> + </a> Represents one network either active or defined (i.e. existing as permanent config file and storage but not currently activated). - The function <code class='docref'>virConnectListAllNetworks</code> + The function + <a href="html/libvirt-libvirt-network.html#virConnectListAllNetworks"> + <code>virConnectListAllNetworks</code> + </a> lists all the virtualization networks for the hypervisor.</li> - <li><code class='docref'>virStorageVolPtr</code> + <li> + <a href="html/libvirt-libvirt-storage.html#virStorageVolPtr"> + <code>virStorageVolPtr</code> + </a> Represents one storage volume generally used as a block device available to one of the domains. The function - <code class="docref">virStorageVolLookupByPath</code> finds - the storage volume object based on its path on the node.</li> - <li><code class='docref'>virStoragePoolPtr</code> + <a href="html/libvirt-libvirt-storage.html#virStorageVolLookupByPath"> + <code>virStorageVolLookupByPath</code> + </a> + finds the storage volume object based on its path on the node.</li> + <li> + <a href="html/libvirt-libvirt-storage.html#virStoragePoolPtr"> + <code>virStoragePoolPtr</code> + </a> Represents a storage pool, which is a logical area used to allocate and store storage volumes. The function - <code class='docref'>virConnectListAllStoragePools</code> lists - all of the virtualization storage pools on the hypervisor. The function - <code class="docref">virStoragePoolLookupByVolume</code> finds - the storage pool containing a given storage volume.</li> + <a href="html/libvirt-libvirt-storage.html#virConnectListAllStoragePools"> + <code>virConnectListAllStoragePools</code> + </a> + lists all of the virtualization storage pools on the hypervisor. + The function + <a href="html/libvirt-libvirt-storage.html#virStoragePoolLookupByVolume"> + <code>virStoragePoolLookupByVolume</code> + </a> + finds the storage pool containing a given storage volume.</li> </ul> Most objects manipulated by the library can also be represented using XML descriptions. This is used primarily to create those object, but is @@ -101,42 +132,114 @@ Used to perform lookups on objects by some type of identifier, such as: <ul> - <li><code class='docref'>virDomainLookupByID</code></li> - <li><code class='docref'>virDomainLookupByName</code></li> - <li><code class='docref'>virDomainLookupByUUID</code></li> - <li><code class='docref'>virDomainLookupByUUIDString</code></li> + <li> + <a href="html/libvirt-libvirt-domain.html#virDomainLookupByID"> + <code>virDomainLookupByID</code> + </a> + </li> + <li> + <a href="html/libvirt-libvirt-domain.html#virDomainLookupByName"> + <code>virDomainLookupByName</code> + </a> + </li> + <li> + <a href="html/libvirt-libvirt-domain.html#virDomainLookupByUUID"> + <code>virDomainLookupByUUID</code> + </a> + </li> + <li> + <a href="html/libvirt-libvirt-domain.html#virDomainLookupByUUIDString"> + <code>virDomainLookupByUUIDString</code> + </a> + </li> </ul> </li> <li>Enumeration [virConnectList..., virConnectNumOf...] Used to enumerate a set of object available to an given hypervisor connection such as: <ul> - <li><code class='docref'>virConnectListDomains</code></li> - <li><code class='docref'>virConnectNumOfDomains</code></li> - <li><code class='docref'>virConnectListNetworks</code></li> - <li><code class='docref'>virConnectListStoragePools</code></li> + <li> + <a href="html/libvirt-libvirt-domain.html#virConnectListDomains"> + <code>virConnectListDomains</code> + </a> + </li> + <li> + <a href="html/libvirt-libvirt-domain.html#virConnectNumOfDomains"> + <code>virConnectNumOfDomains</code> + </a> + </li> + <li> + <a href="html/libvirt-libvirt-network.html#virConnectListNetworks"> + <code>virConnectListNetworks</code> + </a> + </li> + <li> + <a href="html/libvirt-libvirt-storage.html#virConnectListStoragePools"> + <code>virConnectListStoragePools</code> + </a> + </li> </ul> </li> <li>Description [...GetInfo] Generic accessor providing a set of generic information about an object, such as: <ul> - <li><code class='docref'>virNodeGetInfo</code></li> - <li><code class='docref'>virDomainGetInfo</code></li> - <li><code class='docref'>virStoragePoolGetInfo</code></li> - <li><code class='docref'>virStorageVolGetInfo</code></li> + <li> + <a href="html/libvirt-libvirt-host.html#virNodeGetInfo"> + <code>virNodeGetInfo</code> + </a> + </li> + <li> + <a href="html/libvirt-libvirt-domain.html#virDomainGetInfo"> + <code>virDomainGetInfo</code> + </a> + </li> + <li> + <a href="html/libvirt-libvirt-storage.html#virStoragePoolGetInfo"> + <code>virStoragePoolGetInfo</code> + </a> + </li> + <li> + <a href="html/libvirt-libvirt-storage.html#virStorageVolGetInfo"> + <code>virStorageVolGetInfo</code> + </a> + </li> </ul> </li> <li>Accessors [...Get..., ...Set...] Specific accessors used to query or modify data for the given object, such as: <ul> - <li><code class='docref'>virConnectGetType</code></li> - <li><code class='docref'>virDomainGetMaxMemory</code></li> - <li><code class='docref'>virDomainSetMemory</code></li> - <li><code class='docref'>virDomainGetVcpus</code></li> - <li><code class='docref'>virStoragePoolSetAutostart</code></li> - <li><code class='docref'>virNetworkGetBridgeName</code></li> + <li> + <a href="html/libvirt-libvirt-host.html#virConnectGetType"> + <code>virConnectGetType</code> + </a> + </li> + <li> + <a href="html/libvirt-libvirt-domain.html#virDomainGetMaxMemory"> + <code>virDomainGetMaxMemory</code> + </a> + </li> + <li> + <a href="html/libvirt-libvirt-domain.html#virDomainSetMemory"> + <code>virDomainSetMemory</code> + </a> + </li> + <li> + <a href="html/libvirt-libvirt-domain.html#virDomainGetVcpus"> + <code>virDomainGetVcpus</code> + </a> + </li> + <li> + <a href="html/libvirt-libvirt-storage.html#virStoragePoolSetAutostart"> + <code>virStoragePoolSetAutostart</code> + </a> + </li> + <li> + <a href="html/libvirt-libvirt-network.html#virNetworkGetBridgeName"> + <code>virNetworkGetBridgeName</code> + </a> + </li> </ul> </li> <li>Creation [...Create, ...CreateXML] @@ -144,18 +247,46 @@ the object based on an XML description, while the ...Create APIs will create the object based on existing object pointer, such as: <ul> - <li><code class='docref'>virDomainCreate</code></li> - <li><code class='docref'>virDomainCreateXML</code></li> - <li><code class='docref'>virNetworkCreate</code></li> - <li><code class='docref'>virNetworkCreateXML</code></li> + <li> + <a href="html/libvirt-libvirt-domain.html#virDomainCreate"> + <code>virDomainCreate</code> + </a> + </li> + <li> + <a href="html/libvirt-libvirt-domain.html#virDomainCreateXML"> + <code>virDomainCreateXML</code> + </a> + </li> + <li> + <a href="html/libvirt-libvirt-network.html#virNetworkCreate"> + <code>virNetworkCreate</code> + </a> + </li> + <li> + <a href="html/libvirt-libvirt-network.html#virNetworkCreateXML"> + <code>virNetworkCreateXML</code> + </a> + </li> </ul> </li> <li>Destruction [...Destroy] Used to shutdown or deactivate and destroy objects, such as: <ul> - <li><code class='docref'>virDomainDestroy</code></li> - <li><code class='docref'>virNetworkDestroy</code></li> - <li><code class='docref'>virStoragePoolDestroy</code></li> + <li> + <a href="html/libvirt-libvirt-domain.html#virDomainDestroy"> + <code>virDomainDestroy</code> + </a> + </li> + <li> + <a href="html/libvirt-libvirt-network.html#virNetworkDestroy"> + <code>virNetworkDestroy</code> + </a> + </li> + <li> + <a href="html/libvirt-libvirt-storage.html#virStoragePoolDestroy"> + <code>virStoragePoolDestroy</code> + </a> + </li> </ul> </li> </ul> @@ -170,7 +301,11 @@ Drivers are the basic building block for libvirt functionality to support the capability to handle specific hypervisor driver calls. Drivers are discovered and registered during connection processing as - part of the <code class='docref'>virInitialize</code> API. Each driver + part of the + <a href="html/libvirt-libvirt-host.html#virInitialize"> + <code>virInitialize</code> + </a> + API. Each driver has a registration API which loads up the driver specific function references for the libvirt APIs to call. The following is a simplistic view of the hypervisor driver mechanism. Consider the stacked list of @@ -199,7 +334,10 @@ The libvirtd daemon service is started on the host at system boot time and can also be restarted at any time by a properly privileged user, such as root. The libvirtd daemon uses the same libvirt API - <code class='docref'>virInitialize</code> sequence as applications + <a href="html/libvirt-libvirt-host.html#virInitialize"> + <code>virInitialize</code> + </a> + sequence as applications for client-side driver registrations, but then extends the registered driver list to encompass all known drivers supported for all driver types supported on the host. diff --git a/docs/errors.html.in b/docs/errors.html.in index df9aa7c..668d280 100644 --- a/docs/errors.html.in +++ b/docs/errors.html.in @@ -46,9 +46,9 @@ following fields: <li>level: the error level, usually VIR_ERR_ERROR, though there is room for warnings like VIR_ERR_WARNING</li> <li>message: the full human-readable formatted string of the error</li> - <li>conn: if available a pointer to the <a href="html/libvirt-libvirt.html#virConnectPtr">virConnectPtr</a> + <li>conn: if available a pointer to the <a href="html/libvirt-libvirt-host.html#virConnectPtr">virConnectPtr</a> connection to the hypervisor where this happened</li> - <li>dom: if available a pointer to the <a href="html/libvirt-libvirt.html#virDomainPtr">virDomainPtr</a> domain + <li>dom: if available a pointer to the <a href="html/libvirt-libvirt-domain.html#virDomainPtr">virDomainPtr</a> domain targeted in the operation</li> </ul> and then extra raw information about the error which may be initialized diff --git a/docs/formatdomain.html.in b/docs/formatdomain.html.in index d05912e..8fcbd29 100644 --- a/docs/formatdomain.html.in +++ b/docs/formatdomain.html.in @@ -190,7 +190,7 @@ "emulate" (let the hypervisor generate all values), "host" (copy all of Block 0 and Block 1, except for the UUID, from the host's SMBIOS values; - the <a href="html/libvirt-libvirt.html#virConnectGetSysinfo"> + the <a href="html/libvirt-libvirt-host.html#virConnectGetSysinfo"> <code>virConnectGetSysinfo</code></a> call can be used to see what values are copied), or "sysinfo" (use the values in the <a href="#elementsSysinfo">sysinfo</a> element). If not @@ -1196,9 +1196,16 @@ It is sometimes necessary to override the default actions taken on various events. Not all hypervisors support all events and actions. The actions may be taken as a result of calls to libvirt APIs - <code class='docref'>virDomainReboot</code>, - <code class='docref'>virDomainShutdown</code>, or - <code class='docref'>virDomainShutdownFlags</code>. + <a href="html/libvirt-libvirt-domain.html#virDomainReboot"> + <code>virDomainReboot</code> + </a>, + <a href="html/libvirt-libvirt-domain.html#virDomainShutdown"> + <code>virDomainShutdown</code> + </a>, + or + <a href="html/libvirt-libvirt-domain.html#virDomainShutdownFlags"> + <code>virDomainShutdownFlags</code> + </a>. Using <code>virsh reboot</code> or <code>virsh shutdown</code> would also trigger the event. diff --git a/docs/formatdomaincaps.html.in b/docs/formatdomaincaps.html.in index 6959dfe..7beb5a4 100644 --- a/docs/formatdomaincaps.html.in +++ b/docs/formatdomaincaps.html.in @@ -16,11 +16,14 @@ then it needs to be more recent to support VFIO, while legacy KVM is achievable just fine with older qemus. - The main difference between <code - class="docref">virConnectGetCapabilities</code> and the emulator - capabilities API is, the former one aims more on the host capabilities - (e.g. NUMA topology, security models in effect, etc.) while the latter one - specializes on the hypervisor capabilities. + The main difference between + <a href="/html/libvirt-libvirt-host.html#virConnectGetCapabilities"> + <code>virConnectGetCapabilities</code> + </a> + and the emulator capabilities API is, the former one aims more on + the host capabilities (e.g. NUMA topology, security models in + effect, etc.) while the latter one specializes on the hypervisor + capabilities. While the <a href="formatcaps.html">Driver Capabilities</a> provides the host capabilities (e.g NUMA topology, security models in effect, etc.), the @@ -41,7 +44,9 @@ 1.2.7): <pre> - <code class="docref">virConnectGetDomainCapabilities</code> + <a href="/html/libvirt-libvirt-domain.html#virConnectGetDomainCapabilities"> + <code>virConnectGetDomainCapabilities</code> + </a> </pre> The root element that emulator capability XML document starts with has diff --git a/docs/hvsupport.pl b/docs/hvsupport.pl index 6bbd44a..44a30ce 100755 --- a/docs/hvsupport.pl +++ b/docs/hvsupport.pl @@ -4,6 +4,8 @@ use strict; use warnings; use File::Find; +use XML::XPath; +use XML::XPath::XMLParser; die "syntax: $0 SRCDIR\n" unless int(@ARGV) == 1; @@ -52,6 +54,7 @@ open FILE, "<$symslibvirt" my $vers; my $prevvers; +my $apixpath = XML::XPath->new(filename => "$srcdir/../docs/libvirt-api.xml"); while (defined($line = <FILE>)) { chomp $line; next if $line =~ /^\s*#/; @@ -75,7 +78,10 @@ while (defined($line = <FILE>)) { $prevvers = $vers; $vers = undef; } elsif ($line =~ /\s*(\w+)\s*;\s*$/) { - $apis{$1} = $vers; + my $file = $apixpath->find("/api/symbols/function[\@name='$1']/\@file"); + $apis{$1} = {}; + $apis{$1}->{vers} = $vers; + $apis{$1}->{file} = $file; } else { die "unexpected data $line\n"; } @@ -91,6 +97,7 @@ open FILE, "<$symsqemu" $prevvers = undef; $vers = undef; +$apixpath = XML::XPath->new(filename => "$srcdir/../docs/libvirt-qemu-api.xml"); while (defined($line = <FILE>)) { chomp $line; next if $line =~ /^\s*#/; @@ -114,7 +121,10 @@ while (defined($line = <FILE>)) { $prevvers = $vers; $vers = undef; } elsif ($line =~ /\s*(\w+)\s*;\s*$/) { - $apis{$1} = $vers; + my $file = $apixpath->find("/api/symbols/function[\@name='$1']/\@file"); + $apis{$1} = {}; + $apis{$1}->{vers} = $vers; + $apis{$1}->{file} = $file; } else { die "unexpected data $line\n"; } @@ -130,6 +140,7 @@ open FILE, "<$symslxc" $prevvers = undef; $vers = undef; +$apixpath = XML::XPath->new(filename => "$srcdir/../docs/libvirt-lxc-api.xml"); while (defined($line = <FILE>)) { chomp $line; next if $line =~ /^\s*#/; @@ -153,7 +164,10 @@ while (defined($line = <FILE>)) { $prevvers = $vers; $vers = undef; } elsif ($line =~ /\s*(\w+)\s*;\s*$/) { - $apis{$1} = $vers; + my $file = $apixpath->find("/api/symbols/function[\@name='$1']/\@file"); + $apis{$1} = {}; + $apis{$1}->{vers} = $vers; + $apis{$1}->{file} = $file; } else { die "unexpected data $line\n"; } @@ -164,27 +178,27 @@ close FILE; # Some special things which aren't public APIs, # but we want to report -$apis{virConnectSupportsFeature} = "0.3.2"; -$apis{virDomainMigratePrepare} = "0.3.2"; -$apis{virDomainMigratePerform} = "0.3.2"; -$apis{virDomainMigrateFinish} = "0.3.2"; -$apis{virDomainMigratePrepare2} = "0.5.0"; -$apis{virDomainMigrateFinish2} = "0.5.0"; -$apis{virDomainMigratePrepareTunnel} = "0.7.2"; - -$apis{virDomainMigrateBegin3} = "0.9.2"; -$apis{virDomainMigratePrepare3} = "0.9.2"; -$apis{virDomainMigratePrepareTunnel3} = "0.9.2"; -$apis{virDomainMigratePerform3} = "0.9.2"; -$apis{virDomainMigrateFinish3} = "0.9.2"; -$apis{virDomainMigrateConfirm3} = "0.9.2"; - -$apis{virDomainMigrateBegin3Params} = "1.1.0"; -$apis{virDomainMigratePrepare3Params} = "1.1.0"; -$apis{virDomainMigratePrepareTunnel3Params} = "1.1.0"; -$apis{virDomainMigratePerform3Params} = "1.1.0"; -$apis{virDomainMigrateFinish3Params} = "1.1.0"; -$apis{virDomainMigrateConfirm3Params} = "1.1.0"; +$apis{virConnectSupportsFeature}->{vers} = "0.3.2"; +$apis{virDomainMigratePrepare}->{vers} = "0.3.2"; +$apis{virDomainMigratePerform}->{vers} = "0.3.2"; +$apis{virDomainMigrateFinish}->{vers} = "0.3.2"; +$apis{virDomainMigratePrepare2}->{vers} = "0.5.0"; +$apis{virDomainMigrateFinish2}->{vers} = "0.5.0"; +$apis{virDomainMigratePrepareTunnel}->{vers} = "0.7.2"; + +$apis{virDomainMigrateBegin3}->{vers} = "0.9.2"; +$apis{virDomainMigratePrepare3}->{vers} = "0.9.2"; +$apis{virDomainMigratePrepareTunnel3}->{vers} = "0.9.2"; +$apis{virDomainMigratePerform3}->{vers} = "0.9.2"; +$apis{virDomainMigrateFinish3}->{vers} = "0.9.2"; +$apis{virDomainMigrateConfirm3}->{vers} = "0.9.2"; + +$apis{virDomainMigrateBegin3Params}->{vers} = "1.1.0"; +$apis{virDomainMigratePrepare3Params}->{vers} = "1.1.0"; +$apis{virDomainMigratePrepareTunnel3Params}->{vers} = "1.1.0"; +$apis{virDomainMigratePerform3Params}->{vers} = "1.1.0"; +$apis{virDomainMigrateFinish3Params}->{vers} = "1.1.0"; +$apis{virDomainMigrateConfirm3Params}->{vers} = "1.1.0"; @@ -406,10 +420,23 @@ EOF $groups{$grp}->{apis}->{$b} } keys %{$groups{$grp}->{apis}}) { my $api = $groups{$grp}->{apis}->{$field}; - my $vers = $apis{$api}; + my $vers = $apis{$api}->{vers}; + my $htmlgrp = $apis{$api}->{file}; print <<EOF; <tr> -<td><a href=\"html/libvirt-libvirt.html#$api\">$api</a></td> +<td> +EOF + + if (defined $htmlgrp) { + print <<EOF; +<a href=\"html/libvirt-$htmlgrp.html#$api\">$api</a> +EOF + + } else { + print $api; + } + print <<EOF; +</td> <td>$vers</td> EOF diff --git a/docs/java.html.in b/docs/java.html.in index daa7b76..659c0b9 100644 --- a/docs/java.html.in +++ b/docs/java.html.in @@ -98,18 +98,18 @@ the code you can build the code with The bindings are articulated around a few classes in the <code>org/libvirt</code> package, notably the <code>Connect</code>, <code>Domain</code> and <code>Network</code> -ones. Functions in the <a href="html/libvirt-libvirt.html">C API</a> +ones. Functions in the <a href="html/index.html">C API</a> taking <code>virConnectPtr</code>, <code>virDomainPtr</code> or <code>virNetworkPtr</code> as their first argument usually become methods for the classes, their name is just stripped from the virConnect or virDomain(Get) prefix and the first letter gets converted to lower case, for example the C functions: - <code>int <a href="html/libvirt-libvirt.html#virConnectNumOfDomains">virConnectNumOfDomains</a> + <code>int <a href="html/libvirt-libvirt-domain.html#virConnectNumOfDomains">virConnectNumOfDomains</a> (virConnectPtr conn);</code> - <code>int <a href="html/libvirt-libvirt.html#virDomainSetMaxMemory">virDomainSetMaxMemory</a> + <code>int <a href="html/libvirt-libvirt-domain.html#virDomainSetMaxMemory">virDomainSetMaxMemory</a> (virDomainPtr domain, unsigned long memory);</code> become diff --git a/docs/page.xsl b/docs/page.xsl index 7de238e..80164dd 100644 --- a/docs/page.xsl +++ b/docs/page.xsl @@ -10,11 +10,6 @@  <xsl:variable name="sitemap" select="document('sitemap.html.in')/html:html/html:body/html:div[@id='sitemap']"/> - <xsl:template match="html:code[@class='docref']" mode="content"> - <xsl:variable name="name"><xsl:value-of select="."/></xsl:variable> - <a href="html/libvirt-libvirt.html#{$name}"><code><xsl:value-of select="$name"/></code></a> - </xsl:template> - <xsl:template match="node() | @*" mode="content"> <xsl:copy> <xsl:apply-templates select="node() | @*" mode="content"/> diff --git a/docs/python.html.in b/docs/python.html.in index 3033337..36517fe 100644 --- a/docs/python.html.in +++ b/docs/python.html.in @@ -12,11 +12,11 @@ becomes methods for the classes, their name is just stripped from the virConnect or virDomain(Get) prefix and the first letter gets converted to lower case, for example the C functions: - <code>int <a href="html/libvirt-libvirt.html#virConnectNumOfDomains">virConnectNumOfDomains</a> + <code>int <a href="html/libvirt-libvirt-domain.html#virConnectNumOfDomains">virConnectNumOfDomains</a> (virConnectPtr conn);</code> - <code>int <a href="html/libvirt-libvirt.html#virDomainSetMaxMemory">virDomainSetMaxMemory</a> + <code>int <a href="html/libvirt-libvirt-domain.html#virDomainSetMaxMemory">virDomainSetMaxMemory</a> (virDomainPtr domain, unsigned long memory);</code> become @@ -31,10 +31,10 @@ in the file libvirtclass.txt present in the python dir or in the docs.There is a couple of function who don't map directly to their C counterparts due to specificities in their argument conversions: <ul> - <li><code><a href="html/libvirt-libvirt.html#virConnectListDomains">virConnectListDomains</a></code> + <li><code><a href="html/libvirt-libvirt-domain.html#virConnectListDomains">virConnectListDomains</a></code> is replaced by <code>virDomain::listDomainsID(self)</code> which returns a list of the integer ID for the currently running domains</li> - <li><code><a href="html/libvirt-libvirt.html#virDomainGetInfo">virDomainGetInfo</a></code> + <li><code><a href="html/libvirt-libvirt-domain.html#virDomainGetInfo">virDomainGetInfo</a></code> is replaced by <code>virDomain::info()</code> which returns a list of <ol><li>state: one of the state values (virDomainState)</li><li>maxMemory: the maximum memory used by the domain</li><li>memory: the current amount of memory used by the domain</li><li>nbVirtCPU: the number of virtual CPU</li><li>cpuTime: the time used by the domain in nanoseconds</li></ol></li> </ul> diff --git a/docs/uri.html.in b/docs/uri.html.in index 73c3e88..7702ccc 100644 --- a/docs/uri.html.in +++ b/docs/uri.html.in @@ -19,7 +19,15 @@ documents libvirt URIs. <h2><a name="URI_libvirt">Specifying URIs to libvirt</a></h2> -The URI is passed as the <code>name</code> parameter to <a href="html/libvirt-libvirt.html#virConnectOpen"><code>virConnectOpen</code></a> or <a href="html/libvirt-libvirt.html#virConnectOpenReadOnly"><code>virConnectOpenReadOnly</code></a>. For example: + The URI is passed as the <code>name</code> parameter to + <a href="html/libvirt-libvirt-host.html#virConnectOpen"> + <code>virConnectOpen</code> + </a> + or + <a href="html/libvirt-libvirt-host.html#virConnectOpenReadOnly"> + <code>virConnectOpenReadOnly</code> + </a>. + For example: <pre> virConnectPtr conn = virConnectOpenReadOnly ("test:///default"); @@ -291,7 +299,7 @@ Notes: <ol> <li> The HTTP client does not fully support IPv6. </li> <li> Many features do not work as expected across HTTP connections, in - particular, <a href="html/libvirt-libvirt.html#virConnectGetCapabilities">virConnectGetCapabilities</a>. + particular, <a href="html/libvirt-libvirt-host.html#virConnectGetCapabilities">virConnectGetCapabilities</a>. The <a href="remote.html">remote support</a> however does work correctly. </li> <li> XenD's new-style XMLRPC interface is not supported by -- 2.1.3

4 8