Search This Blog

Tuesday, January 20, 2015

Physical to Virtual Machine Conversion–Using Microsoft Virtual Machine Convertor 3.0

 

We just tested MVMC 3.0 (updated on 2 Dec 2014) to perform P2V for the following guest operating system:-

  • Windows Server 2008 R2
  • Windows Server 2012
  • Windows Server 2012 R2
  • Download MVMC 3.0 – Click here

    Make sure MVMC is installed on the host which has installed the following requirements:-

  • .Net Framework 3.5 and .Net 4 (if host running Win 2008 R2 SP1)
  • .Net framework 4.5 (if host running Win 2012 or Win 8)
  • Visual C++ Redistribution for Visual Studio 2012 Update 1. Download Update 4 from here
  • Install BITS feature. Make sure BIT-Compact Server. We forget to install Compact Server features, causing us to fail P2V a server. So remember, to drill into BIT and tick Compact Server features.
  • a Shared folder (refer to screenshot)
  • a Working Folder (refer to screenshot)
  • [ Configuration ]

    Select “Physical machine conversion”

    1

    Enter your source (physical server) details and authentication

    2

    MVMC will install an agent into the source machine

    3

    Once detected, the system will list down and allow you to select partition to convert to Hyper-V Virtual disk. You can select to convert all disk or selected disk. Here it also allow you to specify VHD type format: dynamic or fixed disk.

    4

    Enter new VM name and VM specification (CPU and Memory)

    5

    Next is enter your destination Hyper-V Server detail and credential to hold the virtual machine result.

    6

    Specify a temporary share folder to host the conversion data . Make sure you have sufficient hard disk space.

    7

    The end result will store in working folder

    8

    On the next page, you can define to connect to virtual switch or remain unconnected

    9

    Review the summary before begin the P2V process.

    10

    The end result, MVMC will convert to

    • VHD format
    • Size remain the same after conversion. Mean if your existing size is 1 TB and use space only 30GB, the end result will create 1 TB size. You still need to perform own shrinking to reduce the size.
    • Additional data disk will remain in offline state. You need to manually online the disk. The disk will located in SCSI controller.
    • Virtual disk will name according to drive letter. Example: C.vhd, D.vhd.

    No comments:

    Post a Comment