Qemu/KVM Win10 Client slows down over time and crashes

rwo · 2020-05-15 16:50:05

My setup consists of a Win10 client vm running on an arch host. I manage the vm with virt-manager. The vm files are located on a LUKS encrypted partition. In the first moments after start, the vm works fine and nothing lags. After a runtime of 1-3 hours it gets continuous more laggy and crashes finally. The lag could be described as stop and go. This manifests in the windows shutdown indicator, which stops it's rotation and then continues. The host is not influenced by the vm problem. After a vm shutdown and restart the vm works fine again. How could i diagnose or solve this problem?

My virt manager config(filepath changed):

<domain type='kvm'>
  <name>win10</name>
  <uuid>76eac028-9f57-4b56-adcf-cffbf918d393</uuid>
  <metadata>
    <libosinfo:libosinfo xmlns:libosinfo="http://libosinfo.org/xmlns/libvirt/domain/1.0">
      <libosinfo:os id="http://microsoft.com/win/10"/>
    </libosinfo:libosinfo>
  </metadata>
  <memory unit='KiB'>25600000</memory>
  <currentMemory unit='KiB'>25600000</currentMemory>
  <memoryBacking>
    <hugepages/>
  </memoryBacking>
  <vcpu placement='static' current='5'>12</vcpu>
  <os>
    <type arch='x86_64' machine='pc-q35-4.2'>hvm</type>
    <loader readonly='yes' type='pflash'>/usr/share/ovmf/x64/OVMF_CODE.fd</loader>
    <nvram>/var/lib/libvirt/qemu/nvram/win10_VARS.fd</nvram>
    <boot dev='hd'/>
  </os>
  <features>
    <acpi/>
    <apic/>
    <hyperv>
      <relaxed state='on'/>
      <vapic state='on'/>
      <spinlocks state='on' retries='8191'/>
    </hyperv>
    <vmport state='off'/>
  </features>
  <cpu mode='host-model' check='none'>
    <topology sockets='1' cores='6' threads='2'/>
  </cpu>
  <clock offset='localtime'>
    <timer name='hpet' present='yes'/>
    <timer name='hypervclock' present='yes'/>
  </clock>
  <on_poweroff>destroy</on_poweroff>
  <on_reboot>restart</on_reboot>
  <on_crash>destroy</on_crash>
  <pm>
    <suspend-to-mem enabled='no'/>
    <suspend-to-disk enabled='no'/>
  </pm>
  <devices>
    <emulator>/usr/bin/qemu-system-x86_64</emulator>
    <disk type='file' device='disk'>
      <driver name='qemu' type='qcow2' cache='none' io='native'/>
      <source file='asdf.qcow2'/>
      <target dev='vda' bus='virtio'/>
      <address type='pci' domain='0x0000' bus='0x04' slot='0x00' function='0x0'/>
    </disk>
    <controller type='usb' index='0' model='qemu-xhci' ports='15'>
      <address type='pci' domain='0x0000' bus='0x02' slot='0x00' function='0x0'/>
    </controller>
    <controller type='sata' index='0'>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x1f' function='0x2'/>
    </controller>
    <controller type='pci' index='0' model='pcie-root'/>
    <controller type='pci' index='1' model='pcie-root-port'>
      <model name='pcie-root-port'/>
      <target chassis='1' port='0x10'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0' multifunction='on'/>
    </controller>
    <controller type='pci' index='2' model='pcie-root-port'>
      <model name='pcie-root-port'/>
      <target chassis='2' port='0x11'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x1'/>
    </controller>
    <controller type='pci' index='3' model='pcie-root-port'>
      <model name='pcie-root-port'/>
      <target chassis='3' port='0x12'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x2'/>
    </controller>
    <controller type='pci' index='4' model='pcie-root-port'>
      <model name='pcie-root-port'/>
      <target chassis='4' port='0x13'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x3'/>
    </controller>
    <controller type='pci' index='5' model='pcie-root-port'>
      <model name='pcie-root-port'/>
      <target chassis='5' port='0x14'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x4'/>
    </controller>
    <controller type='pci' index='6' model='pcie-root-port'>
      <model name='pcie-root-port'/>
      <target chassis='6' port='0x15'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x5'/>
    </controller>
    <controller type='pci' index='7' model='pcie-root-port'>
      <model name='pcie-root-port'/>
      <target chassis='7' port='0x16'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x6'/>
    </controller>
    <controller type='pci' index='8' model='pcie-to-pci-bridge'>
      <model name='pcie-pci-bridge'/>
      <address type='pci' domain='0x0000' bus='0x06' slot='0x00' function='0x0'/>
    </controller>
    <controller type='virtio-serial' index='0'>
      <address type='pci' domain='0x0000' bus='0x03' slot='0x00' function='0x0'/>
    </controller>
    <interface type='network'>
      <mac address='52:54:00:1f:17:ed'/>
      <source network='default'/>
      <model type='virtio'/>
      <link state='up'/>
      <address type='pci' domain='0x0000' bus='0x01' slot='0x00' function='0x0'/>
    </interface>
    <channel type='spicevmc'>
      <target type='virtio' name='com.redhat.spice.0'/>
      <address type='virtio-serial' controller='0' bus='0' port='1'/>
    </channel>
    <input type='tablet' bus='usb'>
      <address type='usb' bus='0' port='1'/>
    </input>
    <input type='mouse' bus='ps2'/>
    <input type='keyboard' bus='ps2'/>
    <graphics type='spice' autoport='yes'>
      <listen type='address'/>
      <image compression='off'/>
    </graphics>
    <sound model='ich9'>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x1b' function='0x0'/>
    </sound>
    <video>
      <model type='qxl' ram='262144' vram='262144' vgamem='65536' heads='1' primary='yes'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x0'/>
    </video>
    <hostdev mode='subsystem' type='usb' managed='no'>
      <source>
        <vendor id='0x0bda'/>
        <product id='0x0165'/>
      </source>
      <address type='usb' bus='0' port='5'/>
    </hostdev>
    <redirdev bus='usb' type='spicevmc'>
      <address type='usb' bus='0' port='3'/>
    </redirdev>
    <memballoon model='virtio'>
      <address type='pci' domain='0x0000' bus='0x05' slot='0x00' function='0x0'/>
    </memballoon>
  </devices>
