- #Hyper v vs virtualbox performance 2019 windows 10#
- #Hyper v vs virtualbox performance 2019 windows#
* Some sources suggested disabling 2D acceleration. * Enabling and disabling 3D acceleration. None of the choices seemed to have any effect.
#Hyper v vs virtualbox performance 2019 windows#
I realize it makes no sense to try KVM with a Windows guest, but I tried it anyway for completeness. * Trying each of the available paravirtualization options: None, Default, Legacy, Minimal, Hyper-V, and KVM. * Enabling and disabling PAE/NX, Nested VT-x/AMD-V, and Nested Paging.
Restoring the number of CPUs to 4 restored baseline (poor) performance. Reducing the number of CPUs below 4 made the performance problems worse. * Reducing the number of CPUs allocated to the VM to 2 or 1. * When the VM is working on something CPU intensive, the VBoxHeadless process uses up to 400% CPU on the host (the max possible with 4 virtual CPUs and a 100% execution cap), but Task Manager inside the VM shows moderate and highly variable CPU usage. * When the VM is idle (~1-2% CPU usage as measured by Task Manager), the VBoxHeadless process uses ~25-50% CPU on the host (as measured by top). * There is a delay in launching applications in the Windows VM that seems longer than normal, even when they have recently been run and are cached in memory.
If I am moving the mouse very smoothly, the window may keep up with the cursor for a few moments, but then the window will stop moving even though the cursor continues to move, and the window will catch up with the cursor after another moment. * Dragging windows across the screen inside the VM causes windows to move with unpredictable speed.