virtualbox.org

From version 6.0 on Linux Mint host, Windows 7 desktop is very laggy. When you moving open application tabs on Desktop, clicking on start bar, almost every action is happening with lagging level like is working on very old computer. I tried with several graphic adapter setting, but without any changes in performance.

Configuration that I'm using is:

AMD Ryzen 7 1700X
16GB RAM
NVidia 1030 2GB

When I reinstall VB to version 5.2.x everything is working fine.

Here is log file:

I'm seeing similar behavior. Just built a new system and graphics performance is horrible in windows 7 guest. Simply dragging an explorer window around is choppy.

Performance issue seemed to be resolved by 6.1.0 and enabling 3d acceleration, however, after a while the display becomes corrupt in the vm - lines, portions of screen not updating. Host video is fine.

Also does the same in a second win 7 and windows 10 vm.

Host is running Kubuntu 19.10, Virtualbox 6.1.0 (same issue on 6.0.14) an Ryzen 9 3950x, Radeon Pro WX 4100.

Old system was an older (6 years or so) Intel i7 with low end ATI Radeon card running Virtualbox 6.0.4 - graphics performance is great, can't tell it's a vm in normal office type tasks.

00:00:00.426577   NumCPUs           <integer> = 0x0000000000000008 (8)
00:00:00.643808 CPUM: Physical host cores: 8
00:00:00.644214 Full Name:                       "AMD Ryzen 7 1700X Eight-Core Processor"

You have assigned all your CPUs to the VM. The Host is going to run low on resources, since VirtualBox cares about physical processors (cores), not logical ones (threads). Reduce the number of your CPUs assigned to the Guest to 4.

00:00:00.404455 Guest OS type: 'Windows7_64'
...
00:00:00.426896 [/Devices/usb-xhci/0/Config/] (level 4)

Win7 doesn't natively support USB3 (xHCI). Did you install the Intel drivers on the Guest? See USB basics and troubleshooting » #6: Guest support.

00:00:01.194486 GUI: UIMachineLogicFullscreen: Additions-state actual-change event, rebuild multi-screen layout

Avoid going into FullScreen mode with a fake GPU such as the one that your Guest has. Try something smaller in normal, Windowed mode.

marmoset,
We need to see a complete VBox.log, from a complete VM run, where the problem occurs:

• Start the VM from cold-boot (not from a paused or saved state) / Observe or recreate the problem / Shutdown the VM (force close it if you have to).
• With the VM completely shut down (not paused or saved), right-click on the VM in the VirtualBox Manager and select "Show Log".
• Save only the first "VBox.log", ZIP it and attach it to your response. See the "Upload attachment" tab below the reply form.

Here's the the log where graphics performance is poor, with 3d off.
Thanks

I tried with same setting on Intel I7 4770K, and is working as a charm. Also when I reinstall VB to version 5.2.xx and run with same configuration on same AMD it's working without any problems.

VB on AMD is giving you to allocate 16 CPU, but to 8 is green line, after 8 is red.

My old system where it worked fine was an i7 4770k too. Maybe it's an AMD issue on the newer 6.x version? I've seen reports of people reverting to 5.2 to fix. I'm on kubuntu 19.10 and there's not a 5.2 build for it.

I also think that this is AMD problem, and I hope that they will fix it.

There is an issue with some AMD CPU's
See viewtopic.php?f=7&t=93748

I have an older AMD 8150 8 core and 6.0.x is quite slow

I've also found that graphics performance has become terrible when going from v5 to v6. My host is Linux Mint 19.3 on a Ryzen 3900X with NVidia GPU (GTX-950). Guest is Win7-64.
I run a lot of console tools that output lots of text so scrolling speed of a console window is crucial. In VB 5.2 it was nice and fast, able to scroll through multiple pages in the blink of an eye. In v6 it only manages a few lines per second making it pretty much unusable.

I upgraded to v6 hoping there'd be some improvement in per core overhead. In v5.2 I'm seeing an apparently exponential increase in overhead as I increase the CPUs allocated to the VM. It's so bad that increasing the CPUs past 6 actually decreases the multithreaded performance of the VM even though the build process I run uses all available cores. Unfortunately v6.1 is only a little better (run minimized to remove the impact of the graphics performance).

VBox.log attached.