# virsh start rr00

(using root or any other user with correct group assignments) fails with

error: Failed to start domain 'rr00'
error: internal error: process exited while connecting to monitor: Could not access KVM kernel module: Permission denied
2024-03-20T13:13:36.931920Z qemu-system-x86_64: -accel kvm: failed to initialize kvm: Permission denied

Same problem for other domains. strace -f doesn't show any EPERM problems,
so what is it trying to tell me? Using virtmanager I get a python traceback:

Traceback (most recent call last):
   File "/usr/share/virt-manager/virtManager/asyncjob.py", line 72, in cb_wrapper
     callback(asyncjob, *args, **kwargs)
   File "/usr/share/virt-manager/virtManager/asyncjob.py", line 108, in tmpcb
     callback(*args, **kwargs)
   File "/usr/share/virt-manager/virtManager/object/libvirtobject.py", line 57, in newfn
     ret = fn(self, *args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^
   File "/usr/share/virt-manager/virtManager/object/domain.py", line 1402, in startup
     self._backend.create()
   File "/usr/lib/python3/dist-packages/libvirt.py", line 1373, in create
     raise libvirtError('virDomainCreate() failed')
libvirt.libvirtError: internal error: process exited while connecting to monitor: Could not access KVM kernel module: Permission denied
2024-03-20T13:01:34.319848Z qemu-system-x86_64: -accel kvm: failed to initialize kvm: Permission denied


On the other hand, a simple kvm command line using the same root disk, like

# kvm -drive file=/dev/storage/rr00.vda.lv

seems to work without problems.


Do you think the misleading error message could be improved to provide the
missing details?


Regards

Harri