libvirt/src
Jiri Denemark 266265a560 qemu: Setup infrastructure for HMP passthrough
JSON monitor command implementation can now just directly call text
monitor implementation and it will be automatically encapsulated into
QMP's human-monitor-command.
2011-03-10 14:36:04 +01:00
..
conf qemu: Support vram for video of qxl type 2011-03-06 22:00:27 +08:00
cpu hash: make virHashFree more free-like 2011-02-21 08:27:02 -07:00
esx
interface
lxc
network
node_device
nwfilter
opennebula
openvz
phyp
qemu
remote
secret
security
storage
test
uml
util cgroup: allow fine-tuning of device ACL permissions 2011-03-09 11:35:36 -07:00
vbox
vmware
vmx
xen
xenapi
xenxs
.gitignore
datatypes.c
datatypes.h
driver.c
driver.h
fdstream.c
fdstream.h
gnutls_1_0_compat.h
internal.h
libvirt_bridge.syms
libvirt_daemon.syms
libvirt_driver_modules.syms
libvirt_internal.h
libvirt_linux.syms
libvirt_macvtap.syms
libvirt_nwfilter.syms
libvirt_private.syms
libvirt_public.syms
libvirt_qemu.syms
libvirt_vmx.syms
libvirt-qemu.c
libvirt.c maint: kill all remaining uses of old DEBUG macro 2011-02-21 08:46:52 -07:00
Makefile.am
nodeinfo.c
nodeinfo.h
README
remote_protocol-structs

       libvirt library code README
       ===========================

The directory provides the bulk of the libvirt codebase. Everything
except for the libvirtd daemon and client tools. The build uses a
large number of libtool convenience libraries - one for each child
directory, and then links them together for the final libvirt.so,
although some bits get linked directly to libvirtd daemon instead.

The files directly in this directory are supporting the public API
entry points & data structures.

There are two core shared modules to be aware of:

 * util/  - a collection of shared APIs that can be used by any
            code. This directory is always in the include path
            for all things built

 * conf/  - APIs for parsing / manipulating all the official XML
            files used by the public API. This directory is only
            in the include path for driver implementation modules

 * vmx/   - VMware VMX config handling (used by esx/ and vmware/)


Then there are the hypervisor implementations:

 * esx/          - VMware ESX and GSX support using vSphere API over SOAP
 * lxc/          - Linux Native Containers
 * opennebula/   - Open Nebula using XMLRPC
 * openvz/       - OpenVZ containers using cli tools
 * phyp/         - IBM Power Hypervisor using CLI tools over SSH
 * qemu/         - QEMU / KVM using qemu CLI/monitor
 * remote/       - Generic libvirt native RPC client
 * test/         - A "mock" driver for testing
 * uml/          - User Mode Linux
 * vbox/         - Virtual Box using native API
 * vmware/       - VMware Workstation and Player using the vmrun tool
 * xen/          - Xen using hypercalls, XenD SEXPR & XenStore
 * xenapi/       - Xen using libxenserver


Finally some secondary drivers that are shared for several HVs.
Currently these are used by LXC, OpenVZ, QEMU, UML and Xen drivers.
The ESX, OpenNebula, Power Hypervisor, Remote, Test & VirtualBox
drivers all implement the secondary drivers directly

 * cpu/          - CPU feature management
 * interface/    - Host network interface management
 * network/      - Virtual NAT networking
 * nwfilter/     - Network traffic filtering rules
 * node_device/  - Host device enumeration
 * secret/       - Secret management
 * security/     - Mandatory access control drivers
 * storage/      - Storage management drivers


Since both the hypervisor and secondary drivers can be built as
dlopen()able modules, it is *FORBIDDEN* to have build dependencies
between these directories. Drivers are only allowed to depend on
the public API, and the internal APIs in the util/ and conf/
directories