Switch to Hyper-V is Painful

Simple things are not simple when it comes to Hyper-V

You are not going to find any solutions in this post. It’s just my rant on experimenting with Hyper-V and why that failed.

I recently got a refurbished HP Mini PC and thought of installing Hyper-V instead of my usuals (VMWare Workstation or ESXi). The installation was straightforward but that was the only easy part about this.

I wanted to setup Remnux on it, so I downloaded the Remnux OVA, converted it to Hyper-V format and created a VM (@Cyrus, if you are reading this, please listen to people in the comments section of your video and show us how to get internet working in Remnux Hyper-V VM). The first thing you are advised to do upon launching a Remnux VM is to upgrade it. So I ran the remnux upgrade command, only to find out that internet is not accessible via the VM (despite using Default Switch). To give you a sense of comparison, the same thing worked flawlessly on VMWare Workstation 17. I tried to troubleshoot it but lost interest since it was taking more time than I expected.

Then, I wanted to copy-paste text from host to Remnux VM but that didn’t work either. Turns out, it required Enhanced Session Mode and to enable that there a series of steps that one must follow. Spend 15 mins to get something working that works out of the box in other virtualization software, nah!

Ended up removing Hyper-V and installing VMWare Workstation Pro 17 (which is now free for personal use, by the way).