[SOLVED] Probelms with QEMU/KVM.

Simulacrum · 2017-08-04 11:11:45

Hello everyone.

I recently reinstalled my Arch-Linux and installed QEMU/KVM, Virt-Manager and so on. A full List of installed Packages (depending on this topic) is here:

[user@Machine ~]$ pacman -Qe | grep qemu
qemu 2.9.0-2
qemu-arch-extra 2.9.0-2
qemu-block-gluster 2.9.0-2
qemu-block-iscsi 2.9.0-2
qemu-block-rbd 2.9.0-2
[user@Machine ~]$ pacman -Qe | grep virt-manager
virt-manager 1.4.1-2
[user@Machine ~]$ pacman -Qe | grep firewall
firewalld 0.4.4.5-1
[user@Machine ~]$ pacman -Qe | grep dnsmasq
dnsmasq 2.77-1

I tried different things. For example, I imported a ready-to-use template, but if i try to start, the following Error appears:

Error starting domain: unsupported configuration: 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 88, in cb_wrapper
callback(asyncjob, *args, **kwargs)
File "/usr/share/virt-manager/virtManager/asyncjob.py", line 124, in tmpcb
callback(*args, **kwargs)
File "/usr/share/virt-manager/virtManager/libvirtobject.py", line 83, in newfn
ret = fn(self, *args, **kwargs)
File "/usr/share/virt-manager/virtManager/domain.py", line 1479, in startup
self._backend.create()
File "/usr/lib/python2.7/site-packages/libvirt.py", line 1062, in create
if ret == -1: raise libvirtError ('virDomainCreate() failed', dom=self)
libvirtError: unsupported configuration: CPU mode 'custom' for x86_64 kvm domain on x86_64 host is not supported by hypervisor

When i try to install a new virtual machine (where i set the CPU to copy the hosts configuration) , the following Error appears:

Unable to complete install: 'internal error: process exited while connecting to monitor: 1,masterbus=usb.0,firstport=0,bus=pci.0,multifunction=on,addr=0x5 -device ich9-usb-uhci2,masterbus=usb.0,firstport=2,bus=pci.0,addr=0x5.0x1 -device ich9-usb-uhci3,masterbus=usb.0,firstport=4,bus=pci.0,addr=0x5.0x2 -device virtio-serial-pci,id=virtio-serial0,bus=pci.0,addr=0x6 -drive file=/mnt/hdd/vm_storage/saveweb,format=raw,if=none,id=drive-ide0-0-0 -device ide-hd,bus=ide.0,unit=0,drive=drive-ide0-0-0,id=ide0-0-0,bootindex=2 -drive file=/mnt/hdd/isos/ubuntu-budgie-17.04-desktop-amd64.iso,format=raw,if=none,id=drive-ide0-0-1,readonly=on -device ide-cd,bus=ide.0,unit=1,drive=drive-ide0-0-1,id=ide0-0-1,bootindex=1 -netdev tap,fd=25,id=hostnet0 -device rtl8139,netdev=hostnet0,id=net0,mac=52:54:00:cb:97:7b,bus=pci.0,addr=0x3 -chardev pty,id=charserial0 -device isa-serial,chardev=charserial0,id=serial0 -chardev spicevmc,id=charchannel0,name=vdagent -device virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=com.redhat.spice.0 -spice port=590'
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 477, in start_install
doboot, transient)
File "/usr/share/virt-manager/virtinst/guest.py", line 405, in _create_guest
self.domain.create()
File "/usr/lib/python2.7/site-packages/libvirt.py", line 1062, in create
if ret == -1: raise libvirtError ('virDomainCreate() failed', dom=self)
libvirtError: internal error: process exited while connecting to monitor: 1,masterbus=usb.0,firstport=0,bus=pci.0,multifunction=on,addr=0x5 -device ich9-usb-uhci2,masterbus=usb.0,firstport=2,bus=pci.0,addr=0x5.0x1 -device ich9-usb-uhci3,masterbus=usb.0,firstport=4,bus=pci.0,addr=0x5.0x2 -device virtio-serial-pci,id=virtio-serial0,bus=pci.0,addr=0x6 -drive file=/mnt/hdd/vm_storage/saveweb,format=raw,if=none,id=drive-ide0-0-0 -device ide-hd,bus=ide.0,unit=0,drive=drive-ide0-0-0,id=ide0-0-0,bootindex=2 -drive file=/mnt/hdd/isos/ubuntu-budgie-17.04-desktop-amd64.iso,format=raw,if=none,id=drive-ide0-0-1,readonly=on -device ide-cd,bus=ide.0,unit=1,drive=drive-ide0-0-1,id=ide0-0-1,bootindex=1 -netdev tap,fd=25,id=hostnet0 -device rtl8139,netdev=hostnet0,id=net0,mac=52:54:00:cb:97:7b,bus=pci.0,addr=0x3 -chardev pty,id=charserial0 -device isa-serial,chardev=charserial0,id=serial0 -chardev spicevmc,id=charchannel0,name=vdagent -device virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=com.redhat.spice.0 -spice port=590

