mountainss Cloud and Datacenter Management Blog

Microsoft SystemCenter blogsite about virtualization on-premises and Cloud

Multi-Hypervisor Management with System Center 2012 Virtual Machine Manager #SCVMM to #Hyperv


Architecture SCVMM environment.

In the example above, the Order Processing Tier is installed on a VMware ESXi host, while the business logic tier is installed on a Hyper-V host. As we discussed earlier, VMM can configure and deploy your private cloud infrastructure by abstracting the hypervisor layer and deploying VMs and applications in a consistent manner using service templates.

For the costs of licensing you can check this site The Microsoft Private Cloud Economics Tool

More Microsoft information about Multi-Hypervisor :  Multi-Hypervisor Management in System Center 2012

How to Convert VMware Virtual Machines to Hyper-V

VMM supports the V2V machine conversion of virtual machines that are running on the following versions of VMware ESX:

  • ESX/ESXi 3.5 Update 5
  • ESX/ESXi 4.0
  • ESX/ESXi 4.1
Before you convert a VMware virtual machine to a Hyper-V virtual machine, you must uninstall VMware Tools on the guest operating system of the virtual machine.

To convert a VMware virtual machine to a Hyper-V virtual machine

    1. Open the VMs and Services workspace.
    2. On the Home tab, in the Create group, click the Create Virtual Machine drop-down arrow, and then click Convert Virtual Machine.The Convert Virtual Machine Wizard opens.

  1. On the Select Source page, next to the Select the virtual machine that you would like to convert box, click Browse.
  2. In the Select Virtual Machine Source dialog box, click the VMware virtual machine that you want to convert, and then click OK.
    Verify that the Virtualization Platform column indicates VMware ESX Server.
  3. On the Select Source page, click Next.
  4. On the Specify Virtual Machine Identity page, either keep or change the virtual machine name, enter an optional description, and then click Next.
    The virtual machine name identifies the virtual machine to VMM. The name does not have to match the computer name of the virtual machine. However, to avoid confusion, we recommend that you use the same name as the computer name.
  5. On the Virtual Machine Configuration page, configure the number of processors and the amount of memory to assign (in megabytes or gigabytes), and then click Next.
  6. On the Select Host page, select a Hyper-V host for placement, and then click Next.
  7. On the Select Path page, do the following, and then click Next:
    1. In the Storage location box, configure the storage location on the host for virtual machine files. By default, the default virtual machine paths on the target host are listed. To select a different location, click Browse, click a folder, and then click OK.
      As a best practice, do not specify a path that is on the same drive as the operating system files.
    2. If desired, select the Add this path to the list of default storage locations on the host check box.
  8. On the Select Networks page, select the logical network, the virtual network and the VLAN (if applicable) to use for the virtual machine, and then click Next.
    The list of available logical networks, virtual networks, and VLANs matches what is configured on the host physical network adapters.
  9. On the Add Properties page, configure the desired settings, and then click Next.
  10. On the Summary page, review the settings. Optionally, select the Start the virtual machine after deploying it check box. To start the conversion process, click Create.The Jobs dialog box appears to indicate the job status. Verify that the job has a status of Completed, and then close the dialog box.
  11. To verify that the virtual machine was converted, do the following:
    1. In the VMs and Services workspace, locate and then click the Hyper-V host that you selected during placement.
    2. On the Home tab, in the Show group, click VMs.
    3. In the VMs pane, verify that the virtual machine appears.

Author: James van den Berg

I'm Microsoft Architect and ICT Specialist and Microsoft MVP System Center Cloud and Datacenter Management

2 thoughts on “Multi-Hypervisor Management with System Center 2012 Virtual Machine Manager #SCVMM to #Hyperv

  1. Pingback: Multi-Hypervisor Management with System Center 2012 Virtual … | Network Storage Report

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s