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.
Go to file
Peter Krempa ecdd929761 qemu: capabilities: Add QEMU_CAPS_BLOCKDEV_REOPEN
This capability will be asserted once qemu stabilizes 'blockdev-reopen'.
For now we just add the capability so that we can introduce some code
that will use the reopening call. This will show our willingness to
adopt use of reopen and help qemu developers stabilize it.

Signed-off-by: Peter Krempa <pkrempa@redhat.com>
Reviewed-by: Eric Blake <eblake@redhat.com>
2020-03-16 17:33:08 +01:00
.ctags.d
build-aux build: workaround behaviour regression in gnu make 4.3 2020-03-16 12:07:21 +00:00
ci ci: Drop handling of $PKG_CONFIG_LIBDIR 2020-03-04 11:24:10 +01:00
docs docs: virtiofs: add missing aposthrophe 2020-03-16 16:31:04 +01:00
examples
include/libvirt admin: Introduce virAdmServerUpdateTlsFiles 2020-03-13 17:07:32 +00:00
m4 m4: libxl: properly fail when libxl is required 2020-02-20 22:30:45 +01:00
po src: introduce an abstraction for running event loops 2020-03-11 14:44:04 +00:00
scripts
src qemu: capabilities: Add QEMU_CAPS_BLOCKDEV_REOPEN 2020-03-16 17:33:08 +01:00
tests tests: validate parsing of CPUs with dies > 1 2020-03-16 16:00:27 +00:00
tools virt-host-validate: warn if kvm_hv is not loaded for POWER hosts 2020-03-16 10:38:21 +01:00
.color_coded.in
.ctags
.dir-locals.el
.editorconfig
.gitignore
.gitlab-ci.yml
.gitmodules
.gitpublish
.mailmap
.travis.yml travis: Use dedicated images for MinGW builds 2020-02-24 13:41:58 +01:00
.ycm_extra_conf.py.in
ABOUT-NLS
AUTHORS.in
autogen.sh build: stop running aclocal manually 2020-02-25 09:22:56 +00:00
ChangeLog
config-post.h
configure.ac maint: Post-release version bump to 6.2.0 2020-03-04 10:32:58 +01:00
COPYING
COPYING.LESSER
gitdm.config
GNUmakefile
libvirt-admin.pc.in
libvirt-lxc.pc.in
libvirt-qemu.pc.in
libvirt.pc.in
libvirt.spec.in
Makefile.am
Makefile.nonreentrant
mingw-libvirt.spec.in
README
README-hacking
README.md
run.in

Build Status CII Best Practices

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:

https://libvirt.org

License

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 Public License, version 2.0 (or later). See the files COPYING.LESSER and COPYING for full license terms & conditions.

Installation

Libvirt uses the GNU Autotools build system, so in general can be built 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:

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

While to build & install as an unprivileged user

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

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

Contributing

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

https://libvirt.org/contribute.html

Contact

The libvirt project has two primary mailing lists:

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

https://libvirt.org/contact.html