With the recent release of the 2010 Information Worker VM the grand old Virtual PC needs to be superseded (for me) by the colossus of virtualisation that is Hyper-V. I run a (fairly quick) laptop with the elegant Windows 7 and the ever-boisterous Office 2010 beta (including Project and Visio). What would be my route ahead? Naturally it would be Windows Server 2008 R2 X64 [Rim-shot sound and supportive polite applause from other Villagers].
After an abortive attempt to setup a ‘boot from VHD’ configuration (my fail – it clearly works fine for others) I decided that introducing a well-behaved neighbour of an operating system to share some silicon in an old fashioned dual-boot setup would fall into the ‘suits you sir’ category. After a brief Google, this seemed to be 1. Possible 2. Do-able 3. and most importantly, do-able by me. But How? Could it be as simple as run Setup.exe and DON’T USE C:/WINDOWS?
Fortunately, my laptop has a small partition which I can hijack for the purpose (but I can’t tell you what it is ‘cause you’ll laugh). The question was how much space would be required – baby lemur or sasquatch footprint – Core is not really an option for me despite the amount of command-let and scripting support on the web – nowadays I need an interface which supports me like a virtual Zimmer-frame.
A blog entry (which I can’t find again) mentioned a 6Gb installation so I decided to crash ahead confident of success!!
1.2008 R2 Standard edition has nestled snugly into a 6.5Gb corner of my available extra partition. 2. I now have an (automatically generated) dual boot menu offering me a choice of 2 of Microsoft’s best. 3. Said instance of Win 2008 R2 with the Hyper-V role occupies only around 630Mb of RAM and 4. All do-able by me so far.
The next step is to assemble the VM’s from the down-loaded RAR’s and check that they play nice in my modest sandbox.