You are not logged in.

#1 2020-05-08 00:51:03

BIllzargo
Member
Registered: 2019-09-29
Posts: 7

Windows VM through virt manager now slows down until locks it up

I have been using a VM in Arch with Virtual Machine Manager for a while for Visual Studio for work. After an update it is now slowing down slowly, sometime quickly until it completely locks up. I have checked driver latency which gets crazy in Windows and even disabled some drivers etc, but it has to be Arch which is the problem because I created a new Windows VM which locked up even before I added any drivers. I did noticed there was a spice upgrade which happened around the time of this issue. I tried downgrader and it did not resolve the issue. I don't know if it was a Linux upgrade etc. When I log out I do get a weird message saying there is multiple instances of this:

https://i.ibb.co/RCdT53L/Power-Off-Error.png


Any help would be great as I need this for work. Let me know if you need any files or information, I will provide it.


Virtual Machine:

<domain type="kvm">
  <name>Windows10</name>
  <uuid>8b347556-5758-4d24-99a3-e6410bf12ee2</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">12582912</memory>
  <currentMemory unit="KiB">12582912</currentMemory>
  <vcpu placement="static">8</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/Windows10_VARS.fd</nvram>
    <bootmenu enable="no"/>
  </os>
  <features>
    <acpi/>
    <apic/>
    <hyperv>
      <relaxed state="on"/>
      <vapic state="on"/>
      <spinlocks state="on" retries="8191"/>
      <vendor_id state="on" value="123456789abc"/>
    </hyperv>
    <kvm>
      <hidden state="on"/>
    </kvm>
    <vmport state="off"/>
  </features>
  <cpu mode="host-passthrough" check="none">
    <topology sockets="1" cores="4" threads="2"/>
    <feature policy="require" name="vmx"/>
  </cpu>
  <clock offset="localtime">
    <timer name="rtc" tickpolicy="catchup"/>
    <timer name="pit" tickpolicy="delay"/>
    <timer name="hpet" present="no"/>
    <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"/>
      <source file="/repository/VirtualBoxVMs/Windows10/Win10.qcow2"/>
      <target dev="sda" bus="sata"/>
      <boot order="1"/>
      <address type="drive" controller="0" bus="0" target="0" unit="0"/>
    </disk>
    <disk type="file" device="cdrom">
      <driver name="qemu" type="raw"/>
      <source file="/repository/shared/win-software/Win10_1903_V2_EnglishInternational_x64.iso"/>
      <target dev="sdb" bus="sata"/>
      <readonly/>
      <address type="drive" controller="0" bus="0" target="0" unit="1"/>
    </disk>
    <disk type="file" device="cdrom">
      <driver name="qemu" type="raw"/>
      <source file="/home/bill/Downloads/virtio-win-0.1.171.iso"/>
      <target dev="sdc" bus="sata"/>
      <readonly/>
      <address type="drive" controller="0" bus="0" target="0" unit="2"/>
    </disk>
    <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="0x04" slot="0x00" function="0x0"/>
    </controller>
    <controller type="virtio-serial" index="0">
      <address type="pci" domain="0x0000" bus="0x03" slot="0x00" function="0x0"/>
    </controller>
    <controller type="usb" index="0" model="qemu-xhci">
      <address type="pci" domain="0x0000" bus="0x02" slot="0x00" function="0x0"/>
    </controller>
    <interface type="bridge">
      <mac address="52:54:00:b5:d5:30"/>
      <source bridge="bridge0"/>
      <model type="e1000e"/>
      <address type="pci" domain="0x0000" bus="0x01" slot="0x00" function="0x0"/>
    </interface>
    <serial type="pty">
      <target type="isa-serial" port="0">
        <model name="isa-serial"/>
      </target>
    </serial>
    <console type="pty">
      <target type="serial" port="0"/>
    </console>
    <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="65536" vram="65536" vgamem="65536" heads="1" primary="yes"/>
      <address type="pci" domain="0x0000" bus="0x00" slot="0x01" function="0x0"/>
    </video>
    <memballoon model="virtio">
      <address type="pci" domain="0x0000" bus="0x05" slot="0x00" function="0x0"/>
    </memballoon>
  </devices>
</domain>

