Well, almost J
I got a new laptop last year and having bumped up the RAM and disk, I wanted to use for a virtualised lab on board whilst travelling or at clients. Having experimented and asked around on Twitter there was no way (my preferred method) of having Windows 7 with ESXi running under VMware Workstation and then have 64bit guests in vCentre – the VT is not exposed to the ESX guests. This would have given me the best of ESXi (and a VMware lab), and the VM’s I wanted for carrying a lab in the bag. VMware workstation was not much use to me as without any memory management I would run out of headroom (although the tree cloned drives would be nice).
A non-trivial additional factor was that I insist on encrypted disks in my laptops.
I then experimented with getting a dual boot world going. BitLocker and Boot from VHD work well, but not together. I got a Bitlockered guest machine under Hyper-V as a VHD to boot, but the content was a bit flaky – device drivers). I then tried getting a dual boot to work with the second boot from a VHD but BitLocker got in the way. See: Am I really asking too much of Hyper-V I learned a bit about BDCEDIT along the way.
Becoming impatient, I then restarted my thinking. I continued with the Windows 2008 R2 build (Bitlockered drive), with the intent of then building the VM’s that I wanted.
The first bit was to get Windows Server 2008 R2 look more like Windows 7 so it could be my standard desktop-like working world along with some other bits and pieces – I added the following to the machine (some are dependencies):
- Web Server (IIS)
- .NET Framework 3.5.1 Features
- Desktop Experience
- Ink and Handwriting Services (it’s a tablet)
- Telnet Client (I never usually remember this is off by default!)
- PowerShell ISE
- Wireless LAN Service (it’s a laptop!)
- BitLocker Drive Encryption
- Group Policy Management
- Windows Server Migration Tools (just in case)
So over to the internet.
The first hit was “Create Dual Boot” solution. This works by duplicating the boot entry (back to BCDEDIT), and then you choose to run with or without Hyper-V. Without Hyper-V you can hibernate the machine and bring it back quickly. But you need to reboot the machine to get Hyper-V back, and then you can start your VM’s. After that you can run your productivity apps, but can no longer hibernate the machine. This can be found here: Creating a no hypervisor boot entry on Windows Server 2008
And then I found this:
All you do is the following three steps:
- Set Hyper-V to start on demand “SC CONFIG HVBOOT START= DEMAND” (note the space after the = sign); then reboot the machine
- Enable Hibernation “POWERCFG -HIBERNATE ON”
- Then when you want to run VM’s – “NET START HVBOOT”
Lo and behold. I have a single boot machine. Until I start HVBOOT then the machine will hibernate. Once you have started HVBOOT, then you have to shut down the machine instead, but this is good enough for now. I’m not certain what impact not running Hyper-V will have on the performance of the machine, but not much I guess.
Well I guess that I might put VMware Workstation on as well to get some VM’s running whilst still being able to hibernate – maybe just 1 or two so that I can PowerShell in Windows 7 as well… If only Workstation could use VHD’s (or Hyper-V VMDK’s!!!!)