Posted by: Rick Vanover
Microsoft, Microsoft Hyper-V, Rick Vanover, Virtualization, Virtualization platforms, Virtualization strategies
We continue our first look at Hyper-V technology in Windows Server 2008 . While Windows Server 2008 has been released, Hyper-V is still in pre-release form. Hyper-V is scheduled to be officially released later this year. For now, we’re really looking at a beta version of Microsoft’s new virtualization technology.
All interface-driven tasks are done through the Hyper-V Manager MMC snap-in. This snap-in is added when the Hyper-V role is added to the Windows Server 2008 system. My evaluation of Hyper-V takes place in a full install of Windows Server 2008 Standard, x64. After populating a few virtual machines into Hyper-V, a nice feature caught my eye, one showing the virtual machine uptime. The Hyper-V Manager snap-in is shown below:
Creating a virtual machine
Creating a virtual machine is wizard-driven within the Hyper-V Manager. The wizard asks the following questions while creating a new virtual machine:
- Virtual machine name – This name is used within the virtual management piece, not the DNS name or computer name of the virtual machine.
- Storage location – Hyper-V has a default location for the virtual machines, whether that be local or remote storage. A different location can be specified during the wizard.
- Memory amount – Hyper-V will give a default amount of RAM at 512, which can be changed in the wizard.
- Networking – The network assigned to the virtual machine.
- Virtual hard disk selection and size - Where the virtual hard drive is assigned on the file system. Hyper-V gives a generous 127 GB virtual hard disk size for the virtual machine, but does not allocate that footprint entirely on the file system.
- Installation options – A boot media can be assigned from a physical optical-drive or .ISO image file.
Once the virtual machine is created, you can turn it on and the virtual BIOS splash screen will appear and the virtual machine will start. The virtual machine starting up is shown below:
The virtual machine created is available to run and have an operating system installed at this point.
I hope to answer all of your questions about this virtualization platform. Please post them in the comments section below. And don’t forget to come back to the SearchServerVirtualization blogs for my next entry where I look at the Hyper-V manager and how it will fit in the enterprise.
Edit: The command line interface in the core edition of Windows Server 2008 is not PowerShell but a core prompt: Different than the normal CMD, but nowhere near as functional as PowerShell.