## 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
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
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.
</p>
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.
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.</p>
- <p> Once the application obtains a <code class='docref'>virConnectPtr</code>
+ <p> 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
</p>
<p> The figure above shows the five main objects exported by the API:</p>
<ul>
- <li><code class='docref'>virConnectPtr</code>
+ <li>
+ <a href="html/libvirt-libvirt-host.html#virConnectPtr">
+ <code>virConnectPtr</code>
+ </a>
<p>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.</p></li>
- <li><code class='docref'>virDomainPtr</code>
+ <li>
+ <a href="html/libvirt-libvirt-domain.html#virDomainPtr">
+ <code>virDomainPtr</code>
+ </a>
<p>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.</p></li>
- <li><code class='docref'>virNetworkPtr</code>
+ <li>
+ <a href="html/libvirt-libvirt-network.html#virNetworkPtr">
+ <code>virNetworkPtr</code>
+ </a>
<p>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.</p></li>
- <li><code class='docref'>virStorageVolPtr</code>
+ <li>
+ <a href="html/libvirt-libvirt-storage.html#virStorageVolPtr">
+ <code>virStorageVolPtr</code>
+ </a>
<p>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.</p></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.</p></li>
+ <li>
+ <a href="html/libvirt-libvirt-storage.html#virStoragePoolPtr">
+ <code>virStoragePoolPtr</code>
+ </a>
<p>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.</p></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.</p></li>
</ul>
<p> Most objects manipulated by the library can also be represented using
XML descriptions. This is used primarily to create those object, but is
<p>Used to perform lookups on objects by some type of identifier,
such as:</p>
<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><b>Enumeration</b> [virConnectList..., virConnectNumOf...]
<p>Used to enumerate a set of object available to an given
hypervisor connection such as:</p>
<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><b>Description</b> [...GetInfo]
<p>Generic accessor providing a set of generic information about an
object, such as: </p>
<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><b>Accessors</b> [...Get..., ...Set...]
<p>Specific accessors used to query or modify data for the given object,
such as: </p>
<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><b>Creation</b> [...Create, ...CreateXML]
the object based on an XML description, while the ...Create APIs will
create the object based on existing object pointer, such as: </p>
<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><b>Destruction</b> [...Destroy]
<p>Used to shutdown or deactivate and destroy objects, such as: </p>
<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>
<p>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
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. </p>
<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>
<p>and then extra raw information about the error which may be initialized
"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
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.
</p>
then it needs to be more recent to support VFIO, while legacy KVM is
achievable just fine with older qemus.</p>
- <p>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.</p>
+ <p>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.</p>
<p>While the <a href="formatcaps.html">Driver Capabilities</a> provides the
host capabilities (e.g NUMA topology, security models in effect, etc.), the
1.2.7</span>):</p>
<pre>
- <code class="docref">virConnectGetDomainCapabilities</code>
+ <a href="/html/libvirt-libvirt-domain.html#virConnectGetDomainCapabilities">
+ <code>virConnectGetDomainCapabilities</code>
+ </a>
</pre>
<p>The root element that emulator capability XML document starts with has
use warnings;
use File::Find;
+use XML::XPath;
+use XML::XPath::XMLParser;
die "syntax: $0 SRCDIR\n" unless int(@ARGV) == 1;
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*#/;
$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";
}
$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*#/;
$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";
}
$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*#/;
$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";
}
# 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";
$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
<p>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:</p>
<p>
- <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>
</p>
<p>
- <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>
</p>
<p>become</p>
<!-- The sitemap.html.in page contains the master navigation structure -->
<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"/>
virConnect or virDomain(Get) prefix and the first letter gets converted to
lower case, for example the C functions:</p>
<p>
- <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>
</p>
<p>
- <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>
</p>
<p>become</p>
is a couple of function who don't map directly to their C counterparts due to
specificities in their argument conversions:</p>
<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>
<h2><a name="URI_libvirt">Specifying URIs to libvirt</a></h2>
<p>
-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:
</p>
<pre>
virConnectPtr conn = virConnectOpenReadOnly (<b>"test:///default"</b>);
<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
%endif
BuildRequires: git
BuildRequires: perl
+BuildRequires: perl-XML-XPath
BuildRequires: python
%if %{with_systemd}
BuildRequires: systemd-units
projects / libvirt.git / commitdiff