Computer Specs
Intel Core i9 9900K Octa Core LGA 1151 3.60GHz Unlocked CPU Processor
Gigabyte Z390 AORUS MASTER LGA 1151 ATX Motherboard
G.Skill Trident Z RGB 32GB (4x 8GB) DDR4 3200Mhz Memory
Samsung 970 EVO Plus 1TB NVMe 1.3 M.2 (2280) 3-Bit V-NAND SSD - MZ-V7S1T0BW
Seagate Exos 5E8 8TB 3.5" SATA 6Gb/s Archive HDD
Gigabyte AORUS AP850GM 850W 80 PLUS Gold Fully Modular ATX Power Supply
Gigabyte AORUS GeForce RTX 2080 Ti XTREME WATERFORCE 11GB Video Card
Volans PU34 USB 3.0 4-Port PCI-E Expansion Card
NZXT Kraken X72 360mm AIO Liquid CPU Cooler
NZXT Internal 5-Port USB Hub


moderator edit -- replaced oversized image with link.
Pasting pictures and code

Last edited by 2ManyDogs (2020-05-11 19:44:13)

Offline

#2 2020-05-08 03:02:24

ian.soarch.blvd.00
Member
Registered: 2020-03-29
Posts: 3

Re: Windows VM through virt manager now slows down until locks it up

Same here.

I use Windows10 vm via qemu/virtmanager everyday.
Since updated yesterday, this morning Windows vm got too laggy to use just small app, and couldn't even shut down softly.

I'm not sure but I suspect that the update of linux-lts might cause this problem, or not.

Offline

#3 2020-05-08 03:42:39

BIllzargo
Member
Registered: 2019-09-29
Posts: 7

Re: Windows VM through virt manager now slows down until locks it up

It sounds like my issue. Very laggy, and can not shut down most of the time.

Offline

#4 2020-05-08 16:08:46

Kateykat
Member
Registered: 2020-05-08
Posts: 1

Re: Windows VM through virt manager now slows down until locks it up

Just throwing in my report -- Qemu/KVM/virtmanager. Slows down within about 10-15 minutes from boot to a complete stall, force shutdown + reboot fixes until another 10-15 minutes. Possibly/likely related to https://bugs.archlinux.org/task/66578 -- my CPU is AMD Ryzen 9 3900X.

Offline

#5 2020-05-08 16:12:59

joeydc
Member
Registered: 2020-05-08
Posts: 1

Re: Windows VM through virt manager now slows down until locks it up

Same issue since the update yesterday.
My CPU is AMD 2500U

Last edited by joeydc (2020-05-08 16:16:25)

Offline

#6 2020-05-09 00:18:39

BIllzargo
Member
Registered: 2019-09-29
Posts: 7

Re: Windows VM through virt manager now slows down until locks it up

My CPU is i9 9900k

In case it helps here is some of the stuff in my box. Left out RGB fans etc.

Intel Core i9 9900K Octa Core LGA 1151 3.60GHz Unlocked CPU Processor
Gigabyte Z390 AORUS MASTER LGA 1151 ATX Motherboard
G.Skill Trident Z RGB 32GB (4x 8GB) DDR4 3200Mhz Memory
Samsung 970 EVO Plus 1TB NVMe 1.3 M.2 (2280) 3-Bit V-NAND SSD - MZ-V7S1T0BW
Seagate Exos 5E8 8TB 3.5" SATA 6Gb/s Archive HDD
Gigabyte AORUS AP850GM 850W 80 PLUS Gold Fully Modular ATX Power Supply
Gigabyte AORUS GeForce RTX 2080 Ti XTREME WATERFORCE 11GB Video Card
Volans PU34 USB 3.0 4-Port PCI-E Expansion Card
NZXT Kraken X72 360mm AIO Liquid CPU Cooler
NZXT Internal 5-Port USB Hub

Offline

#7 2020-05-09 02:14:48

BIllzargo
Member
Registered: 2019-09-29
Posts: 7

Re: Windows VM through virt manager now slows down until locks it up

This is not a fix, but a workaround for anyone that needs to us the VM. I have downgraded my system after reading the link @Kateykat - https://bugs.archlinux.org/task/66578 shared. Thank you.

Change to you pacman mirrorlist directory:

cd /etc/pacman.d

Backup your mirror list, set it back when you know the issue has been resolved:

sudo mv mirrorlist mirrorlist.bak

Create a new mirrorlist

sudo nano mirrorlist

I used the date from the link @KateyKat shared that OP downgraded to. Add this to the text file:

Server=https://archive.archlinux.org/repos/2020/05/05/$repo/os/$arch

Perform the downgrade:

sudo pacman -Syyuu

This seems to be working for me, make sure you have an Arch install disk/usb ready if it does not work for you to repair your system. Just set the old mirror list back and upgrade.

Offline

#8 2020-05-09 06:14:17

| )ar|us
Member
Registered: 2020-05-09
Posts: 1

Re: Windows VM through virt manager now slows down until locks it up

Yes i can confirm the snapshot is working. Thanks for posting!

Seeing Intel is also impacted, looks that it is not Zen2 related.
I can see that at least Gigabyte Motherboard is still a constant.

