README.rst 3.0 KB
Newer Older
A
Andrea Bolognani 已提交
1 2 3
.. image:: https://gitlab.com/libvirt/libvirt/badges/master/pipeline.svg
     :target: https://gitlab.com/libvirt/libvirt/pipelines
     :alt: GitLab CI Build Status
4 5 6 7 8 9
.. image:: https://travis-ci.org/libvirt/libvirt.svg
     :target: https://travis-ci.org/libvirt/libvirt
     :alt: Travis CI Build Status
.. image:: https://bestpractices.coreinfrastructure.org/projects/355/badge
     :target: https://bestpractices.coreinfrastructure.org/projects/355
     :alt: CII Best Practices
10

11
==============================
12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31
Libvirt API for virtualization
==============================

Libvirt provides a portable, long term stable C API for managing the
virtualization technologies provided by many operating systems. It
includes support for QEMU, KVM, Xen, LXC, bhyve, Virtuozzo, VMware
vCenter and ESX, VMware Desktop, Hyper-V, VirtualBox and the POWER
Hypervisor.

For some of these hypervisors, it provides a stateful management
daemon which runs on the virtualization host allowing access to the
API both by non-privileged local users and remote users.

Layered packages provide bindings of the libvirt C API into other
languages including Python, Perl, PHP, Go, Java, OCaml, as well as
mappings into object systems such as GObject, CIM and SNMP.

Further information about the libvirt project can be found on the
website:

32
https://libvirt.org
33 34 35


License
36
=======
37 38 39 40

The libvirt C API is distributed under the terms of GNU Lesser General
Public License, version 2.1 (or later). Some parts of the code that are
not part of the C library may have the more restrictive GNU General
41 42
Public License, version 2.0 (or later). See the files ``COPYING.LESSER``
and ``COPYING`` for full license terms & conditions.
43 44 45


Installation
46
============
47 48

Libvirt uses the GNU Autotools build system, so in general can be built
49 50 51
and installed with the usual commands, however, we mandate to have the
build directory different than the source directory. For example, to build
in a manner that is suitable for installing as root, use:
52

53 54 55 56 57 58
::

  $ mkdir build && cd build
  $ ../configure --prefix=/usr --sysconfdir=/etc --localstatedir=/var
  $ make
  $ sudo make install
59 60 61

While to build & install as an unprivileged user

62 63 64 65 66 67
::

  $ mkdir build && cd build
  $ ../configure --prefix=$HOME/usr
  $ make
  $ make install
68 69

The libvirt code relies on a large number of 3rd party libraries. These will
70
be detected during execution of the ``configure`` script and a summary printed
71 72 73 74
which lists any missing (optional) dependencies.


Contributing
75
============
76 77 78

The libvirt project welcomes contributions in many ways. For most components
the best way to contribute is to send patches to the primary development
79
mailing list. Further guidance on this can be found on the website:
80

81
https://libvirt.org/contribute.html
82 83 84


Contact
85
=======
86 87 88

The libvirt project has two primary mailing lists:

89 90
* libvirt-users@redhat.com (**for user discussions**)
* libvir-list@redhat.com (**for development only**)
91

92
Further details on contacting the project are available on the website:
93

94
https://libvirt.org/contact.html