You are not logged in.
Hi, I'm trying to setup a PCI passthrough so a Windows guest VM can access my Video Card.
I've done my best to follow the guide. But when it comes time to begin the installation with virt-manager I run into an error.
I can't find the error I'm encountering in the guide, or online.
Unable to complete install: 'internal error: process exited while connecting to monitor: Could not access KVM kernel module: Permission denied
failed to initialize KVM: Permission denied'
Traceback (most recent call last):
File "/usr/share/virt-manager/virtManager/asyncjob.py", line 88, in cb_wrapper
callback(asyncjob, *args, **kwargs)
File "/usr/share/virt-manager/virtManager/create.py", line 2288, in _do_async_install
guest.start_install(meter=meter)
File "/usr/share/virt-manager/virtinst/guest.py", line 461, in start_install
doboot, transient)
File "/usr/share/virt-manager/virtinst/guest.py", line 396, in _create_guest
self.domain = self.conn.createXML(install_xml or final_xml, 0)
File "/usr/lib/python2.7/site-packages/libvirt.py", line 3777, in createXML
if ret is None:raise libvirtError('virDomainCreateXML() failed', conn=self)
libvirtError: internal error: process exited while connecting to monitor: Could not access KVM kernel module: Permission denied
failed to initialize KVM: Permission denied
P.S. Is there a way to format code in this forum?
Last edited by superiorplatypus (2016-07-17 00:36:13)
Offline
I'm having the same problem. So far I haven't been able to find a solution. Are you a member of the kvm group and does that group have read/write permissions for /dev/kvm?
Offline
The last time I used libvirt it worked out of the box. Now I'm stuck at the exact same problem. Any advice?
@OP: yes, use BB Tags [code.] and [/code.], but remove the dots.
EDIT:
After further investigation I found this forum thread.
They are mentioning a file called /etc/udev/rules.d/65-kvm.rules. Seems to be missing on my system.
Last edited by s4Ne (2017-08-04 00:21:13)
Offline
@s4Ne I suspect your issue will have a different cause.
What is the output of
$ getent group kvm
Offline
@loqs:
$ getent group kvm
kvm:x:999:s4ne
Just realized that we are in 2017... sorry for reviving this old thread.
Last edited by s4Ne (2017-08-04 00:24:31)
Offline
https://bugs.archlinux.org/task/54943
kvm is expected to have gid 78 but systemd 234 gives it a dynamic id or other patches need to be applied to deal with kvm not having that gid.
Also because the issue is caused by a change in systemd 234 it could not have been the cause of the superiorplatypus issue in 2016 due to 234's recent release.
Offline
Thanks for helping me out, I hope they will fix it soon...
Offline
I tried what was suggested in the issue, but had no luck.
chown -R 0:kvm /var/lib/libvirt/qemu doesn't persist after a reboot.
Commenting out the kvm group in basic.conf doesn't help.
When using the default CPU configuration I get
Unable to complete install: 'unsupported configuration: CPU mode 'custom' for x86_64 kvm domain on x86_64 host is not supported by hypervisor'
When I enabled "Copy host CPU configuration"
Unable to complete install: 'internal error: process exited while connecting to monitor: 2017-08-09T13:03:38.002488Z qemu-system-x86_64: -object secret,id=masterKey0,format=raw,file=/var/lib/libvirt/qemu/domain-4-generic/master-key.aes: Unable to read /var/lib/libvirt/qemu/domain-4-generic/master-key.aes: Failed to open file “/var/lib/libvirt/qemu/domain-4-generic/master-key.aes”: Permission denied'
Do you have any ideas what I'm doing wrong?
Offline
I would suggest changing group=78 to group=kvm in /etc/libvirt/qemu.conf or change the gid of the kvm group to 78 in /etc/group and rerun the chown command.
Offline
Thanks, it did the trick!
Offline
Thanks, it did the trick!
Which suggestion worked for you?
Offline
marmistrz wrote:Thanks, it did the trick!
Which suggestion worked for you?
Recently encountered this bug as well. Changing group=78 to group=kvm in /etc/libvirt/qemu.conf worked for me.
Offline