.NET (29) Archiving (10) ASP.NET (9) Books (3) C Sharp (30) Code Generation (3) Dasblog (16) Design Patterns (4) Development (37) Exchange (14) Family (10) GPS (7) Hardware (10) mixuk07 (1) Mountaineering (7) MSCRM (6) Office (3) Outlook (13) Personal Development (4) PHP (4) PowerShell (7) Productivity (9) RSS (15) Running (2) Scripting (20) SCRUM (3) Service (3) Software (60) Support (17) TaHoGen (2) Technical (50) Tools (13) Twitter (5) Web (16) Windows 7 (4) Windows Mobile (10) WS* (1)
Sign In
I ran into some trouble with Hyper V the other day – I had booted from a VHD into Windows Server 2008 R2 and was trying to start a VM – I got the usual ‘The virtual machine could not be started because the hypervisor is not running” error.I had just had a BIOS failure on the machine so I figured it may have switched hardware virtualization support off in the BIOS when it reloaded the defaults.
Checking the BIOS, I found it was switched on – strange. I Googled a bit but everything seemed to be around flipping the setting in BIOS, when I knew to be correct.Some further investigation around the boot environment and BCDEDIT settings I found the parameter “HypervisorLaunchType”, thinking this could well be connected, I set the parameter to “auto” in the BCD configuration:
BCDEDIT /set {big-long-guid} hypervisorlaunchtype auto
This fixed it !!So now all my BCD configurations go like this:
BCDEDIT /copy {current-or-guid} /d "New Boot Option" BCDEDIT /set {new-guid} device vhd=[V:]\vmimage.vhd BCDEDIT /set {new-guid} osdevice vhd=[V:]\vmimage.vhd BCDEDIT /set {new-guid} detecthal on BCDEDIT /set {new-guid} hypervisorlaunchtype auto
Remember Me
a@href@title, b, blockquote@cite, em, i, strike, strong, sub, sup, u