Hyper-V and VirtualBox are two virtualization platforms that we both use in our system administration courses. Unfortunately, once Hyper-V is active, it won’t coexist with other virtualization platforms. In this post, I discuss a method to work around this problem by setting up a custom boot entry for each platform.
One of the greatest pitfalls when working with VirtualBox VMs is a good understanding of how networking works. In this post, we’ll discuss the most important differences between them, and their limitations when you use VirtualBox to experiment with setting up network services on a VM.
In our system administration courses, we use VirtualBox to allow students to set up their own Linux machines without having to resort to dual booting. VirtualBox is certainly not the “best” virtualization platform, but it is supported on the three common desktop platforms and works similarly on all of them.
