Windows 8 Hyper-V Requirements

According to the Official Blog post by Microsoft http://blogs.msdn.com/b/b8/archive/2011/09/07/bringing-hyper-v-to-windows-8.aspx to have Hyper-V on an upcoming Windows 8 Operating System you will need to meet certain requirements.

One of the requirements for Hyper-V is that it requires a 64-bit system that has Second Level Address Translation (SLAT). This is a feature that the current processors comes along with.

How do we check whether our existing systems/processors support this feature? this is the ultimate question

According to this blog Intel and AMD have different types of SLAT, Intel calls this Enhanced Page Tables (EPT) and AMD calls it as Nested Page Tables (NPT).

Microsoft Sysinternals has a tool called Coreinfo which can be downloaded here, using this tool we can view whether our processors support either one of EPT or NPT depending on the processor make.

Once you download the Coreinfo, extract the software to your C: drive. Open command prompt and navigate C:\ and type Coreinfo.exe –v

This command will give you whether your processor supports EPT or NPT 

Coreinfo

Hyper-V in Windows 8

As an IT Pro, we are required to do R&D a lot. At the rate of new technologies being implemented specially in the Microsoft arena we have to do a lot of research to be in par with the technology.

Mostly, what we do is virtualize the newly released products and test it out, but the common problem most of us face is that to have a descent virtualization solution such as hyper-v, we are compelled to install Windows Server as the base operating system.

I have a Lenovo W520 with a Core i7 vPro and 16GB of RAM and I run Windows Server 2008 R2 as my base OS, purely because I need to run Hyper-V. The Biggest problem I face is that once I enable Hyper-V, I cannot hibernate or put my Lenovo Notebook to sleep.

Hold on.. Microsoft just released a blog post on their Windows 8 Engineering Blog that Windows 8 will support Hyper-V on itSmile. This is something super cool and most of the IT Pros out their will love this for sure. The best part is that hibernation/Sleep ill still be there even if you install Hyper-V on Windows 8 

The requirement is that you will need to have a Windows 8 x64bit OS and a minimum of 4GB of RAM.

For more information and for a video click Bringing Hyper-V to “Windows 8”

Providing Internet Access to Hyper-V machines through a WiFi Adapter

I was helping an organization to install and configure their infrastructure recently. They wanted to have an Active Directory, a Database Server and a SharePoint Server and wanted me to install and configure it for them.

The total solution had to be virtualized, hence I as usual preferred to use a Microsoft technology and selected Hyper-V.

I started the installation on my notebook, which has 8GB of RAM and runs on Windows Server 2008 R2. I started to install the first Guest OS (for the Active Directory). The installation went smooth without any problems. As soon as I finished the installation I faced a problem when I wanted to provide internet access to the guest machine (virtual machine). There was no way I could bind my WiFi adapter on the physical machine to my virtual machine, to see I could only bind an Ethernet connection to a Hyper-V machine.

There should be a solution for this and I started searching; BINGO 🙂 bridge your WiFi network adapter with the virtual network adapter on the host machine.

The following is what I did,

  • Open Hyper-V manager
  • Click on the Virtual Network Manager and create an Internal Virtual Network by selecting Internal and clicking Add.
  • Give a meaningful Name
  • Apply and OK
  • Now a Virtual Network has been created which can be associated with 1 or more virtual machines.
  • On the host machine, in the Network and Sharing Center click on Change Adapter Settings
  • Select your WiFi Adapter and the Internal Virtual Network you created.
  • Right click and select Bridge Network and the bridge is created.
  • In the Hyper-V Manager, right click the virtual machine and select settings
  • Add a Network Adapter and select the Internal Virtual Network you created initially from the drop down.
  • click apply and ok

And that’s about it :)              

Windows Server 2008 Hyper-V issue when deployed using Sysprep Image

What a day!!!

I was preparing for a training on Windows 7 which is to be started tomorrow and was setting up the lab’s along with the virtual images. I had to set up around 10 PC’s so i thought of creating a Windows Server 2008 Image using Sysprep.exe and ImageX.exe since the virtual machines are configured to run on hyper-v.

I started off with my reference computer, by installing Windows Server 2008, Microsoft Office, etc along with the Hyper-V role installed. I made sure that the ImageX.exe is saved in a place where it can be accessed easily (D:). As soon as I installed the reference computer I opened up RUN and typed sysprep and executed the system preparation tool on which I selected the generalize option along with shutdown under the Shutdown Options.

The System Preperation Tool started its job and it completed by shutting down my reference computer which i restarted using a Windows OEM Pre Installation CD. The computer booted with the Pre installation kit, through which i navigated to my D: where i already copied my ImageX utility and executed the following command to capture the image

imagex /capture c: d:\Win2k8.wim “Win2K8”

It started to capture and save the Win2K8 image on my D drive.

Now that my reference computers image is captured, i started to apply the images on other computers by booting them up using the Windows Pre Installation CD and executing the following command

Imagex.exe /apply D:\win2k8sp2.wim 1 C:\

The image applied successfully and Windows Server 2008 was installed on all the computers. I copied the virtual images to all the computers and started one of the images, BOOOOOM!!!! It gave me an error and wouldn’t start 😦

“The virtual machine could not be started because the Hypervisor is not running” 

To see the issue is because because there is no Sysprep provider for Hyper-V. Therefore, the HypervisorLaunchType BCD entry is removed from the Boot Configuration Data (BCD) file when you run Sysprep.

And to resolve it, you will have to open CMD with elevated privilege and navigate to

C:\Windows\System32

and type the following Bcdedit /set {current} hypervisorlaunchtype auto

then restart the computer and that will fix the issue with Hyper-V not starting or loading the VM’s.  

For more information related to this error, please visit

Microsoft KB 954356