c4d96fdd3c
virProcessActivateMaxFiles sets rlim_cur to rlim_max. If rlim_max is RLIM_INFINITY, 2023-08-15 15:17:51.944+0000: 4456752640: debug : virProcessActivateMaxFiles:1067 : Initial max files was 2560 2023-08-15 15:17:51.944+0000: 4456752640: debug : virProcessActivateMaxFiles:1077 : Raised max files to 9223372036854775807 then when virCommandMassClose does `int openmax = sysconf( _SC_OPEN_MAX)`, `openmax < 0` is true and virCommandMassClose reports an error and bails. Setting rlim_cur instead to at most OPEN_MAX, as macOS' documentation suggests, both avoids this problem 2023-08-18 16:01:44.366+0000: 4359562752: debug : virProcessActivateMaxFiles:1072 : Initial max files was 256 2023-08-18 16:01:44.366+0000: 4359562752: debug : virProcessActivateMaxFiles:1086 : Raised max files to 10240 and eliminates a case of what the documentation declares to be invalid input to setrlimit anyway. Signed-off-by: Laura Hild <lsh@jlab.org> |
||
|---|---|---|
| .ctags.d | ||
| .github/workflows | ||
| .gitlab/issue_templates | ||
| build-aux | ||
| ci | ||
| docs | ||
| examples | ||
| include | ||
| po | ||
| scripts | ||
| src | ||
| subprojects | ||
| tests | ||
| tools | ||
| .ctags | ||
| .dir-locals.el | ||
| .editorconfig | ||
| .gitattributes | ||
| .gitignore | ||
| .gitlab-ci.yml | ||
| .gitmodules | ||
| .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 | ||
| meson_options.txt | ||
| meson.build | ||
| NEWS.rst | ||
| README.rst | ||
| run.in | ||
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: