Bug#1033872: Hotplug of vsock device fails: No file descriptor supplied via SCM_RIGHTS

Package: libvirt Version: 9.0.0 Hotplug of vsock device fails with "unable to execute QEMU command 'getfd': No file descriptor supplied via SCM_RIGHTS" 1. Have a running VM 2. Hotplug vsock device, for example by running: virt-xml vmName --add-device --vsock cid.auto=no,cid.address=8 --update A

Bug#1032990: podman unshare sults in chown: Invalid argument

Package: podman Version: 4.3.1. System information: Distributor ID: Debian Description:Debian GNU/Linux bookworm/sid Release:testing Codename: bookworm Description: "podman unshare chown 1:1 ~/somefile" fails Steps to reproduce: 1. touch ~/somefile 2. podman unshare chown 1:1 ~/

Bug#1007916: virtinst: VM creation fails: Could not open '/var/lib/libvirt/qemu/nvram/VmNotInstalled_VARS.fd'

Package: virtinst Version: 4.0.0 VM creation using virt-install with flag --boot uefi fails 1. Have som qcow2 disk, let's say at /var/lib/libvirt/images/myDisk.qcow2 2. Create VM using: virt-install --connect qemu:///system --name VmNotInstalled --os-variant fedora28 --memory 2048 --noautoconsol

Bug#1005284: Hotplug of interface with virtio model to libvirt VM fails after VM was restarted

Package: libvirt Version: 8.0.0 Hot-unplugging a virtual network interface with "virito" model from a running VM, restarting the VM and trying to hot-plug the same virtual network interface fails. You can recreate problem by running these steps: 0. (Have some VM, let's call it "vm1") 1. echo ""

Bug#979964: Apparmor bpf and perfmon capname denial when creating a libvirt VM

Package: apparmor Version: 2.13.6-3 -- System information: Linux debian 5.9.0-5-cloud-amd64 #1 SMP Debian 5.9.15-1 (2020-12-17) x86_64 GNU/Linux When creating a new VM on a clean instance of debian bullseye, the following apparmor denial is printed to /var/log/kern.log: Jan 12 11:16:08 debian ke