67e4fed61c
When creating a TAP interface we can end up with multiple FDs, each representing one queue. However, these FDs must be relabelled as they are then passed to QEMU. In case of qemuBuildInterfaceConnect() we allocate the array for the FDs and then let function corresponding to the <interface/> type to fill the array with FDs. When any of the functions meets an error, it's also responsible for closing previously opened FDs. However, the functions take a shortcut: iterate through each member of the array and close it (if it's non-negative). This assumes that the array is initialized to negative values, which use to be the case before rewrite in v8.4.0-rc1~170 but after it it's no longer the case. Subsequently, "random" FDs are closed (okay, not that random since the array is allocated via g_new0(), but hey - FD 0 is still valid FD and might be valuable, actually). Resolves: https://bugzilla.redhat.com/show_bug.cgi?id=2075383#c18 Fixes: 7a38d3946bc1a7ef0206f36dfe3dbf422fb8d578 Signed-off-by: Michal Privoznik <mprivozn@redhat.com> Reviewed-by: Peter Krempa <pkrempa@redhat.com>
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:
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: