我有同样的问题这里,但该解决方案对我不起作用。每次我想使用 virt-manager 创建或运行虚拟机时,我都会收到相同的消息:
Error al iniciar dominio: configuración no soportada: CPU mode 'custom' for x86_64 kvm domain on x86_64 host is not supported by hypervisor
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 1069, in create
if ret == -1: raise libvirtError ('virDomainCreate() failed', dom=self)
libvirtError: configuración no soportada: CPU mode 'custom' for x86_64 kvm domain on x86_64 host is not supported by hypervisor
然而,当从提到的线程应用修复时,我得到:
Error al iniciar dominio: internal error: process exited while connecting to monitor: Could not access KVM kernel module: Permission denied
2018-03-13T22:43:10.555542Z 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 1069, 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-03-13T22:43:10.555542Z qemu-system-x86_64: failed to initialize KVM: Permission denied
我也以 root 身份尝试过,但结果相同。
我的系统是 Parabola GNU/Linux-libre (Arch-based) x86_64
答案1
尝试重新启动主机。
这看起来很奇怪,但它就发生在我身上。我正在使用 debianstretch,并且在安装后第一次在 KVM 上安装 gust 操作系统(ubuntu 的某些发行版)时,我收到了相同的警报。我关闭了主机,导致问题未解决,第二天再次尝试时,完全没有错误。与此同时,我什么也没做。 KVM 可能需要重新启动才能完成安装或收集必要的数据。虽然我不确定 arch,但你可以在继续寻找另一个解决方案之前尝试一下。
答案2
我遇到了同样的问题,问题是 libvirt 无法访问/dev/kvm
.因此,您需要确保用户具有访问设备节点的正确权限,例如,通过运行chown root.kvm /dev/kvm;chmod 660 /dev/kvm
.
我想它只是尝试机器配置并在任何不起作用时返回此错误,因为它认为配置是问题所在。