</domain>

sxmwht · 2020-05-15 16:58:00

This is happening to me too, it never used to, but since I updated recently, the issue has arisen. If I start a game, it happens very quickly.

I have disabled the virtual sound device, and that has helped. When the issue happens, task manager in the Windows guest shows "System interrupts" using 100% of the CPU. So I believe it's some sort of driver issue.

post-factum · 2020-05-15 17:57:52

What's your qemu pkg version? Make sure you stay up to date in order to not hit [1].

[1] https://bugs.archlinux.org/task/66578

rwo · 2020-05-15 19:16:06

I use version 5.0.0-5.

[rwo@pc ~]$ /usr/bin/qemu-system-x86_64 --version
QEMU emulator version 5.0.0
Copyright (c) 2003-2020 Fabrice Bellard and the QEMU Project developers

[rwo@pc ~]$ pacman -Q --info qemu
Name            : qemu
Version         : 5.0.0-5

I upgraded to 5.0.0-6 with the following command. I will try it now.

sudo pacman -U https://www.archlinux.org/packages/extra/x86_64/qemu/download/

[rwo@pc ~]$ pacman -Q --info qemu
Name            : qemu
Version         : 5.0.0-6

Last edited by rwo (2020-05-15 19:16:23)

post-factum · 2020-05-15 19:21:46

5.0.0-5 is indeed affected while 5.0.0-6 is not. So hopefully the issue will be fixed for you.

Also make sure to not do partial upgrade and download packages randomly. Use -Syu instead.

loqs · 2020-05-15 19:22:13

rwo wrote:

I upgraded to 5.0.0-6 with the following command. I will try it now.
sudo pacman -U https://www.archlinux.org/packages/extra/x86_64/qemu/download/

Why did you not update the system using `pacman -Syu` to update to qemu 5.0.0-6?
Edit:
See https://bbs.archlinux.org/viewtopic.php?id=130309 second point and Partial upgrades are unsupported.

Last edited by loqs (2020-05-15 19:55:54)

sxmwht · 2020-05-18 08:20:34

Yep, the latest Qemu fixed this for me. Which is nice, because I did a huge upgrade with Qemu, kernel, and I'd installed virtio drivers in my VM etc., all in one go, so I didn't even know where to start

Arch Linux

#1 2020-05-15 16:50:05

Qemu/KVM Win10 Client slows down over time and crashes

#2 2020-05-15 16:58:00

Re: Qemu/KVM Win10 Client slows down over time and crashes

#3 2020-05-15 17:57:52

Re: Qemu/KVM Win10 Client slows down over time and crashes

#4 2020-05-15 19:16:06

Re: Qemu/KVM Win10 Client slows down over time and crashes

#5 2020-05-15 19:21:46

Re: Qemu/KVM Win10 Client slows down over time and crashes

#6 2020-05-15 19:22:13

Re: Qemu/KVM Win10 Client slows down over time and crashes

#7 2020-05-18 08:20:34

Re: Qemu/KVM Win10 Client slows down over time and crashes

Board footer