Every time I try to start my virtual machines (they worked before I changed this system to use Artix) through virt-manager it comes up with this error:
Error starting domain: internal error: process exited while connecting to monitor: Could not access KVM kernel module: Permission denied
2018-07-08T17:10:31.289729Z qemu-system-x86_64: failed to initialize KVM: Permission denied
Traceback (most recent call last):
File "/usr/share/virt-manager/virtManager/asyncjob.py", line 89, in cb_wrapper
callback(asyncjob, *args, **kwargs)
File "/usr/share/virt-manager/virtManager/asyncjob.py", line 125, in tmpcb
callback(*args, **kwargs)
File "/usr/share/virt-manager/virtManager/libvirtobject.py", line 82, in newfn
ret = fn(self, *args, **kwargs)
File "/usr/share/virt-manager/virtManager/domain.py", line 1508, in startup
self._backend.create()
File "/usr/lib/python2.7/site-packages/libvirt.py", line 1068, in create
if ret == -1: raise libvirtError ('virDomainCreate() failed', dom=self)
libvirtError: internal error: process exited while connecting to monitor: Could not access KVM kernel module: Permission denied
2018-07-08T17:10:31.289729Z qemu-system-x86_64: failed to initialize KVM: Permission denied
I added my user to the kvm and libvirt groups, to no avail. Adding myself to libvirt did remove the password prompt, so that's at least something. Looks like the problem here is that my user can't access /dev/kvm, since cat /dev/kvm returns with "Permission denied" as well. What is up here?
Also, to even get libvirtd to start I had to comment out the need firewalld line in /etc/init.d/libvirtd or run it with rc-service start libvirtd -D, otherwise it would complain that that service doesn't exist. Pretty sure this has nothing to do with this issue, but it's a bit strange in my opinion.