• To ensure you get the most out of your CIN membership and stay connected with the latest updates, we are asking all members to update their community profiles. Please take a few moments to log in and: • Complete all sections of your profile • Review your current information for accuracy • Enter an alternative email address if desired (CIN requires your valid business email address for your training organization). Keeping your profile up to date helps us better serve you, ensures your account is correctly linked with CompTIA’s CRM, streamlines processes, enhances communication, and guarantees you never miss out on valuable CIN opportunities. Thank you for taking this important step! step!

Linux+ Train the Trainer session 2025-09-09

Great session today, Jason. Back on the issue of HyperV vs. Oracle Box, can someone share their preference and why?
I could see using Hyper-V because for a student that may be more likely to use a Windows environment, Hyper-V would be easier to set up and get going. In fact, one command in an Admin PowerShell window and you're there:

Enable-WindowsOptionalFeature -Online -FeatureName Microsoft-Hyper-V -All

/r
 
  • Like
Reactions: jarrelrivera
For me, the choice of hypervisor depends on the cohort:

If the student is new to virtualization, I prefer to use Oracle VirtualBox

If the cohorts are professionals:
  • Hyper-V if the client is using Microsoft-based products, or KVM if they are into Linux
  • I've used VMware workstation and/or VMWare ESXi before, until it was bought by Broadcom
  • for Type-1 virtualization, I prefer Proxmox
 
  • Like
Reactions: Joel Mayberry
Great session today, Jason. Back on the issue of HyperV vs. Oracle Box, can someone share their preference and why?
Hyper-V is a Type 1 (bare-metal) hypervisor that comes with Windows Pro and higher editions (though it can be installed on Home if you look up how). Being Type 1 means Hyper-V runs directly on the hardware, with a lightweight virtualization layer in between. This allows near-native performance.

In contrast, Oracle VirtualBox is a Type 2 (hosted) hypervisor by default—it runs as a regular application on top of Windows. As a result, all VM hardware access must go through the Windows OS first, which adds overhead and reduces performance compared to Type 1 hypervisors.

So, in general, Hyper-V is faster than VirtualBox by default.

However, there’s a neat trick: if you have both Hyper-V and VirtualBox installed, you can configure VirtualBox to use Hyper-V as its backend. To do this:
  1. Open the settings for your VirtualBox VM,
  2. Go to System > Acceleration,
  3. Set Paravirtualization Interface to Hyper-V.
This allows VirtualBox to leverage Hyper-V’s performance benefits while maintaining VirtualBox’s compatibility and features.

Why is this useful? In cybersecurity, many pre-built VM targets and OS images are packaged specifically for VirtualBox. So for students taking a cybersecurity course, it makes sense to use VirtualBox—but enabling Hyper-V paravirtualization gives the best of both worlds: broad compatibility and improved performance.

If you're not teaching a cybersecurity course, however, it makes sense to have a simpler setup where you just stick with Hyper-V for faster, cleaner VM performance on Windows.
 
Last edited:
  • Like
Reactions: Joel Mayberry
Hyper-V is a Type 1 (bare-metal) hypervisor that comes with Windows Pro and higher editions (though it can be installed on Home if you look up how). Being Type 1 means Hyper-V runs directly on the hardware, with a lightweight virtualization layer in between. This allows near-native performance.
I always debated this point en principio - of whether Hyper-V was a true type 1 hypervisor, because it requires Windows to be loaded as the OS before the hypervisor runs. Now, other folks would say, "Hyper-V is part of the Windows OS", so by extension, makes it Type 1, etc etc. I know MSFT claims that when Hyper-V is loaded, it adds a hypervisor layer to run on bare-metal and the "host" Windows OS becomes 'virtualized'.

Hurts my head, sometimes...
 
  • Like
Reactions: Joel Mayberry