NuKVM/libvirt
3
0
Fork 0
mirror of https://github.com/libvirt/libvirt.git synced 2025-02-25 18:55:26 -06:00
Code Issues Packages Projects Releases Wiki Activity

* NEWS virsh.1 docs//* include/libvirt/libvirt.h[.in] qemud/mdns.h

Browse Source 
src/libvirt.c src/qemu.conf src/remote_internal.c src/xend_internal.c
  tests/confdata/libvirtd.conf tests/confdata/libvirtd.out: patch from
  Atsushi SAKAI fixing a ot more typo
Daniel
This commit is contained in:
Daniel Veillard
2008-03-17 10:27:31 +00:00
parent 7ae13660cf
commit 08ecf61b35
22 changed files with 111 additions and 104 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
docs/architecture.html
View File

@@ -40,9 +40,9 @@ domain, by specifying the architecture and machine type targetted.</p><p>The cod
<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
channels with the current hypervisor, and should also be able to use
different kind of hypervisor. To simplify the internal design, code, ease
maintainance and simplify the support of other virtualization engine the
maintenance 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
acting as a front-end for the library API and a set of hypervisor 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