getting started with Hyper-V
Don’t get me wrong, I love Linux. It’s the perfect environment for development. The problem is having to deal with hardware support on bleeding-edge hardware. When Apple decides to release a MacBook 13” with 32GB of RAM and a decent GPU, without leaving you bankrupt, I might reconsider it, but for now, I feel like it’s not worth it. I’ve got tired. Then Microsoft started investing heavily on open-source, started doing a lot of right things (and a lot of wrongs too, but let’s hold it for now). Friends and co-workers started telling great things about Windows 10. It’s not perfect, but I’m liking it so far. Can’t complain about the battery life. Naturally, I’m still running Linux inside a VM.
Hyper-V is a really interesting virtualization software, I’ve been impressed both by the performance and features (like dynamic memory). But I’ve been spoiled by software like VirtualBox, which is geared towards end-users. Hyper-V, on the other hand, is geared towards data centers and enterprise-grade virtualization solutions. I’ve spent a lot of time trying to figure out how to make my guest Linux VM to get a private IPv4 address on an internal virtual switch. (host-only network in VirtualBox terminology). Hyper-V has no built-in DHCP server. You’ve been warned! After more time searching, I’ve found a simple and free DHCP Server that you can bind to the virtual switch, making your life way easier. I could use a Linux guest VM with dnsmasq running, but laziness won. Now that I have
minikuberunning on Hyper-V, next step is finding a convenient way of transporting
kubectl settings to the Linux box.