VM /ETC

From a Microsoft Server 2008 system you can use the Hyper-V Tools MMC to create and manage virtual machines (VM) on Hyper-V hosts. In this post I demonstrate the steps to create a VM on a Hyper-V Server 2008 R2 Beta host. The environment used for creating this post consists of:

• Server 2008 64 bit running Hyper-V Tools
  • The server is also a Domain Controller
• Hyper-V Server 2008 R2 Beta
  • Joined to the Domain
• Both servers are VMs running on VMware Server 2.0

I do not want to mislead anyone. The Hyper-V VM inside the VMware Server VM will not run in my environment. I do show the process of loading the virtual CD and starting the VM along with the error message that is generated.

However, you are able to explore all the configuration options of Hyper-V Server 2008 R2 and the new VM. This may or may not be of value to you, but this post provides a visual how to demonstration that shows the simple process of creating a Hyper-V VM.

On Server 2008 Open Hyper-V Tools connected to the Hyper-V Server 2008 R2 Beta
In the Actions section click New and choose Virtual Machine to start the New Virtual Machine Wizard Click Next
Specify VM Name and Location
Assign Memory
Configure Networking !!Note: Be sure to manually create the External VM Network before creating a new VM. This is not explained here, but can be done via the Virtual Network Manager option in the Actions section of the Hyper-V Tools MMC
Connect Virtual Hard Disk. I changed the size of the .vhd from the default 127 GB to 10 GB
Installation Options I chose to install an operating system later
Completing the New VM Wizard
New VM in Hyper-V Tools MMC Now ready to connect the installation media and start the VM
Select the new VM and edit the settings to attach the Server 2008 system’s CDrom. I actually loaded a .iso file in the VMware Server VM’s vCDrom which appears as the Server 2008 VM’s physical CDrom. The settings options allow
Start the VM	Does it run hosted in a VMware Server VM ???????
The VM will not run. Hyper-V Manager gives the following error: Failed to create partition: Unspecified Error
	Check out this thread “The reason is actually quite simple and obvious if you think about it – Hyper-V depends on the hardware virtualization support of the underlying Intel or AMD processor. Only one process can control that hardware virtualization in the current iterations of CPUs, therefore a hyper-v child VM can’t possibly have access to the hardware virtualiztion – the hyper-v parent already “owns” it.”

Related Posts

• Configuring Hyper-V Tools for Hyper-V Server 2008 R2 Beta (0)
• Frustrated with Installing the Hyper-V Manager to remotely manage Hyper-V Server 2008 (10)
• Restore Connectivity To ESXi 4 Management Network After Adding Second NIC (4)
• 24 Hour Timeout Prevents Removing ESX vNetwork Distributed Switch (0)
• Rack Your Home Lab With $8 IKEA Lack Tables (9)
• Force Remove VMware Tools and Manual Clean Up (1)
• Easy Removal Of HP Server Utilities After P2V Migration (2)
• Simply Automating Virtual Machine IP Addressing For Disaster Recovery Sites (without scripting) (15)
• Increase Allowed Simultaneous VMotions of VMware Guests (3)
• VMware vSphere Client Navigation Keyboard Shortcuts (4)