I tried Hyper-V for a while but I found the network configuration really cumbersome. Therefore I went back to Virtualbox but I should probably request my employer to buy a license for Vmware.
Is it because you switched frequently from one adapter to another (like wifi to ethernet)? Otherwise I don't think I ever had any problem with the network configuration.
In Windows 10, we provide a NAT network option by default. This should work seamlessly even if you switch between WiFi and Ethernet. So even this problem should go away for most people now.
Not if you use the Virtualbox extension pack to VNC (that's the free/GPL extension pack, not the Oracle one). That will work with anything. Hell, it'll work with a DOS 1.0 guest.
(and yes, it's VNC, not RDP, I believe the oracle extension pack actually allows for Virtualbox to do RDP as well. But you can stay GPL-only and still support headless VNC. I believe phpVirtualbox uses it with beautiful results)
Can't you only RDP (and here is the qualifier) out-of-the-box with an "Enhanced Guest" VM, like what comes with some of the later Windows 10 builds, like 1809?
Otherwise, don't you have to do everything by hand to configured xrdp on the Linux guest?
I think Hyper-V is Windows 8+ (or similar generations of Windows Server), isn't it?
Much of the Windows world is still on Windows 7, and it would be rather ironic if they were updating because of concerns about software phoning home...
I've had nothing but issues trying to run Ubuntu in Hyper-V. Even the Windows Ubuntu LTS image that comes with the quick-create didn't work for very long.
Not sure what I'm doing wrong, but I've never has success with non-windows OS's.
What host version? I'm running 18.04 on Server 2016, for reference, did absolutely nothing special or unique, downloaded the iso, built the machine and loaded it and it's up running dns & unifi controller 24/7 for my home network with no issues.