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.
is quite cool. I decided to install in on my laptop, and after a few hours trying to get it to work, I rebooted for a third time, and then Windows decided to configure the features I had selected. Well, as they say, the third time's the charm!
After getting it to work, I installed Windows Server 2012 on it, and that went without any real notable issues, other than the fact I had to define network interfaces beforehand, and I did not realize that.
While using Google to try and figure out why Hyper V did not want to install, I found that the latest version of Fedora (18) includes the required kernel drivers for Hyper V, and has been confirmed to work correctly, so I am thinking of installing that as well.
Hyper-V, by default, does not have any network interfaces defined for VMs. I had to go to an options dialog and define a network interface so that the VMs could access the internet. I did not know that (VMWare has them predefined upon installation of the application), and found it out when I started to install the WS2012 VM.