Arch Linux

DeKay

Member

Registered: 2008-11-15

Posts: 14

[Solved] KVM internal error after Arch update

My setup was working great until a "pacman -Syu" this morning. Running on a Ryzen 1700. Kernel is now 5.8.13-arch1-1 and qemu version 5.1.0-1 trying to run a Win10 guest. Any ideas?

(qemu) KVM internal error. Suberror: 1
emulation failure
KVM internal error. Suberror: 1
<snip - same error repeated>
EAX=000f4eea EBX=00000000 ECX=000002ff EDX=00000005
ESI=00000000 EDI=00000000 EBP=00000000 ESP=00006ce0
EIP=000fd0a0 EFL=00000006 [-----P-] CPL=0 II=0 A20=1 SMM=0 HLT=0
ES =0010 00000000 ffffffff 00c09300 DPL=0 DS   [-WA]
<snip>

My qemu command line.  Note that I am passing through a graphics card here. 

qemu-system-x86_64 -name Windows10 -machine q35,accel=kvm,kernel_irqchip=on,usb=on -overcommit cpu-pm=on -m 8192 -cpu host,kvm=off,+invtsc,+topoext,hv_relaxed,hv_spinlocks=0x1fff,hv_vapic,hv_time,hv_vendor_id=whatever,hv_vpindex,hv_synic,hv_stimer,hv_reset,hv_runtime -smp 8,sockets=1,cores=4,threads=2 -device ioh3420,bus=pcie.0,multifunction=on,port=1,chassis=1,id=root.1 -device vfio-pci,host=2e:00.0,bus=root.1,multifunction=on,addr=00.0,x-vga=on,romfile=./169223.rom -device vfio-pci,host=2e:00.1,bus=root.1,addr=00.1 -vga none -boot order=cd -device vfio-pci,host=2f:00.3 -device virtio-mouse-pci -device virtio-keyboard-pci -object input-linux,id=kbd1,evdev=/dev/input/by-id/usb-Microsoft_Microsoft®_2.4GHz_Transceiver_v9.0-event-kbd,grab_all=on,repeat=on -object input-linux,id=mouse1,evdev=/dev/input/by-id/usb-ROCCAT_ROCCAT_Kone_Pure_Military-event-mouse -drive file=./Win10LTSC.qcow2,format=qcow2,index=0,media=disk,if=virtio -serial none -parallel none -rtc driftfix=slew,base=utc -global kvm-pit.lost_tick_policy=discard -monitor stdio

Posted question to reddit as well.

Edit: from looking at /var/cache/pacman/pkg, it was only the kernel that was updated.  Previous version was 5.7.11.arch1-1 I had been using since the end of July.

Solved: Figured it out by tedious trial and error of shortening the qemu command line until something worked. It seems "-overcommit cpu-pm=on" that I got from here is incompatible with the "-smp" option. Deleted the former and I'm back in business.

Hope this helps the next guy.

Last edited by DeKay (2020-11-15 13:47:27)