[opensuse-factory] Bad Windows 10 performance on Qemu 4.0
Since several months I have performance problems with my Windows 10 virtual machine. The host system (Intel Core i5 750, 2.8 GHz; 16 GB RAM; 3 TB WD Red harddisk for the VMs) with openSUSE TW (Qemu 4.0) should be strong enough to run a single Windows 10 desktop in a virtual machine. Other VMs (Linux, FreeBSD) are running without performance problems. But if I start Windows 10 as a single Qemu KVM guest system, the desktop of the host system sometimes becomes unresponsive during Windows boot. The performance of the Windows 10 desktop is bad, approximately 10-20x slower than native and the host system performance also becomes worse. I had the performance problems with Windows 10 1809. Now I installed a fresh Windows 10 1903 machine. The performance is better compared to the old VM, but also bad. I implemented the common performance hints: - enough hard disk (55 GB) and RAM (2-5 GB) and CPU cores (2) for the guest system - all available Virtio drivers (disk, network, balloon, spice, tablet) installed - disabled disk cache (currently cache='unsafe', but also tried cache='none') - HyperV options enabled (see https://bugs.launchpad.net/qemu/+bug/1775702) Here is my Windows 10 1903 quest setup: http://paste.opensuse.org/view/56376915 Does anyone has a working configuration on TW or configuration hints for me? I also wonder about the following "CLOSE WONTFIX" comment on https://bugzilla.redhat.com/show_bug.cgi?id=1690641 "For me this is fixed in the EV variant of the software." Qemu-ev is Redhat's own version of Qemu? Greetings, Björn -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Wed 10 Jul 2019 09:35:48 PM CDT, Bjoern Voigt wrote:
Since several months I have performance problems with my Windows 10 virtual machine.
The host system (Intel Core i5 750, 2.8 GHz; 16 GB RAM; 3 TB WD Red harddisk for the VMs) with openSUSE TW (Qemu 4.0) should be strong enough to run a single Windows 10 desktop in a virtual machine. Other VMs (Linux, FreeBSD) are running without performance problems.
But if I start Windows 10 as a single Qemu KVM guest system, the desktop of the host system sometimes becomes unresponsive during Windows boot. The performance of the Windows 10 desktop is bad, approximately 10-20x slower than native and the host system performance also becomes worse.
I had the performance problems with Windows 10 1809. Now I installed a fresh Windows 10 1903 machine. The performance is better compared to the old VM, but also bad.
I implemented the common performance hints: - enough hard disk (55 GB) and RAM (2-5 GB) and CPU cores (2) for the guest system - all available Virtio drivers (disk, network, balloon, spice, tablet) installed - disabled disk cache (currently cache='unsafe', but also tried cache='none') - HyperV options enabled (see https://bugs.launchpad.net/qemu/+bug/1775702)
Here is my Windows 10 1903 quest setup: http://paste.opensuse.org/view/56376915
Does anyone has a working configuration on TW or configuration hints for me?
I also wonder about the following "CLOSE WONTFIX" comment on https://bugzilla.redhat.com/show_bug.cgi?id=1690641 "For me this is fixed in the EV variant of the software."
Qemu-ev is Redhat's own version of Qemu?
Greetings, Björn Hi I'm using UEFI, pc-q35-4.0, RH virtio for the disk and gpu passthrough.
Two cores (i5-3470S) and 4G RAM allocated. I'm using this setup for openSUSE/SLE and Windows guests. The only thing I did on the WinX (1903v1) guest was remove unused apps (xbox, game bar, onedrive etc), however also killed of SearchUI.exe (aka Cortana) as that was a hog, now I have a reasonable WinX desktop for testing. I don't see any lagging on the host (Tumbleweed) or guests... The next thing I see is TiWorker.exe busy... updates.... -- Cheers Malcolm °¿° SUSE Knowledge Partner (Linux Counter #276890) Tumbleweed 20190708 | GNOME Shell 3.32.2 | 5.1.16-1-default Intel DQ77MK MB | i5-3470S X4 @ 3.60 GHz | Intel Ivybridge HD 2500 up 3:25, 2 users, load average: 7.98, 3.07, 1.37 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Malcolm wrote:
The only thing I did on the WinX (1903v1) guest was remove unused apps (xbox, game bar, onedrive etc), however also killed of SearchUI.exe (aka Cortana) as that was a hog, now I have a reasonable WinX desktop for testing. Thanks. Now I also disabled all autostarts, Cortana and Microsoft Compatibility Telemetry (both disabled with group policies) and Superfetch. Performance is now a bit better, but still not good.
Greetings, Björn -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 11/07/2019 05:05, Bjoern Voigt wrote:
Since several months I have performance problems with my Windows 10 virtual machine.
The host system (Intel Core i5 750, 2.8 GHz; 16 GB RAM; 3 TB WD Red harddisk for the VMs) with openSUSE TW (Qemu 4.0) should be strong enough to run a single Windows 10 desktop in a virtual machine. Other VMs (Linux, FreeBSD) are running without performance problems.
But if I start Windows 10 as a single Qemu KVM guest system, the desktop of the host system sometimes becomes unresponsive during Windows boot. The performance of the Windows 10 desktop is bad, approximately 10-20x slower than native and the host system performance also becomes worse.
I had the performance problems with Windows 10 1809. Now I installed a fresh Windows 10 1903 machine. The performance is better compared to the old VM, but also bad.
I implemented the common performance hints: - enough hard disk (55 GB) and RAM (2-5 GB) and CPU cores (2) for the guest system - all available Virtio drivers (disk, network, balloon, spice, tablet) installed - disabled disk cache (currently cache='unsafe', but also tried cache='none') - HyperV options enabled (see https://bugs.launchpad.net/qemu/+bug/1775702)
Here is my Windows 10 1903 quest setup: http://paste.opensuse.org/view/56376915
Does anyone has a working configuration on TW or configuration hints for me?
This is a support question and should be on the openSUSE support mailing list, not the general openSUSE development list, as a rule of thumb generally posts here should affect more then one package, or most users. -- Simon Lees (Simotek) http://simotek.net Emergency Update Team keybase.io/simotek SUSE Linux Adelaide Australia, UTC+10:30 GPG Fingerprint: 5B87 DB9D 88DC F606 E489 CEC5 0922 C246 02F0 014B -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 7/10/19 9:35 PM, Bjoern Voigt wrote:
Since several months I have performance problems with my Windows 10 virtual machine.
My be relevant: https://www.reddit.com/r/VFIO/comments/cblpup/a_little_info_for_people_using... -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
https://www.reddit.com/r/VFIO/comments/cblpup/a_little_info_for_people_using...
Most likely this is th OPs problem if qemu does not have a patch included yet. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Cristian Rodríguez wrote:
https://www.reddit.com/r/VFIO/comments/cblpup/a_little_info_for_people_using... Most likely this is th OPs problem if qemu does not have a patch included yet.
As far as I understand the bug only applies if the Qemu machine type is set to Q35. The machine type of my Windows 10 VM is pc-1.2: <os> <type arch='x86_64' machine='pc-1.2'>hvm</type> <boot dev='hd'/> <bootmenu enable='yes'/> </os> When I switch to Q35 <os> <type arch='x86_64' machine='pc-q35-4.0'>hvm</type> <boot dev='hd'/> <bootmenu enable='yes'/> </os> my Windows 10 VM losses its activation. So I can not switch to the currently buggy Q35 machine type. Maybe there is another root cause on my Windows 10 Qemu problems. According to my latest tests, the VM runs Okay if some memory hungry desktop programs like Firefox and Netbeans are closed. I thought that 16 GB RAM is enough for one 4 GB VM and some desktop programs. So I probably have to analyze possible memory problems. Unfortunately the output of tools like "top" and "ksysguard" is not very helpful. Firefox shows 993 MB physical memory, but 4.330 GB virtual memory. Chrome shows 66 MB physical memory, but 12,098 GB (!!) virtual memory. The Ksysguard tooltip says, that virtual memory is nearly useless. Greetings, Björn -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
participants (5)
-
Bjoern Voigt -
Cristian Rodríguez -
Malcolm -
Michael Pujos -
Simon Lees