Hi, On Sat, Jun 22, 2019 at 07:17:15PM +0200, Raphaël Hertzog wrote: > Source: libvirt > Version: 5.0.0-4 > Severity: serious > > For a few days/weeks (I'm not sure when it started exactly), I can no > longer run my VM with virt-manager. > > On startup of libvirtd I have many messages like this one (one for each VM > I guess): > libvirtd[8281]: invalid argument: could not find capabilities for arch=x86_64 > domaintype=kvm > > When I try to start a VM I see this in the logs of libvirtd: > libvirtd[12569]: Unable to read from monitor: Connexion ré-initialisée par le > correspondant > libvirtd[12569]: internal error: qemu unexpectedly closed the monitor: Could > not access KVM kernel module: Permission denied > 2019-06-22T17:07:23.635870Z qemu-system-x86_64: failed to > initialize KVM: Permission denied > libvirtd[12569]: internal error: process exited while connecting to monitor: > Could not access KVM kernel module: Permission denied > 2019-06-22T17:07:23.635870Z qemu-system-x86_64: failed to > initialize KVM: Permission denied > > But I do have /dev/kvm and I have hardware virtualization enabled in the > BIOS.
Is that qemu://session or qemu://system? If one doesn't work, does the other? Output of - id libvirt-qemu - getfacl /dev/kvm - id please. The later is mostly relevant for qemu://session. Cheers, -- Guido