Obviously, this is another Error then above. As is changed the CPU configuration for the template to above "Copy hosts CPU configuration", the following error appeared:

Error starting domain: 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/asyncjob.py", line 124, in tmpcb
callback(*args, **kwargs)
File "/usr/share/virt-manager/virtManager/libvirtobject.py", line 83, in newfn
ret = fn(self, *args, **kwargs)
File "/usr/share/virt-manager/virtManager/domain.py", line 1479, in startup
self._backend.create()
File "/usr/lib/python2.7/site-packages/libvirt.py", line 1062, 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
failed to initialize KVM: Permission denied

Which leads me to the thinking that there are some problems with the permissions (no shit). My user-info:

passwd-Output:

[user@Machine ~]$ cat /etc/passwd
root:x:0:0:root:/root:/bin/bash
bin:x:1:1:bin:/bin:/usr/bin/nologin
daemon:x:2:2:daemon:/:/usr/bin/nologin
mail:x:8:12:mail:/var/spool/mail:/usr/bin/nologin
ftp:x:14:11:ftp:/srv/ftp:/usr/bin/nologin
http:x:33:33:http:/srv/http:/usr/bin/nologin
nobody:x:99:99:nobody:/:/usr/bin/nologin
systemd-journal-gateway:x:191:191:systemd-journal-gateway:/:/usr/bin/nologin
systemd-timesync:x:192:192:systemd-timesync:/:/usr/bin/nologin
systemd-network:x:193:193:systemd-network:/:/usr/bin/nologin
systemd-bus-proxy:x:194:194:systemd-bus-proxy:/:/usr/bin/nologin
systemd-resolve:x:195:195:systemd-resolve:/:/usr/bin/nologin
systemd-coredump:x:996:996:systemd Core Dumper:/:/sbin/nologin
dbus:x:81:81::/:/sbin/nologin
systemd-journal-upload:x:998:998:systemd Journal Upload:/:/sbin/nologin
uuidd:x:68:68::/:/sbin/nologin
systemd-journal-remote:x:997:997:systemd Journal Remote:/:/sbin/nologin
user:x:1000:100::/home/user:/bin/bash
avahi:x:84:84:avahi:/:/bin/nologin
sddm:x:995:995:Simple Desktop Display Manager:/var/lib/sddm:/usr/bin/nologin
polkitd:x:102:102:Policy Kit Daemon:/:/usr/bin/nologin
rtkit:x:133:133:RealtimeKit:/proc:/bin/false
usbmux:x:140:140:usbmux user:/:/sbin/nologin
colord:x:124:124::/var/lib/colord:/bin/false
git:x:994:994:git daemon user:/:/bin/bash
tor:x:43:43::/var/lib/tor:/bin/false
ceph:x:991:991::/run/ceph:/sbin/nologin
dnsmasq:x:990:990:dnsmasq daemon:/:/sbin/nologin

My groups:

[user@Machine ~]$ groups user
lp wheel optical storage scanner power kvm libvirt users

Another, probably relevent information: I isolated a PCI-e slot to pass my dedicated GPU to a guest. i followed the steps described here https://wiki.archlinux.org/index.php/PC … h_via_OVMF

So, the output of the "checkings" is:

[user@Machine ~]$ dmesg|grep -e DMAR -e IOMMU
[ 0.000000] ACPI: DMAR 0x000000006EE705C8 0000A8 (v01 INTEL KBL 0000000
1 INTL 00000001)
[ 0.000000] DMAR: IOMMU enabled
[ 0.029280] DMAR: Host address width 39
[ 0.029281] DMAR: DRHD base: 0x000000fed90000 flags: 0x0
[ 0.029284] DMAR: dmar0: reg_base_addr fed90000 ver 1:0 cap 1c0000c40660462 ecap 19e2ff0505e
[ 0.029285] DMAR: DRHD base: 0x000000fed91000 flags: 0x1
[ 0.029287] DMAR: dmar1: reg_base_addr fed91000 ver 1:0 cap d2008c40660462 ecap f050da
[ 0.029287] DMAR: RMRR base: 0x0000006e618000 end: 0x0000006e637fff
[ 0.029289] DMAR: RMRR base: 0x0000006f800000 end: 0x0000007fffffff
[ 0.029290] DMAR-IR: IOAPIC id 2 under DRHD base 0xfed91000 IOMMU 1
[ 0.029290] DMAR-IR: HPET id 0 under DRHD base 0xfed91000
[ 0.029291] DMAR-IR: Queued invalidation will be enabled to support x2apic and Intr-remapping.
[ 0.030627] DMAR-IR: Enabled IRQ remapping in x2apic mode
[ 1.041735] DMAR: No ATSR found
[ 1.042060] DMAR: dmar0: Using Queued invalidation
[ 1.042150] DMAR: dmar1: Using Queued invalidation
[ 1.042353] DMAR: Setting RMRR:
[ 1.042404] DMAR: Setting identity map for device 0000:00:02.0 [0x6f800000 - 0x7fffffff]
[ 1.042425] DMAR: Setting identity map for device 0000:00:14.0 [0x6e618000 - 0x6e637fff]
[ 1.042428] DMAR: Prepare 0-16MiB unity mapping for LPC
[ 1.042443] DMAR: Setting identity map for device 0000:00:1f.0 [0x0 - 0xffffff]
[ 1.042600] DMAR: Intel(R) Virtualization Technology for Directed I/O

The script output:

[user@Machine ~]$ ./script_for_valid_groups.sh
IOMMU Group 0 00:00.0 Host bridge [0600]: Intel Corporation Device [8086:591f] (
rev 05)
IOMMU Group 10 00:1f.6 Ethernet controller [0200]: Intel Corporation Ethernet Co
nnection (2) I219-V [8086:15b8]
IOMMU Group 1 00:01.0 PCI bridge [0604]: Intel Corporation Skylake PCIe Controll
er (x16) [8086:1901] (rev 05)
IOMMU Group 1 01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GP104
[GeForce GTX 1070] [10de:1b81] (rev a1)
IOMMU Group 1 01:00.1 Audio device [0403]: NVIDIA Corporation GP104 High Definit
ion Audio Controller [10de:10f0] (rev a1)
IOMMU Group 2 00:02.0 VGA compatible controller [0300]: Intel Corporation Device [8086:5912] (rev 04)
IOMMU Group 3 00:14.0 USB controller [0c03]: Intel Corporation 200 Series PCH USB 3.0 xHCI Controller [8086:a2af]
IOMMU Group 3 00:14.2 Signal processing controller [1180]: Intel Corporation 200 Series PCH Thermal Subsystem [8086:a2b1]
IOMMU Group 4 00:16.0 Communication controller [0780]: Intel Corporation 200 Series PCH CSME HECI #1 [8086:a2ba]
IOMMU Group 5 00:17.0 SATA controller [0106]: Intel Corporation 200 Series PCH SATA controller [AHCI mode] [8086:a282]
IOMMU Group 6 00:1b.0 PCI bridge [0604]: Intel Corporation 200 Series PCH PCI Express Root Port #17 [8086:a2e7] (rev f0)
IOMMU Group 7 00:1c.0 PCI bridge [0604]: Intel Corporation 200 Series PCH PCI Express Root Port #1 [8086:a290] (rev f0)
IOMMU Group 8 00:1d.0 PCI bridge [0604]: Intel Corporation 200 Series PCH PCI Express Root Port #9 [8086:a298] (rev f0)
IOMMU Group 9 00:1f.0 ISA bridge [0601]: Intel Corporation 200 Series PCH LPC Controller (Z270) [8086:a2c5]
IOMMU Group 9 00:1f.2 Memory controller [0580]: Intel Corporation 200 Series PCH PMC [8086:a2a1]
IOMMU Group 9 00:1f.3 Audio device [0403]: Intel Corporation 200 Series PCH HD Audio [8086:a2f0]
IOMMU Group 9 00:1f.4 SMBus [0c05]: Intel Corporation 200 Series PCH SMBus Controller [8086:a2a3]

