99349ba18e
This reverts commit 8511b96a319836700b4829816cdae27c3630060d. Turns out, we need to do a bit more than just plain qemuSecurityDomainSetPathLabel() which sets svirt_image_t. Passt has its own SELinux policy and as a part of that they invent passt_log_t for log files. Right now, I don't know how libvirt could query that and even if I did, passt SELinux policy would need to permit relabelling from svirt_t to passt_log_t, which it doesn't [1]. Until these problems are addressed we shouldn't be pre-creating the file as it puts users into way worse position - even scenarios that used to work don't work. But then again - using log file for passt is usually valuable for developers only and not regular users. 1: https://bugzilla.redhat.com/show_bug.cgi?id=2209191#c10 Signed-off-by: Michal Privoznik <mprivozn@redhat.com> Reviewed-by: Martin Kletzander <mkletzan@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: