Composing a Gen 1/VHD - Conversion Processes and Limitations of Conversion Tools (ASR Requirements) [DRAFT]

Donald Van Patten -

First Direct Lending
 
A little bit of digging tells me that to export from vCenter, you use a vSphere client (either standalone or web based), which means the option is an OVA/OVF file.
 
There is a VMware standalone converter, but that is only for moving virtual machines among the different VMware products (Fusion [Mac], Workstation [Windows], etc) and it does not write a usable disk image.
 
There is another VMware tool I’ve used in the past, OVFtool. It is command line only and creates an OVA/OVF file(s). So if the GUI approach is to hard, this is worse.

-----------------------------------------------------------------------------------

This is for vSphere, I still need to look at the vCenter export options.

Customer Side
 
Export VM to OVA or OVF.
Give exported file(s) to Workspot.
                Things that are good to know about the VM
                Number of cores
                Amount of memory
                Number of NIC’s
                Admin or user password
 
On Workspot side
Copy OVA/OVF to hv05
If single OVA file, use 7-zip or similar to extract *.vmdk files
If OVF (folder of files), identify *.vmdk files
Install Microsoft Virtual Machine Converter (this is already on hv05)
Start Powershell with elevated privileges
 
PS C:\> Import-Module "C:\Program Files\Microsoft Virtual Machine Converter\MvmcCmdlet.psd1"
PS C:\> ConvertTo-MvmcVirtualHardDisk .\SourceVMwareDisk.vmdk -DestinationLiteralPath .\DestinationHyper-VDisk.vhd -VhdType FixedHardDisk -VhdFormat Vhd
 
If necessary copy new *.vhd disk to Hyper-V
 
Create new Hyper-V VM
Do not create disk
After VM is created, add converted disk
 
This has worked exactly once, so consider it a work in progress
 

---------------------------------------------------------------

No single path.............

Initial/Common:

  • OS Disk < 300 Gig
  • System name – Not have special characters, including ‘_’
  • Server 2012r2 or 2016 with Hyper-V role enabled. Hyper-V Core is not adequate
  • If upload process includes conversions, free disk space (2 x size of VM), ideally on the Hyper-V server or other high speed storage connection
  • Hyper-V server needs network connectivity to source machine or VM host and Azure.

Potential Path Entry Points:

  • Physical Machine
  • VMware VM
  • Hyper-V VM
  • VMDK – Vmware disk image
  • VHD – Hyper-V Generation 1 disk image
  • VHDX – Hyper-V Generation 2 disk image
  • Other

Physical Machine

  1. ASR or P2V process goes here

VMware VM

  1. ASR process goes here

Hyper-V VM

  1. ASR process goes here

VMDK

  1. TBD

VHD

  1. On Hyper-V server create Generation 1 Virtual Machine with no disk
  2. Attach VHD disk(s) to newly created system
  3. Boot VM
  4. If system boots, continue using Hyper-V VM process
  5. If system does not boot, there may be an issue with VHD image.
  6. Remove (disconnect) the VHD disk from the VM
  7. Use Powershell convert-vhd cmdlet to try and convert from Generation 1 (VHD) to Generation 2 (VHDX) format
  8. Attach the new VHDX disk to VM
  9. Boot VM
  10. If system boots, continue using the Hyper-V VM process.
  11. If system does not boot, remove the VHDX disk from the VM
  12. Use Powershell convert-vhd cmdlet to convert Generation 2 (VHDX) to Generation 1 (VHD) format
  13. Attach the new VHD disk to VM
  14. Boot VM
  15. If system boots, continue using the Hyper-V VM process.
  16. If the system does not boot try using the VHDX process

VHDX

  1. On Hyper-V server create Generation 2 Virtual Machine with no disk
  2. Attach VHD disk(s) to newly created system
  3. Boot VM
  4. If system boots, continue using Hyper-V VM process
  5. If system does not boot, there may be an issue with VHDX image.
  6. Remove (disconnect) the VHDX disk from the VM
  7. Use Powershell convert-vhd cmdlet to try and convert from Generation 2 (VHDX) to Generation 1 (VHD) format
  8. Attach the new VHD disk to VM
  9. Boot VM
  10. If system boots, continue using the Hyper-V VM process.
  11. If system does not boot, remove the VHD disk from the VM
  12. Use Powershell convert-vhd cmdlet to convert Generation 1 (VHD) to Generation 2 (VHDX) format
  13. Attach the new VHDX disk to VM
  14. Boot VM
  15. If system boots, continue using the Hyper-V VM process.
  16. If the system does not boot try using the VHD process

Other VM

Other disk image

  1. Use qemu to convert disk image to VHD
  2. Follow VHD process

 

===============================================

20170620-VMReadinessForAzureMigration.txt


===P2V and Image Conversion to Azure-Compatible===
=====Generation 1 - VHD==================
=========UEFI-to-BIOS==================

hyper-V UEFI format
https://www.google.com/search?q=hyper-V+UEIF+format&oq=hyper-V+UEIF+format&aqs=chrome..69i57.10312j0j8&sourceid=chrome&ie=UTF-8

The generation of a virtual machine determines the virtual hardware and functionality that is presented to the virtual machine. In Hyper-V there are two supported virtual machine generations, generation 1 and generation 2. Generation 2 virtual machines have a simplified virtual hardware model, and supports Unified Extensible Firmware Interface (UEFI) firmware instead of BIOS-based firmware. The majority of legacy devices have also been removed from generation 2 virtual machines.


