The Lounge is rated PG. If you're about to post something you wouldn't want your
kid sister to read then don't post it. No flame wars, no abusive conduct, no programming
questions and please don't post ads.
In addition to Fedora having support, Microsoft also supports Red Hat Enterprise Linux (RHEL) (downstream version of Fedora) and thus, CentOS (clone of RHEL with the branding stripped out). You can get the Linux Integration Components (LIC) here.[^]
You can run Linux in Hyper-V without the extensions, but it's nice to have the host monitoring, proper NIC (without using Legacy Network Adapter) etc. It also includes mouse support since LIC v 3.2. I've even found that when I power down Windows 8 with a Hyper-V machine going, that the state got saved and restored on bootup (might have been my imagination though
So far, I've had CentOS, OpenSUSE and Fedora going in Hyper-V (dumped OpenSUSE after they dumped MONO though, that was the only reason I bothered with them).
I usually only run it in command line mode and connect to it from Windows with PuTTY (I love PuTTY
If you're looking for info on the various Linux Distros, DistroWatch[^] is a good place to start.
I used Hyper-V quite extensively in my previous job and ran Debian Linux machines (literally my first experience with Linux) to test FTP, SFTP and FTPS adapters as well as Win 2008 Server/SQL Server 2008 machines to test installation of our web application. I took advantage of the network setup options to closely mimic the customer's configuration.
Hyper-V has its quirks and in 2010 the interface wasn't as graphic as VMWare. But there are plenty of tutorials out there and once you learn to properly copy/clone the machines and maintain snapshots, it's very easy to use. Plus, as a QA Engineer, I loved having control of my test environment, knowing that I wouldn't have to worry about how someone else's changes to the environment might affect my testing.
I haven't found Virtual Box to function as well on Windows but had decent experiences with it on Linux. And while VMWare has some advantages over Hyper-V, I'd probably go back to Hyper-V given the option.
I'm curious to know how you managed to get it to work. I've been trying to activate Hyper-V on my Windows 8 Pro laptop for several months without success. I've followed all of the suggestions I've found on the Internet, to no avail. I've done all the testing on my laptop's setup, including the BIOS, and everything that's required seems to be in place. But when I try to activate Hyper-V, after the reboot I always get an unexplained error followed by "Reverting ...". I'd be grateful for some information about the problems you encountered and how you overcame them.
As a followup, I finally gave up and installed VirtualBox. It works great, so I can now run a program I use occasionally that will not work on anything later than Windows XP. It's an old MS-DOS program that takes over the entire screen, so Vista and later prevent it from running. VirtualBox was easy to install under Win 8 Pro and seems to work fine.
I like Hyper-V, but I find it very end user unfriendly, noted in fact that you had to set up the network interfaces yourself without proper documentation stating what you're supposed to do, other thing I don't like is the lack of drag and drop between the host and the virtual machines (although I believe this can be done connecting via RDP instead of the built in viewer), also I have noted that it hits the performance of the host computer, even if you're not running any virtual machine, and also ruins other things like (DRMed) media.
I see it as a Server feature that was given for free to the common user, but for the end user I find VMware Workstation far easier to use.
Well, I did try to indicate it was meant as a harmless joke. I don't actually have anything against Canadians. After all, you should respect the people who came to the New World and said "Dibs on the cold part up North" .
"When you don't know what you're doing it's best to do it quickly" - Jase #DuckDynasty