I've mentioned it before, but it probably bears mentioning again: While KVM/QEMU performance is great from a CPU perspective (especially with GNU/Linux guests), unless you're using PCI passthrough and a dedicated GPU VirtualBox still blows it out of the water for graphics performance with Windows guests... Primarily because it includes a custom WINE/DXVK-based Windows driver as part of the "Virtualbox guest additions", which for most "simple" 3D workloads (including acceleration of the windows UI/Aero etc) "just works" with no fiddling required.A caveat to remember with my advice is it is coming from legit workstation class experience with a whatever it takes mandate
...
From what I understand VBox is much better on low end hardware and may be your answer.
If the goal is an easy to set up on-demand Winblows installation for casual desktop use, much as I loathe Oracle, VirtualBox really does offer a compelling solution. Doubly so if you also want your VM image to be just a couple of files that you can drop on a flash drive and boot up on a random Windows host.
For a more permanent solution with many always-on (primarily GNU/Linux) VMs, efficient host resource sharing, network (spice/vnc etc.) graphics, and better native integration and CLI tooling, QEMU/libvirt all the way... But I get the impression that's not really the OPs use-case.
Statistics: Posted by steve_v — 2024-03-24 11:11 — Replies 50 — Views 1406