Page 1 of 1
File not recognized
Posted: Sat Apr 23, 2016 12:21 am
by jadjad
I ran the V2V converter on a Hyper-V 2008r2 VHD to VMDK, but on our ESX cluster when I browse to the file location, the file is not available to use. It just shows the folder on the LUN as empty. I'm trying to add it as a hard drive to a VM I set up.
It looks like we are using vCenter Server 5.5.0. The converter recognizes the source file as a "Microsoft VHD Growable image" 60GB. I selected "VMware ESX Server image" as the output.
What version of VMDK does the converter produce when you output for ESX? Is it only compatible with certain versions of ESX?
--j
Re: File not recognized
Posted: Mon Apr 25, 2016 11:22 am
by PoSaP
Hello
Could you please try to use the function "VMware growable image"
It may help.
Re: File not recognized
Posted: Mon Apr 25, 2016 6:32 pm
by jadjad
Great! That got me past the unrecognized file, but it won't boot on the cluster.
An error was received from the ESX host while powering on VM vsrvweb01.
Failed to start the virtual machine.
Module DevicePowerOn power on failed.
Unable to create virtual SCSI device for scsi0:0, '/vmfs/volumes/56d6594a-cf146c6f-12d8-f8bc0346b23e/vsrvweb01/Server01_Base2008R2SP1_Converted.vmdk'
Failed to open disk scsi0:0: Unsupported or invalid disk type 7. Ensure that the disk has been imported.
I'm quite the n00b when it comes to converting VMs like this.
--j
Re: File not recognized
Posted: Tue Apr 26, 2016 10:22 am
by Dmitry (staff)
Hello jadjad
First time you was right, you should convert into VMware ESX server image.
Your ESXi system should see converted file.
Can you try to convert another VM?
Thank you.
Re: File not recognized
Posted: Tue Apr 26, 2016 5:04 pm
by jadjad
Holy cow! We got it to work. I reran the conversion using PoSaP's "VM growable image" format suggestion, only this time I selected IDE instead of a SCSI drive and it booted right up on the ESX cluster. I went back and double checked the original Hyper-V settings for this VM and it was indeed an IDE configured VM.
/facepalm
I'll be honest and admit that was a fundamental error, and I'm coming clean for the sake of my IT Admin soul. I hope this solution can be of value to other users.
It does appear that there is a potential compatibility issue between the Starwind V2V outputted "VMware ESX server image" file format and ESX 5.5.0 when converting a "Microsoft VDH growable image" from a Hyper-V 2008r2 cluster VM.
Thanks for the help
--j
Re: File not recognized
Posted: Wed Apr 27, 2016 10:24 am
by Dmitry (staff)
Do not hesitate to ask any additional questions
Thank you