How about something positive, for a change?

VirtualBox sucks in performance. Hyper V sucks in features and user interface. But if you marry them, then you get the best of both worlds. Here's how.

Since somewhere about v. 6+ of VB, you can use Hyper V API as its back end. It supposedly automatically detects its presence and switches to it. What's in it to you?

VirtualBox guest OSs perform at about 50% rate of that on Hyper V. A VM running on VB is about half the speed of the same VM on Hyper V.

The mere presence of a Hyper V (or its role, if server OS) on Windows slows it down by about 10% in memory access and about as much in CPU computational power. Do not get me wrong! You do not slow down your PC by 20% by installing Hyper V! It only slows down by about 10% across the board.

So, by installing the new version of VB and Hyper V and by running your guest OSs in VB but on Hyper V back end, you gain about 40% performance vs. running them on VB's own back end.

Posted by: LinuxLies at 11:45 AM | No Comments | Add Comment
Post contains 201 words, total size 1 kb.