1. Check if your CPU supports virtualization technology . Download CPU-Z and check instructions list for Intel VT-X or AMD-V.
2. Check if virtualization enabled on your CPU (CPU Configuration, BIOS). For example, on Intel Sr1670HV Intel Virtualization Tech and Execute-Disable Bit Capability must be enabled. Usually, you have to just find settings (in CPU Configuration) that contains “Virtualization” or “Execution” and enable them.
3. I had a problem with enabling hypervisor on my server and both (1,2) steps did not help me.Before it I have had an issue with OS loading, so I repared my server using bootrec.exe utility (/rebuildbcd and /fixboot parameters). According with http://msdn.microsoft.com/en-us/library/windows/hardware/ff542202(v=vs.85).aspx I checked my bcdedit (just type it into cmd) for the following parameter and noticed there were no one:
hypervisorlaunchtype [ Off | Auto ]
Controls the hypervisor launch options. If you are setting up a debugger to debug Hyper-V on a target computer, set this option to Auto on the target computer.
I solved it by running bcdedit /set hypervisorlaunchtype auto.Restarted server and successfully started my VMs.
As you know, there are limitations on the available memory depending on the version of the operating system . These limitations may be caused by BIOS, hardware or instruction set architectures (x86,x64) too. Sometimes really hard to predict and troubleshoot them . Everything looks good, but doesn’t work. Let’s analyze basic steps that I have used to solve issues in different situations.
– Check memory limits for supported Windows releases
Check Memory Mode in BIOS (Independent, Channel Mirroring, Lockstep, Sparing). For example, Channel Mirroring decreases your memory size by default. To use the full size of memory you should check that Memory mode is independent
During POST, notice additional information about memory testing. Full size of memory must be OK. For example, you have 4 Gb installed memory and test shows «4096MB OK» if no problems with BIOS settings or hardware
– Sometimes the reason is hardware. I had a problem on other Intel SR1670HV server system “DIMM A1 and DIMM A2 are disabled by BIOS”. Unfortunately, it’s mainboard’s bug (upgrading firmware and replacing DIMMs don’t resolve the issue)
If your OS uses unoriginal boot configuration , check Maximum Memory option at msconfig>boot > advanced options
I’ve had a very strange memory limitiation in my OS (Server 2008 R2 SP1 Ent). After server shutdown only 4 gb of 48 gb (6 x 8 Gb) were usable. I tried to change BIOS and OS settings plus checked firmware version. Everything was fine. I did not realize one thing. Why is only 4 gb instead 8 gb? If it was problem with DIMMs I had to get 8 x X Gb of memory. If it was problem with BIOS , I had to receive an information during POST test. So, something happened bad with OS after shutdown. I decided to change server edition using DISM utility (anyway, I had to change it because of VM’s amount) Curiously enough, changing server edition is solution. (I’m sure, simple re-activation can solve too) . To re-activate or change edition use PS and DISM.
Run Powershell. Use DISM /online /Get-CurrentEdition to get your edition
Then paste DISM /online /Get-TargetEditionsto view possible target editions