How to P2V Windows Server 2012 R2 with UEFI and a GPT disk
https://4sysops.com/archives/how-to-p2v-windows-server-2012-r2-with-uefi-and-a-gpt-disk/

Generation 2 Virtual Machine Overview
https://technet.microsoft.com/en-us/library/dn282285(v=ws.11).aspx

Notes of UEFI, GPT, UEFI boot process, disk partitions, and Hyper-V differencing disks with a Generation 2 VM
https://rakhesh.com/windows/notes-of-uefi-gpt-uefi-boot-process-disk-partitions-and-hyper-v-differencing-disks-with-a-generation-2-vm/

Converting Hyper-V UEFI VM to BIOS VM on Acropolis HV
http://harshahosur.com/2016/01/converting-uefi-vm-to-bios-vm-on-acropolishv/

How to convert UEFI or GPT Windows Server Partitions to Hyper V
https://www.youtube.com/watch?v=DDaSFRAviq4

----------------
https://www.google.com/search?q=can+a+generation+1+vm+be+in+uefi+format&oq=can+a+generation+1+vm+be+in+uefi+format&aqs=chrome..69i57.15579j0j8&sourceid=chrome&ie=UTF-8


Should I create a generation 1 or 2 virtual machine in Hyper-V?
https://docs.microsoft.com/en-us/windows-server/virtualization/hyper-v/plan/should-i-create-a-generation-1-or-2-virtual-machine-in-hyper-v

================================================================================

vmdk to vhd converted vm black screens with fast blink cursor

1.Boot the guest OS off of the Windows CD or mount the ISO.
2.Select: recovery options.
3.From the command prompt.
4.Run: bcdedit
5.You should see the boot manager in one partition and the loader in another one.
1.If so run:
bootrec /fixmbr
bootrec /fixboot
reboot guest

2.If not in separate partitions:
Run:
bcdboot C:\Windows
reboot guest:

On-Premises Management Server Prerequisites:
1-1. Windows Server 2012 R2
1-2. Network Connectivity to Azure (See ASR documentation for necessary details)
1-3. Static IP address
1-4. English Operating System
1-5. VMware vSphere PowerCLI 6.0
- latest at this writing, VMware-PowerCLI-6.5.0-4624819, does not work error says install current version
- this version worked - VMware-PowerCLI-6.0.0-2548067
Note: PowerCLI, language and OS supported may change
Documentation: https://aka.ms/asr_vmware, https://aka.ms/asr_deployment_planner
https://docs.microsoft.com/en-us/azure/site-recovery/site-recovery-vmware-to-azure
https://www.microsoft.com/en-us/download/confirmation.aspx?id=41653

===============================================================================================

Microsoft Virtual Machine Converter 3.1
https://www.microsoft.com/en-us/download/details.aspx?id=42497
<font face="Times New Roman, serif"><font size="3"><font color="#3d464d"><font face="Segoe UI, serif"><font size="2"><em>
(*) Microsoft Virtual Machine Converter 3.1 - the link is for MVMC 3.0 but the downloaded MSI file is version 3.1.</em></font></font></font></font></font>
<br />

Microsoft Virtual Machine Converter 3.1 - where is the downloaded url?
https://social.technet.microsoft.com/Forums/ie/en-US/36799874-7b82-4559-9d54-0d735579be2c/microsoft-virtual-machine-converter-31-where-is-the-downloaded-url-?forum=MVMC

NOT GOOD -- In some non-MS article , they might mentioned 3.1 version but the link still point to MVMC 3.0:
http://www.experts-exchange.com/articles/17453/HOW-TO-P2V-V2V-for-FREE-to-Hyper-V-Microsoft-Virtual-Machine-Converter-3-1.html

----------------------------------------------------------------------------------------------------
Availability and support for the converter ends on June 3, 2017.
Azure Site Recovery is recommended as the long-term solution.
For details about the retirement of Microsoft Virtual Machine Converter, see the blogpost,
Important update regarding Microsoft Virtual Machine Converter (MVMC).

Requirements for Conversion to Hyper-V Destination - Updated: June 8, 2016
https://technet.microsoft.com/en-us/library/dn874003(v=ws.11).aspx
------------------------------------------------------------------
(*) Applies To: Hyper-V Server 2012, Windows Server 2012 R2, Windows Server 2012,
Hyper-V Server 2012 R2, Azure, Windows Server 2008 R2 with SP1
(*) Important: Remote access through Windows Management Instrumentation (WMI) must be enabled
on the source virtual machine. For more information, see Requirements for Conversion to
Hyper-V Destination in this guide.
------------------------------------------------------------------
the link ist for MVMC 3.0 but the downloaded MSI file is version 3.1
https://www.microsoft.com/en-us/download/details.aspx?id=42497

----------------------------------------------------------------------------------------------------
Microsoft Virtual Machine Converter
https://technet.microsoft.com/en-us/library/dn874008%28v=ws.11%29.aspx?f=255&MSPPError=-2147217396

Convert VMware virtual machines and virtual disks to Hyper-V by using the GUI
https://technet.microsoft.com/en-us/library/dn874008%28v=ws.11%29.aspx?f=255&MSPPError=-2147217396#Convert VMware virtual machines and virtual disks by using Windows PowerShell

 

Have more questions? Submit a request

Comments

Powered by Zendesk