My Specs:
AMD Ryzen 9 3900X
Gigabyte x570 Aorus Elite
Seagate FireCuda 520 SSD
GeForce GTX 1650


> Windows Guest setup 2 Weeks ago with libvirt/virt-manager was running fine untlil update at 8th of may. Windows guest tools - spice-guest-tools-latest from 8th of may didn't help. Shutdown basically never works. Runs for around 2 and a half minutes while playing a random full-hd video in Firefox then is frozen.
> Linux Guest appears working or far less affected
> Linux Host appears working ( and i haven't seen anything related in dmesg )


<domain type="kvm">
  <name>win10-buero</name>
  <uuid>b3a343ce-d2cf-4e33-a34e-446067617e34</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">4194304</memory>
  <currentMemory unit="KiB">4194304</currentMemory>
  <vcpu placement="static">4</vcpu>
  <os>
    <type arch="x86_64" machine="pc-q35-4.2">hvm</type>
    <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"/>
  <clock offset="localtime">
    <timer name="rtc" tickpolicy="catchup"/>
    <timer name="pit" tickpolicy="delay"/>
    <timer name="hpet" present="no"/>
    <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="cdrom">
      <driver name="qemu" type="raw"/>
      <target dev="sdb" bus="sata"/>
      <readonly/>
      <address type="drive" controller="0" bus="0" target="0" unit="1"/>
    </disk>
    <disk type="file" device="disk">
      <driver name="qemu" type="qcow2"/>
      <source file="/run/media/Daten/VM/win10-buero.qcow2"/>
      <target dev="sde" bus="sata"/>
      <address type="drive" controller="0" bus="0" target="0" unit="4"/>
    </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="virtio-serial" index="0">
      <address type="pci" domain="0x0000" bus="0x03" slot="0x00" function="0x0"/>
    </controller>
    <interface type="user">
      <mac address="52:54:00:e1:de:9a"/>
      <model type="e1000e"/>
      <address type="pci" domain="0x0000" bus="0x01" slot="0x00" function="0x0"/>
    </interface>
    <serial type="pty">
      <target type="isa-serial" port="0">
        <model name="isa-serial"/>
      </target>
    </serial>
    <console type="pty">
      <target type="serial" port="0"/>
    </console>
    <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" keymap="de">
      <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="65536" vram="65536" vgamem="16384" heads="1" primary="yes"/>
      <address type="pci" domain="0x0000" bus="0x00" slot="0x01" function="0x0"/>
    </video>
    <redirdev bus="usb" type="spicevmc">
      <address type="usb" bus="0" port="2"/>
    </redirdev>
    <redirdev bus="usb" type="spicevmc">
      <address type="usb" bus="0" port="3"/>
    </redirdev>
    <memballoon model="virtio">
      <address type="pci" domain="0x0000" bus="0x04" slot="0x00" function="0x0"/>
    </memballoon>
  </devices>
</domain>

Last edited by | )ar|us (2020-05-09 06:44:09)

Offline

#9 2020-05-09 06:51:09

ian.soarch.blvd.00
Member
Registered: 2020-03-29
Posts: 3

Re: Windows VM through virt manager now slows down until locks it up

Yeah, me too.
Restoring to 5/5, solved this problem.

I tried to downgrade qemu, but partial downgrade didn't work.
I guess more things must be dependent on one another behind.

Offline

#10 2020-05-09 08:50:56

wkchu
Member
Registered: 2013-09-09
Posts: 4

Re: Windows VM through virt manager now slows down until locks it up

Hey guys, it seems that I experience the same problem on my Ryzen 2700x. Windows runs fine for about 5 minutes, after which it starts becoming highly sluggish or even totally unresponsive. I could reproduce on a quite minimal VM - no passthrough involved. Downgrading to 4.2 solves it.

I spent my night bisecting the issue and could narrow it down to this commit:
73fd282

Bisecting this issue is tedious as I'm always afraid to mark a bad commit as good due to the nature of the bug (which takes around 10 minutes to manifest itself). But 73fd282 causes problem after 5 minutes on my machine while b321051 (the previous commit) has run fine for the entire night now.

I've just opened a bug on Qemu's launch pad. It would be fine if other people affected could validate my bisect. I'm not sure what the easiest way would be but building qemu is rather straightforward (edit the commands accordingly):

git clone https://github.com/qemu/qemu.git
git checkout b321051cf48ccc2d3d832af111d688f2282f089b
mkdir build && cd build
../configure --target-list="x86_64-softmmu" --enable-spice && make -j16
replace the <emulator> line in your /etc/libvirt/qemu/win10.xml under the <devices> node: <emulator>/home/user/git/qemu/build/x86_64-softmmu/qemu-system-x86_64</emulator>

