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
Laine Stump cd2843f546 util: use "stubDriverType" instead of just "stubDriver"
In the past we just kept track of the type of the "stub driver" (the
driver that is bound to a device in order to assign it to a
guest). The next commit will add a stubDriverName to go along with
type, so lets use stubDriverType for the existing enum to make it
easier to keep track of whether we're talking about the name or the
type.

Signed-off-by: Laine Stump <laine@redhat.com>
Reviewed-by: Michal Privoznik <mprivozn@redhat.com>
2023-08-24 23:36:18 -04:00
.ctags.d
.github/workflows
.gitlab/issue_templates
build-aux tests: Introduce viracpitest 2023-04-06 12:48:22 +02:00
ci ci: lcitool: Maintain project package deps lists here 2023-08-22 12:10:01 +02:00
docs capabilities: report full external snapshot support 2023-08-24 19:08:20 +02:00
examples Use G_N_ELEMENTS() more 2023-03-13 13:29:07 +01:00
include include: Fix 'Since' for new VIR_MIGRATE_PARAM_COMPRESSION_* macros 2023-05-31 19:20:33 +02:00
po Translated using Weblate (Swedish) 2023-08-17 23:21:13 +02:00
scripts scripts: Fix the flake8 syntax-check failures 2023-06-29 11:51:27 +02:00
src util: use "stubDriverType" instead of just "stubDriver" 2023-08-24 23:36:18 -04:00
subprojects Move src/keycodemapdb -> subprojects/keycodemapdb 2023-04-17 15:02:38 +02:00
tests util: use "stubDriverType" instead of just "stubDriver" 2023-08-24 23:36:18 -04:00
tools virsh: doMigrate: Require --copy-storage-(all|inc) with --migrate-disks 2023-08-10 14:53:27 +02:00
.ctags
.dir-locals.el
.editorconfig
.gitattributes
.gitignore Revert ".gitignore: Ignore cscope and other *tags files" 2023-02-08 17:24:31 +01:00
.gitlab-ci.yml gitlab-ci.yml: Use $HOME for rpmbuild's topdir instead of PWD 2023-08-11 15:09:04 +02:00
.gitmodules Move src/keycodemapdb -> subprojects/keycodemapdb 2023-04-17 15:02:38 +02:00
.gitpublish
.mailmap
AUTHORS.rst.in
config.h
configmake.h.in
CONTRIBUTING.rst
COPYING
COPYING.LESSER
gitdm.config
libvirt-admin.pc.in
libvirt-lxc.pc.in
libvirt-qemu.pc.in
libvirt.pc.in
libvirt.spec.in qemu: Move channelTargetDir into stateDir 2023-08-17 17:22:09 +02:00
meson_options.txt meson: Introduce initconfdir option 2023-05-05 15:08:19 +02:00
meson.build Post-release version bump to 9.7.0 2023-08-01 11:49:29 +02:00
NEWS.rst NEWS: Mention fixes to firmware selection 2023-08-21 13:51:38 +02:00
README.rst
run.in run: add ability to set selinux context 2023-08-23 14:22:36 -05:00

GitLab CI Build Status

CII Best Practices

Translation status

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

Instructions on building and installing libvirt can be found on the website:

https://libvirt.org/compiling.html

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