The modinfo options:

[user@Machine ~]$ cat /etc/modprobe.d/vfio.conf
options vfio-pci ids=10de:1b81,10de:10f0

my modules:

[user@Machine ~]$ cat /etc/mkinitcpio.conf | grep -e MODULES
# MODULES
# MODULES="piix ide_disk reiserfs"
MODULES="vfio vfio_iommu_type1 vfio_pci vfio_virqfd"
# 'filesystems' is _required_ unless you specify your fs modules in MODULES
## This setup specifies all modules in the MODULES setting above.

"modconf" is also in the kernel-hooks.

vfio should have loaded properly:

[user@Machine ~]$ dmesg | grep -i vfio
[ 1.306948] VFIO - User Level meta-driver version: 0.3
[ 1.307929] vfio-pci 0000:01:00.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=none
[ 1.325085] vfio_pci: add [10de:1b81[ffff:ffff]] class 0x000000/00000000
[ 1.345066] vfio_pci: add [10de:10f0[ffff:ffff]] class 0x000000/00000000
[ 20.495961] vfio-pci 0000:01:00.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=none
[ 21.201868] syscopyarea sysfillrect battery sysimgblt fb_sys_fops i2c_algo_bit ecdh_generic shpchp rfkill i2c_hid video intel_lpss_acpi intel_lpss acpi_als kfifo_buf wmi industrialio tpm_tis tpm_tis_core tpm button acpi_pad sch_fq_codel ip_tables x_tables ext4 crc16 jbd2 fscrypto mbcache algif_skcipher af_alg dm_crypt dm_mod dax sd_mod hid_generic usbhid hid crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel pcbc aesni_intel aes_x86_64 crypto_simd glue_helper cryptd ahci libahci xhci_pci libata xhci_hcd scsi_mod usbcore usb_common serio vfio_pci irqbypass vfio_virqfd vfio_iommu_type1 vfio
[ 21.214190] syscopyarea sysfillrect battery sysimgblt fb_sys_fops i2c_algo_bit ecdh_generic shpchp rfkill i2c_hid video intel_lpss_acpi intel_lpss acpi_als kfifo_buf wmi industrialio tpm_tis tpm_tis_core tpm button acpi_pad sch_fq_codel ip_tables x_tables ext4 crc16 jbd2 fscrypto mbcache algif_skcipher af_alg dm_crypt dm_mod dax sd_mod hid_generic usbhid hid crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel pcbc aesni_intel aes_x86_64 crypto_simd glue_helper cryptd ahci libahci xhci_pci libata xhci_hcd scsi_mod usbcore usb_common serio vfio_pci irqbypass vfio_virqfd vfio_iommu_type1 vfio

I hope i provided enough information for now. I'm just wondering, because my laptop works finde with the same programm... (but its not the same hardware, though... ). Sorry for my bad english and thanks in advance

Greetings
Simulacrum

Last edited by Simulacrum (2017-08-04 13:22:12)

loqs · 2017-08-04 11:16:15

https://bbs.archlinux.org/viewtopic.php … 1#p1728381?

Simulacrum · 2017-08-04 11:43:11

it worked. Thanks mate, and sorry for my incapacity to use the search function (to be honest, i searched the search-function, didn't found it)

Can be closed.

loqs · 2017-08-04 11:47:00

Normally when a solution is found, you would mark your thread as solved by editing the first post and prepending the tag [SOLVED] to the title in the "Subject" field.
If you wish it to be closed/deleted please use the report button to contact a moderator who can perform that action.

Simulacrum · 2017-08-04 13:22:46

Edited. I just thought it could be closed because the topic is already covered by the thread mentioned above. Thanks

Arch Linux

#1 2017-08-04 11:11:45

[SOLVED] Probelms with QEMU/KVM.

#2 2017-08-04 11:16:15

Re: [SOLVED] Probelms with QEMU/KVM.

#3 2017-08-04 11:43:11

Re: [SOLVED] Probelms with QEMU/KVM.

#4 2017-08-04 11:47:00

Re: [SOLVED] Probelms with QEMU/KVM.

#5 2017-08-04 13:22:46

Re: [SOLVED] Probelms with QEMU/KVM.

Board footer