mirror of https://gitlab.com/libvirt/libvirt.git synced 2024-07-17 15:17:17 +00:00

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 2a51ff7b40 openvswitch: don't delete existing OVS port prior to recreating same port Connecting a tap device to an Open vSwitch is done by adding a "port" to the switch with the ovs-vsctl "add-port" command. The port will have the same name as the tap device, but it is a separate entity, and can survive beyond the destruction of the tap device (although under normal circumstances the port will be deleted around the same time the tap device is deleted). This makes it possible for a port of a particular name to already exist at the time libvirt calls ovs-vsctl to add that port. The original commit of Open vSwitch support (commit `df81004632`, libvirt 0.9.10, Feb. 2012) used the "--may-exist" option to the add-port command to indicate that a port of the desired name might already exist, and that it was okay to simply re-use this port (rather than failing with an error message). Then in commit `33445ce844` (libvirt 1.2.7, April 2014) the command was changed to use "--if-exists del-port blah" instead of "--may-exist". The reason given was that there was a bug in OVS where a stale port would be unusable even though it still existed; the workaround was to forcibly delete any existing port prior to adding the new port (of the same name). This is the ovs-vsctl command still in use by libvirt today. It recently came up in the discussion of a bug concerning guest packet loss during OpenStack upgrades (https://bugzilla.redhat.com/1963164) that the bug in OVS that necessitated the del-port workaround was fixed quite a long time ago (August 2015): `e21c6643a0` thus rendering the workaround in libvirt unnecessary. The assertion in that discussion is that this workaround is now the cause of the packet loss being experienced during OpenStack upgrades. I'm not convinced this is the case, but it does appear that there is no reason to carry this workaround in libvirt any longer, so this patch reverts the code back to the original behavior (using "--may-exist" instead of "--if-exists del-port"). Signed-off-by: Laine Stump <laine@redhat.com> Reviewed-by: Daniel P. Berrangé <berrange@redhat.com>		2021-06-10 01:23:47 -04:00
.ctags.d
.github	github: skip lockdown of old issues/prs	2020-04-07 17:50:54 +01:00
.gitlab/issue_templates	gitlab: Add issue template for a feature request	2020-12-02 09:11:27 +01:00
build-aux	Remove test 'args' file rewrapping infrastructure	2021-04-12 15:55:10 +02:00
ci	gitlab: avoid building libvirt twice and running syntax-check twice	2021-05-12 14:18:15 +01:00
docs	docs: switch ci status page to use Go -module repos	2021-06-09 14:48:40 +01:00
examples	nodedev: add DEFINED/UNDEFINED lifecycle events	2021-04-07 15:07:45 -05:00
include	Add basic driver for the Cloud-Hypervisor	2021-06-04 10:56:06 +01:00
po	Translated using Weblate (Korean)	2021-06-07 10:46:26 +02:00
scripts	lib: Drop internal virXXXPtr typedefs	2021-04-13 17:00:38 +02:00
src	openvswitch: don't delete existing OVS port prior to recreating same port	2021-06-10 01:23:47 -04:00
tests	qemu: wire up support for timer period audio setting	2021-06-04 12:08:03 +01:00
tools	virt-host-validate: Fix IOMMU output on aarch64	2021-06-09 12:51:36 +02:00
.color_coded.in	gnulib: delete all gnulib integration	2020-02-07 15:03:54 +00:00
.ctags
.dir-locals.el
.editorconfig	Add .editorconfig	2019-09-06 12:47:46 +02:00
.gitignore	gitignore: Ignore __pycache__ directory	2021-03-22 12:05:11 +01:00
.gitlab-ci.yml	gitlab: avoid building libvirt twice and running syntax-check twice	2021-05-12 14:18:15 +01:00
.gitmodules	gnulib: delete all gnulib integration	2020-02-07 15:03:54 +00:00
.gitpublish	gitpublish: add a subject prefix	2020-01-16 13:04:11 +00:00
.mailmap	mailmap: consolidate my email addresses	2020-10-06 12:05:09 +02:00
.ycm_extra_conf.py.in	gnulib: delete all gnulib integration	2020-02-07 15:03:54 +00:00
AUTHORS.rst.in	AUTHORS: Remove Emacs file variables	2020-09-02 13:20:17 +02:00
config.h	meson: Declare GLIB_VERSION_* macros at configure	2021-05-03 12:08:26 +02:00
configmake.h.in	meson: generate configmake.h	2020-08-03 09:26:48 +02:00
CONTRIBUTING.rst	meson: adjust our documentation to mention meson instead of autoconf	2020-08-03 09:27:09 +02:00
COPYING	maint: follow recommended practice for using LGPL	2013-05-20 14:15:21 -06:00
COPYING.LESSER
gitdm.config	gitdm: add 'ibm' file	2019-10-18 17:32:52 +02:00
libvirt-admin.pc.in
libvirt-lxc.pc.in	Add pkg-config files for libvirt-qemu & libvirt-lxc	2014-06-23 16:17:27 +01:00
libvirt-qemu.pc.in
libvirt.pc.in
libvirt.spec.in	Add basic driver for the Cloud-Hypervisor	2021-06-04 10:56:06 +01:00
meson_options.txt	Add basic driver for the Cloud-Hypervisor	2021-06-04 10:56:06 +01:00
meson.build	meson.build: Compile with -Walloca	2021-06-08 13:59:43 +02:00
mingw-libvirt.spec.in	meson: Turn apparmor_profiles into a feature	2021-06-01 14:32:02 +02:00
NEWS.rst	Post-release version bump to 7.5.0	2021-06-01 12:05:41 +02:00
README.rst	README: drop Travis CI badge	2020-08-03 15:08:28 +02:00
run.in	run: fix spawning of daemons	2021-04-07 11:41:26 +01:00

README.rst

Libvirt API for virtualization

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:

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

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

https://libvirt.org/contact.html