Over the weekend I decided to install Fedora Core 21 Server on my Windows 8.1 home server running Hyper-V. I was able to install Fedora Core 21 Server without having to run Linux Integration Services which is very nice as network, mouse/keyboard, hard drive functions work “out-of-the-box.”
On initial installation I disabled “Secure Boot.” In most cases I find that UEFI “Secure Boot” for Linux Virtual Machines in Hyper-V does not work.
Fedora Core 21 must have built in kernel support for Hyper-V however I have not been able to find any official documentation regarding “native kernel support for Hyper-V.” Fedora Core is similar to Red Hat and Cent OS so I am assuming the development team has included native kernel support for Hyper-V, as they do with the newer releases of Red Hat and Cent OS.
It is worth noting that Hyper-V does not report Integration Services status or an IP address via the Hyper-V management console. Based on my experience with Hyper-V only Window’s Virtual Machines are reliable when reporting status such as Integration Services, Network IP, Heartbeat, etc.
Microsoft Tech Net highlights Linux Virtual Machine Guest Operating System Support here. Note that Fedora Core is not amongst the supported guest operating systems.
I also tried installing Fedora Core 21 Workstation which did not work. The Cloud version of Fedora Core 21Cloud requires a different environment in order to be deployed (openstack).
Here is a quick guide on how to install the Hyper-V role in Windows 8.1 Pro!
Depending on your computer’s hardware you may or may not be able to install the Hyper-V role. Additional information on Client-Hyper-V for Window 8/8.1.
Step 1) Open up Control Panel and Select “Turn Windows features on or off”
Step 2) Expand the Hyper-V check box:
Step 3) Select all options related to the expanded Hyper-V role and select ok. The Hyper-V role will be installed and you will need to reboot your machine once the installation completes. Upon reboot Hyper-V will be ready for use.
Do you have a Windows Server that is low on disk space? If so here is one of the best ways to cleanup disk space and increase the usable storage capacity of your server.
In order to cleanup disk space on a Windows Server we will use the DISM command (Deployment Image Service and Management). To run the below command please open the command prompt (cmd), be sure to run the command prompt with elevated privileges (Run as Administrator):
DISM /online /Cleanup-Image /SpSuperseded
Capacity before DISM command is run
Running the DISM command
DISM command completion
Capacity after DISM command completes, approximately 3 GBs is restored for use
You can view the official Microsoft webpage here: Clean Up the WinSxS Folder
There are several other methods we can use to cleanup space on a Windows Server. This will depend on your servers role. For example if you have a BlackBerry BES Server you should probably check the BES Log Files as these may build up over the days/weeks/months/years.
The other Windows Server that often runs low on disk capacity is a WSUS server (Windows Server Update Services).
If you have any questions feel free to post to this thread!