run your VM and confirm the problem is gone. Alternatively, you can checkout 73fd282e7b6dd4e4ea1c3bbb3d302c8db51e4ccf and confirm the problem reappears. You can check that you're running the right qemu by looking at /var/log/libvirt/qemu/win10.log:

2020-05-09 02:14:35.278+0000: starting up libvirt version: 5.10.0, qemu version: 4.2.50v4.2.0-2206-gb321051cf4, kernel: 5.6.10-arch1-1, hostname: cc.localdomain

NOTE: the bug I'm talking about here seems to be different from https://bugs.archlinux.org/task/66578 which seems to affect Zen2 but NOT Zen+ (at least not me).

EDIT: please don't use your everyday machine to debug (data loss, blah) smile

Last edited by wkchu (2020-05-09 09:00:34)

Offline

#11 2020-05-09 09:25:09

Toolybird
Member
Registered: 2017-09-30
Posts: 28

Re: Windows VM through virt manager now slows down until locks it up

Hey @wkchu, great work on the bisection.

Care to try any of the suggestions here?

https://bugs.archlinux.org/task/66578#comment189223

Offline

#12 2020-05-09 20:52:05

hifigraz
Member
Registered: 2017-05-01
Posts: 27

Re: Windows VM through virt manager now slows down until locks it up

sad to tell, same problem here

[ EDIT: ]

Downgrade helped for me too!
Desktop: Ryzen 1st gen
Notebook: Intel 8th gen
both affected

[ EDIT 2: ]

Shouldn't there be a big fat warning in the archlinux.org newsfeed, that libvirt will be broken with the update?

Last edited by hifigraz (2020-05-10 10:27:08)

Offline

#13 2020-05-10 12:40:57

Lone_Wolf
Member
From: Netherlands, Europe
Registered: 2005-10-04
Posts: 8,086

Re: Windows VM through virt manager now slows down until locks it up

Shouldn't there be a big fat warning in the archlinux.org newsfeed, that libvirt will be broken with the update?

libvirt description wrote:

API for controlling virtualization engines (openvz,kvm,qemu,virtualbox,xen,etc)

Checking the bug report suggests that this issue only appears on VMs using qemu AND use io_uring .
So it's not libvirt that's broken but qemu.

I've seen no reports of users with non-windows VMs, so it looks like only a small part of qemu VMs are affected.

Also archlinux users are supposed to check what gets updated before updating.
Seeing qemu being updated from 4.2.0-2  to 5.0.0-xyz should have raised a huge red flag : "Hey qemu has a new major version, maybe that will break my VMs. Better delay the update and check changes first."

TL;DR: nope


Multi-init booting with apg Openrc and systemd coexisting
Automounting : not needed, i prefer pmount
Aur helpers : makepkg + my own local repo === rarely need them

Offline

#14 2020-05-10 13:54:08

wkchu
Member
Registered: 2013-09-09
Posts: 4

Re: Windows VM through virt manager now slows down until locks it up

Hey @Toolybird, I missed your message.

Looks like you've noticed from the upstream bug report already, but FTR: yes, --disable-linux-io-uring on master fixes it.

Cheers

Offline

#15 2020-05-11 18:22:28

hifigraz
Member
Registered: 2017-05-01
Posts: 27

Re: Windows VM through virt manager now slows down until locks it up

Lone_Wolf wrote:

Seeing qemu being updated from 4.2.0-2  to 5.0.0-xyz should have raised a huge red flag : "Hey qemu has a new major version, maybe that will break my VMs. Better delay the update and check changes first."

That's a point but also a broken package should be revoked until it's fixed.

Offline

#16 2020-05-11 18:51:31

loqs
Member
Registered: 2014-03-06
Posts: 10,644

Re: Windows VM through virt manager now slows down until locks it up

hifigraz wrote:
Lone_Wolf wrote:

Seeing qemu being updated from 4.2.0-2  to 5.0.0-xyz should have raised a huge red flag : "Hey qemu has a new major version, maybe that will break my VMs. Better delay the update and check changes first."

That's a point but also a broken package should be revoked until it's fixed.

https://git.archlinux.org/svntogit/pack … ee7d922b0b are you still experiencing the issue with qemu 5.0.0-6?

Offline

#17 2020-05-11 22:46:09

BIllzargo
Member
Registered: 2019-09-29
Posts: 7

Re: Windows VM through virt manager now slows down until locks it up

qemu-5.0.0-6 does stop the VM from locking up. I have both Visual Studio and Tibco JasperSoft Studio open for about an hour now and it is still running fine.

Offline

Board footer

Powered by FluxBB