converter 5.0 will crash when vcenter is upgraded to 5.1. Does anybody know any temp work around or fix? thanks
Well this totally blows. It would be nice to get an ETA to when a "working" converter will be released. Rolled out a standalone server using 5.1 (I'll think twice about using the "latest" versions of ESXi in the future), sent it to a remote client 500 miles away in hopes of P2Ving their old physical server.
Yep, we got stuck as well.
I'm moving machines by connecting them to the ISCSI network and doing migrate to the vmdk
Afterwards migrating the host
But it requires me to have them on the same datacenter and to convert them from other VMware servers.
Any workaround for converting hyper-v VMs? Maybe a third-party tool?
Hey no worries everyone. Because of a project deadline I will be forced to rebuild ESX server as 5.0 on Monday, so that I can use the vmware converter tool.
The fix for this is sure to come out the minute after I am done.
Per some advice I read in another thread I was able to do a P2V conversion using version 4.1 of the standalone converter (didn't bother trying 4.3, but thinking that version may work too)! It's currently running now, waiting for it to complete... if it fails I'll update this post.
A solution I'm going to approach is the following:
1. Prepare a system with the free vSphere Hypervisor 5.0
2. Proceed with the conversion of the server (Server 2003) with the target being vSphere Hypervisor 5.0
3. Once the conversion is done, immedietly move/copy the file to ESXi 5.1
Anyone see a problem with this approach?
I was able to convert SBS2008 to esxi 5.1 using converter 4.3 but what I did to get it to work was weird. For those of y'all that know what you are doing, you may laugh at the steps I took (I'm not very knowledgeable of the product) but it worked for me. Here is what I did:
Funny I had the same 95% issue converting a 2003 SBS server. My issue was that there was software RAID and the primary disk wasn't marked as active. I attached the vmdk to another machine, marked it as active in disk manager and it booted up.
I believe you can upgrade the v4 VM to a v7 v8 VM by shutting it down, right clicking in vSphere, upgrade hardware.
I would like to thank everyone for highlighting this issue and for sugegsting the various possible solutions.
While there are few possible workarounds (described in this KB article) we consider this issue with highest priority and we're actively working on resolving it as soon as possible.
If you subscribe for updates on this KB article you'll be notified when it is resolved.
-- Antoan Arnaudov
Product Manager @ VMware