2005-12-09 13:04:05 +00:00
<?xml version="1.0" encoding="ISO-8859-1"?>
2008-04-25 16:23:51 +00:00
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
2008-04-23 17:08:31 +00:00
< html xmlns = "http://www.w3.org/1999/xhtml" >
<!--
This file is autogenerated from architecture.html.in
Do not edit this file. Changes will be lost.
-->
< head >
< meta http-equiv = "Content-Type" content = "text/html; charset=ISO-8859-1" / >
< link rel = "stylesheet" type = "text/css" href = "main.css" / >
< link rel = "SHORTCUT ICON" href = "32favicon.png" / >
< title > libvirt: libvirt architecture< / title >
< meta name = "description" content = "libvirt, virtualization, virtualization API" / >
< / head >
< body >
< div id = "header" >
< div id = "headerLogo" > < / div >
< div id = "headerSearch" >
2008-04-25 16:23:51 +00:00
< form action = "search.php" enctype = "application/x-www-form-urlencoded" method = "get" > < div >
< input id = "query" name = "query" type = "text" size = "12" value = "" / >
< input id = "submit" name = "submit" type = "submit" value = "Search" / >
< / div > < / form >
2008-04-23 17:08:31 +00:00
< / div >
< / div >
< div id = "body" >
2008-04-25 16:23:51 +00:00
< div id = "menu" >
< ul class = "l0" > < li >
< div >
< a title = "Front page of the libvirt website" class = "inactive" href = "index.html" > Home< / a >
< / div >
< / li > < li >
< div >
< a title = "Details of new features and bugs fixed in each release" class = "inactive" href = "news.html" > News< / a >
< / div >
< / li > < li >
< div >
< a title = "Get the latest source releases, binary builds and get access to the source repository" class = "inactive" href = "downloads.html" > Downloads< / a >
< / div >
< / li > < li >
< div >
< a title = "Information for users, administrators and developers" class = "inactive" href = "docs.html" > Documentation< / a >
< / div >
< / li > < li >
< div >
< a title = "User contributed content" class = "inactive" href = "http://wiki.libvirt.org" > Wiki< / a >
< / div >
< / li > < li >
< div >
< a title = "Frequently asked questions" class = "inactive" href = "FAQ.html" > FAQ< / a >
< / div >
< / li > < li >
< div >
< a title = "How and where to report bugs and request features" class = "inactive" href = "bugs.html" > Bug reports< / a >
< / div >
< / li > < li >
< div >
< a title = "How to contact the developers via email and IRC" class = "inactive" href = "contact.html" > Contact< / a >
< / div >
< / li > < li >
< div >
< a title = "Miscellaneous links of interest related to libvirt" class = "inactive" href = "relatedlinks.html" > Related Links< / a >
< / div >
< / li > < li >
< div >
< a title = "Overview of all content on the website" class = "inactive" href = "sitemap.html" > Sitemap< / a >
< / div >
< / li > < / ul >
< / div >
2008-04-23 17:08:31 +00:00
< div id = "content" >
< h1 > libvirt architecture< / h1 >
< p > Currently libvirt supports 2 kind of virtualization, and its
2007-04-27 15:39:20 +00:00
internal structure is based on a driver model which simplifies adding new
2008-04-23 17:08:31 +00:00
engines:< / p >
< ul > < li >
< a href = "#Xen" > Xen hypervisor< / a >
< / li > < li >
< a href = "#QEmu" > QEmu and KVM based virtualization< / a >
< / li > < li >
< a href = "#drivers" > the driver architecture< / a >
< / li > < / ul >
< h3 >
< a name = "Xen" id = "Xen" > Libvirt Xen support< / a >
< / h3 >
< p > When running in a Xen environment, programs using libvirt have to execute
2007-03-22 15:17:31 +00:00
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
2008-03-14 11:08:03 +00:00
domains. It also runs the Xen Store, a database of information shared by the
2007-03-22 15:17:31 +00:00
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
2008-04-23 17:08:31 +00:00
this environment:< / p >
< img src = "architecture.gif" alt = "The Xen architecture" / >
< p > The library can be initialized in 2 ways depending on the level of
2008-04-04 07:58:29 +00:00
privilege of the embedding program. If it runs with root access,
2007-04-27 15:39:20 +00:00
virConnectOpen() can be used, it will use three different ways to connect to
2008-04-23 17:08:31 +00:00
the Xen infrastructure:< / p >
< ul > < li > a connection to the Xen Daemon though an HTTP RPC layer< / li > < li > a read/write connection to the Xen Store< / li > < li > use Xen Hypervisor calls< / li > < li > when used as non-root libvirt connect to a proxy daemon running
as root and providing read-only support< / li > < / ul >
< p > The library will usually interact with the Xen daemon for any operation
2007-03-22 15:17:31 +00:00
changing the state of the system, but for performance and accuracy reasons
2008-03-14 11:08:03 +00:00
may talk directly to the hypervisor when gathering state information at
2007-03-22 15:17:31 +00:00
least when possible (i.e. when the running program using libvirt has root
2008-04-23 17:08:31 +00:00
privilege access).< / p >
< p > If it runs without root access virConnectOpenReadOnly() should be used to
2007-04-27 15:39:20 +00:00
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
2008-04-23 17:08:31 +00:00
then only useful for reporting and monitoring.< / p >
< h3 >
< a name = "QEmu" id = "QEmu" > Libvirt QEmu and KVM support< / a >
< / h3 >
< p > The model for QEmu and KVM is completely similar, basically KVM is based
2007-04-27 15:39:20 +00:00
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
2008-04-23 17:08:31 +00:00
domain, by specifying the architecture and machine type targeted.< / p >
< p > The code controlling the QEmu process is available in the
< code > qemud/< / code > directory.< / p >
< h3 >
< a name = "drivers" id = "drivers" > the driver based architecture< / a >
< / h3 >
< p > As the previous section explains, libvirt can communicate using different
2007-04-27 15:39:20 +00:00
channels with the current hypervisor, and should also be able to use
different kind of hypervisor. To simplify the internal design, code, ease
2008-03-17 10:27:31 +00:00
maintenance and simplify the support of other virtualization engine the
2007-03-22 15:17:31 +00:00
internals have been structured as one core component, the libvirt.c module
2008-03-17 10:27:31 +00:00
acting as a front-end for the library API and a set of hypervisor drivers
2008-04-04 07:58:29 +00:00
defining a common set of routines. That way the Xen Daemon access, the Xen
2007-03-22 15:17:31 +00:00
Store one, the Hypervisor hypercall are all isolated in separate C modules
implementing at least a subset of the common operations defined by the
2008-04-23 17:08:31 +00:00
drivers present in driver.h:< / p >
< ul > < li > xend_internal: implements the driver functions though the Xen
Daemon< / li > < li > xs_internal: implements the subset of the driver available though the
Xen Store< / li > < li > xen_internal: provide the implementation of the functions possible via
direct hypervisor access< / li > < li > proxy_internal: provide read-only Xen access via a proxy, the proxy code
is in the < code > proxy/< / code > directory.< / li > < li > xm_internal: provide support for Xen defined but not running
domains.< / li > < li > qemu_internal: implement the driver functions for QEmu and
2007-04-27 15:39:20 +00:00
KVM virtualization engines. It also uses a qemud/ specific daemon
2008-04-23 17:08:31 +00:00
which interacts with the QEmu process to implement libvirt API.< / li > < li > test: this is a test driver useful for regression tests of the
front-end part of libvirt.< / li > < / ul >
< p > Note that a given driver may only implement a subset of those functions,
2007-04-27 15:39:20 +00:00
(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 for
2008-04-23 17:08:31 +00:00
unsupported functions are initialized to NULL.< / p >
< p > < / p >
< / div >
< / div >
< div id = "footer" >
2008-04-28 08:29:35 +00:00
< p id = "sponsor" >
Sponsored by:< br / > < a href = "http://et.redhat.com/" > < img src = "et.png" alt = "Project sponsored by Red Hat Emerging Technology" / > < / a > < / p >
2008-04-23 17:08:31 +00:00
< / div >
< / body >
< / html >
