A C toolkit to interract with the virtualization capabilities of Linux
Libvirt is a C toolkit to interact with the virtualization
capabilities of Linux. Virtualization of the Linux Operating System means
the ability to run multiple instances of Operating Systems concurrently
on a single hardware system where the basic resources are driven by a
Linux instance. The library aims to provide long term stable C API
to interact with Linux virtualization technologies.
- Developed at Virtualization
- Sources inherited from project openSUSE:Factory
-
9
derived packages
- Download package
-
Checkout Package
osc -A https://api.opensuse.org checkout openSUSE:Factory:Rebuild/libvirt && cd $_
- Create Badge
Refresh
Refresh
Source Files
Filename | Size | Changed |
---|---|---|
README.packaging.txt | 0000000350 350 Bytes | |
_service | 0000000791 791 Bytes | |
baselibs.conf | 0000000098 98 Bytes | |
libvirt-10.3.0.tar.xz | 0009822088 9.37 MB | |
libvirt-rpmlintrc | 0000000189 189 Bytes | |
libvirt-supportconfig | 0000003429 3.35 KB | |
libvirt.changes | 0000231977 227 KB | |
libvirt.spec | 0000067534 66 KB | |
libvirtd-relocation-server.xml | 0000000224 224 Bytes | |
suse-qemu-domain-hook.py | 0000009555 9.33 KB |
Revision 398 (latest revision is 407)
Dominique Leuenberger (dimstar_suse)
accepted
request 1172820
from
James Fehlig (jfehlig)
(revision 398)
- CVE-2024-4418: rpc: ensure temporary GSource is removed from client event loop bsc#1223849 - libxl: Fix domxml-to-native conversion bsc#1222584
Comments 8
libvirt 4.7.0 has been released: ftp://libvirt.org/libvirt/libvirt-4.7.0.tar.xz
We need a resolution to bug#1106813 before libvirt 4.7.0 can be submitted to Factory. Note that I have 4.7.0 packaged and staged in my home project
https://build.opensuse.org/package/show/home:jfehlig:branches:Virtualization/libvirt
I couldn't find a place to report an issue, hopefully some developer take a look this comment
libvirt doesn't use the symbol g_uri_ref. There's likely something wrong with your libgobject installation. I just updated one of my TW machines and don't see the problem
Apparently this was an issue which can only be reproduced in the version
v1.0.20201025
of the vagrant box image , I upgraded it tov1.0.20201026
and the issue is gone. Thanks @jfehligVirtualBox is now at version 6.1.16. please update
The libvirt vbox driver is disabled. I'm happy to enable it if there is an interested maintainer.
oh i got the impression that libvirt maintainer also was the maintainer for Virtualbox. sorry for the confusion