diff --git a/.cvsignore b/.cvsignore index 4efaaf2b81..1cd172b8c6 100644 --- a/.cvsignore +++ b/.cvsignore @@ -1,3 +1,4 @@ +.git Makefile aclocal.m4 autom4te.cache diff --git a/ChangeLog b/ChangeLog index e67433b487..e05acdb34e 100644 --- a/ChangeLog +++ b/ChangeLog @@ -1,3 +1,18 @@ +Thu Mar 15 18:20:03 CET 2007 Daniel Veillard + + * include/libvirt/libvirt.h[.in] include/libvirt/virterror.h + proxy/libvirt_proxy.c qemud/Makefile.am qemud/conf.c qemud/conf.h + qemud/dispatch.c qemud/internal.h qemud/protocol.h + src/driver.h src/internal.h src/libvirt.c src/libvirt_sym.version + src/proxy_internal.c src/proxy_internal.h src/qemu_internal.c + src/test.c src/virsh.c src/virterror.c src/xen_internal.c + src/xen_internal.h src/xend_internal.c src/xm_internal.c + src/xml.h src/xs_internal.c: applied patch from Richard Jones + adding virConnectGetCapabilities(), plus various small little + fixes + * docs/*: fixed the api extractor script and regenerated + + Thu Mar 15 16:21:46 CET 2007 Daniel Veillard * python/generator.py: fix the python binding generation for diff --git a/NEWS b/NEWS index 6a6a9cd928..795786ff15 100644 --- a/NEWS +++ b/NEWS @@ -6,14 +6,14 @@ Releases 0.2.0: Feb 14 2007: - - Various internal cleanups (Mark McLoughlin, Richard Jones, - Daniel Berrange, Karel Zak) - - Bug fixes: avoid a crash in connect (Daniel Berrange), virsh args - parsing (Richard Jones) + - Various internal cleanups (Mark McLoughlin, Richard Jones,Daniel + Berrange, Karel Zak) + - Bug fixes: avoid a crash in connect (Daniel Berrange), virsh + argsparsing (Richard Jones) - Add support for QEmu and KVM virtualization (Daniel Berrange) - Add support for network configuration (Mark McLoughlin) - - Minor improvements: regression testing (Daniel Berrange), - localization string updates + - Minor improvements: regression testing (Daniel Berrange),localization + string updates 0.1.11: Jan 22 2007: @@ -25,12 +25,18 @@ Releases 0.1.10: Dec 20 2006: - more localizations - - bug fixes: VCPU info breakages on xen 3.0.3, xenDaemonListDomains buffer overflow (Daniel Berrange), reference count bug when creating Xen domains (Daniel Berrange). - - improvements: support graphic framebuffer for Xen paravirt (Daniel Berrange), VNC listen IP range support (Daniel Berrange), support for default Xen config files and inactive domains of 3.0.4 (Daniel Berrange). + - bug fixes: VCPU info breakages on xen 3.0.3, xenDaemonListDomains + buffer overflow (Daniel Berrange), reference count bug when creating Xen + domains (Daniel Berrange). + - improvements: support graphic framebuffer for Xen paravirt (Daniel + Berrange), VNC listen IP range support (Daniel Berrange), support for + default Xen config files and inactive domains of 3.0.4 (Daniel + Berrange). 0.1.9: Nov 29 2006: - - python bindings: release interpeter lock when calling C (Daniel Berrange) + - python bindings: release interpeter lock when calling C (Daniel + Berrange) - don't raise HTTP error when looking informations for a domain - some refactoring to use the driver for all entry points - better error reporting (Daniel Berrange) @@ -38,15 +44,20 @@ Releases - provide XML parsing errors - extension of the test framework (Daniel Berrange) - fix the reconnect regression test - - python bindings: Domain instances now link to the Connect to avoid garbage collection and disconnect - - separate the notion of maximum memory and current use at the XML level + - python bindings: Domain instances now link to the Connect to avoid + garbage collection and disconnect + - separate the notion of maximum memory and current use at the XML + level - Fix a memory leak (Daniel Berrange) - add support for shareable drives - - add support for non-bridge style networking configs for guests(Daniel Berrange) + - add support for non-bridge style networking configs for guests(Daniel + Berrange) - python bindings: fix unsigned long marshalling (Daniel Berrange) - - new config APIs virConfNew() and virConfSetValue() to build configs from scratch + - new config APIs virConfNew() and virConfSetValue() to build configs + from scratch - hot plug device support based on Michel Ponceau patch - - added support for inactive domains, new APIs, various associated cleanup (Daniel Berrange) + - added support for inactive domains, new APIs, various associated + cleanup (Daniel Berrange) - special device model for HVM guests (Daniel Berrange) - add API to dump core of domains (but requires a patched xend) - pygrub bootloader informations take over informations @@ -54,72 +65,78 @@ Releases 0.1.8: Oct 16 2006: - - Bug for system with page size != 4k - - vcpu number initialization (Philippe Berthault) - - don't label crashed domains as shut off (Peter Vetere) - - fix virsh man page (Noriko Mizumoto) - - blktapdd support for alternate drivers like blktap (Daniel Berrange) - - memory leak fixes (xend interface and XML parsing) (Daniel Berrange) - - compile fix - - mlock/munlock size fixes (Daniel Berrange) - - improve error reporting + - Bug for system with page size != 4k + - vcpu number initialization (Philippe Berthault) + - don't label crashed domains as shut off (Peter Vetere) + - fix virsh man page (Noriko Mizumoto) + - blktapdd support for alternate drivers like blktap (Daniel + Berrange) + - memory leak fixes (xend interface and XML parsing) (Daniel + Berrange) + - compile fix + - mlock/munlock size fixes (Daniel Berrange) + - improve error reporting 0.1.7: Sep 29 2006: - - fix a memory bug on getting vcpu informations from xend (Daniel Berrange) - - fix another problem in the hypercalls change in Xen changeset - 86d26e6ec89b when getting domain informations (Daniel Berrange) + - fix a memory bug on getting vcpu informations from xend (Daniel + Berrange) + - fix another problem in the hypercalls change in Xen + changeset86d26e6ec89b when getting domain informations (Daniel + Berrange) 0.1.6: Sep 22 2006: - Support for localization of strings using gettext (Daniel Berrange) - - Support for new Xen-3.0.3 cdrom and disk configuration (Daniel Berrange) - - Support for setting VNC port when creating domains with new - xend config files (Daniel Berrange) + - Support for new Xen-3.0.3 cdrom and disk configuration (Daniel + Berrange) + - Support for setting VNC port when creating domains with newxend config + files (Daniel Berrange) - Fix bug when running against xen-3.0.2 hypercalls (Jim Fehlig) - Fix reconnection problem when talking directly to http xend 0.1.5: Sep 5 2006: - Support for new hypercalls change in Xen changeset 86d26e6ec89b - - bug fixes: virParseUUID() was wrong, netwoking for paravirt guestsi - (Daniel Berrange), virsh on non-existent domains (Daniel Berrange), - string cast bug when handling error in python (Pete Vetere), HTTP - 500 xend error code handling (Pete Vetere and Daniel Berrange) - - improvements: test suite for SEXPR <-> XML format conversions (Daniel - Berrange), virsh output regression suite (Daniel Berrange), new environ - variable VIRSH_DEFAULT_CONNECT_URI for the default URI when connecting - (Daniel Berrange), graphical console support for paravirt guests - (Jeremy Katz), parsing of simple Xen config files (with Daniel Berrange), - early work on defined (not running) domains (Daniel Berrange), - virsh output improvement (Daniel Berrange + - bug fixes: virParseUUID() was wrong, netwoking for paravirt + guestsi(Daniel Berrange), virsh on non-existent domains (Daniel + Berrange),string cast bug when handling error in python (Pete Vetere), + HTTP500 xend error code handling (Pete Vetere and Daniel Berrange) + - improvements: test suite for SEXPR <-> XML format conversions + (DanielBerrange), virsh output regression suite (Daniel Berrange), new + environvariable VIRSH_DEFAULT_CONNECT_URI for the default URI when + connecting(Daniel Berrange), graphical console support for paravirt + guests(Jeremy Katz), parsing of simple Xen config files (with Daniel + Berrange),early work on defined (not running) domains (Daniel + Berrange),virsh output improvement (Daniel Berrange 0.1.4: Aug 16 2006: - - bug fixes: spec file fix (Mark McLoughlin), error report problem (with - Hugh Brock), long integer in Python bindings (with Daniel Berrange), XML - generation bug for CDRom (Daniel Berrange), bug whem using number() XPath - function (Mark McLoughlin), fix python detection code, remove duplicate - initialization errors (Daniel Berrange) - - improvements: UUID in XML description (Peter Vetere), proxy code - cleanup, virtual CPU and affinity support + virsh support (Michel - Ponceau, Philippe Berthault, Daniel Berrange), port and tty informations - for console in XML (Daniel Berrange), added XML dump to driver and proxy - support (Daniel Berrange), extention of boot options with support for - floppy and cdrom (Daniel Berrange), features block in XML to report/ask - PAE, ACPI, APIC for HVM domains (Daniel Berrange), fail saide-effect - operations when using read-only connection, large improvements to test - driver (Daniel Berrange) + - bug fixes: spec file fix (Mark McLoughlin), error report problem + (withHugh Brock), long integer in Python bindings (with Daniel Berrange), + XMLgeneration bug for CDRom (Daniel Berrange), bug whem using number() + XPathfunction (Mark McLoughlin), fix python detection code, remove + duplicateinitialization errors (Daniel Berrange) + - improvements: UUID in XML description (Peter Vetere), proxy + codecleanup, virtual CPU and affinity support + virsh support + (MichelPonceau, Philippe Berthault, Daniel Berrange), port and tty + informationsfor console in XML (Daniel Berrange), added XML dump to + driver and proxysupport (Daniel Berrange), extention of boot options with + support forfloppy and cdrom (Daniel Berrange), features block in XML to + report/askPAE, ACPI, APIC for HVM domains (Daniel Berrange), fail + saide-effectoperations when using read-only connection, large + improvements to testdriver (Daniel Berrange) - documentation: spelling (Daniel Berrange), test driver examples. 0.1.3: Jul 11 2006: - - bugfixes: build as non-root, fix xend access when root, handling of - empty XML elements (Mark McLoughlin), XML serialization and parsing fixes - (Mark McLoughlin), allow to create domains without disk (Mark - McLoughlin), - - improvement: xenDaemonLookupByID from O(n^2) to O(n) (Daniel Berrange), - support for fully virtualized guest (Jim Fehlig, DV, Mark McLoughlin) + - bugfixes: build as non-root, fix xend access when root, handling + ofempty XML elements (Mark McLoughlin), XML serialization and parsing + fixes(Mark McLoughlin), allow to create domains without disk + (MarkMcLoughlin), + - improvement: xenDaemonLookupByID from O(n^2) to O(n) (Daniel + Berrange),support for fully virtualized guest (Jim Fehlig, DV, Mark + McLoughlin) - documentation: augmented to cover hvm domains @@ -129,57 +146,57 @@ Releases 0.1.1: Jun 21 2006: - - building fixes: ncurses fallback (Jim Fehlig), VPATH builds (Daniel P. - Berrange) - - driver cleanups: new entry points, cleanup of libvirt.c (with Daniel P. - Berrange) + - building fixes: ncurses fallback (Jim Fehlig), VPATH builds (Daniel + P.Berrange) + - driver cleanups: new entry points, cleanup of libvirt.c (with Daniel + P.Berrange) - Cope with API change introduced in Xen changeset 10277 - new test driver for regression checks (Daniel P. Berrange) - - improvements: added UUID to XML serialization, buffer usage (Karel - Zak), --connect argument to virsh (Daniel P. Berrange), - - bug fixes: uninitialized memory access in error reporting, S-Expr - parsing (Jim Fehlig, Jeremy Katz), virConnectOpen bug, remove a TODO in - xs_internal.c - - documentation: Python examples (David Lutterkort), new Perl binding - URL, man page update (Karel Zak) + - improvements: added UUID to XML serialization, buffer usage (KarelZak), + --connect argument to virsh (Daniel P. Berrange), + - bug fixes: uninitialized memory access in error reporting, + S-Exprparsing (Jim Fehlig, Jeremy Katz), virConnectOpen bug, remove a + TODO inxs_internal.c + - documentation: Python examples (David Lutterkort), new Perl bindingURL, + man page update (Karel Zak) 0.1.0: Apr 10 2006: - - building fixes: --with-xen-distdir option (Ronald Aigner), out of tree - build and pkginfo cflag fix (Daniel Berrange) - - enhancement and fixes of the XML description format (David Lutterkort - and Jim Fehlig) + - building fixes: --with-xen-distdir option (Ronald Aigner), out of + treebuild and pkginfo cflag fix (Daniel Berrange) + - enhancement and fixes of the XML description format (David + Lutterkortand Jim Fehlig) - new APIs: for Node information and Reboot - - internal code cleanup: refactoring internals into a driver model, more - error handling, structure sharing, thread safety and ref counting - - bug fixes: error message (Jim Meyering), error allocation in virsh (Jim - Meyering), virDomainLookupByID (Jim Fehlig), - - documentation: updates on architecture, and format, typo fix (Jim - Meyering) - - bindings: exception handling in examples (Jim Meyering), perl ones out - of tree (Daniel Berrange) - - virsh: more options, create, nodeinfo (Karel Zak), renaming of some - options (Karel Zak), use stderr only for errors (Karel Zak), man page - (Andrew Puch) + - internal code cleanup: refactoring internals into a driver model, + moreerror handling, structure sharing, thread safety and ref counting + - bug fixes: error message (Jim Meyering), error allocation in virsh + (JimMeyering), virDomainLookupByID (Jim Fehlig), + - documentation: updates on architecture, and format, typo fix + (JimMeyering) + - bindings: exception handling in examples (Jim Meyering), perl ones + outof tree (Daniel Berrange) + - virsh: more options, create, nodeinfo (Karel Zak), renaming of + someoptions (Karel Zak), use stderr only for errors (Karel Zak), man + page(Andrew Puch) 0.0.6: Feb 28 2006: - add UUID lookup and extract API - add error handling APIs both synchronous and asynchronous - - added minimal hook for error handling at the python level, improved the - python bindings + - added minimal hook for error handling at the python level, improved + thepython bindings - augment the documentation and tests to cover error handling 0.0.5: Feb 23 2006: - - Added XML description parsing, dependance to libxml2, implemented the - creation API virDomainCreateLinux() + - Added XML description parsing, dependance to libxml2, implemented + thecreation API virDomainCreateLinux() - new APIs to lookup and name domain by UUID - fixed the XML dump when using the Xend access - Fixed a few more problem related to the name change - Adding regression tests in python and examples in C - - web site improvement, extended the documentation to cover the XML - format and Python API + - web site improvement, extended the documentation to cover the XMLformat + and Python API - Added devhelp help for Gnome/Gtk programmers @@ -195,8 +212,8 @@ Releases 0.0.2: Jan 29 2006: - Update of the documentation, web site redesign (Diana Fong) - - integration of HTTP xend RPC based on libxend by Anthony Liquori for - most operations + - integration of HTTP xend RPC based on libxend by Anthony Liquori + formost operations - Adding Save and Restore APIs - extended the virsh command line tool (Karel Zak) - remove xenstore transactions (Anthony Liguori) diff --git a/configure.in b/configure.in index 0529a2503a..3ef27757cc 100644 --- a/configure.in +++ b/configure.in @@ -43,6 +43,8 @@ AC_PATH_PROG(TAR, tar, /bin/tar) AC_PATH_PROG(XMLLINT, xmllint, /usr/bin/xmllint) AC_PATH_PROG(XSLTPROC, xsltproc, /usr/bin/xsltproc) +dnl Availability of various common functions. +AC_CHECK_FUNCS([regexec]) dnl Make sure we have an ANSI compiler AM_C_PROTOTYPES @@ -50,6 +52,8 @@ test "x$U" != "x" && AC_MSG_ERROR(Compiler not ANSI compliant) AM_PROG_LIBTOOL +AM_PROG_CC_C_O + LIBVIRT_COMPILE_WARNINGS(maximum) dnl Specific dir for HTML output ? diff --git a/docs/APIchunk0.html b/docs/APIchunk0.html index 2458c142e9..22b93276dd 100644 --- a/docs/APIchunk0.html +++ b/docs/APIchunk0.html @@ -113,11 +113,17 @@ virDomainGetXMLDesc
virGetLastError
virNetworkGetXMLDesc
-
Provides
virConnectNumOfDefinedDomains
+
Provides
virConnectGetCapabilities
+virConnectGetMaxVcpus
+virConnectNumOfDefinedDomains
virConnectNumOfDefinedNetworks
virConnectNumOfDomains
virConnectNumOfNetworks
+virDomainGetAutostart
+virDomainGetMaxVcpus
virGetVersion
+virNetworkGetAutostart
+virNetworkGetBridgeName

Letter R:

RFC4122
virDomainGetUUIDString
virNetworkGetUUIDString
Read-Only
virConnectGetVersion
@@ -127,11 +133,6 @@ virResetLastError
Resume
virDomainResume
Retrieve
virDomainGetMaxMemory
-
Returns
virConnectGetMaxVcpus
-virDomainGetAutostart
-virDomainGetMaxVcpus
-virNetworkGetAutostart
-virNetworkGetBridgeName

Letter S:

Set
virConnSetErrorFunc
virSetErrorFunc
Shutdown
virDomainShutdown
@@ -147,6 +148,7 @@ VIR_NODEINFO_MAXCPUS
VIR_UNUSE_CPU
VIR_USE_CPU
+VIR_UUID_BUFLEN
VIR_UUID_STRING_BUFLEN
cpumap
virConnectClose
diff --git a/docs/APIchunk1.html b/docs/APIchunk1.html index 539813b57c..fee89cd061 100644 --- a/docs/APIchunk1.html +++ b/docs/APIchunk1.html @@ -34,7 +34,8 @@ virConnectNumOfNetworks
virDomainSuspend
add
virDomainShutdown
-
after
virDomainReboot
+
after
virConnectGetCapabilities
+virDomainReboot
virDomainSave
virDomainShutdown
against
virGetVersion
@@ -137,7 +138,8 @@ virNetworkGetAutostart
virNetworkSetAutostart
bridge
virNetworkGetBridgeName
-
buffer
VIR_UUID_STRING_BUFLEN
+
buffer
VIR_UUID_BUFLEN
+VIR_UUID_STRING_BUFLEN
but
VIR_NODEINFO_MAXCPUS
virConnGetLastError
virDomainDefineXML
@@ -186,6 +188,7 @@
can
virConnectGetVersion
virDomainGetInfo
virDomainPinVcpu
+
capabilities
virConnectGetCapabilities
capacities
virConnectGetVersion
caught
virConnCopyLastError
virConnGetLastError
@@ -200,6 +203,7 @@ virDomainSetMemory
virDomainSetVcpus
clean
virResetError
+
client
virConnectGetCapabilities
closes
virConnectClose
code
_virError
virConnCopyLastError
diff --git a/docs/APIchunk2.html b/docs/APIchunk2.html index 855d07d7b3..8302588608 100644 --- a/docs/APIchunk2.html +++ b/docs/APIchunk2.html @@ -54,7 +54,8 @@ virDomainCreate
down
virDomainDestroy
virNetworkDestroy
-
driver
virGetVersion
+
driver
virConnectGetCapabilities
+virGetVersion
dump
virDomainCoreDump

Letter e:

each
virDomainPinVcpu
element
virConnectGetMaxVcpus
@@ -93,6 +94,7 @@ virConnectNumOfNetworks
virCopyLastError
free
virConnCopyLastError
+virConnectGetCapabilities
virCopyLastError
virDomainGetXMLDesc
virNetworkGetBridgeName
diff --git a/docs/APIchunk3.html b/docs/APIchunk3.html index 77b808ba0a..932f13d931 100644 --- a/docs/APIchunk3.html +++ b/docs/APIchunk3.html @@ -29,6 +29,7 @@
launch
virDomainCreate
least
virDomainPinVcpu
length
VIR_CPU_MAPLEN
+VIR_UUID_BUFLEN
VIR_UUID_STRING_BUFLEN
maplen
level
virConnectGetVersion
@@ -78,6 +79,7 @@ VIR_NODEINFO_MAXCPUS
VIR_UNUSE_CPU
VIR_USE_CPU
+VIR_UUID_BUFLEN
VIR_UUID_STRING_BUFLEN
major
virConnectGetVersion
virGetVersion
@@ -141,6 +143,7 @@ virGetLastError
virInitialize
must
cpumap
+virConnectGetCapabilities
virDomainGetOSType
virDomainGetVcpus
virDomainGetXMLDesc
diff --git a/docs/APIchunk4.html b/docs/APIchunk4.html index cfe07aa3e5..954dacae15 100644 --- a/docs/APIchunk4.html +++ b/docs/APIchunk4.html @@ -19,6 +19,7 @@ virNetworkCreateXML
only
virConnectGetVersion
virDomainGetInfo
+
opaque
virConnectGetCapabilities
operation
virDomainGetOSType
virDomainReboot
option
virDomainShutdown
@@ -84,7 +85,8 @@ virConnectListDefinedNetworks
virErrorFunc
virSetErrorFunc
-
provides
VIR_UUID_STRING_BUFLEN
+
provides
VIR_UUID_BUFLEN
+VIR_UUID_STRING_BUFLEN
providing
LIBVIR_VERSION_NUMBER
public
virDomainGetName
virNetworkGetName
@@ -116,6 +118,7 @@
request
virDomainReboot
virDomainShutdown
required
VIR_CPU_MAPLEN
+VIR_UUID_BUFLEN
VIR_UUID_STRING_BUFLEN
requires
virDomainCreateLinux
virDomainDestroy
@@ -146,12 +149,15 @@ virDomainDestroy
virGetVersion
virNetworkDestroy
-
returned
virDomainCreateLinux
+
returned
virConnectGetCapabilities
+virDomainCreateLinux
+virDomainGetAutostart
virDomainGetVcpus
virDomainGetXMLDesc
virDomainPinVcpu
virGetVersion
virNetworkCreateXML
+virNetworkGetAutostart
virNetworkGetBridgeName
virNetworkGetXMLDesc
returns
VIR_CPU_MAPLEN
@@ -199,9 +205,11 @@ virConnectOpenReadOnly
virDomainDestroy
virDomainFree
+virDomainSetAutostart
virDomainShutdown
virNetworkDestroy
virNetworkFree
+virNetworkSetAutostart
shutdown
virDomainDestroy
virNetworkDestroy
significant
virDomainPinVcpu
@@ -255,6 +263,7 @@ virConnectListDefinedNetworks
string
_virError
_virNodeInfo
+virConnectGetCapabilities
virConnectGetType
virDomainGetName
virDomainGetOSType
@@ -263,7 +272,8 @@ virNetworkGetName
virNetworkGetUUIDString
virNetworkLookupByUUIDString
-
structure
virDomainDestroy
+
structure
virConnectGetCapabilities
+virDomainDestroy
virDomainFree
virDomainGetInfo
virNetworkDestroy
diff --git a/docs/APIfiles.html b/docs/APIfiles.html index c02cc049bc..cd09dda774 100644 --- a/docs/APIfiles.html +++ b/docs/APIfiles.html @@ -35,6 +35,7 @@ _virVcpuInfo
virConnect
virConnectClose
+virConnectGetCapabilities
virConnectGetMaxVcpus
virConnectGetType
virConnectGetVersion
@@ -155,6 +156,7 @@ VIR_ERR_POST_FAILED
VIR_ERR_READ_FAILED
VIR_ERR_SEXPR_SERIAL
+VIR_ERR_SYSTEM_ERROR
VIR_ERR_UNKNOWN_HOST
VIR_ERR_WARNING
VIR_ERR_WRITE_FAILED
diff --git a/docs/APIfunctions.html b/docs/APIfunctions.html index ba0060f21f..e676b5fcde 100644 --- a/docs/APIfunctions.html +++ b/docs/APIfunctions.html @@ -25,6 +25,7 @@ virConnResetLastError
virConnSetErrorFunc
virConnectClose
+virConnectGetCapabilities
virConnectGetMaxVcpus
virConnectGetType
virConnectGetVersion
diff --git a/docs/APIsymbols.html b/docs/APIsymbols.html index c8c7eb78b0..2566ff065f 100644 --- a/docs/APIsymbols.html +++ b/docs/APIsymbols.html @@ -55,6 +55,7 @@ VIR_ERR_POST_FAILED
VIR_ERR_READ_FAILED
VIR_ERR_SEXPR_SERIAL
+VIR_ERR_SYSTEM_ERROR
VIR_ERR_UNKNOWN_HOST
VIR_ERR_WARNING
VIR_ERR_WRITE_FAILED
@@ -93,6 +94,7 @@ virConnSetErrorFunc
virConnect
virConnectClose
+virConnectGetCapabilities
virConnectGetMaxVcpus
virConnectGetType
virConnectGetVersion
diff --git a/docs/FAQ.html b/docs/FAQ.html index f541e975de..dabdfc3305 100644 --- a/docs/FAQ.html +++ b/docs/FAQ.html @@ -5,48 +5,49 @@
  • Compilation
  • Developer corner

    • License(s)

    1. Licensing Terms for libvirt -

      libvirt is released under the GNU Lesser - General Public License, see the file COPYING.LIB in the distribution - for the precise wording. The only library that libvirt depends upon is - the Xen store access library which is also licenced under the LGPL.

      +

      libvirt is released under the GNU + LesserGeneral Public License, see the file COPYING.LIB in the + distributionfor the precise wording. The only library that libvirt + depends upon isthe Xen store access library which is also licenced under + the LGPL.

    2. Can I embed libvirt in a proprietary application ? -

      Yes. The LGPL allows you to embed libvirt into a proprietary - application. It would be graceful to send-back bug fixes and improvements - as patches for possible incorporation in the main development tree. It - will decrease your maintainance costs anyway if you do so.

      +

      Yes. The LGPL allows you to embed libvirt into a + proprietaryapplication. It would be graceful to send-back bug fixes and + improvementsas patches for possible incorporation in the main development + tree. Itwill decrease your maintainance costs anyway if you do so.

      3. -

    Installation

    1. Where can I get libvirt ? +

    Installation

    1. Where can I get libvirt?

      The original distribution comes from ftp://libvirt.org/libvirt/.

      2. -
    2. I can't install the libvirt/libvirt-devel RPM packages due to - failed dependencies -

      The most generic solution is to re-fetch the latest src.rpm , and - rebuild it locally with

      +
    3. I can't install the libvirt/libvirt-devel RPM packages due tofailed + dependencies +

      The most generic solution is to re-fetch the latest src.rpm , + andrebuild it locally with

      rpm --rebuild libvirt-xxx.src.rpm.

      -

      If everything goes well it will generate two binary rpm packages (one - providing the shared libs and virsh, and the other one, the -devel - package, providing includes, static libraries and scripts needed to build - applications with libvirt that you can install locally.

      +

      If everything goes well it will generate two binary rpm packages + (oneproviding the shared libs and virsh, and the other one, the + -develpackage, providing includes, static libraries and scripts needed to + buildapplications with libvirt that you can install locally.

      One can also rebuild the RPMs from a tarball:

      rpmbuild -ta libdir-xxx.tar.gz

      Or from a configured tree with:

      make rpm

    4. Failure to use the API for non-root users -

      Large parts of the API may only be accessible with root priviledges, - however the read only access to the xenstore data doesnot have to be - forbidden to user, at least for monitoring purposes. If "virsh dominfo" - fails to run as an user, change the mode of the xenstore read-only socket - with:

      +

      Large parts of the API may only be accessible with root + priviledges,however the read only access to the xenstore data doesnot + have to beforbidden to user, at least for monitoring purposes. If "virsh + dominfo"fails to run as an user, change the mode of the xenstore + read-only socketwith:

      chmod 666 /var/run/xenstored/socket_ro

      -

      and also make sure that the Xen Daemon is running correctly with local - HTTP server enabled, this is defined in - /etc/xen/xend-config.sxp which need the following line to be - enabled:

      +

      and also make sure that the Xen Daemon is running correctly with + localHTTP server enabled, this is defined + in/etc/xen/xend-config.sxpwhich need the following line to + beenabled:

      (xend-http-server yes)

      -

      If needed restart the xend daemon after making the change with the - following command run as root:

      +

      If needed restart the xend daemon after making the change with + thefollowing command run as root:

      service xend restart

    Compilation

    1. What is the process to compile libvirt ? @@ -58,23 +59,24 @@

      ./configure [possible options]

      make

      make install

      -

      At that point you may have to rerun ldconfig or a similar utility to - update your list of installed shared libs.

      +

      At that point you may have to rerun ldconfig or a similar utility + toupdate your list of installed shared libs.

    2. What other libraries are needed to compile/install libvirt ? -

      Libvirt requires libxenstore, which is usually provided by the xen - packages as well as the public headers to compile against libxenstore.

      +

      Libvirt requires libxenstore, which is usually provided by the + xenpackages as well as the public headers to compile against + libxenstore.

    3. I use the CVS version and there is no configure script -

      The configure script (and other Makefiles) are generated. Use the - autogen.sh script to regenerate the configure script and Makefiles, - like:

      +

      The configure script (and other Makefiles) are generated. Use + theautogen.sh script to regenerate the configure script and + Makefiles,like:

      ./autogen.sh --prefix=/usr --disable-shared

      4. -

    Developer corner

    1. Troubles compiling or linking programs using libvirt -

      To simplify the process of reusing the library, libvirt comes with - pkgconfig support, which can be used directly from autoconf support or - via the pkg-config command line tool, like:

      +

    Developercorner

    1. Troubles compiling or linking programs using libvirt +

      To simplify the process of reusing the library, libvirt comes + withpkgconfig support, which can be used directly from autoconf support + orvia the pkg-config command line tool, like:

      pkg-config libvirt --libs

    main menu

    related links

    Graphics and design by Diana Fong

    diff --git a/docs/apibuild.py b/docs/apibuild.py index e8fc4a1d13..972174242c 100755 --- a/docs/apibuild.py +++ b/docs/apibuild.py @@ -33,6 +33,8 @@ ignored_files = { "xs_internal.c": "internal code", "xm_internal.h": "internal code", "xm_internal.c": "internal code", + "qemu_internal.h": "internal code", + "qemu_internal.c": "internal code", "sexpr.h": "internal includes and defines", "sexpr.c": "internal code", "xml.h": "internal includes and defines", diff --git a/docs/architecture.html b/docs/architecture.html index ac1948411f..7e6814854e 100644 --- a/docs/architecture.html +++ b/docs/architecture.html @@ -1,67 +1,68 @@ -libvirt architecture

    libvirt architecture

    Currently libvirt supports 2 kind of virtualization, and its internal -structure is based on a driver model which simplifies adding new engines:

    Libvirt Xen support

    When running in a Xen environment, programs using libvirt have to execute -in "Domain 0", which is the primary Linux OS loaded on the machine. That OS -kernel provides most if not all of the actual drivers used by the set of -domains. It also runs the Xen Store, a database of informations shared by the -hypervisor, the kernels, the drivers and the xen daemon. Xend. The xen daemon -supervise the control and execution of the sets of domains. The hypervisor, -drivers, kernels and daemons communicate though a shared system bus -implemented in the hypervisor. The figure below tries to provide a view of -this environment:

    The Xen architecture

    The library can be initialized in 2 ways depending on the level of -priviledge of the embedding program. If it runs with root access, -virConnectOpen() can be used, it will use different ways to connect to -the Xen infrastructure:

    • a connection to the Xen Daemon though an HTTP RPC layer
      • +libvirt architecture

      libvirt architecture

      Currently libvirt supports 2 kind of virtualization, and its +internalstructure is based on a driver model which simplifies adding new +engines:

      Libvirt Xen support

      When running in a Xen environment, programs using libvirt have to +executein "Domain 0", which is the primary Linux OS loaded on the machine. +That OSkernel provides most if not all of the actual drivers used by the set +ofdomains. It also runs the Xen Store, a database of informations shared by +thehypervisor, the kernels, the drivers and the xen daemon. Xend. The xen +daemonsupervise the control and execution of the sets of domains. The +hypervisor,drivers, kernels and daemons communicate though a shared system +busimplemented in the hypervisor. The figure below tries to provide a view +ofthis environment:

      The Xen architecture

      The library can be initialized in 2 ways depending on the level +ofpriviledge of the embedding program. If it runs with root +access,virConnectOpen() can be used, it will use different ways to connect +tothe Xen infrastructure:

      • a connection to the Xen Daemon though an HTTP RPC layer
      • a read/write connection to the Xen Store
      • use Xen Hypervisor calls
        • -
      • when used as non-root libvirt connect to a proxy daemon running - as root and providing read-only support
        • -

      The library will usually interact with the Xen daemon for any operation -changing the state of the system, but for performance and accuracy reasons -may talk directly to the hypervisor when gathering state informations at -least when possible (i.e. when the running program using libvirt has root -priviledge access).

      If it runs without root access virConnectOpenReadOnly() should be used to -connect to initialize the library. It will then fork a libvirt_proxy program -running as root and providing read_only access to the API, this is then -only useful for reporting and monitoring.

      Libvirt QEmu and KVM support

      The model for QEmu and KVM is completely similar, basically KVM is -based on QEmu for the process controlling a new domain, only small details -differs between the two. In both case the libvirt API is provided -by a controlling process forked by libvirt in the background and -which launch and control the QEmu or KVM process. That program called -libvirt_qemud talks though a specific protocol to the library, and -connects to the console of the QEmu process in order to control and -report on its status. Libvirt tries to expose all the emulations -models of QEmu, the selection is done when creating the new domain, -by specifying the architecture and machine type targetted.

      The code controlling the QEmu process is available in the -qemud/ subdirectory.

      the driver based architecture

      As the previous section explains, libvirt can communicate using different -channels with the Xen hypervisor, and is also able to use different kind -of hypervisor. To simplify the internal design, code, ease -maintainance and simplify the support of other virtualization engine the -internals have been structured as one core component, the libvirt.c module -acting as a front-end for the library API and a set of hypvisor drivers -defining a common set of routines. That way the Xen Daemon accces, the Xen -Store one, the Hypervisor hypercall are all isolated in separate C modules -implementing at least a subset of the common operations defined by the -drivers present in driver.h. The driver architecture is used to add support -for other virtualization engines and

      • xend_internal: implements the driver functions though the Xen - Daemon.
        • -
      • xs_internal: implements the subset of the driver availble though the - Xen Store.
        • -
      • xen_internal: provide the implementation of the functions possible via - direct Xen hypervisor access.
        • -
      • proxy_internal: provide read-only Xen access via a proxy, the proxy - code is in the proxy/ sub directory.
        • -
      • xm_internal: provide support for Xen defined but not running domains.
        • -
      • qemu_internal: implement the driver functions for QEmu and KVM - virtualization engines. It also uses a qemud/ specific daemon which - interracts with the QEmu process to implement libvirt API.
        • -
      • test: this is a test driver useful for regression tests of the - front-end part of libvirt.
        • -

      Note that a given driver may only implement a subset of those functions, -for example saving a Xen domain state to disk and restoring it is only possible -though the Xen Daemon, in that case the driver entry points are initialized to -NULL.

      main menu

      related links

      Graphics and design by Diana Fong

      +
    • when used as non-root libvirt connect to a proxy daemon runningas root + and providing read-only support
      • +

    The library will usually interact with the Xen daemon for any +operationchanging the state of the system, but for performance and accuracy +reasonsmay talk directly to the hypervisor when gathering state informations +atleast when possible (i.e. when the running program using libvirt has +rootpriviledge access).

    If it runs without root access virConnectOpenReadOnly() should be used +toconnect to initialize the library. It will then fork a libvirt_proxy +programrunning as root and providing read_only access to the API, this is +thenonly useful for reporting and monitoring.

    Libvirt QEmu and KVM support

    The model for QEmu and KVM is completely similar, basically KVM isbased on +QEmu for the process controlling a new domain, only small detailsdiffers +between the two. In both case the libvirt API is providedby a controlling +process forked by libvirt in the background andwhich launch and control the +QEmu or KVM process. That program calledlibvirt_qemud talks though a specific +protocol to the library, andconnects to the console of the QEmu process in +order to control andreport on its status. Libvirt tries to expose all the +emulationsmodels of QEmu, the selection is done when creating the new +domain,by specifying the architecture and machine type targetted.

    The code controlling the QEmu process is available in +theqemud/subdirectory.

    the driver based architecture

    As the previous section explains, libvirt can communicate using +differentchannels with the Xen hypervisor, and is also able to use different +kindof hypervisor. To simplify the internal design, code, easemaintainance +and simplify the support of other virtualization engine theinternals have +been structured as one core component, the libvirt.c moduleacting as a +front-end for the library API and a set of hypvisor driversdefining a common +set of routines. That way the Xen Daemon accces, the XenStore one, the +Hypervisor hypercall are all isolated in separate C modulesimplementing at +least a subset of the common operations defined by thedrivers present in +driver.h. The driver architecture is used to add supportfor other +virtualization engines and

    • xend_internal: implements the driver functions though the + XenDaemon.
      • +
    • xs_internal: implements the subset of the driver availble though theXen + Store.
      • +
    • xen_internal: provide the implementation of the functions possible + viadirect Xen hypervisor access.
      • +
    • proxy_internal: provide read-only Xen access via a proxy, the proxycode + is in the proxy/sub directory.
      • +
    • xm_internal: provide support for Xen defined but not running + domains.
      • +
    • qemu_internal: implement the driver functions for QEmu and + KVMvirtualization engines. It also uses a qemud/ specific daemon + whichinterracts with the QEmu process to implement libvirt API.
      • +
    • test: this is a test driver useful for regression tests of thefront-end + part of libvirt.
      • +

    Note that a given driver may only implement a subset of those +functions,for example saving a Xen domain state to disk and restoring it is +only possiblethough the Xen Daemon, in that case the driver entry points are +initialized toNULL.

    main menu

    related links

    Graphics and design by Diana Fong

    diff --git a/docs/bugs.html b/docs/bugs.html index 1a7a94e5f1..61848666a3 100644 --- a/docs/bugs.html +++ b/docs/bugs.html @@ -1,12 +1,13 @@ -Reporting bugs and getting help

    Reporting bugs and getting help

    There is a mailing-list libvir-list@redhat.com for libvirt, -with an on-line -archive. Please subscribe to this list before posting by visiting the associated Web -page and follow the instructions. Patches with explanations and provided as -attachments are really appreciated and will be discussed on the mailing list. -If possible generate the patches by using cvs diff -u in a CVS checkout.

    We use Red Hat Bugzilla to track bugs to libvirt. If you want to report a -bug, please check the existing open bugs, then if yours isn't a duplicate of -an existing bug, log a new bug. It may be good -to post to the mailing-list -too if the issue looks serious, thanks !

    main menu

    related links

    Graphics and design by Diana Fong

    +Reporting bugs and getting help

    Reporting bugs and getting help

    There is a mailing-list libvir-list@redhat.comfor +libvirt,with an on-linearchive. +Please subscribe to this list before posting by visiting the associated +Webpage and follow the instructions. Patches with explanations and +provided asattachments are really appreciated and will be discussed on the +mailing list.If possible generate the patches by using cvs diff -u in a CVS +checkout.

    We use Red Hat Bugzilla to track bugs to libvirt. If you want to report +abug, please check the +existing open bugs, then if yours isn't a duplicate ofan existing bug, log +a new bug. It may be goodto post to the mailing-listtoo if the issue looks +serious, thanks !

    main menu

    related links

    Graphics and design by Diana Fong

    diff --git a/docs/devhelp/libvirt-libvirt.html b/docs/devhelp/libvirt-libvirt.html index c68f8eba58..828b182079 100644 --- a/docs/devhelp/libvirt-libvirt.html +++ b/docs/devhelp/libvirt-libvirt.html @@ -77,7 +77,7 @@ int virDomainShutdown (virNetworkUndefine (virNetworkPtr network); int virGetVersion (unsigned long * libVer,
    const char * type,
    unsigned long * typeVer); int virConnectListDefinedDomains (virConnectPtr conn,
    char ** const names,
    int maxnames); -int virDomainSetMaxMemory (virDomainPtr domain,
    unsigned long memory); +char * virConnectGetCapabilities (virConnectPtr conn); int virNetworkGetUUID (virNetworkPtr network,
    unsigned char * uuid); virDomainPtr virDomainLookupByName (virConnectPtr conn,
    const char * name); virNetworkPtr virNetworkLookupByUUID (virConnectPtr conn,
    const unsigned char * uuid); @@ -131,6 +131,7 @@ int virDomainDetachDevice (virDomainGetAutostart (virDomainPtr domain,
    int * autostart); int virDomainGetVcpus (virDomainPtr domain,
    virVcpuInfoPtr info,
    int maxinfo,
    unsigned char * cpumaps,
    int maplen); char * virDomainGetXMLDesc (virDomainPtr domain,
    int flags); +int virDomainSetMaxMemory (virDomainPtr domain,
    unsigned long memory); int virConnectGetVersion (virConnectPtr conn,
    unsigned long * hvVer); int virConnectListNetworks (virConnectPtr conn,
    char ** const names,
    int maxnames); virDomainPtr virDomainLookupByID (virConnectPtr conn,
    int id); @@ -176,7 +177,7 @@ int virConnectListNetworks (

    Macro VIR_UUID_BUFLEN

    #define VIR_UUID_BUFLEN;
-

    +

    This macro provides the length of the buffer required for virDomainGetUUID()

    Macro VIR_UUID_STRING_BUFLEN

    #define VIR_UUID_STRING_BUFLEN;
@@ -317,10 +318,14 @@ The content of this structure is not made public by the API.
         
    virConnectClose ()
    int	virConnectClose			(virConnectPtr conn)
    
 
    This function closes the connection to the Hypervisor. This should not be called if further interaction with the Hypervisor are needed especially if there is running domain which need further monitoring by the application.
    
 
    conn:pointer to the hypervisor connection
    Returns:0 in case of success or -1 in case of error.
    
+        
    
+        
    virConnectGetCapabilities ()
    char *	virConnectGetCapabilities	(virConnectPtr conn)
    
+
    Provides capabilities of the hypervisor / driver.
    
+
    conn:pointer to the hypervisor connection
    Returns:NULL in case of error, or a pointer to an opaque virCapabilities structure (virCapabilitiesPtr). The client must free the returned string after use.
    
         
    
         
    virConnectGetMaxVcpus ()
    int	virConnectGetMaxVcpus		(virConnectPtr conn, 
    					 const char * type)
    
-
    
-
    conn:pointer to the hypervisor connection
    type:value of the 'type' attribute in the <domain> element
    Returns:the maximum number of virtual CPUs supported for a guest VM of a specific type. The 'type' parameter here corresponds to the 'type' attribute in the <domain> element of the XML. Returns the maximum of virtual CPU or -1 in case of error.
    
+

    Provides the maximum number of virtual CPUs supported for a guest VM of a specific type. The 'type' parameter here corresponds to the 'type' attribute in the <domain> element of the XML.

    +
    conn:pointer to the hypervisor connection
    type:value of the 'type' attribute in the <domain> element
    Returns:the maximum of virtual CPU or -1 in case of error.

    virConnectGetType ()

    const char *	virConnectGetType	(virConnectPtr conn)

    Get the name of the Hypervisor software used.

    @@ -403,8 +408,8 @@ The content of this structure is not made public by the API.
    domain:a domain object
    Returns:0 in case of success and -1 in case of failure.

    virDomainGetAutostart ()

    int	virDomainGetAutostart		(virDomainPtr domain, 
    					 int * autostart)
    
-

    -

    domain:a domain object
    autostart:
    Returns:a boolean value indicating whether the domain configured to be automatically started when the host machine boots. Returns -1 in case of error, 0 in case of success
    +

    Provides a boolean value indicating whether the domain configured to be automatically started when the host machine boots.

    +
    domain:a domain object
    autostart:the value returned
    Returns:-1 in case of error, 0 in case of success

    virDomainGetID ()

    unsigned int	virDomainGetID		(virDomainPtr domain)

    Get the hypervisor ID number for the domain

    @@ -419,8 +424,8 @@ The content of this structure is not made public by the API.
    domain:a domain object or NULL
    Returns:the memory size in kilobytes or 0 in case of error.

    virDomainGetMaxVcpus ()

    int	virDomainGetMaxVcpus		(virDomainPtr domain)
    
-

    -

    domain:pointer to domain object
    Returns:the maximum number of virtual CPUs supported for the guest VM. If the guest is inactive, this is basically the same as virConnectGetMaxVcpus. If the guest is running this will reflect the maximum number of virtual CPUs the guest was booted with. Returns the maximum of virtual CPU or -1 in case of error.
    +

    Provides the maximum number of virtual CPUs supported for the guest VM. If the guest is inactive, this is basically the same as virConnectGetMaxVcpus. If the guest is running this will reflect the maximum number of virtual CPUs the guest was booted with.

    +
    domain:pointer to domain object
    Returns:the maximum of virtual CPU or -1 in case of error.

    virDomainGetName ()

    const char *	virDomainGetName	(virDomainPtr domain)

    Get the public name for that domain

    @@ -484,7 +489,7 @@ The content of this structure is not made public by the API.

    virDomainSetAutostart ()

    int	virDomainSetAutostart		(virDomainPtr domain, 
    					 int autostart)

    Configure the domain to be automatically started when the host machine boots.

    -
    domain:a domain object
    autostart:
    Returns:-1 in case of error, 0 in case of success
    +
    domain:a domain object
    autostart:whether the domain should be automatically started 0 or 1
    Returns:-1 in case of error, 0 in case of success

    virDomainSetMaxMemory ()

    int	virDomainSetMaxMemory		(virDomainPtr domain, 
    					 unsigned long memory)

    Dynamically change the maximum amount of physical memory allocated to a domain. If domain is NULL, then this change the amount of memory reserved to Domain0 i.e. the domain where the application runs. This function requires priviledged access to the hypervisor.

    @@ -539,12 +544,12 @@ The content of this structure is not made public by the API.
    network:a network object
    Returns:0 in case of success and -1 in case of failure.

    virNetworkGetAutostart ()

    int	virNetworkGetAutostart		(virNetworkPtr network, 
    					 int * autostart)
    
-

    -

    network:a network object
    autostart:
    Returns:a boolean value indicating whether the network configured to be automatically started when the host machine boots. Returns -1 in case of error, 0 in case of success
    +

    Provides a boolean value indicating whether the network configured to be automatically started when the host machine boots.

    +
    network:a network object
    autostart:the value returned
    Returns:-1 in case of error, 0 in case of success

    virNetworkGetBridgeName ()

    char *	virNetworkGetBridgeName		(virNetworkPtr network)
    
-

    -

    network:a network object
    Returns:a bridge interface name to which a domain may connect a network interface in order to join the network. Returns a 0 terminated interface name, or NULL in case of error. the caller must free() the returned value.
    +

    Provides a bridge interface name to which a domain may connect a network interface in order to join the network.

    +
    network:a network object
    Returns:a 0 terminated interface name, or NULL in case of error. the caller must free() the returned value.

    virNetworkGetName ()

    const char *	virNetworkGetName	(virNetworkPtr network)

    Get the public name for that network

    @@ -576,7 +581,7 @@ The content of this structure is not made public by the API.

    virNetworkSetAutostart ()

    int	virNetworkSetAutostart		(virNetworkPtr network, 
    					 int autostart)

    Configure the network to be automatically started when the host machine boots.

    -
    network:a network object
    autostart:
    Returns:-1 in case of error, 0 in case of success
    +
    network:a network object
    autostart:whether the network should be automatically started 0 or 1
    Returns:-1 in case of error, 0 in case of success

    virNetworkUndefine ()

    int	virNetworkUndefine		(virNetworkPtr network)

    Undefine a network but does not stop it if it is running

    diff --git a/docs/devhelp/libvirt-virterror.html b/docs/devhelp/libvirt-virterror.html index 365d9e199d..10806fa373 100644 --- a/docs/devhelp/libvirt-virterror.html +++ b/docs/devhelp/libvirt-virterror.html @@ -142,7 +142,8 @@ void virConnResetLastError (VIR_ERR_WRITE_FAILED = 34 /* failed to write a conf file */ VIR_ERR_XML_DETAIL = 35 /* detail of an XML error */ VIR_ERR_INVALID_NETWORK = 36 /* invalid network object */ - VIR_ERR_NETWORK_EXIST = 37 /* the network already exist */ + VIR_ERR_NETWORK_EXIST = 37 /* the network already exist */ + VIR_ERR_SYSTEM_ERROR = 38 /* general system call failure */ };

    diff --git a/docs/downloads.html b/docs/downloads.html index c92bf51155..0e07081ab9 100644 --- a/docs/downloads.html +++ b/docs/downloads.html @@ -1,10 +1,10 @@ -Downloads

    Downloads

    The latest versions of libvirt can be found on the libvirt.org server ( HTTP, FTP). You will find there the released -versions as well as snapshot -tarballs updated from CVS head every hour

    Anonymous CVS is also -available, first register onto the server:

    cvs -d :pserver:anoncvs@libvirt.org:2401/data/cvs login

    it will request a password, enter anoncvs. Then you can -checkout the development tree with:

    cvs -d :pserver:anoncvs@libvirt.org:2401/data/cvs co -libvirt

    Use ./autogen.sh to configure the local checkout, then make -and make install, as usual. All normal cvs commands are now -available except commiting to the base.

    main menu

    related links

    Graphics and design by Diana Fong

    +Downloads

    Downloads

    The latest versions of libvirt can be found on the libvirt.orgserver ( HTTP, FTP). You will find there the +releasedversions as well as snapshottarballsupdated +from CVS head every hour

    Anonymous CVSis +alsoavailable, first register onto the server:

    cvs -d :pserver:anoncvs@libvirt.org:2401/data/cvs login

    it will request a password, enter anoncvs. Then you +cancheckout the development tree with:

    cvs -d :pserver:anoncvs@libvirt.org:2401/data/cvs +colibvirt

    Use ./autogen.sh to configure the local checkout, then +makeand make install, as usual. All normal cvs +commands are nowavailable except commiting to the base.

    main menu

    related links

    Graphics and design by Diana Fong

    diff --git a/docs/errors.html b/docs/errors.html index a518a1b3ad..2447c3924f 100644 --- a/docs/errors.html +++ b/docs/errors.html @@ -3,67 +3,65 @@ Handling of errors

    Handling of errors

    The main goals of libvirt when it comes to error handling are:

    • provide as much detail as possible
    • provide the informations as soon as possible
    • dont force the library user into one style of error handling
      • -

    As result the library provide both synchronous, callback based and -asynchronous error reporting. When an error happens in the library code the -error is logged, allowing to retrieve it later and if the user registered an -error callback it will be called synchronously. Once the call to libvirt ends -the error can be detected by the return value and the full information for -the last logged error can be retrieved.

    To avoid as much as prossible troubles with a global variable in a -multithreaded environment, libvirt will associate when possible the errors to -the current connection they are related to, that way the error is stored in a -dynamic structure which can be made thread specific. Error callback can be -set specifically to a connection with

    So error handling in the code is the following:

    1. if the error can be associated to a connection for example when failing - to look up a domain -
      1. if there is a callback associated to the connection set with virConnSetErrorFunc, - call it with the error informations
        2. -
      2. otherwise if there is a global callback set with virSetErrorFunc, - call it with the error information
        3. -
      3. otherwise call virDefaultErrorFunc - which is the default error function of the library issuing the error - on stderr
        4. +

        As result the library provide both synchronous, callback based +andasynchronous error reporting. When an error happens in the library code +theerror is logged, allowing to retrieve it later and if the user registered +anerror callback it will be called synchronously. Once the call to libvirt +endsthe error can be detected by the return value and the full information +forthe last logged error can be retrieved.

        To avoid as much as prossible troubles with a global variable in +amultithreaded environment, libvirt will associate when possible the errors +tothe current connection they are related to, that way the error is stored in +adynamic structure which can be made thread specific. Error callback can +beset specifically to a connection with

        So error handling in the code is the following:

        1. if the error can be associated to a connection for example when + failingto look up a domain +
          1. if there is a callback associated to the connection set with virConnSetErrorFunc,call + it with the error informations
            2. +
          2. otherwise if there is a global callback set with virSetErrorFunc,call + it with the error information
            3. +
          3. otherwise call virDefaultErrorFuncwhich + is the default error function of the library issuing the erroron + stderr
          4. save the error in the connection for later retrieval with virConnGetLastError
        2. otherwise like when failing to create an hypervisor connection: -
          1. if there is a global callback set with virSetErrorFunc, - call it with the error information
            2. -
          2. otherwise call virDefaultErrorFunc - which is the default error function of the library issuing the error - on stderr
            3. +
            1. if there is a global callback set with virSetErrorFunc,call + it with the error information
              2. +
            2. otherwise call virDefaultErrorFuncwhich + is the default error function of the library issuing the erroron + stderr
            3. save the error in the connection for later retrieval with virGetLastError
            -

          In all cases the error informations are provided as a virErrorPtr pointer to -read-only structure virError containing the -following fields:

          • code: an error number from the virErrorNumber - enum
            • -
          • domain: an enum indicating which part of libvirt raised the error see - virErrorDomain
            • -
          • level: the error level, usually VIR_ERR_ERROR, though there is room for - warnings like VIR_ERR_WARNING
            • +

        In all cases the error informations are provided as a virErrorPtrpointer +toread-only structure virErrorcontaining +thefollowing fields:

        • code: an error number from the virErrorNumberenum
          • +
        • domain: an enum indicating which part of libvirt raised the error seevirErrorDomain
          • +
        • level: the error level, usually VIR_ERR_ERROR, though there is room + forwarnings like VIR_ERR_WARNING
        • message: the full human-readable formatted string of the error
          • -
        • conn: if available a pointer to the virConnectPtr - connection to the hypervisor where this happened
          • -
        • dom: if available a pointer to the virDomainPtr domain - targetted in the operation
          • -

        and then extra raw informations about the error which may be initialized -to 0 or NULL if unused

        • str1, str2, str3: string informations, usually str1 is the error - message format
          • +
        • conn: if available a pointer to the virConnectPtrconnection + to the hypervisor where this happened
          • +
        • dom: if available a pointer to the virDomainPtrdomaintargetted + in the operation
          • +

        and then extra raw informations about the error which may be initializedto +0 or NULL if unused

        • str1, str2, str3: string informations, usually str1 is the errormessage + format
        • int1, int2: integer informations
          • -

        So usually, setting up specific error handling with libvirt consist of -registering an handler with with virSetErrorFunc or -with virConnSetErrorFunc, -chech the value of the code value, take appropriate action, if needed let -libvirt print the error on stderr by calling virDefaultErrorFunc. -For asynchronous error handing, set such a function doing nothing to avoid -the error being reported on stderr, and call virConnGetLastError or -virGetLastError when an API call returned an error value. It can be a good -idea to use virResetError or virConnResetLastError -once an error has been processed fully.

        At the python level, there only a global reporting callback function at -this point, see the error.py example about it:

        def handler(ctxt, err):
+
        So usually, setting up specific error handling with libvirt consist
+ofregistering an handler with with virSetErrorFuncorwith
+virConnSetErrorFunc,chech
+the value of the code value, take appropriate action, if needed letlibvirt
+print the error on stderr by calling virDefaultErrorFunc.For
+asynchronous error handing, set such a function doing nothing to avoidthe
+error being reported on stderr, and call virConnGetLastError
+orvirGetLastError when an API call returned an error value. It can be a
+goodidea to use virResetErroror virConnResetLastErroronce
+an error has been processed fully.
        At the python level, there only a global reporting callback function
+atthis point, see the error.py example about it:
        def handler(ctxt, err):
     global errno
 
     #print "handler(%s, %s)" % (ctxt, err)
     errno = err
 
-libvirt.registerErrorHandler(handler, 'context') 
        the second argument to the registerErrorHandler function is passed as the
-fist argument of the callback like in the C version. The error is a tuple
-containing the same field as a virError in C, but cast to Python.

    main menu

    related links

    Graphics and design by Diana Fong

    +libvirt.registerErrorHandler(handler, 'context')

    the second argument to the registerErrorHandler function is passed as +thefist argument of the callback like in the C version. The error is a +tuplecontaining the same field as a virError in C, but cast to Python.

    main menu

    related links

    Graphics and design by Diana Fong

    diff --git a/docs/format.html b/docs/format.html index fd18950780..32b89a9544 100644 --- a/docs/format.html +++ b/docs/format.html @@ -1,17 +1,18 @@ -XML Format

    XML Format

    This section describes the XML format used to represent domains, there are -variations on the format based on the kind of domains run and the options -used to launch them:

    The formats try as much as possible to follow the same structure and reuse -elements and attributes where it makes sense.

    Normal paravirtualized Xen -domains:

    The library use an XML format to describe domains, as input to virDomainCreateLinux() -and as the output of virDomainGetXMLDesc(), -the following is an example of the format as returned by the shell command -virsh xmldump fc4 , where fc4 was one of the running domains:

    <domain type='xen' id='18'>
+XML Format
    XML Format
    This section describes the XML format used to represent domains, there
+arevariations on the format based on the kind of domains run and the
+optionsused to launch them:
    The formats try as much as possible to follow the same structure and
+reuseelements and attributes where it makes sense.
    Normal paravirtualized
+Xendomains:
    The library use an XML format to describe domains, as input to virDomainCreateLinux()and
+as the output of virDomainGetXMLDesc(),the
+following is an example of the format as returned by the shell
+commandvirsh xmldump fc4, where fc4 was one of the running
+domains:
    <domain type='xen' id='18'>
   <name>fc4</name>
   <os>
     <type>linux</type>
@@ -34,70 +35,72 @@ the following is an example of the format as returned by the shell command
     </interface>
     <console tty='/dev/pts/5'/>
   </devices>
-</domain>
    The root element must be called domain with no namespace, the
-type attribute indicates the kind of hypervisor used, 'xen' is
-the default value. The id attribute gives the domain id at
-runtime (not however that this may change, for example if the domain is saved
-to disk and restored). The domain has a few children whose order is not
-significant:
    • name: the domain name, preferably ASCII based
      • 
+</domain>

    The root element must be called domainwith no namespace, +thetypeattribute indicates the kind of hypervisor used, 'xen' +isthe default value. The idattribute gives the domain id +atruntime (not however that this may change, for example if the domain is +savedto disk and restored). The domain has a few children whose order is +notsignificant:

    • name: the domain name, preferably ASCII based
    • memory: the maximum memory allocated to the domain in kilobytes
    • vcpu: the number of virtual cpu configured for the domain
      • -
    • os: a block describing the Operating System, its content will be - dependant on the OS type +
    • os: a block describing the Operating System, its content will + bedependant on the OS type
      • type: indicate the OS type, always linux at this point
      • kernel: path to the kernel on the Domain 0 filesystem
        • -
      • initrd: an optional path for the init ramdisk on the Domain 0 - filesystem
        • +
      • initrd: an optional path for the init ramdisk on the Domain + 0filesystem
      • cmdline: optional command line to the kernel
        • -
      • root: the root filesystem from the guest viewpoint, it may be - passed as part of the cmdline content too
        • +
      • root: the root filesystem from the guest viewpoint, it may bepassed + as part of the cmdline content too
      • -
    • devices: a list of disk, interface and - console descriptions in no special order
      • -

    The format of the devices and their type may grow over time, but the -following should be sufficient for basic use:

    A disk device indicates a block device, it can have two -values for the type attribute either 'file' or 'block' corresponding to the 2 -options availble at the Xen layer. It has two mandatory children, and one -optional one in no specific order:

    • source with a file attribute containing the path in Domain 0 to the - file or a dev attribute if using a block device, containing the device - name ('hda5' or '/dev/hda5')
      • -
    • target indicates in a dev attribute the device where it is mapped in - the guest
      • -
    • readonly an optional empty element indicating the device is - read-only
      • -

    An interface element describes a network device mapped on the -guest, it also has a type whose value is currently 'bridge', it also have a -number of children in no specific order:

    • source: indicating the bridge name
      • +
    • devices: a list of disk, + interfaceandconsoledescriptions in no special + order
      • +

    The format of the devices and their type may grow over time, but +thefollowing should be sufficient for basic use:

    A diskdevice indicates a block device, it can have twovalues +for the type attribute either 'file' or 'block' corresponding to the 2options +availble at the Xen layer. It has two mandatory children, and oneoptional one +in no specific order:

    • source with a file attribute containing the path in Domain 0 to thefile + or a dev attribute if using a block device, containing the devicename + ('hda5' or '/dev/hda5')
      • +
    • target indicates in a dev attribute the device where it is mapped inthe + guest
      • +
    • readonly an optional empty element indicating the device + isread-only
      • +

    An interfaceelement describes a network device mapped on +theguest, it also has a type whose value is currently 'bridge', it also have +anumber of children in no specific order:

    • source: indicating the bridge name
    • mac: the optional mac address provided in the address attribute
    • ip: the optional IP address provided in the address attribute
    • script: the script used to bridge the interfcae in the Domain 0
    • target: and optional target indicating the device name.
      • -

    A console element describes a serial console connection to -the guest. It has no children, and a single attribute tty which -provides the path to the Pseudo TTY on which the guest console can be -accessed

    Life cycle actions for the domain can also be expressed in the XML format, -they drive what should be happening if the domain crashes, is rebooted or is -poweroff. There is various actions possible when this happen:

    • destroy: The domain is cleaned up (that's the default normal processing - in Xen)
      • -
    • restart: A new domain is started in place of the old one with the same - configuration parameters
      • -
    • preserve: The domain will remain in memory until it is destroyed - manually, it won't be running but allows for post-mortem debugging
      • -
    • rename-restart: a variant of the previous one but where the old domain - is renamed before being saved to allow a restart
      • +

    A consoleelement describes a serial console connection tothe +guest. It has no children, and a single attribute +ttywhichprovides the path to the Pseudo TTY on which the guest +console can beaccessed

    Life cycle actions for the domain can also be expressed in the XML +format,they drive what should be happening if the domain crashes, is rebooted +or ispoweroff. There is various actions possible when this happen:

    • destroy: The domain is cleaned up (that's the default normal + processingin Xen)
      • +
    • restart: A new domain is started in place of the old one with the + sameconfiguration parameters
      • +
    • preserve: The domain will remain in memory until it is + destroyedmanually, it won't be running but allows for post-mortem + debugging
      • +
    • rename-restart: a variant of the previous one but where the old + domainis renamed before being saved to allow a restart

    The following could be used for a Xen production system:

    <domain>
   ...
   <on_reboot>restart</on_reboot>
   <on_poweroff>destroy</on_poweroff>
   <on_crash>rename-restart</on_crash>
   ...
-</domain>

    While the format may be extended in various ways as support for more -hypervisor types and features are added, it is expected that this core subset -will remain functional in spite of the evolution of the library.

    Fully virtualized guests -(added in 0.1.3):

    Here is an example of a domain description used to start a fully -virtualized (a.k.a. HVM) Xen domain. This requires hardware virtualization -support at the processor level but allows to run unmodified operating -systems:

    <domain type='xen' id='3'>
+</domain>

    While the format may be extended in various ways as support for +morehypervisor types and features are added, it is expected that this core +subsetwill remain functional in spite of the evolution of the library.

    Fully virtualized +guests(added in 0.1.3):

    Here is an example of a domain description used to start a +fullyvirtualized (a.k.a. HVM) Xen domain. This requires hardware +virtualizationsupport at the processor level but allows to run unmodified +operatingsystems:

    <domain type='xen' id='3'>
   <name>fv0</name>
   <uuid>4dea22b31d52d8f32516782e98ab3fa0</uuid>
   <os>
@@ -137,46 +140,75 @@ systems:
    <domain type='xen' id='3'>
     </disk>
     <graphics type='vnc' port='5904'/>
   </devices>
-</domain>
    There is a few things to notice specifically for HVM domains:
    • the optional <features> block is used to enable
-    certain guest CPU / system features. For HVM guests the following
-    features are defined:
-    
      • pae - enable PAE memory addressing
        • 
-      
      • apic - enable IO APIC
        • 
-      
      • acpi - enable ACPI bios
        • 
+</domain>

    There is a few things to notice specifically for HVM domains:

    • the optional <features>block is used to + enablecertain guest CPU / system features. For HVM guests the + followingfeatures are defined: +
      • pae- enable PAE memory addressing
        • +
      • apic- enable IO APIC
        • +
      • acpi- enable ACPI bios
      • -
    • the <os> block description is very different, first - it indicates that the type is 'hvm' for hardware virtualization, then - instead of a kernel, boot and command line arguments, it points to an os - boot loader which will extract the boot informations from the boot device - specified in a separate boot element. The dev attribute on - the boot tag can be one of: -
      • fd - boot from first floppy device
        • -
      • hd - boot from first harddisk device
        • -
      • cdrom - boot from first cdrom device
        • +
      • the <os>block description is very different, firstit + indicates that the type is 'hvm' for hardware virtualization, theninstead + of a kernel, boot and command line arguments, it points to an osboot + loader which will extract the boot informations from the boot + devicespecified in a separate boot element. The devattribute + onthe boottag can be one of: +
        • fd- boot from first floppy device
          • +
        • hd- boot from first harddisk device
          • +
        • cdrom- boot from first cdrom device
        • -
      • the <devices> section includes an emulator entry - pointing to an additional program in charge of emulating the devices
        • -
      • the disk entry indicates in the dev target section that the emulation - for the drive is the first IDE disk device hda. The list of device names - supported is dependant on the Hypervisor, but for Xen it can be any IDE - device hda-hdd, or a floppy device - fda, fdb. The <disk> element - also supports a 'device' attribute to indicate what kinda of hardware to - emulate. The following values are supported: -
        • floppy - a floppy disk controller
          • -
        • disk - a generic hard drive (the default it - omitted)
          • -
        • cdrom - a CDROM device
          • +
        • the <devices>section includes an emulator + entrypointing to an additional program in charge of emulating the + devices
          • +
        • the disk entry indicates in the dev target section that the + emulationfor the drive is the first IDE disk device hda. The list of + device namessupported is dependant on the Hypervisor, but for Xen it can + be any IDEdevice hda-hdd, or a floppy + devicefda, fdb. The + <disk>elementalso supports a 'device' attribute to + indicate what kinda of hardware toemulate. The following values are + supported: +
          • floppy- a floppy disk controller
            • +
          • disk- a generic hard drive (the default itomitted)
            • +
          • cdrom- a CDROM device
          - For Xen 3.0.2 and earlier a CDROM device can only be emulated on the - hdc channel, while for 3.0.3 and later, it can be emulated - on any IDE channel.
          • -
        • the <devices> section also include at least one - entry for the graphic device used to render the os. Currently there is - just 2 types possible 'vnc' or 'sdl'. If the type is 'vnc', then an - additional port attribute will be present indicating the TCP - port on which the VNC server is accepting client connections.
          • -

        It is likely that the HVM description gets additional optional elements -and attributes as the support for fully virtualized domain expands, -especially for the variety of devices emulated and the graphic support -options offered.

        KVM domain

        QEmu domain

    main menu

    related links

    Graphics and design by Diana Fong

    + For Xen 3.0.2 and earlier a CDROM device can only be emulated on + thehdcchannel, while for 3.0.3 and later, it can be + emulatedon any IDE channel. +
  • the <devices>section also include at least oneentry + for the graphic device used to render the os. Currently there isjust 2 + types possible 'vnc' or 'sdl'. If the type is 'vnc', then anadditional + portattribute will be present indicating the TCPport on + which the VNC server is accepting client connections.
    • +

    It is likely that the HVM description gets additional optional elementsand +attributes as the support for fully virtualized domain expands,especially for +the variety of devices emulated and the graphic supportoptions offered.

    KVM domain (added in 0.2.0)

    Support for the KVM virtualization is provided in recent Linux kernels +(2.6.20 and onward). This requires specific hardware with acceleration +support and the availability of the special version of the QEmu binary. Since this +relies on QEmu for the machine emulation like fully virtualized guests the +XML description is quite similar, here is a simple example:

    <domain type='kvm'>
+  <name>demo2</name>
+  <uuid>4dea24b3-1d52-d8f3-2516-782e98a23fa0</uuid>
+  <memory>131072</memory>
+  <vcpu>1</vcpu>
+  <os>
+    <type>hvm</type>
+  </os>
+  <devices>
+    <emulator>/home/user/usr/kvm-devel/bin/qemu-system-x86_64</emulator>
+    <disk type='file' device='disk'>
+      <source file='/home/user/fedora/diskboot.img'/>
+      <target dev='hda'/>
+    </disk>
+    <interface type='user'>
+      <mac address='24:42:53:21:52:45'/>
+    </interface>
+    <graphics type='vnc' port='-1'/>
+  </devices>
+</domain>

    The specific points to note if using KVM are:

    • the top level domain element carries a type of 'kvm'
      • +
    • the <devices> emulator points to the special qemu binary required + for KVM
      • +
    • networking interface definitions definitions are somewhat different due + to a different model from Xen (@@TODO)
      • +

    except those points the options should be quite similar to Xen HVM +ones.

    QEmu domain (added in 0.2.0)

    main menu

    related links

    Graphics and design by Diana Fong

    diff --git a/docs/index.html b/docs/index.html index cb40b2b7be..95e58ca134 100644 --- a/docs/index.html +++ b/docs/index.html @@ -15,16 +15,15 @@

    what is libvirt?

    -

    Libvirt is a C toolkit to interact with the virtualization capabilities -of recent versions of Linux (and other OSes). It is free software available -under the GNU -Lesser General Public License. Virtualization of the Linux Operating -System means the ability to run multiple instances of Operating Systems -concurently on a single hardware system where the basic resources are driven -by a Linux instance. The library aim at providing long term stable C API -initially for the Xen -paravirtualization but should be able to integrate other virtualization -mechanisms if needed.

    +

    Libvirt is a C toolkit to interact with the virtualization capabilitiesof +recent versions of Linux (and other OSes). It is free software availableunder +the GNULesser +General Public License. Virtualization of the Linux OperatingSystem means +the ability to run multiple instances of Operating Systemsconcurently on a +single hardware system where the basic resources are drivenby a Linux +instance. The library aim at providing long term stable C APIinitially for +the Xenparavirtualizationbut +should be able to integrate other virtualizationmechanisms if needed.

    diff --git a/docs/intro.html b/docs/intro.html index d432e2ad36..e1849168fa 100644 --- a/docs/intro.html +++ b/docs/intro.html @@ -1,32 +1,32 @@ -Introduction

    Introduction

    Libvirt is a C toolkit to interact with the virtualization capabilities of -recent versions of Linux (and other OSes), but libvirt won't try to provide -all possible interfaces for interacting with the virtualization features.

    To avoid ambiguity about the terms used here here are the definitions for -some of the specific concepts used in libvirt documentation:

    • a node is a single physical machine
      • -
    • an hypervisor is a layer of software allowing to - virtualize a node in a set of virtual machines with possibly different - configurations than the node itself
      • -
    • a domain is an instance of an operating system running - on a virtualized machine provided by the hypervisor
      • -

    Hypervisor and domains running on a node

    Now we can define the goal of libvirt: to provide the lowest possible -generic and stable layer to manage domains on a node.

    This implies the following:

    • the API is not targetted to a single virtualization environment, it - currently supports Xen and QEmu/KVM. This also implies that some very - specific capabilities which are not generic enough may not be provided as - libvirt APIs
      • -
    • the API should allow to do efficiently and cleanly all the operations - needed to manage domains on a node
      • -
    • the API will not try to provide hight level multi-nodes management - features like load balancing, though they could be implemented on top of - libvirt
      • -
    • stability of the API is a big concern, libvirt should isolate - applications from the frequent changes expected at the lower level of the - virtualization framework
      • -

    So libvirt should be a building block for higher level management tools -and for applications focusing on virtualization of a single node (the only -exception being domain migration between node capabilities which may need to -be added at the libvirt level). Where possible libvirt should be extendable -to be able to provide the same API for remote nodes, however this is not the -case at the moment, the code currently handle only local node accesses -(extension for remote access support is being worked on, see -the mailing list discussions about it).

    main menu

    related links

    Graphics and design by Diana Fong

    +Introduction

    Introduction

    Libvirt is a C toolkit to interact with the virtualization capabilities +ofrecent versions of Linux (and other OSes), but libvirt won't try to +provideall possible interfaces for interacting with the virtualization +features.

    To avoid ambiguity about the terms used here here are the definitions +forsome of the specific concepts used in libvirt documentation:

    • a nodeis a single physical machine
      • +
    • an hypervisoris a layer of software allowing + tovirtualize a node in a set of virtual machines with possibly + differentconfigurations than the node itself
      • +
    • a domainis an instance of an operating system + runningon a virtualized machine provided by the hypervisor
      • +

    Hypervisor and domains running on a node

    Now we can define the goal of libvirt: to provide the lowest +possiblegeneric and stable layer to manage domains on a node.

    This implies the following:

    • the API is not targetted to a single virtualization environment, + itcurrently supports Xen and QEmu/KVM. This also implies that some + veryspecific capabilities which are not generic enough may not be + provided aslibvirt APIs
      • +
    • the API should allow to do efficiently and cleanly all the + operationsneeded to manage domains on a node
      • +
    • the API will not try to provide hight level multi-nodes + managementfeatures like load balancing, though they could be implemented + on top oflibvirt
      • +
    • stability of the API is a big concern, libvirt should + isolateapplications from the frequent changes expected at the lower level + of thevirtualization framework
      • +

    So libvirt should be a building block for higher level management toolsand +for applications focusing on virtualization of a single node (the +onlyexception being domain migration between node capabilities which may need +tobe added at the libvirt level). Where possible libvirt should be +extendableto be able to provide the same API for remote nodes, however this +is not thecase at the moment, the code currently handle only local node +accesses(extension for remote access support is being worked on, seethe mailing listdiscussions about it).

    main menu

    related links

    Graphics and design by Diana Fong

    diff --git a/docs/libvir.html b/docs/libvir.html index 01615ba2c2..f7d69b5846 100644 --- a/docs/libvir.html +++ b/docs/libvir.html @@ -1,48 +1,48 @@ - + Libvirt the virtualization API

    Libvirt the virtualization API

    -

    Note: this is the flat content of the web -site

    +

    Note: this is the flat content of the website

    libvirt

    what is libvirt?

    -

    Libvirt is a C toolkit to interact with the virtualization capabilities -of recent versions of Linux (and other OSes). It is free software available -under the GNU -Lesser General Public License. Virtualization of the Linux Operating -System means the ability to run multiple instances of Operating Systems -concurently on a single hardware system where the basic resources are driven -by a Linux instance. The library aim at providing long term stable C API -initially for the Xen -paravirtualization but should be able to integrate other virtualization -mechanisms if needed.

    +

    Libvirt is a C toolkit to interact with the virtualization capabilitiesof +recent versions of Linux (and other OSes). It is free software availableunder +the GNULesser +General Public License. Virtualization of the Linux OperatingSystem means +the ability to run multiple instances of Operating Systemsconcurently on a +single hardware system where the basic resources are drivenby a Linux +instance. The library aim at providing long term stable C APIinitially for +the Xenparavirtualizationbut +should be able to integrate other virtualizationmechanisms if needed.

    Releases

    -

    Here is the list of official releases, however since it is early on in the -development of libvirt, it is preferable when possible to just use the CVS version or snapshot, contact the mailing list -and check the ChangeLog to gauge progresses.

    +

    Here is the list of official releases, however since it is early on in +thedevelopment of libvirt, it is preferable when possible to just use the CVS version or snapshot, contact the mailing +listand check the ChangeLogto gauge +progresses.

    0.2.0: Feb 14 2007

      -
    • Various internal cleanups (Mark McLoughlin, Richard Jones, - Daniel Berrange, Karel Zak)
      • -
    • Bug fixes: avoid a crash in connect (Daniel Berrange), virsh args - parsing (Richard Jones)
      • +
    • Various internal cleanups (Mark McLoughlin, Richard Jones,Daniel + Berrange, Karel Zak)
      • +
    • Bug fixes: avoid a crash in connect (Daniel Berrange), virsh + argsparsing (Richard Jones)
    • Add support for QEmu and KVM virtualization (Daniel Berrange)
    • Add support for network configuration (Mark McLoughlin)
      • -
    • Minor improvements: regression testing (Daniel Berrange), - localization string updates
      • +
    • Minor improvements: regression testing (Daniel Berrange),localization + string updates

    0.1.11: Jan 22 2007

    @@ -56,13 +56,19 @@ and check the ChangeLog to gauge progresses.

    0.1.10: Dec 20 2006

    • more localizations
      • -
    • bug fixes: VCPU info breakages on xen 3.0.3, xenDaemonListDomains buffer overflow (Daniel Berrange), reference count bug when creating Xen domains (Daniel Berrange).
      • -
    • improvements: support graphic framebuffer for Xen paravirt (Daniel Berrange), VNC listen IP range support (Daniel Berrange), support for default Xen config files and inactive domains of 3.0.4 (Daniel Berrange).
      • +
    • bug fixes: VCPU info breakages on xen 3.0.3, xenDaemonListDomains + buffer overflow (Daniel Berrange), reference count bug when creating Xen + domains (Daniel Berrange).
      • +
    • improvements: support graphic framebuffer for Xen paravirt (Daniel + Berrange), VNC listen IP range support (Daniel Berrange), support for + default Xen config files and inactive domains of 3.0.4 (Daniel + Berrange).

    0.1.9: Nov 29 2006

      -
    • python bindings: release interpeter lock when calling C (Daniel Berrange)
      • +
    • python bindings: release interpeter lock when calling C (Daniel + Berrange)
    • don't raise HTTP error when looking informations for a domain
    • some refactoring to use the driver for all entry points
    • better error reporting (Daniel Berrange)
      • @@ -70,90 +76,105 @@ and check the ChangeLog to gauge progresses.

    • provide XML parsing errors
    • extension of the test framework (Daniel Berrange)
    • fix the reconnect regression test
      • -
    • python bindings: Domain instances now link to the Connect to avoid garbage collection and disconnect
      • -
    • separate the notion of maximum memory and current use at the XML level
      • +
    • python bindings: Domain instances now link to the Connect to avoid + garbage collection and disconnect
      • +
    • separate the notion of maximum memory and current use at the XML + level
    • Fix a memory leak (Daniel Berrange)
    • add support for shareable drives
      • -
    • add support for non-bridge style networking configs for guests(Daniel Berrange)
      • +
    • add support for non-bridge style networking configs for guests(Daniel + Berrange)
    • python bindings: fix unsigned long marshalling (Daniel Berrange)
      • -
    • new config APIs virConfNew() and virConfSetValue() to build configs from scratch
      • +
    • new config APIs virConfNew() and virConfSetValue() to build configs + from scratch
    • hot plug device support based on Michel Ponceau patch
      • -
    • added support for inactive domains, new APIs, various associated cleanup (Daniel Berrange)
      • +
    • added support for inactive domains, new APIs, various associated + cleanup (Daniel Berrange)
    • special device model for HVM guests (Daniel Berrange)
    • add API to dump core of domains (but requires a patched xend)
    • pygrub bootloader informations take over <os> informations
    • updated the localization strings
    +

    0.1.8: Oct 16 2006

      -
    • Bug for system with page size != 4k
      • -
    • vcpu number initialization (Philippe Berthault)
      • -
    • don't label crashed domains as shut off (Peter Vetere)
      • -
    • fix virsh man page (Noriko Mizumoto)
      • -
    • blktapdd support for alternate drivers like blktap (Daniel Berrange)
      • -
    • memory leak fixes (xend interface and XML parsing) (Daniel Berrange)
      • -
    • compile fix
      • -
    • mlock/munlock size fixes (Daniel Berrange)
      • -
    • improve error reporting
      • +
    • Bug for system with page size != 4k
      • +
    • vcpu number initialization (Philippe Berthault)
      • +
    • don't label crashed domains as shut off (Peter Vetere)
      • +
    • fix virsh man page (Noriko Mizumoto)
      • +
    • blktapdd support for alternate drivers like blktap (Daniel + Berrange)
      • +
    • memory leak fixes (xend interface and XML parsing) (Daniel + Berrange)
      • +
    • compile fix
      • +
    • mlock/munlock size fixes (Daniel Berrange)
      • +
    • improve error reporting
    +

    0.1.7: Sep 29 2006

      -
    • fix a memory bug on getting vcpu informations from xend (Daniel Berrange)
      • -
    • fix another problem in the hypercalls change in Xen changeset - 86d26e6ec89b when getting domain informations (Daniel Berrange)
      • +
    • fix a memory bug on getting vcpu informations from xend (Daniel + Berrange)
      • +
    • fix another problem in the hypercalls change in Xen + changeset86d26e6ec89b when getting domain informations (Daniel + Berrange)
    +

    0.1.6: Sep 22 2006

    • Support for localization of strings using gettext (Daniel Berrange)
      • -
    • Support for new Xen-3.0.3 cdrom and disk configuration (Daniel Berrange)
      • -
    • Support for setting VNC port when creating domains with new - xend config files (Daniel Berrange)
      • +
    • Support for new Xen-3.0.3 cdrom and disk configuration (Daniel + Berrange)
      • +
    • Support for setting VNC port when creating domains with newxend config + files (Daniel Berrange)
    • Fix bug when running against xen-3.0.2 hypercalls (Jim Fehlig)
    • Fix reconnection problem when talking directly to http xend
    +

    0.1.5: Sep 5 2006

    • Support for new hypercalls change in Xen changeset 86d26e6ec89b
      • -
    • bug fixes: virParseUUID() was wrong, netwoking for paravirt guestsi - (Daniel Berrange), virsh on non-existent domains (Daniel Berrange), - string cast bug when handling error in python (Pete Vetere), HTTP - 500 xend error code handling (Pete Vetere and Daniel Berrange)
      • -
    • improvements: test suite for SEXPR <-> XML format conversions (Daniel - Berrange), virsh output regression suite (Daniel Berrange), new environ - variable VIRSH_DEFAULT_CONNECT_URI for the default URI when connecting - (Daniel Berrange), graphical console support for paravirt guests - (Jeremy Katz), parsing of simple Xen config files (with Daniel Berrange), - early work on defined (not running) domains (Daniel Berrange), - virsh output improvement (Daniel Berrange
      • +
    • bug fixes: virParseUUID() was wrong, netwoking for paravirt + guestsi(Daniel Berrange), virsh on non-existent domains (Daniel + Berrange),string cast bug when handling error in python (Pete Vetere), + HTTP500 xend error code handling (Pete Vetere and Daniel Berrange)
      • +
    • improvements: test suite for SEXPR <-> XML format conversions + (DanielBerrange), virsh output regression suite (Daniel Berrange), new + environvariable VIRSH_DEFAULT_CONNECT_URI for the default URI when + connecting(Daniel Berrange), graphical console support for paravirt + guests(Jeremy Katz), parsing of simple Xen config files (with Daniel + Berrange),early work on defined (not running) domains (Daniel + Berrange),virsh output improvement (Daniel Berrange

    0.1.4: Aug 16 2006

      -
    • bug fixes: spec file fix (Mark McLoughlin), error report problem (with - Hugh Brock), long integer in Python bindings (with Daniel Berrange), XML - generation bug for CDRom (Daniel Berrange), bug whem using number() XPath - function (Mark McLoughlin), fix python detection code, remove duplicate - initialization errors (Daniel Berrange)
      • -
    • improvements: UUID in XML description (Peter Vetere), proxy code - cleanup, virtual CPU and affinity support + virsh support (Michel - Ponceau, Philippe Berthault, Daniel Berrange), port and tty informations - for console in XML (Daniel Berrange), added XML dump to driver and proxy - support (Daniel Berrange), extention of boot options with support for - floppy and cdrom (Daniel Berrange), features block in XML to report/ask - PAE, ACPI, APIC for HVM domains (Daniel Berrange), fail saide-effect - operations when using read-only connection, large improvements to test - driver (Daniel Berrange)
      • +
    • bug fixes: spec file fix (Mark McLoughlin), error report problem + (withHugh Brock), long integer in Python bindings (with Daniel Berrange), + XMLgeneration bug for CDRom (Daniel Berrange), bug whem using number() + XPathfunction (Mark McLoughlin), fix python detection code, remove + duplicateinitialization errors (Daniel Berrange)
      • +
    • improvements: UUID in XML description (Peter Vetere), proxy + codecleanup, virtual CPU and affinity support + virsh support + (MichelPonceau, Philippe Berthault, Daniel Berrange), port and tty + informationsfor console in XML (Daniel Berrange), added XML dump to + driver and proxysupport (Daniel Berrange), extention of boot options with + support forfloppy and cdrom (Daniel Berrange), features block in XML to + report/askPAE, ACPI, APIC for HVM domains (Daniel Berrange), fail + saide-effectoperations when using read-only connection, large + improvements to testdriver (Daniel Berrange)
    • documentation: spelling (Daniel Berrange), test driver examples.

    0.1.3: Jul 11 2006

      -
    • bugfixes: build as non-root, fix xend access when root, handling of - empty XML elements (Mark McLoughlin), XML serialization and parsing fixes - (Mark McLoughlin), allow to create domains without disk (Mark - McLoughlin),
      • -
    • improvement: xenDaemonLookupByID from O(n^2) to O(n) (Daniel Berrange), - support for fully virtualized guest (Jim Fehlig, DV, Mark McLoughlin)
      • +
    • bugfixes: build as non-root, fix xend access when root, handling + ofempty XML elements (Mark McLoughlin), XML serialization and parsing + fixes(Mark McLoughlin), allow to create domains without disk + (MarkMcLoughlin),
      • +
    • improvement: xenDaemonLookupByID from O(n^2) to O(n) (Daniel + Berrange),support for fully virtualized guest (Jim Fehlig, DV, Mark + McLoughlin)
    • documentation: augmented to cover hvm domains
    @@ -165,60 +186,60 @@ and check the ChangeLog to gauge progresses.

    0.1.1: Jun 21 2006

      -
    • building fixes: ncurses fallback (Jim Fehlig), VPATH builds (Daniel P. - Berrange)
      • -
    • driver cleanups: new entry points, cleanup of libvirt.c (with Daniel P. - Berrange)
      • +
    • building fixes: ncurses fallback (Jim Fehlig), VPATH builds (Daniel + P.Berrange)
      • +
    • driver cleanups: new entry points, cleanup of libvirt.c (with Daniel + P.Berrange)
    • Cope with API change introduced in Xen changeset 10277
    • new test driver for regression checks (Daniel P. Berrange)
      • -
    • improvements: added UUID to XML serialization, buffer usage (Karel - Zak), --connect argument to virsh (Daniel P. Berrange),
      • -
    • bug fixes: uninitialized memory access in error reporting, S-Expr - parsing (Jim Fehlig, Jeremy Katz), virConnectOpen bug, remove a TODO in - xs_internal.c
      • -
    • documentation: Python examples (David Lutterkort), new Perl binding - URL, man page update (Karel Zak)
      • +
    • improvements: added UUID to XML serialization, buffer usage (KarelZak), + --connect argument to virsh (Daniel P. Berrange),
      • +
    • bug fixes: uninitialized memory access in error reporting, + S-Exprparsing (Jim Fehlig, Jeremy Katz), virConnectOpen bug, remove a + TODO inxs_internal.c
      • +
    • documentation: Python examples (David Lutterkort), new Perl bindingURL, + man page update (Karel Zak)

    0.1.0: Apr 10 2006

      -
    • building fixes: --with-xen-distdir option (Ronald Aigner), out of tree - build and pkginfo cflag fix (Daniel Berrange)
      • -
    • enhancement and fixes of the XML description format (David Lutterkort - and Jim Fehlig)
      • +
    • building fixes: --with-xen-distdir option (Ronald Aigner), out of + treebuild and pkginfo cflag fix (Daniel Berrange)
      • +
    • enhancement and fixes of the XML description format (David + Lutterkortand Jim Fehlig)
    • new APIs: for Node information and Reboot
      • -
    • internal code cleanup: refactoring internals into a driver model, more - error handling, structure sharing, thread safety and ref counting
      • -
    • bug fixes: error message (Jim Meyering), error allocation in virsh (Jim - Meyering), virDomainLookupByID (Jim Fehlig),
      • -
    • documentation: updates on architecture, and format, typo fix (Jim - Meyering)
      • -
    • bindings: exception handling in examples (Jim Meyering), perl ones out - of tree (Daniel Berrange)
      • -
    • virsh: more options, create, nodeinfo (Karel Zak), renaming of some - options (Karel Zak), use stderr only for errors (Karel Zak), man page - (Andrew Puch)
      • +
    • internal code cleanup: refactoring internals into a driver model, + moreerror handling, structure sharing, thread safety and ref counting
      • +
    • bug fixes: error message (Jim Meyering), error allocation in virsh + (JimMeyering), virDomainLookupByID (Jim Fehlig),
      • +
    • documentation: updates on architecture, and format, typo fix + (JimMeyering)
      • +
    • bindings: exception handling in examples (Jim Meyering), perl ones + outof tree (Daniel Berrange)
      • +
    • virsh: more options, create, nodeinfo (Karel Zak), renaming of + someoptions (Karel Zak), use stderr only for errors (Karel Zak), man + page(Andrew Puch)

    0.0.6: Feb 28 2006

    • add UUID lookup and extract API
    • add error handling APIs both synchronous and asynchronous
      • -
    • added minimal hook for error handling at the python level, improved the - python bindings
      • +
    • added minimal hook for error handling at the python level, improved + thepython bindings
    • augment the documentation and tests to cover error handling

    0.0.5: Feb 23 2006

      -
    • Added XML description parsing, dependance to libxml2, implemented the - creation API virDomainCreateLinux()
      • +
    • Added XML description parsing, dependance to libxml2, implemented + thecreation API virDomainCreateLinux()
    • new APIs to lookup and name domain by UUID
    • fixed the XML dump when using the Xend access
    • Fixed a few more problem related to the name change
    • Adding regression tests in python and examples in C
      • -
    • web site improvement, extended the documentation to cover the XML - format and Python API
      • +
    • web site improvement, extended the documentation to cover the XMLformat + and Python API
    • Added devhelp help for Gnome/Gtk programmers
    @@ -237,8 +258,8 @@ and check the ChangeLog to gauge progresses.

    0.0.2: Jan 29 2006

    • Update of the documentation, web site redesign (Diana Fong)
      • -
    • integration of HTTP xend RPC based on libxend by Anthony Liquori for - most operations
      • +
    • integration of HTTP xend RPC based on libxend by Anthony Liquori + formost operations
    • Adding Save and Restore APIs
    • extended the virsh command line tool (Karel Zak)
    • remove xenstore transactions (Anthony Liguori)
      • @@ -254,199 +275,203 @@ and check the ChangeLog to gauge progresses.

      Introduction

      -

      Libvirt is a C toolkit to interact with the virtualization capabilities of -recent versions of Linux (and other OSes), but libvirt won't try to provide -all possible interfaces for interacting with the virtualization features.

      +

      Libvirt is a C toolkit to interact with the virtualization capabilities +ofrecent versions of Linux (and other OSes), but libvirt won't try to +provideall possible interfaces for interacting with the virtualization +features.

      -

      To avoid ambiguity about the terms used here here are the definitions for -some of the specific concepts used in libvirt documentation:

      +

      To avoid ambiguity about the terms used here here are the definitions +forsome of the specific concepts used in libvirt documentation:

        -
      • a node is a single physical machine
        • -
      • an hypervisor is a layer of software allowing to - virtualize a node in a set of virtual machines with possibly different - configurations than the node itself
        • -
      • a domain is an instance of an operating system running - on a virtualized machine provided by the hypervisor
        • +
      • a nodeis a single physical machine
        • +
      • an hypervisoris a layer of software allowing + tovirtualize a node in a set of virtual machines with possibly + differentconfigurations than the node itself
        • +
      • a domainis an instance of an operating system + runningon a virtualized machine provided by the hypervisor

      Hypervisor and domains running on a node

      -

      Now we can define the goal of libvirt: to provide the lowest possible -generic and stable layer to manage domains on a node.

      +

      Now we can define the goal of libvirt: to provide the lowest +possiblegeneric and stable layer to manage domains on a node.

      This implies the following:

        -
      • the API is not targetted to a single virtualization environment, it - currently supports Xen and QEmu/KVM. This also implies that some very - specific capabilities which are not generic enough may not be provided as - libvirt APIs
        • -
      • the API should allow to do efficiently and cleanly all the operations - needed to manage domains on a node
        • -
      • the API will not try to provide hight level multi-nodes management - features like load balancing, though they could be implemented on top of - libvirt
        • -
      • stability of the API is a big concern, libvirt should isolate - applications from the frequent changes expected at the lower level of the - virtualization framework
        • +
      • the API is not targetted to a single virtualization environment, + itcurrently supports Xen and QEmu/KVM. This also implies that some + veryspecific capabilities which are not generic enough may not be + provided aslibvirt APIs
        • +
      • the API should allow to do efficiently and cleanly all the + operationsneeded to manage domains on a node
        • +
      • the API will not try to provide hight level multi-nodes + managementfeatures like load balancing, though they could be implemented + on top oflibvirt
        • +
      • stability of the API is a big concern, libvirt should + isolateapplications from the frequent changes expected at the lower level + of thevirtualization framework
      -

      So libvirt should be a building block for higher level management tools -and for applications focusing on virtualization of a single node (the only -exception being domain migration between node capabilities which may need to -be added at the libvirt level). Where possible libvirt should be extendable -to be able to provide the same API for remote nodes, however this is not the -case at the moment, the code currently handle only local node accesses -(extension for remote access support is being worked on, see -the mailing list discussions about it).

      +

      So libvirt should be a building block for higher level management toolsand +for applications focusing on virtualization of a single node (the +onlyexception being domain migration between node capabilities which may need +tobe added at the libvirt level). Where possible libvirt should be +extendableto be able to provide the same API for remote nodes, however this +is not thecase at the moment, the code currently handle only local node +accesses(extension for remote access support is being worked on, seethe mailing listdiscussions about it).

      libvirt architecture

      -

      Currently libvirt supports 2 kind of virtualization, and its internal -structure is based on a driver model which simplifies adding new engines:

      +

      Currently libvirt supports 2 kind of virtualization, and its +internalstructure is based on a driver model which simplifies adding new +engines:

      Libvirt Xen support

      -

      When running in a Xen environment, programs using libvirt have to execute -in "Domain 0", which is the primary Linux OS loaded on the machine. That OS -kernel provides most if not all of the actual drivers used by the set of -domains. It also runs the Xen Store, a database of informations shared by the -hypervisor, the kernels, the drivers and the xen daemon. Xend. The xen daemon -supervise the control and execution of the sets of domains. The hypervisor, -drivers, kernels and daemons communicate though a shared system bus -implemented in the hypervisor. The figure below tries to provide a view of -this environment:

      +

      When running in a Xen environment, programs using libvirt have to +executein "Domain 0", which is the primary Linux OS loaded on the machine. +That OSkernel provides most if not all of the actual drivers used by the set +ofdomains. It also runs the Xen Store, a database of informations shared by +thehypervisor, the kernels, the drivers and the xen daemon. Xend. The xen +daemonsupervise the control and execution of the sets of domains. The +hypervisor,drivers, kernels and daemons communicate though a shared system +busimplemented in the hypervisor. The figure below tries to provide a view +ofthis environment:

      The Xen architecture -

      The library can be initialized in 2 ways depending on the level of -priviledge of the embedding program. If it runs with root access, -virConnectOpen() can be used, it will use different ways to connect to -the Xen infrastructure:

      +

      The library can be initialized in 2 ways depending on the level +ofpriviledge of the embedding program. If it runs with root +access,virConnectOpen() can be used, it will use different ways to connect +tothe Xen infrastructure:

      • a connection to the Xen Daemon though an HTTP RPC layer
      • a read/write connection to the Xen Store
      • use Xen Hypervisor calls
        • -
      • when used as non-root libvirt connect to a proxy daemon running - as root and providing read-only support
        • +
      • when used as non-root libvirt connect to a proxy daemon runningas root + and providing read-only support
      -

      The library will usually interact with the Xen daemon for any operation -changing the state of the system, but for performance and accuracy reasons -may talk directly to the hypervisor when gathering state informations at -least when possible (i.e. when the running program using libvirt has root -priviledge access).

      +

      The library will usually interact with the Xen daemon for any +operationchanging the state of the system, but for performance and accuracy +reasonsmay talk directly to the hypervisor when gathering state informations +atleast when possible (i.e. when the running program using libvirt has +rootpriviledge access).

      -

      If it runs without root access virConnectOpenReadOnly() should be used to -connect to initialize the library. It will then fork a libvirt_proxy program -running as root and providing read_only access to the API, this is then -only useful for reporting and monitoring.

      +

      If it runs without root access virConnectOpenReadOnly() should be used +toconnect to initialize the library. It will then fork a libvirt_proxy +programrunning as root and providing read_only access to the API, this is +thenonly useful for reporting and monitoring.

      Libvirt QEmu and KVM support

      -

      The model for QEmu and KVM is completely similar, basically KVM is -based on QEmu for the process controlling a new domain, only small details -differs between the two. In both case the libvirt API is provided -by a controlling process forked by libvirt in the background and -which launch and control the QEmu or KVM process. That program called -libvirt_qemud talks though a specific protocol to the library, and -connects to the console of the QEmu process in order to control and -report on its status. Libvirt tries to expose all the emulations -models of QEmu, the selection is done when creating the new domain, -by specifying the architecture and machine type targetted.

      -

      The code controlling the QEmu process is available in the -qemud/ subdirectory.

      + +

      The model for QEmu and KVM is completely similar, basically KVM isbased on +QEmu for the process controlling a new domain, only small detailsdiffers +between the two. In both case the libvirt API is providedby a controlling +process forked by libvirt in the background andwhich launch and control the +QEmu or KVM process. That program calledlibvirt_qemud talks though a specific +protocol to the library, andconnects to the console of the QEmu process in +order to control andreport on its status. Libvirt tries to expose all the +emulationsmodels of QEmu, the selection is done when creating the new +domain,by specifying the architecture and machine type targetted.

      + +

      The code controlling the QEmu process is available in +theqemud/subdirectory.

      the driver based architecture

      -

      As the previous section explains, libvirt can communicate using different -channels with the Xen hypervisor, and is also able to use different kind -of hypervisor. To simplify the internal design, code, ease -maintainance and simplify the support of other virtualization engine the -internals have been structured as one core component, the libvirt.c module -acting as a front-end for the library API and a set of hypvisor drivers -defining a common set of routines. That way the Xen Daemon accces, the Xen -Store one, the Hypervisor hypercall are all isolated in separate C modules -implementing at least a subset of the common operations defined by the -drivers present in driver.h. The driver architecture is used to add support -for other virtualization engines and

      +

      As the previous section explains, libvirt can communicate using +differentchannels with the Xen hypervisor, and is also able to use different +kindof hypervisor. To simplify the internal design, code, easemaintainance +and simplify the support of other virtualization engine theinternals have +been structured as one core component, the libvirt.c moduleacting as a +front-end for the library API and a set of hypvisor driversdefining a common +set of routines. That way the Xen Daemon accces, the XenStore one, the +Hypervisor hypercall are all isolated in separate C modulesimplementing at +least a subset of the common operations defined by thedrivers present in +driver.h. The driver architecture is used to add supportfor other +virtualization engines and

        -
      • xend_internal: implements the driver functions though the Xen - Daemon.
        • -
      • xs_internal: implements the subset of the driver availble though the - Xen Store.
        • -
      • xen_internal: provide the implementation of the functions possible via - direct Xen hypervisor access.
        • -
      • proxy_internal: provide read-only Xen access via a proxy, the proxy - code is in the proxy/ sub directory.
        • -
      • xm_internal: provide support for Xen defined but not running domains.
        • -
      • qemu_internal: implement the driver functions for QEmu and KVM - virtualization engines. It also uses a qemud/ specific daemon which - interracts with the QEmu process to implement libvirt API.
        • -
      • test: this is a test driver useful for regression tests of the - front-end part of libvirt.
        • +
      • xend_internal: implements the driver functions though the + XenDaemon.
        • +
      • xs_internal: implements the subset of the driver availble though theXen + Store.
        • +
      • xen_internal: provide the implementation of the functions possible + viadirect Xen hypervisor access.
        • +
      • proxy_internal: provide read-only Xen access via a proxy, the proxycode + is in the proxy/sub directory.
        • +
      • xm_internal: provide support for Xen defined but not running + domains.
        • +
      • qemu_internal: implement the driver functions for QEmu and + KVMvirtualization engines. It also uses a qemud/ specific daemon + whichinterracts with the QEmu process to implement libvirt API.
        • +
      • test: this is a test driver useful for regression tests of thefront-end + part of libvirt.
      -

      Note that a given driver may only implement a subset of those functions, -for example saving a Xen domain state to disk and restoring it is only possible -though the Xen Daemon, in that case the driver entry points are initialized to -NULL.

      +

      Note that a given driver may only implement a subset of those +functions,for example saving a Xen domain state to disk and restoring it is +only possiblethough the Xen Daemon, in that case the driver entry points are +initialized toNULL.

      Downloads

      The latest versions of libvirt can be found on the libvirt.org server ( libvirt.orgserver ( HTTP, FTP). You will find there the released -versions as well as snapshot -tarballs updated from CVS head every hour

      +href="ftp://libvirt.org/libvirt/">FTP). You will find there the +releasedversions as well as snapshottarballsupdated +from CVS head every hour

      -

      Anonymous CVS is also -available, first register onto the server:

      +

      Anonymous CVSis +alsoavailable, first register onto the server:

      cvs -d :pserver:anoncvs@libvirt.org:2401/data/cvs login

      -

      it will request a password, enter anoncvs. Then you can -checkout the development tree with:

      +

      it will request a password, enter anoncvs. Then you +cancheckout the development tree with:

      -

      cvs -d :pserver:anoncvs@libvirt.org:2401/data/cvs co -libvirt

      +

      cvs -d :pserver:anoncvs@libvirt.org:2401/data/cvs +colibvirt

      -

      Use ./autogen.sh to configure the local checkout, then make -and make install, as usual. All normal cvs commands are now -available except commiting to the base.

      +

      Use ./autogen.sh to configure the local checkout, then +makeand make install, as usual. All normal cvs +commands are nowavailable except commiting to the base.

      XML Format

      -

      This section describes the XML format used to represent domains, there are -variations on the format based on the kind of domains run and the options -used to launch them:

      - +

      This section describes the XML format used to represent domains, there +arevariations on the format based on the kind of domains run and the +optionsused to launch them:

      -

      The formats try as much as possible to follow the same structure and reuse -elements and attributes where it makes sense.

      +

      The formats try as much as possible to follow the same structure and +reuseelements and attributes where it makes sense.

      -

      Normal paravirtualized Xen -domains:

      +

      Normal paravirtualized +Xendomains:

      The library use an XML format to describe domains, as input to virDomainCreateLinux() -and as the output of virDomainGetXMLDesc(), -the following is an example of the format as returned by the shell command -virsh xmldump fc4 , where fc4 was one of the running domains:

      +href="html/libvirt-libvirt.html#virDomainCreateLinux">virDomainCreateLinux()and +as the output of virDomainGetXMLDesc(),the +following is an example of the format as returned by the shell +commandvirsh xmldump fc4, where fc4 was one of the running +domains:

      <domain type='xen' id='18'>
   <name>fc4</name>
   <os>
@@ -472,52 +497,53 @@ the following is an example of the format as returned by the shell command
   </devices>
 </domain>
      -

      The root element must be called domain with no namespace, the -type attribute indicates the kind of hypervisor used, 'xen' is -the default value. The id attribute gives the domain id at -runtime (not however that this may change, for example if the domain is saved -to disk and restored). The domain has a few children whose order is not -significant:

      +

      The root element must be called domainwith no namespace, +thetypeattribute indicates the kind of hypervisor used, 'xen' +isthe default value. The idattribute gives the domain id +atruntime (not however that this may change, for example if the domain is +savedto disk and restored). The domain has a few children whose order is +notsignificant:

      • name: the domain name, preferably ASCII based
      • memory: the maximum memory allocated to the domain in kilobytes
      • vcpu: the number of virtual cpu configured for the domain
        • -
      • os: a block describing the Operating System, its content will be - dependant on the OS type +
      • os: a block describing the Operating System, its content will + bedependant on the OS type
        • type: indicate the OS type, always linux at this point
        • kernel: path to the kernel on the Domain 0 filesystem
          • -
        • initrd: an optional path for the init ramdisk on the Domain 0 - filesystem
          • +
        • initrd: an optional path for the init ramdisk on the Domain + 0filesystem
        • cmdline: optional command line to the kernel
          • -
        • root: the root filesystem from the guest viewpoint, it may be - passed as part of the cmdline content too
          • +
        • root: the root filesystem from the guest viewpoint, it may bepassed + as part of the cmdline content too
        • -
      • devices: a list of disk, interface and - console descriptions in no special order
        • +
      • devices: a list of disk, + interfaceandconsoledescriptions in no special + order
      -

      The format of the devices and their type may grow over time, but the -following should be sufficient for basic use:

      +

      The format of the devices and their type may grow over time, but +thefollowing should be sufficient for basic use:

      -

      A disk device indicates a block device, it can have two -values for the type attribute either 'file' or 'block' corresponding to the 2 -options availble at the Xen layer. It has two mandatory children, and one -optional one in no specific order:

      +

      A diskdevice indicates a block device, it can have twovalues +for the type attribute either 'file' or 'block' corresponding to the 2options +availble at the Xen layer. It has two mandatory children, and oneoptional one +in no specific order:

        -
      • source with a file attribute containing the path in Domain 0 to the - file or a dev attribute if using a block device, containing the device - name ('hda5' or '/dev/hda5')
        • -
      • target indicates in a dev attribute the device where it is mapped in - the guest
        • -
      • readonly an optional empty element indicating the device is - read-only
        • +
      • source with a file attribute containing the path in Domain 0 to thefile + or a dev attribute if using a block device, containing the devicename + ('hda5' or '/dev/hda5')
        • +
      • target indicates in a dev attribute the device where it is mapped inthe + guest
        • +
      • readonly an optional empty element indicating the device + isread-only
      -

      An interface element describes a network device mapped on the -guest, it also has a type whose value is currently 'bridge', it also have a -number of children in no specific order:

      +

      An interfaceelement describes a network device mapped on +theguest, it also has a type whose value is currently 'bridge', it also have +anumber of children in no specific order:

      • source: indicating the bridge name
      • mac: the optional mac address provided in the address attribute
        • @@ -526,23 +552,24 @@ number of children in no specific order:

      • target: and optional target indicating the device name.
      -

      A console element describes a serial console connection to -the guest. It has no children, and a single attribute tty which -provides the path to the Pseudo TTY on which the guest console can be -accessed

      +

      A consoleelement describes a serial console connection tothe +guest. It has no children, and a single attribute +ttywhichprovides the path to the Pseudo TTY on which the guest +console can beaccessed

      -

      Life cycle actions for the domain can also be expressed in the XML format, -they drive what should be happening if the domain crashes, is rebooted or is -poweroff. There is various actions possible when this happen:

      +

      Life cycle actions for the domain can also be expressed in the XML +format,they drive what should be happening if the domain crashes, is rebooted +or ispoweroff. There is various actions possible when this happen:

        -
      • destroy: The domain is cleaned up (that's the default normal processing - in Xen)
        • -
      • restart: A new domain is started in place of the old one with the same - configuration parameters
        • -
      • preserve: The domain will remain in memory until it is destroyed - manually, it won't be running but allows for post-mortem debugging
        • -
      • rename-restart: a variant of the previous one but where the old domain - is renamed before being saved to allow a restart
        • +
      • destroy: The domain is cleaned up (that's the default normal + processingin Xen)
        • +
      • restart: A new domain is started in place of the old one with the + sameconfiguration parameters
        • +
      • preserve: The domain will remain in memory until it is + destroyedmanually, it won't be running but allows for post-mortem + debugging
        • +
      • rename-restart: a variant of the previous one but where the old + domainis renamed before being saved to allow a restart

      The following could be used for a Xen production system:

      @@ -554,17 +581,17 @@ poweroff. There is various actions possible when this happen:

      ... </domain> -

      While the format may be extended in various ways as support for more -hypervisor types and features are added, it is expected that this core subset -will remain functional in spite of the evolution of the library.

      +

      While the format may be extended in various ways as support for +morehypervisor types and features are added, it is expected that this core +subsetwill remain functional in spite of the evolution of the library.

      -

      Fully virtualized guests -(added in 0.1.3):

      +

      Fully virtualized +guests(added in 0.1.3):

      -

      Here is an example of a domain description used to start a fully -virtualized (a.k.a. HVM) Xen domain. This requires hardware virtualization -support at the processor level but allows to run unmodified operating -systems:

      +

      Here is an example of a domain description used to start a +fullyvirtualized (a.k.a. HVM) Xen domain. This requires hardware +virtualizationsupport at the processor level but allows to run unmodified +operatingsystems:

      <domain type='xen' id='3'>
   <name>fv0</name>
   <uuid>4dea22b31d52d8f32516782e98ab3fa0</uuid>
@@ -609,86 +636,125 @@ systems:
      
 
 
      There is a few things to notice specifically for HVM domains:
      
 
        
-  
      • the optional <features> block is used to enable
-    certain guest CPU / system features. For HVM guests the following
-    features are defined:
+  
      • the optional <features>block is used to
+    enablecertain guest CPU / system features. For HVM guests the
+    followingfeatures are defined:
     
          
-      
        • pae - enable PAE memory addressing
          • 
-      
        • apic - enable IO APIC
          • 
-      
        • acpi - enable ACPI bios
          • 
+      
        • pae- enable PAE memory addressing
          • 
+      
        • apic- enable IO APIC
          • 
+      
        • acpi- enable ACPI bios
          • 
     
        
   
        • 
-  
      • the <os> block description is very different, first
-    it indicates that the type is 'hvm' for hardware virtualization, then
-    instead of a kernel, boot and command line arguments, it points to an os
-    boot loader which will extract the boot informations from the boot device
-    specified in a separate boot element. The dev attribute on
-    the boot tag can be one of:
+  
      • the <os>block description is very different, firstit
+    indicates that the type is 'hvm' for hardware virtualization, theninstead
+    of a kernel, boot and command line arguments, it points to an osboot
+    loader which will extract the boot informations from the boot
+    devicespecified in a separate boot element. The devattribute
+    onthe boottag can be one of:
     
          
-      
        • fd - boot from first floppy device
          • 
-      
        • hd - boot from first harddisk device
          • 
-      
        • cdrom - boot from first cdrom device
          • 
+      
        • fd- boot from first floppy device
          • 
+      
        • hd- boot from first harddisk device
          • 
+      
        • cdrom- boot from first cdrom device
          • 
     
        
   
        • 
-  
      • the <devices> section includes an emulator entry
-    pointing to an additional program in charge of emulating the devices
        • 
-  
      • the disk entry indicates in the dev target section that the emulation
-    for the drive is the first IDE disk device hda. The list of device names
-    supported is dependant on the Hypervisor, but for Xen it can be any IDE
-    device hda-hdd, or a floppy device
-    fda, fdb. The <disk> element
-    also supports a 'device' attribute to indicate what kinda of hardware to
-    emulate. The following values are supported:
+  
      • the <devices>section includes an emulator
+    entrypointing to an additional program in charge of emulating the
+  devices
        • 
+  
      • the disk entry indicates in the dev target section that the
+    emulationfor the drive is the first IDE disk device hda. The list of
+    device namessupported is dependant on the Hypervisor, but for Xen it can
+    be any IDEdevice hda-hdd, or a floppy
+    devicefda, fdb. The
+    <disk>elementalso supports a 'device' attribute to
+    indicate what kinda of hardware toemulate. The following values are
+    supported:
     
          
-      
        • floppy - a floppy disk controller
          • 
-      
        • disk - a generic hard drive (the default it
-      omitted)
          • 
-      
        • cdrom - a CDROM device
          • 
+      
        • floppy- a floppy disk controller
          • 
+      
        • disk- a generic hard drive (the default itomitted)
          • 
+      
        • cdrom- a CDROM device
          • 
     
        
-    For Xen 3.0.2 and earlier a CDROM device can only be emulated on the
-    hdc channel, while for 3.0.3 and later, it can be emulated
-    on any IDE channel.
        • 
-  
      • the <devices> section also include at least one
-    entry for the graphic device used to render the os. Currently there is
-    just 2 types possible 'vnc' or 'sdl'. If the type is 'vnc', then an
-    additional port attribute will be present indicating the TCP
-    port on which the VNC server is accepting client connections.
        • 
+    For Xen 3.0.2 and earlier a CDROM device can only be emulated on
+    thehdcchannel, while for 3.0.3 and later, it can be
+    emulatedon any IDE channel.
+  
      • the <devices>section also include at least oneentry
+    for the graphic device used to render the os. Currently there isjust 2
+    types possible 'vnc' or 'sdl'. If the type is 'vnc', then anadditional
+    portattribute will be present indicating the TCPport on
+    which the VNC server is accepting client connections.
        • 
 
      
 
-
      It is likely that the HVM description gets additional optional elements
-and attributes as the support for fully virtualized domain expands,
-especially for the variety of devices emulated and the graphic support
-options offered.
      
+
      It is likely that the HVM description gets additional optional elementsand
+attributes as the support for fully virtualized domain expands,especially for
+the variety of devices emulated and the graphic supportoptions offered.
      
 
-
      KVM domain
      
-
      
+
      KVM domain (added in 0.2.0)
      
+
+
      Support for the KVM virtualization is provided in recent Linux kernels
+(2.6.20 and onward). This requires specific hardware with acceleration
+support and the availability of the special version of the QEmu binary. Since this
+relies on QEmu for the machine emulation like fully virtualized guests the
+XML description is quite similar, here is a simple example:
      
+
      <domain type='kvm'>
+  <name>demo2</name>
+  <uuid>4dea24b3-1d52-d8f3-2516-782e98a23fa0</uuid>
+  <memory>131072</memory>
+  <vcpu>1</vcpu>
+  <os>
+    <type>hvm</type>
+  </os>
+  <devices>
+    <emulator>/home/user/usr/kvm-devel/bin/qemu-system-x86_64</emulator>
+    <disk type='file' device='disk'>
+      <source file='/home/user/fedora/diskboot.img'/>
+      <target dev='hda'/>
+    </disk>
+    <interface type='user'>
+      <mac address='24:42:53:21:52:45'/>
+    </interface>
+    <graphics type='vnc' port='-1'/>
+  </devices>
+</domain>
      
+
+
      The specific points to note if using KVM are:
      
+
        
+  
      • the top level domain element carries a type of 'kvm'
        • 
+  
      • the <devices> emulator points to the special qemu binary required
+    for KVM
        • 
+  
      • networking interface definitions definitions are somewhat different due
+    to a different model from Xen (@@TODO)
        • 
+
      
+
+
      except those points the options should be quite similar to Xen HVM
+ones.
      
+
+
      QEmu domain (added in 0.2.0)
      
 
-
      QEmu domain
      
 
      
 
 
      Binding for Python
      
 
-
      Libvirt comes with direct support for the Python language (just make sure
-you installed the libvirt-python package if not compiling from sources). Also
-note that Daniel Berrange provides bindings for Perl
-too.
      
+
      Libvirt comes with direct support for the Python language (just make
+sureyou installed the libvirt-python package if not compiling from sources).
+Alsonote that Daniel Berrange provides bindings for
+Perltoo.
      
 
-
      The Python binding should be complete and are mostly automatically
-generated from the formal description of the API in xml. The bindings are
-articulated around 2 classes virConnect and virDomain mapping to
-the C types. Functions in the C API taking either type as argument then
-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:
      
+
      The Python binding should be complete and are mostly
+automaticallygenerated from the formal description of the API in xml. The
+bindings arearticulated around 2 classes virConnectand virDomain
+mapping tothe C types. Functions in the C API taking either type as argument
+thenbecomes methods for the classes, their name is just stripped from
+thevirConnect or virDomain(Get) prefix and the first letter gets converted
+tolower case, for example the C functions:
      
 
 
      int virConnectNumOfDomains
-(virConnectPtr conn);
      
+href="html/libvirt-libvirt.html#virConnectNumOfDomains">virConnectNumOfDomains(virConnectPtr
+conn);
      
 
 
      int virDomainSetMaxMemory
-(virDomainPtr domain, unsigned long memory);
      
+href="html/libvirt-libvirt.html#virDomainSetMaxMemory">virDomainSetMaxMemory(virDomainPtr
+domain, unsigned long memory);
      
 
 
      become
      
 
@@ -696,18 +762,18 @@ href="html/libvirt-libvirt.html#virDomainSetMaxMemory">virDomainSetMaxMemory
 
 
      virDomain::setMaxMemory(self, memory)
      
 
-
      This process is fully automated, you can get a summary of the conversion
-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:
      
+
      This process is fully automated, you can get a summary of the conversionin
+the file libvirtclass.txt present in the python dir or in the docs.Thereis a
+couple of function who don't map directly to their C counterparts due
+tospecificities in their argument conversions:
      
 
        
   
      • virConnectListDomains
-    is replaced by virDomain::listDomainsID(self) which returns
-    a list of the integer ID for the currently running domains
        • 
+    href="html/libvirt-libvirt.html#virConnectListDomains">virConnectListDomainsis
+    replaced by virDomain::listDomainsID(self)which returnsa
+    list of the integer ID for the currently running domains
   
      • virDomainGetInfo
-    is replaced by virDomain::info() which returns a list of
+    href="html/libvirt-libvirt.html#virDomainGetInfo">virDomainGetInfois
+    replaced by virDomain::info()which returns a list of
     
          
       
        1. state: one of the state values (virDomainState)
          2. 
       
        2. maxMemory: the maximum memory used by the domain
          3. 
@@ -718,8 +784,9 @@ specificities in their argument conversions:
          
   
 
      
 
-
      So let's look at a simple example inspired from the basic.py
-test found in python/tests/ in the source tree:
      
+
      So let's look at a simple example inspired from the
+basic.pytest found in python/tests/in the source
+tree:
      
 
      import libvirt
 import sys
 
@@ -737,20 +804,20 @@ except:
 print "Domain 0: id %d running %s" % (dom0.ID(), dom0.OSType())
 print dom0.info()
      
 
-
      There is not much to comment about it, it really is a straight mapping
-from the C API, the only points to notice are:
      
+
      There is not much to comment about it, it really is a straight mappingfrom
+the C API, the only points to notice are:
      
 
        
   
      • the import of the module called libvirt
        • 
-  
      • getting a connection to the hypervisor, in that case using the
-    openReadOnly function allows the code to execute as a normal user.
        • 
+  
      • getting a connection to the hypervisor, in that case using
+    theopenReadOnly function allows the code to execute as a normal user.
        • 
   
      • getting an object representing the Domain 0 using lookupByName
        • 
   
      • if the domain is not found a libvirtError exception will be raised
        • 
-  
      • extracting and printing some informations about the domain using
-    various methods
-    associated to the virDomain class.
        • 
+  
      • extracting and printing some informations about the domain usingvarious
+    methodsassociated
+    to the virDomain class.
        • 
 
      
 
 
      Handling of errors
      
@@ -762,34 +829,34 @@ from the C API, the only points to notice are:
      
   
    • dont force the library user into one style of error handling
      •
    -

    As result the library provide both synchronous, callback based and -asynchronous error reporting. When an error happens in the library code the -error is logged, allowing to retrieve it later and if the user registered an -error callback it will be called synchronously. Once the call to libvirt ends -the error can be detected by the return value and the full information for -the last logged error can be retrieved.

    +

    As result the library provide both synchronous, callback based +andasynchronous error reporting. When an error happens in the library code +theerror is logged, allowing to retrieve it later and if the user registered +anerror callback it will be called synchronously. Once the call to libvirt +endsthe error can be detected by the return value and the full information +forthe last logged error can be retrieved.

    -

    To avoid as much as prossible troubles with a global variable in a -multithreaded environment, libvirt will associate when possible the errors to -the current connection they are related to, that way the error is stored in a -dynamic structure which can be made thread specific. Error callback can be -set specifically to a connection with

    +

    To avoid as much as prossible troubles with a global variable in +amultithreaded environment, libvirt will associate when possible the errors +tothe current connection they are related to, that way the error is stored in +adynamic structure which can be made thread specific. Error callback can +beset specifically to a connection with

    So error handling in the code is the following:

      -
    1. if the error can be associated to a connection for example when failing - to look up a domain +
    2. if the error can be associated to a connection for example when + failingto look up a domain
      1. if there is a callback associated to the connection set with virConnSetErrorFunc, - call it with the error informations
        2. + href="html/libvirt-virterror.html#virConnSetErrorFunc">virConnSetErrorFunc,call + it with the error informations
      2. otherwise if there is a global callback set with virSetErrorFunc, - call it with the error information
        3. + href="html/libvirt-virterror.html#virSetErrorFunc">virSetErrorFunc,call + it with the error information
      3. otherwise call virDefaultErrorFunc - which is the default error function of the library issuing the error - on stderr
        4. + href="html/libvirt-virterror.html#virDefaultErrorFunc">virDefaultErrorFuncwhich + is the default error function of the library issuing the erroron + stderr
      4. save the error in the connection for later retrieval with virConnGetLastError
      @@ -797,12 +864,12 @@ set specifically to a connection with

    3. otherwise like when failing to create an hypervisor connection:
      1. if there is a global callback set with virSetErrorFunc, - call it with the error information
        2. + href="html/libvirt-virterror.html#virSetErrorFunc">virSetErrorFunc,call + it with the error information
      2. otherwise call virDefaultErrorFunc - which is the default error function of the library issuing the error - on stderr
        3. + href="html/libvirt-virterror.html#virDefaultErrorFunc">virDefaultErrorFuncwhich + is the default error function of the library issuing the erroron + stderr
      3. save the error in the connection for later retrieval with virGetLastError
      @@ -810,54 +877,52 @@ set specifically to a connection with

    In all cases the error informations are provided as a virErrorPtr pointer to -read-only structure virError containing the -following fields:

    +href="html/libvirt-virterror.html#virErrorPtr">virErrorPtrpointer +toread-only structure virErrorcontaining +thefollowing fields:

    • code: an error number from the virErrorNumber - enum
      • -
    • domain: an enum indicating which part of libvirt raised the error see - virErrorDomain
      • -
    • level: the error level, usually VIR_ERR_ERROR, though there is room for - warnings like VIR_ERR_WARNING
      • + href="html/libvirt-virterror.html#virErrorNumber">virErrorNumberenum +
    • domain: an enum indicating which part of libvirt raised the error seevirErrorDomain
      • +
    • level: the error level, usually VIR_ERR_ERROR, though there is room + forwarnings like VIR_ERR_WARNING
    • message: the full human-readable formatted string of the error
    • conn: if available a pointer to the virConnectPtr - connection to the hypervisor where this happened
      • + href="html/libvirt-libvirt.html#virConnectPtr">virConnectPtrconnection + to the hypervisor where this happened
    • dom: if available a pointer to the virDomainPtr domain - targetted in the operation
      • + href="html/libvirt-libvirt.html#virDomainPtr">virDomainPtrdomaintargetted + in the operation
    -

    and then extra raw informations about the error which may be initialized -to 0 or NULL if unused

    +

    and then extra raw informations about the error which may be initializedto +0 or NULL if unused

      -
    • str1, str2, str3: string informations, usually str1 is the error - message format
      • +
    • str1, str2, str3: string informations, usually str1 is the errormessage + format
    • int1, int2: integer informations
    -

    So usually, setting up specific error handling with libvirt consist of -registering an handler with with virSetErrorFunc or -with virConnSetErrorFunc, -chech the value of the code value, take appropriate action, if needed let -libvirt print the error on stderr by calling virDefaultErrorFunc. -For asynchronous error handing, set such a function doing nothing to avoid -the error being reported on stderr, and call virConnGetLastError or -virGetLastError when an API call returned an error value. It can be a good -idea to use virResetError or virConnResetLastError -once an error has been processed fully.

    +

    So usually, setting up specific error handling with libvirt consist +ofregistering an handler with with virSetErrorFuncorwith +virConnSetErrorFunc,chech +the value of the code value, take appropriate action, if needed letlibvirt +print the error on stderr by calling virDefaultErrorFunc.For +asynchronous error handing, set such a function doing nothing to avoidthe +error being reported on stderr, and call virConnGetLastError +orvirGetLastError when an API call returned an error value. It can be a +goodidea to use virResetErroror virConnResetLastErroronce +an error has been processed fully.

    -

    At the python level, there only a global reporting callback function at -this point, see the error.py example about it:

    +

    At the python level, there only a global reporting callback function +atthis point, see the error.py example about it:

    def handler(ctxt, err):
     global errno
 
@@ -866,9 +931,9 @@ this point, see the error.py example about it:
    
 
 libvirt.registerErrorHandler(handler, 'context')
    -

    the second argument to the registerErrorHandler function is passed as the -fist argument of the callback like in the C version. The error is a tuple -containing the same field as a virError in C, but cast to Python.

    +

    the second argument to the registerErrorHandler function is passed as +thefist argument of the callback like in the C version. The error is a +tuplecontaining the same field as a virError in C, but cast to Python.

    FAQ

    @@ -884,53 +949,54 @@ containing the same field as a virError in C, but cast to Python.

    1. Licensing Terms for libvirt

      libvirt is released under the GNU Lesser - General Public License, see the file COPYING.LIB in the distribution - for the precise wording. The only library that libvirt depends upon is - the Xen store access library which is also licenced under the LGPL.

      + href="http://www.opensource.org/licenses/lgpl-license.html">GNU + LesserGeneral Public License, see the file COPYING.LIB in the + distributionfor the precise wording. The only library that libvirt + depends upon isthe Xen store access library which is also licenced under + the LGPL.

    2. Can I embed libvirt in a proprietary application ? -

      Yes. The LGPL allows you to embed libvirt into a proprietary - application. It would be graceful to send-back bug fixes and improvements - as patches for possible incorporation in the main development tree. It - will decrease your maintainance costs anyway if you do so.

      +

      Yes. The LGPL allows you to embed libvirt into a + proprietaryapplication. It would be graceful to send-back bug fixes and + improvementsas patches for possible incorporation in the main development + tree. Itwill decrease your maintainance costs anyway if you do so.

    Installation

      -
    1. Where can I get libvirt ? +
    2. Where can I get libvirt?

      The original distribution comes from ftp://libvirt.org/libvirt/.

      3. -
    3. I can't install the libvirt/libvirt-devel RPM packages due to - failed dependencies -

      The most generic solution is to re-fetch the latest src.rpm , and - rebuild it locally with

      +
    4. I can't install the libvirt/libvirt-devel RPM packages due tofailed + dependencies +

      The most generic solution is to re-fetch the latest src.rpm , + andrebuild it locally with

      rpm --rebuild libvirt-xxx.src.rpm.

      -

      If everything goes well it will generate two binary rpm packages (one - providing the shared libs and virsh, and the other one, the -devel - package, providing includes, static libraries and scripts needed to build - applications with libvirt that you can install locally.

      +

      If everything goes well it will generate two binary rpm packages + (oneproviding the shared libs and virsh, and the other one, the + -develpackage, providing includes, static libraries and scripts needed to + buildapplications with libvirt that you can install locally.

      One can also rebuild the RPMs from a tarball:

      rpmbuild -ta libdir-xxx.tar.gz

      Or from a configured tree with:

      make rpm

    5. Failure to use the API for non-root users -

      Large parts of the API may only be accessible with root priviledges, - however the read only access to the xenstore data doesnot have to be - forbidden to user, at least for monitoring purposes. If "virsh dominfo" - fails to run as an user, change the mode of the xenstore read-only socket - with:

      +

      Large parts of the API may only be accessible with root + priviledges,however the read only access to the xenstore data doesnot + have to beforbidden to user, at least for monitoring purposes. If "virsh + dominfo"fails to run as an user, change the mode of the xenstore + read-only socketwith:

      chmod 666 /var/run/xenstored/socket_ro

      -

      and also make sure that the Xen Daemon is running correctly with local - HTTP server enabled, this is defined in - /etc/xen/xend-config.sxp which need the following line to be - enabled:

      +

      and also make sure that the Xen Daemon is running correctly with + localHTTP server enabled, this is defined + in/etc/xen/xend-config.sxpwhich need the following line to + beenabled:

      (xend-http-server yes)

      -

      If needed restart the xend daemon after making the change with the - following command run as root:

      +

      If needed restart the xend daemon after making the change with + thefollowing command run as root:

      service xend restart

    @@ -946,27 +1012,28 @@ containing the same field as a virError in C, but cast to Python.

    ./configure [possible options]

    make

    make install

    -

    At that point you may have to rerun ldconfig or a similar utility to - update your list of installed shared libs.

    +

    At that point you may have to rerun ldconfig or a similar utility + toupdate your list of installed shared libs.

  • What other libraries are needed to compile/install libvirt ? -

    Libvirt requires libxenstore, which is usually provided by the xen - packages as well as the public headers to compile against libxenstore.

    +

    Libvirt requires libxenstore, which is usually provided by the + xenpackages as well as the public headers to compile against + libxenstore.

  • I use the CVS version and there is no configure script -

    The configure script (and other Makefiles) are generated. Use the - autogen.sh script to regenerate the configure script and Makefiles, - like:

    +

    The configure script (and other Makefiles) are generated. Use + theautogen.sh script to regenerate the configure script and + Makefiles,like:

    ./autogen.sh --prefix=/usr --disable-shared

    • -

    Developer corner

    +

    Developercorner

    1. Troubles compiling or linking programs using libvirt -

      To simplify the process of reusing the library, libvirt comes with - pkgconfig support, which can be used directly from autoconf support or - via the pkg-config command line tool, like:

      +

      To simplify the process of reusing the library, libvirt comes + withpkgconfig support, which can be used directly from autoconf support + orvia the pkg-config command line tool, like:

      pkg-config libvirt --libs

    @@ -974,18 +1041,23 @@ containing the same field as a virError in C, but cast to Python.

    Reporting bugs and getting help

    There is a mailing-list libvir-list@redhat.com for libvirt, -with an on-line -archive. Please subscribe to this list before posting by visiting the associated Web -page and follow the instructions. Patches with explanations and provided as -attachments are really appreciated and will be discussed on the mailing list. -If possible generate the patches by using cvs diff -u in a CVS checkout.

    +href="mailto:libvir-list@redhat.com">libvir-list@redhat.comfor +libvirt,with an on-linearchive. +Please subscribe to this list before posting by visiting the associated +Webpage and follow the instructions. Patches with explanations and +provided asattachments are really appreciated and will be discussed on the +mailing list.If possible generate the patches by using cvs diff -u in a CVS +checkout.

    -

    We use Red Hat Bugzilla to track bugs to libvirt. If you want to report a -bug, please check the existing open bugs, then if yours isn't a duplicate of -an existing bug, log a new bug. It may be good -to post to the mailing-list -too if the issue looks serious, thanks !

    +

    We use Red Hat Bugzilla to track bugs to libvirt. If you want to report +abug, please check the +existing open bugs, then if yours isn't a duplicate ofan existing bug, log +a new bug. It may be goodto post to the mailing-listtoo if the issue looks +serious, thanks !

    diff --git a/docs/libvirt-api.xml b/docs/libvirt-api.xml index 24ab373daa..d301f08893 100644 --- a/docs/libvirt-api.xml +++ b/docs/libvirt-api.xml @@ -67,7 +67,7 @@ - + @@ -121,6 +121,7 @@ + @@ -132,6 +133,7 @@ Daniel Veillard <veillard@redhat.com> + @@ -245,6 +247,7 @@ + This macro provides the length of the buffer required for virDomainGetUUID() This macro provides the length of the buffer required for virDomainGetUUIDString() @@ -277,7 +280,7 @@ - + @@ -300,6 +303,7 @@ + @@ -423,9 +427,14 @@ + + Provides capabilities of the hypervisor / driver. + + + - - + Provides the maximum number of virtual CPUs supported for a guest VM of a specific type. The 'type' parameter here corresponds to the 'type' attribute in the <domain> element of the XML. + @@ -556,10 +565,10 @@ - - + Provides a boolean value indicating whether the domain configured to be automatically started when the host machine boots. + - + Get the hypervisor ID number for the domain @@ -578,8 +587,8 @@ - - + Provides the maximum number of virtual CPUs supported for the guest VM. If the guest is inactive, this is basically the same as virConnectGetMaxVcpus. If the guest is running this will reflect the maximum number of virtual CPUs the guest was booted with. + @@ -678,7 +687,7 @@ Configure the domain to be automatically started when the host machine boots. - + Dynamically change the maximum amount of physical memory allocated to a domain. If domain is NULL, then this change the amount of memory reserved to Domain0 i.e. the domain where the application runs. This function requires priviledged access to the hypervisor. @@ -762,14 +771,14 @@ - - + Provides a boolean value indicating whether the network configured to be automatically started when the host machine boots. + - + - - + Provides a bridge interface name to which a domain may connect a network interface in order to join the network. + @@ -817,7 +826,7 @@ Configure the network to be automatically started when the host machine boots. - + Undefine a network but does not stop it if it is running diff --git a/docs/libvirt-refs.xml b/docs/libvirt-refs.xml index 217156127e..f42c5465df 100644 --- a/docs/libvirt-refs.xml +++ b/docs/libvirt-refs.xml @@ -56,6 +56,7 @@ + @@ -94,6 +95,7 @@ + @@ -251,6 +253,7 @@ + @@ -293,6 +296,7 @@ + @@ -464,6 +468,7 @@ + @@ -595,6 +600,7 @@ + @@ -717,6 +723,7 @@ + @@ -960,11 +967,17 @@ + + + + + + @@ -989,13 +1002,6 @@ - - - - - - - @@ -1028,6 +1034,7 @@ + @@ -1170,6 +1177,7 @@ + @@ -1349,6 +1357,7 @@ + @@ -1423,6 +1432,9 @@ + + + @@ -1447,6 +1459,9 @@ + + + @@ -1626,6 +1641,7 @@ + @@ -1709,6 +1725,7 @@ + @@ -1969,6 +1986,7 @@ + @@ -2048,6 +2066,7 @@ + @@ -2155,6 +2174,7 @@ + @@ -2273,6 +2293,9 @@ + + + @@ -2395,6 +2418,7 @@ + @@ -2465,6 +2489,7 @@ + @@ -2517,12 +2542,15 @@ + + + @@ -2598,9 +2626,11 @@ + + @@ -2700,6 +2730,7 @@ + @@ -2710,6 +2741,7 @@ + @@ -2873,6 +2905,7 @@ + @@ -2934,6 +2967,12 @@ + + + + + + @@ -2950,6 +2989,9 @@ + + + @@ -3054,7 +3096,9 @@ + + diff --git a/docs/news.html b/docs/news.html index e1cb428684..b702657de5 100644 --- a/docs/news.html +++ b/docs/news.html @@ -1,23 +1,30 @@ -Releases

    Releases

    Here is the list of official releases, however since it is early on in the -development of libvirt, it is preferable when possible to just use the CVS version or snapshot, contact the mailing list -and check the ChangeLog to gauge progresses.

    0.2.0: Feb 14 2007

    • Various internal cleanups (Mark McLoughlin, Richard Jones, - Daniel Berrange, Karel Zak)
      • -
    • Bug fixes: avoid a crash in connect (Daniel Berrange), virsh args - parsing (Richard Jones)
      • +Releases

      Releases

      Here is the list of official releases, however since it is early on in +thedevelopment of libvirt, it is preferable when possible to just use the CVS version or snapshot, contact the mailing +listand check the ChangeLogto gauge +progresses.

      0.2.0: Feb 14 2007

      • Various internal cleanups (Mark McLoughlin, Richard Jones,Daniel + Berrange, Karel Zak)
        • +
      • Bug fixes: avoid a crash in connect (Daniel Berrange), virsh + argsparsing (Richard Jones)
      • Add support for QEmu and KVM virtualization (Daniel Berrange)
      • Add support for network configuration (Mark McLoughlin)
        • -
      • Minor improvements: regression testing (Daniel Berrange), - localization string updates
        • +
      • Minor improvements: regression testing (Daniel Berrange),localization + string updates

      0.1.11: Jan 22 2007

      • Finish XML <-> XM config files support
      • Remove memory leak when freeing virConf objects
      • Finishing inactive domain support (Daniel Berrange)
      • Added a Relax-NG schemas to check XML instances

      0.1.10: Dec 20 2006

      • more localizations
        • -
      • bug fixes: VCPU info breakages on xen 3.0.3, xenDaemonListDomains buffer overflow (Daniel Berrange), reference count bug when creating Xen domains (Daniel Berrange).
        • -
      • improvements: support graphic framebuffer for Xen paravirt (Daniel Berrange), VNC listen IP range support (Daniel Berrange), support for default Xen config files and inactive domains of 3.0.4 (Daniel Berrange).
        • -

      0.1.9: Nov 29 2006

      • python bindings: release interpeter lock when calling C (Daniel Berrange)
        • +
      • bug fixes: VCPU info breakages on xen 3.0.3, xenDaemonListDomains + buffer overflow (Daniel Berrange), reference count bug when creating Xen + domains (Daniel Berrange).
        • +
      • improvements: support graphic framebuffer for Xen paravirt (Daniel + Berrange), VNC listen IP range support (Daniel Berrange), support for + default Xen config files and inactive domains of 3.0.4 (Daniel + Berrange).
        • +

      0.1.9: Nov 29 2006

      • python bindings: release interpeter lock when calling C (Daniel + Berrange)
      • don't raise HTTP error when looking informations for a domain
      • some refactoring to use the driver for all entry points
      • better error reporting (Daniel Berrange)
        • @@ -25,123 +32,134 @@ and check the ChangeLog to gauge progresses.

        provide XML parsing errors
      • extension of the test framework (Daniel Berrange)
      • fix the reconnect regression test
        • -
      • python bindings: Domain instances now link to the Connect to avoid garbage collection and disconnect
        • -
      • separate the notion of maximum memory and current use at the XML level
        • +
      • python bindings: Domain instances now link to the Connect to avoid + garbage collection and disconnect
        • +
      • separate the notion of maximum memory and current use at the XML + level
      • Fix a memory leak (Daniel Berrange)
      • add support for shareable drives
        • -
      • add support for non-bridge style networking configs for guests(Daniel Berrange)
        • +
      • add support for non-bridge style networking configs for guests(Daniel + Berrange)
      • python bindings: fix unsigned long marshalling (Daniel Berrange)
        • -
      • new config APIs virConfNew() and virConfSetValue() to build configs from scratch
        • +
      • new config APIs virConfNew() and virConfSetValue() to build configs + from scratch
      • hot plug device support based on Michel Ponceau patch
        • -
      • added support for inactive domains, new APIs, various associated cleanup (Daniel Berrange)
        • +
      • added support for inactive domains, new APIs, various associated + cleanup (Daniel Berrange)
      • special device model for HVM guests (Daniel Berrange)
      • add API to dump core of domains (but requires a patched xend)
      • pygrub bootloader informations take over <os> informations
      • updated the localization strings
        • -

      0.1.8: Oct 16 2006

      • Bug for system with page size != 4k
        • -
      • vcpu number initialization (Philippe Berthault)
        • -
      • don't label crashed domains as shut off (Peter Vetere)
        • -
      • fix virsh man page (Noriko Mizumoto)
        • -
      • blktapdd support for alternate drivers like blktap (Daniel Berrange)
        • -
      • memory leak fixes (xend interface and XML parsing) (Daniel Berrange)
        • -
      • compile fix
        • -
      • mlock/munlock size fixes (Daniel Berrange)
        • -
      • improve error reporting
        • -

      0.1.7: Sep 29 2006

      • fix a memory bug on getting vcpu informations from xend (Daniel Berrange)
        • -
      • fix another problem in the hypercalls change in Xen changeset - 86d26e6ec89b when getting domain informations (Daniel Berrange)
        • +

      0.1.8: Oct 16 2006

      • Bug for system with page size != 4k
        • +
      • vcpu number initialization (Philippe Berthault)
        • +
      • don't label crashed domains as shut off (Peter Vetere)
        • +
      • fix virsh man page (Noriko Mizumoto)
        • +
      • blktapdd support for alternate drivers like blktap (Daniel + Berrange)
        • +
      • memory leak fixes (xend interface and XML parsing) (Daniel + Berrange)
        • +
      • compile fix
        • +
      • mlock/munlock size fixes (Daniel Berrange)
        • +
      • improve error reporting
        • +

      0.1.7: Sep 29 2006

      • fix a memory bug on getting vcpu informations from xend (Daniel + Berrange)
        • +
      • fix another problem in the hypercalls change in Xen + changeset86d26e6ec89b when getting domain informations (Daniel + Berrange)

      0.1.6: Sep 22 2006

      • Support for localization of strings using gettext (Daniel Berrange)
        • -
      • Support for new Xen-3.0.3 cdrom and disk configuration (Daniel Berrange)
        • -
      • Support for setting VNC port when creating domains with new - xend config files (Daniel Berrange)
        • +
      • Support for new Xen-3.0.3 cdrom and disk configuration (Daniel + Berrange)
        • +
      • Support for setting VNC port when creating domains with newxend config + files (Daniel Berrange)
      • Fix bug when running against xen-3.0.2 hypercalls (Jim Fehlig)
      • Fix reconnection problem when talking directly to http xend

      0.1.5: Sep 5 2006

      • Support for new hypercalls change in Xen changeset 86d26e6ec89b
        • -
      • bug fixes: virParseUUID() was wrong, netwoking for paravirt guestsi - (Daniel Berrange), virsh on non-existent domains (Daniel Berrange), - string cast bug when handling error in python (Pete Vetere), HTTP - 500 xend error code handling (Pete Vetere and Daniel Berrange)
        • -
      • improvements: test suite for SEXPR <-> XML format conversions (Daniel - Berrange), virsh output regression suite (Daniel Berrange), new environ - variable VIRSH_DEFAULT_CONNECT_URI for the default URI when connecting - (Daniel Berrange), graphical console support for paravirt guests - (Jeremy Katz), parsing of simple Xen config files (with Daniel Berrange), - early work on defined (not running) domains (Daniel Berrange), - virsh output improvement (Daniel Berrange
        • -

      0.1.4: Aug 16 2006

      • bug fixes: spec file fix (Mark McLoughlin), error report problem (with - Hugh Brock), long integer in Python bindings (with Daniel Berrange), XML - generation bug for CDRom (Daniel Berrange), bug whem using number() XPath - function (Mark McLoughlin), fix python detection code, remove duplicate - initialization errors (Daniel Berrange)
        • -
      • improvements: UUID in XML description (Peter Vetere), proxy code - cleanup, virtual CPU and affinity support + virsh support (Michel - Ponceau, Philippe Berthault, Daniel Berrange), port and tty informations - for console in XML (Daniel Berrange), added XML dump to driver and proxy - support (Daniel Berrange), extention of boot options with support for - floppy and cdrom (Daniel Berrange), features block in XML to report/ask - PAE, ACPI, APIC for HVM domains (Daniel Berrange), fail saide-effect - operations when using read-only connection, large improvements to test - driver (Daniel Berrange)
        • +
      • bug fixes: virParseUUID() was wrong, netwoking for paravirt + guestsi(Daniel Berrange), virsh on non-existent domains (Daniel + Berrange),string cast bug when handling error in python (Pete Vetere), + HTTP500 xend error code handling (Pete Vetere and Daniel Berrange)
        • +
      • improvements: test suite for SEXPR <-> XML format conversions + (DanielBerrange), virsh output regression suite (Daniel Berrange), new + environvariable VIRSH_DEFAULT_CONNECT_URI for the default URI when + connecting(Daniel Berrange), graphical console support for paravirt + guests(Jeremy Katz), parsing of simple Xen config files (with Daniel + Berrange),early work on defined (not running) domains (Daniel + Berrange),virsh output improvement (Daniel Berrange
        • +

      0.1.4: Aug 16 2006

      • bug fixes: spec file fix (Mark McLoughlin), error report problem + (withHugh Brock), long integer in Python bindings (with Daniel Berrange), + XMLgeneration bug for CDRom (Daniel Berrange), bug whem using number() + XPathfunction (Mark McLoughlin), fix python detection code, remove + duplicateinitialization errors (Daniel Berrange)
        • +
      • improvements: UUID in XML description (Peter Vetere), proxy + codecleanup, virtual CPU and affinity support + virsh support + (MichelPonceau, Philippe Berthault, Daniel Berrange), port and tty + informationsfor console in XML (Daniel Berrange), added XML dump to + driver and proxysupport (Daniel Berrange), extention of boot options with + support forfloppy and cdrom (Daniel Berrange), features block in XML to + report/askPAE, ACPI, APIC for HVM domains (Daniel Berrange), fail + saide-effectoperations when using read-only connection, large + improvements to testdriver (Daniel Berrange)
      • documentation: spelling (Daniel Berrange), test driver examples.
        • -

      0.1.3: Jul 11 2006

      • bugfixes: build as non-root, fix xend access when root, handling of - empty XML elements (Mark McLoughlin), XML serialization and parsing fixes - (Mark McLoughlin), allow to create domains without disk (Mark - McLoughlin),
        • -
      • improvement: xenDaemonLookupByID from O(n^2) to O(n) (Daniel Berrange), - support for fully virtualized guest (Jim Fehlig, DV, Mark McLoughlin)
        • +

      0.1.3: Jul 11 2006

      • bugfixes: build as non-root, fix xend access when root, handling + ofempty XML elements (Mark McLoughlin), XML serialization and parsing + fixes(Mark McLoughlin), allow to create domains without disk + (MarkMcLoughlin),
        • +
      • improvement: xenDaemonLookupByID from O(n^2) to O(n) (Daniel + Berrange),support for fully virtualized guest (Jim Fehlig, DV, Mark + McLoughlin)
      • documentation: augmented to cover hvm domains

      0.1.2: Jul 3 2006

      • headers include paths fixup
      • proxy mechanism for unpriviledged read-only access by httpu
        • -

      0.1.1: Jun 21 2006

      • building fixes: ncurses fallback (Jim Fehlig), VPATH builds (Daniel P. - Berrange)
        • -
      • driver cleanups: new entry points, cleanup of libvirt.c (with Daniel P. - Berrange)
        • +

      0.1.1: Jun 21 2006

      • building fixes: ncurses fallback (Jim Fehlig), VPATH builds (Daniel + P.Berrange)
        • +
      • driver cleanups: new entry points, cleanup of libvirt.c (with Daniel + P.Berrange)
      • Cope with API change introduced in Xen changeset 10277
      • new test driver for regression checks (Daniel P. Berrange)
        • -
      • improvements: added UUID to XML serialization, buffer usage (Karel - Zak), --connect argument to virsh (Daniel P. Berrange),
        • -
      • bug fixes: uninitialized memory access in error reporting, S-Expr - parsing (Jim Fehlig, Jeremy Katz), virConnectOpen bug, remove a TODO in - xs_internal.c
        • -
      • documentation: Python examples (David Lutterkort), new Perl binding - URL, man page update (Karel Zak)
        • -

      0.1.0: Apr 10 2006

      • building fixes: --with-xen-distdir option (Ronald Aigner), out of tree - build and pkginfo cflag fix (Daniel Berrange)
        • -
      • enhancement and fixes of the XML description format (David Lutterkort - and Jim Fehlig)
        • +
      • improvements: added UUID to XML serialization, buffer usage (KarelZak), + --connect argument to virsh (Daniel P. Berrange),
        • +
      • bug fixes: uninitialized memory access in error reporting, + S-Exprparsing (Jim Fehlig, Jeremy Katz), virConnectOpen bug, remove a + TODO inxs_internal.c
        • +
      • documentation: Python examples (David Lutterkort), new Perl bindingURL, + man page update (Karel Zak)
        • +

      0.1.0: Apr 10 2006

      • building fixes: --with-xen-distdir option (Ronald Aigner), out of + treebuild and pkginfo cflag fix (Daniel Berrange)
        • +
      • enhancement and fixes of the XML description format (David + Lutterkortand Jim Fehlig)
      • new APIs: for Node information and Reboot
        • -
      • internal code cleanup: refactoring internals into a driver model, more - error handling, structure sharing, thread safety and ref counting
        • -
      • bug fixes: error message (Jim Meyering), error allocation in virsh (Jim - Meyering), virDomainLookupByID (Jim Fehlig),
        • -
      • documentation: updates on architecture, and format, typo fix (Jim - Meyering)
        • -
      • bindings: exception handling in examples (Jim Meyering), perl ones out - of tree (Daniel Berrange)
        • -
      • virsh: more options, create, nodeinfo (Karel Zak), renaming of some - options (Karel Zak), use stderr only for errors (Karel Zak), man page - (Andrew Puch)
        • +
      • internal code cleanup: refactoring internals into a driver model, + moreerror handling, structure sharing, thread safety and ref counting
        • +
      • bug fixes: error message (Jim Meyering), error allocation in virsh + (JimMeyering), virDomainLookupByID (Jim Fehlig),
        • +
      • documentation: updates on architecture, and format, typo fix + (JimMeyering)
        • +
      • bindings: exception handling in examples (Jim Meyering), perl ones + outof tree (Daniel Berrange)
        • +
      • virsh: more options, create, nodeinfo (Karel Zak), renaming of + someoptions (Karel Zak), use stderr only for errors (Karel Zak), man + page(Andrew Puch)

      0.0.6: Feb 28 2006

      • add UUID lookup and extract API
      • add error handling APIs both synchronous and asynchronous
        • -
      • added minimal hook for error handling at the python level, improved the - python bindings
        • +
      • added minimal hook for error handling at the python level, improved + thepython bindings
      • augment the documentation and tests to cover error handling
        • -

      0.0.5: Feb 23 2006

      • Added XML description parsing, dependance to libxml2, implemented the - creation API virDomainCreateLinux()
        • +

      0.0.5: Feb 23 2006

      • Added XML description parsing, dependance to libxml2, implemented + thecreation API virDomainCreateLinux()
      • new APIs to lookup and name domain by UUID
      • fixed the XML dump when using the Xend access
      • Fixed a few more problem related to the name change
      • Adding regression tests in python and examples in C
        • -
      • web site improvement, extended the documentation to cover the XML - format and Python API
        • +
      • web site improvement, extended the documentation to cover the XMLformat + and Python API
      • Added devhelp help for Gnome/Gtk programmers

      0.0.4: Feb 10 2006

      • Fix various bugs introduced in the name change

      0.0.3: Feb 9 2006

      • Switch name from from 'libvir' to libvirt
      • Starting infrastructure to add code examples
      • Update of python bindings for completeness

      0.0.2: Jan 29 2006

      • Update of the documentation, web site redesign (Diana Fong)
        • -
      • integration of HTTP xend RPC based on libxend by Anthony Liquori for - most operations
        • +
      • integration of HTTP xend RPC based on libxend by Anthony Liquori + formost operations
      • Adding Save and Restore APIs
      • extended the virsh command line tool (Karel Zak)
      • remove xenstore transactions (Anthony Liguori)
        • diff --git a/docs/python.html b/docs/python.html index 26679f9106..fe6d9a595f 100644 --- a/docs/python.html +++ b/docs/python.html @@ -1,32 +1,33 @@ -Binding for Python

        Binding for Python

        Libvirt comes with direct support for the Python language (just make sure -you installed the libvirt-python package if not compiling from sources). Also -note that Daniel Berrange provides bindings for Perl -too.

        The Python binding should be complete and are mostly automatically -generated from the formal description of the API in xml. The bindings are -articulated around 2 classes virConnect and virDomain mapping to -the C types. Functions in the C API taking either type as argument then -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:

        int virConnectNumOfDomains -(virConnectPtr conn);

        int virDomainSetMaxMemory -(virDomainPtr domain, unsigned long memory);

        become

        virConn::numOfDomains(self)

        virDomain::setMaxMemory(self, memory)

        This process is fully automated, you can get a summary of the conversion -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:

        • virConnectListDomains - is replaced by virDomain::listDomainsID(self) which returns - a list of the integer ID for the currently running domains
          • -
        • virDomainGetInfo - is replaced by virDomain::info() which returns a list of +Binding for Python

          Binding for Python

          Libvirt comes with direct support for the Python language (just make +sureyou installed the libvirt-python package if not compiling from sources). +Alsonote that Daniel Berrange provides bindings for +Perltoo.

          The Python binding should be complete and are mostly +automaticallygenerated from the formal description of the API in xml. The +bindings arearticulated around 2 classes virConnectand virDomain +mapping tothe C types. Functions in the C API taking either type as argument +thenbecomes methods for the classes, their name is just stripped from +thevirConnect or virDomain(Get) prefix and the first letter gets converted +tolower case, for example the C functions:

          int virConnectNumOfDomains(virConnectPtr +conn);

          int virDomainSetMaxMemory(virDomainPtr +domain, unsigned long memory);

          become

          virConn::numOfDomains(self)

          virDomain::setMaxMemory(self, memory)

          This process is fully automated, you can get a summary of the conversionin +the file libvirtclass.txt present in the python dir or in the docs.Thereis a +couple of function who don't map directly to their C counterparts due +tospecificities in their argument conversions:

          • virConnectListDomainsis + replaced by virDomain::listDomainsID(self)which returnsa + list of the integer ID for the currently running domains
            • +
          • virDomainGetInfois + replaced by virDomain::info()which returns a list of
            1. state: one of the state values (virDomainState)
            2. maxMemory: the maximum memory used by the domain
            3. memory: the current amount of memory used by the domain
            4. nbVirtCPU: the number of virtual CPU
            5. cpuTime: the time used by the domain in nanoseconds
            • -

          So let's look at a simple example inspired from the basic.py -test found in python/tests/ in the source tree:

          import libvirt
+

        So let's look at a simple example inspired from the +basic.pytest found in python/tests/in the source +tree:

        import libvirt
 import sys
 
 conn = libvirt.openReadOnly(None)
@@ -41,13 +42,13 @@ except:
     sys.exit(1)
 
 print "Domain 0: id %d running %s" % (dom0.ID(), dom0.OSType())
-print dom0.info()

        There is not much to comment about it, it really is a straight mapping -from the C API, the only points to notice are:

        • the import of the module called libvirt
          • -
        • getting a connection to the hypervisor, in that case using the - openReadOnly function allows the code to execute as a normal user.
          • +print dom0.info()

          There is not much to comment about it, it really is a straight mappingfrom +the C API, the only points to notice are:

          • the import of the module called libvirt
            • +
          • getting a connection to the hypervisor, in that case using + theopenReadOnly function allows the code to execute as a normal user.
          • getting an object representing the Domain 0 using lookupByName
          • if the domain is not found a libvirtError exception will be raised
            • -
          • extracting and printing some informations about the domain using - various methods - associated to the virDomain class.
            • +
          • extracting and printing some informations about the domain usingvarious + methodsassociated + to the virDomain class.

        main menu

        related links

        Graphics and design by Diana Fong

        diff --git a/include/libvirt/libvirt.h b/include/libvirt/libvirt.h index 46f2545212..0da97ab0ec 100644 --- a/include/libvirt/libvirt.h +++ b/include/libvirt/libvirt.h @@ -188,7 +188,7 @@ struct _virNodeInfo { typedef virNodeInfo *virNodeInfoPtr; /** - * VIR_UUID_STRING_BUFLEN: + * VIR_UUID_BUFLEN: * * This macro provides the length of the buffer required * for virDomainGetUUID() @@ -231,10 +231,15 @@ int virConnectClose (virConnectPtr conn); const char * virConnectGetType (virConnectPtr conn); int virConnectGetVersion (virConnectPtr conn, unsigned long *hvVer); -int virConnectGetMaxVcpus (virConnectPtr conn, +/* + * Capabilities of the connection / driver. + */ + +int virConnectGetMaxVcpus (virConnectPtr conn, const char *type); int virNodeGetInfo (virConnectPtr conn, virNodeInfoPtr info); +char * virConnectGetCapabilities (virConnectPtr conn); /* * Gather list of running domains diff --git a/include/libvirt/libvirt.h.in b/include/libvirt/libvirt.h.in index 5a86c5bf96..e5496283e1 100644 --- a/include/libvirt/libvirt.h.in +++ b/include/libvirt/libvirt.h.in @@ -188,7 +188,7 @@ struct _virNodeInfo { typedef virNodeInfo *virNodeInfoPtr; /** - * VIR_UUID_STRING_BUFLEN: + * VIR_UUID_BUFLEN: * * This macro provides the length of the buffer required * for virDomainGetUUID() @@ -231,10 +231,15 @@ int virConnectClose (virConnectPtr conn); const char * virConnectGetType (virConnectPtr conn); int virConnectGetVersion (virConnectPtr conn, unsigned long *hvVer); -int virConnectGetMaxVcpus (virConnectPtr conn, +/* + * Capabilities of the connection / driver. + */ + +int virConnectGetMaxVcpus (virConnectPtr conn, const char *type); int virNodeGetInfo (virConnectPtr conn, virNodeInfoPtr info); +char * virConnectGetCapabilities (virConnectPtr conn); /* * Gather list of running domains diff --git a/include/libvirt/virterror.h b/include/libvirt/virterror.h index cc0c95fa23..93078764ce 100644 --- a/include/libvirt/virterror.h +++ b/include/libvirt/virterror.h @@ -119,6 +119,7 @@ typedef enum { VIR_ERR_XML_DETAIL, /* detail of an XML error */ VIR_ERR_INVALID_NETWORK, /* invalid network object */ VIR_ERR_NETWORK_EXIST, /* the network already exist */ + VIR_ERR_SYSTEM_ERROR, /* general system call failure */ } virErrorNumber; /** @@ -133,7 +134,7 @@ typedef void (*virErrorFunc) (void *userData, virErrorPtr error); /* * Errors can be handled as asynchronous callbacks or after the routine * failed. They can also be handled globally at the library level, or - * at the connection level (which then has priority + * at the connection level (which then has priority). */ virErrorPtr virGetLastError (void); diff --git a/proxy/libvirt_proxy.c b/proxy/libvirt_proxy.c index 746029be27..2d3e71dca4 100644 --- a/proxy/libvirt_proxy.c +++ b/proxy/libvirt_proxy.c @@ -788,9 +788,24 @@ int main(int argc, char **argv) { proxyCloseUnixSocket(); exit(0); } + #else /* WITHOUT_XEN */ int main(void) { fprintf(stderr, "libvirt was compiled without Xen support\n"); exit(1); } #endif /* WITH_XEN */ + +/* + * vim: set tabstop=4: + * vim: set shiftwidth=4: + * vim: set expandtab: + */ +/* + * Local variables: + * indent-tabs-mode: nil + * c-indent-level: 4 + * c-basic-offset: 4 + * tab-width: 4 + * End: + */ diff --git a/qemud/Makefile.am b/qemud/Makefile.am index 73b0c5e3d9..73c6439577 100644 --- a/qemud/Makefile.am +++ b/qemud/Makefile.am @@ -11,7 +11,8 @@ libvirt_qemud_SOURCES = qemud.c internal.h protocol.h \ conf.c conf.h \ bridge.c bridge.h \ iptables.c iptables.h \ - uuid.c uuid.h + uuid.c uuid.h \ + buf.c buf.h #-D_XOPEN_SOURCE=600 -D_XOPEN_SOURCE_EXTENDED=1 -D_POSIX_C_SOURCE=199506L libvirt_qemud_CFLAGS = \ -I$(top_srcdir)/include -I$(top_builddir)/include $(LIBXML_CFLAGS) \ diff --git a/qemud/conf.c b/qemud/conf.c index a0f7e99196..a18b3aa5b6 100644 --- a/qemud/conf.c +++ b/qemud/conf.c @@ -46,6 +46,7 @@ #include "driver.h" #include "iptables.h" #include "uuid.h" +#include "buf.h" /* Free all memory associated with a struct qemud_vm object */ void qemudFreeVMDef(struct qemud_vm_def *def) { @@ -122,49 +123,46 @@ qemudEnsureDir(const char *path) return 0; } -struct qemu_arch_info { - const char *arch; - const char **machines; - const char *binary; -}; - /* The list of possible machine types for various architectures, as supported by QEMU - taken from 'qemu -M ?' for each arch */ static const char *arch_info_x86_machines[] = { - "pc", "isapc" + "pc", "isapc", NULL }; static const char *arch_info_mips_machines[] = { - "mips" + "mips", NULL }; static const char *arch_info_sparc_machines[] = { - "sun4m" + "sun4m", NULL }; static const char *arch_info_ppc_machines[] = { - "g3bw", "mac99", "prep" + "g3bw", "mac99", "prep", NULL }; /* The archicture tables for supported QEMU archs */ -static struct qemu_arch_info archs[] = { - { "i686", arch_info_x86_machines, "qemu" }, - { "x86_64", arch_info_x86_machines, "qemu-system-x86_64" }, - { "mips", arch_info_mips_machines, "qemu-system-mips" }, - { "mipsel", arch_info_mips_machines, "qemu-system-mipsel" }, - { "sparc", arch_info_sparc_machines, "qemu-system-sparc" }, - { "ppc", arch_info_ppc_machines, "qemu-system-ppc" }, +struct qemu_arch_info qemudArchs[] = { + /* i686 must be in position 0 */ + { "i686", 32, arch_info_x86_machines, "qemu" }, + /* x86_64 must be in position 1 */ + { "x86_64", 64, arch_info_x86_machines, "qemu-system-x86_64" }, + { "mips", 32, arch_info_mips_machines, "qemu-system-mips" }, + { "mipsel", 32, arch_info_mips_machines, "qemu-system-mipsel" }, + { "sparc", 32, arch_info_sparc_machines, "qemu-system-sparc" }, + { "ppc", 32, arch_info_ppc_machines, "qemu-system-ppc" }, + { NULL, -1, NULL, NULL } }; /* Return the default architecture if none is explicitly requested*/ static const char *qemudDefaultArch(void) { - return archs[0].arch; + return qemudArchs[0].arch; } /* Return the default machine type for a given architecture */ static const char *qemudDefaultMachineForArch(const char *arch) { int i; - for (i = 0 ; i < (int)(sizeof(archs) / sizeof(struct qemu_arch_info)) ; i++) { - if (!strcmp(archs[i].arch, arch)) { - return archs[i].machines[0]; + for (i = 0; qemudArchs[i].arch; i++) { + if (!strcmp(qemudArchs[i].arch, arch)) { + return qemudArchs[i].machines[0]; } } @@ -175,9 +173,9 @@ static const char *qemudDefaultMachineForArch(const char *arch) { static const char *qemudDefaultBinaryForArch(const char *arch) { int i; - for (i = 0 ; i < (int)(sizeof(archs) / sizeof(struct qemu_arch_info)) ; i++) { - if (!strcmp(archs[i].arch, arch)) { - return archs[i].binary; + for (i = 0 ; qemudArchs[i].arch; i++) { + if (!strcmp(qemudArchs[i].arch, arch)) { + return qemudArchs[i].binary; } } @@ -2354,72 +2352,20 @@ int qemudScanConfigs(struct qemud_server *server) { return 0; } -/* Simple grow-on-demand string buffer */ -/* XXX re-factor to shared library */ -struct qemudBuffer { - char *data; - int len; - int used; -}; - -static -int qemudBufferAdd(struct qemudBuffer *buf, const char *str) { - int need = strlen(str); - - if ((need+1) > (buf->len-buf->used)) { - return -1; - } - - memcpy(buf->data + buf->used, str, need+1); - buf->used += need; - - return 0; -} - - -static -int qemudBufferPrintf(struct qemudBuffer *buf, - const char *format, ...) { - int size, count; - va_list locarg, argptr; - - if ((format == NULL) || (buf == NULL)) { - return -1; - } - size = buf->len - buf->used - 1; - va_start(argptr, format); - va_copy(locarg, argptr); - - if ((count = vsnprintf(&buf->data[buf->used], - size, - format, - locarg)) >= size) { - return -1; - } - va_end(locarg); - buf->used += count; - - buf->data[buf->used] = '\0'; - return 0; -} - /* Generate an XML document describing the guest's configuration */ char *qemudGenerateXML(struct qemud_server *server, struct qemud_vm *vm, struct qemud_vm_def *def, int live) { - struct qemudBuffer buf; + bufferPtr buf = 0; unsigned char *uuid; struct qemud_vm_disk_def *disk; struct qemud_vm_net_def *net; const char *type = NULL; int n; - buf.len = QEMUD_MAX_XML_LEN; - buf.used = 0; - buf.data = malloc(buf.len); - - if (!buf.data) + buf = bufferNew (QEMUD_MAX_XML_LEN); + if (!buf) goto no_memory; switch (def->virtType) { @@ -2439,50 +2385,50 @@ char *qemudGenerateXML(struct qemud_server *server, } if (qemudIsActiveVM(vm) && live) { - if (qemudBufferPrintf(&buf, "\n", type, vm->id) < 0) + if (bufferVSprintf(buf, "\n", type, vm->id) < 0) goto no_memory; } else { - if (qemudBufferPrintf(&buf, "\n", type) < 0) + if (bufferVSprintf(buf, "\n", type) < 0) goto no_memory; } - if (qemudBufferPrintf(&buf, " %s\n", def->name) < 0) + if (bufferVSprintf(buf, " %s\n", def->name) < 0) goto no_memory; uuid = def->uuid; - if (qemudBufferPrintf(&buf, " %02x%02x%02x%02x-%02x%02x-%02x%02x-%02x%02x-%02x%02x%02x%02x%02x%02x\n", + if (bufferVSprintf(buf, " %02x%02x%02x%02x-%02x%02x-%02x%02x-%02x%02x-%02x%02x%02x%02x%02x%02x\n", uuid[0], uuid[1], uuid[2], uuid[3], uuid[4], uuid[5], uuid[6], uuid[7], uuid[8], uuid[9], uuid[10], uuid[11], uuid[12], uuid[13], uuid[14], uuid[15]) < 0) goto no_memory; - if (qemudBufferPrintf(&buf, " %d\n", def->maxmem) < 0) + if (bufferVSprintf(buf, " %d\n", def->maxmem) < 0) goto no_memory; - if (qemudBufferPrintf(&buf, " %d\n", def->memory) < 0) + if (bufferVSprintf(buf, " %d\n", def->memory) < 0) goto no_memory; - if (qemudBufferPrintf(&buf, " %d\n", def->vcpus) < 0) + if (bufferVSprintf(buf, " %d\n", def->vcpus) < 0) goto no_memory; - if (qemudBufferAdd(&buf, " \n") < 0) + if (bufferAdd(buf, " \n", -1) < 0) goto no_memory; if (def->virtType == QEMUD_VIRT_QEMU) { - if (qemudBufferPrintf(&buf, " %s\n", + if (bufferVSprintf(buf, " %s\n", def->os.arch, def->os.machine, def->os.type) < 0) goto no_memory; } else { - if (qemudBufferPrintf(&buf, " %s\n", def->os.type) < 0) + if (bufferVSprintf(buf, " %s\n", def->os.type) < 0) goto no_memory; } if (def->os.kernel[0]) - if (qemudBufferPrintf(&buf, " %s\n", def->os.kernel) < 0) + if (bufferVSprintf(buf, " %s\n", def->os.kernel) < 0) goto no_memory; if (def->os.initrd[0]) - if (qemudBufferPrintf(&buf, " %s\n", def->os.initrd) < 0) + if (bufferVSprintf(buf, " %s\n", def->os.initrd) < 0) goto no_memory; if (def->os.cmdline[0]) - if (qemudBufferPrintf(&buf, " %s\n", def->os.cmdline) < 0) + if (bufferVSprintf(buf, " %s\n", def->os.cmdline) < 0) goto no_memory; for (n = 0 ; n < def->os.nBootDevs ; n++) { @@ -2501,27 +2447,27 @@ char *qemudGenerateXML(struct qemud_server *server, boottype = "net"; break; } - if (qemudBufferPrintf(&buf, " \n", boottype) < 0) + if (bufferVSprintf(buf, " \n", boottype) < 0) goto no_memory; } - if (qemudBufferAdd(&buf, " \n") < 0) + if (bufferAdd(buf, " \n", -1) < 0) goto no_memory; if (def->features & QEMUD_FEATURE_ACPI) { - if (qemudBufferAdd(&buf, " \n") < 0) + if (bufferAdd(buf, " \n", -1) < 0) goto no_memory; - if (qemudBufferAdd(&buf, " \n") < 0) + if (bufferAdd(buf, " \n", -1) < 0) goto no_memory; - if (qemudBufferAdd(&buf, " \n") < 0) + if (bufferAdd(buf, " \n", -1) < 0) goto no_memory; } - if (qemudBufferAdd(&buf, " \n") < 0) + if (bufferAdd(buf, " \n", -1) < 0) goto no_memory; - if (qemudBufferPrintf(&buf, " %s\n", def->os.binary) < 0) + if (bufferVSprintf(buf, " %s\n", def->os.binary) < 0) goto no_memory; disk = def->disks; @@ -2539,21 +2485,21 @@ char *qemudGenerateXML(struct qemud_server *server, "cdrom", "floppy", }; - if (qemudBufferPrintf(&buf, " \n", + if (bufferVSprintf(buf, " \n", types[disk->type], devices[disk->device]) < 0) goto no_memory; - if (qemudBufferPrintf(&buf, " \n", typeAttrs[disk->type], disk->src) < 0) + if (bufferVSprintf(buf, " \n", typeAttrs[disk->type], disk->src) < 0) goto no_memory; - if (qemudBufferPrintf(&buf, " \n", disk->dst) < 0) + if (bufferVSprintf(buf, " \n", disk->dst) < 0) goto no_memory; if (disk->readonly) - if (qemudBufferAdd(&buf, " \n") < 0) + if (bufferAdd(buf, " \n", -1) < 0) goto no_memory; - if (qemudBufferPrintf(&buf, " \n") < 0) + if (bufferVSprintf(buf, " \n") < 0) goto no_memory; disk = disk->next; @@ -2570,42 +2516,42 @@ char *qemudGenerateXML(struct qemud_server *server, "network", "bridge", }; - if (qemudBufferPrintf(&buf, " \n", + if (bufferVSprintf(buf, " \n", types[net->type]) < 0) goto no_memory; - if (qemudBufferPrintf(&buf, " \n", + if (bufferVSprintf(buf, " \n", net->mac[0], net->mac[1], net->mac[2], net->mac[3], net->mac[4], net->mac[5]) < 0) goto no_memory; switch (net->type) { case QEMUD_NET_NETWORK: - if (qemudBufferPrintf(&buf, " \n", net->dst.network.name) < 0) + if (bufferVSprintf(buf, " \n", net->dst.network.name) < 0) goto no_memory; if (net->dst.network.ifname[0] != '\0') { - if (qemudBufferPrintf(&buf, " \n", net->dst.network.ifname) < 0) + if (bufferVSprintf(buf, " \n", net->dst.network.ifname) < 0) goto no_memory; } break; case QEMUD_NET_ETHERNET: if (net->dst.ethernet.ifname[0] != '\0') { - if (qemudBufferPrintf(&buf, " \n", net->dst.ethernet.ifname) < 0) + if (bufferVSprintf(buf, " \n", net->dst.ethernet.ifname) < 0) goto no_memory; } if (net->dst.ethernet.script[0] != '\0') { - if (qemudBufferPrintf(&buf, "