Your error is (agent's log):
2015-05-05T17:55:19.643-07:00 [03300 warning 'Default'] Failed to get capacity for \\.\PhysicalDrive1: error opening disk device: The process cannot access the file because it is being used by another process (32)
2015-05-05T17:55:19.643-07:00 [03300 warning 'Default'] Skipping hard disk '\\.\PhysicalDrive1'
Turn off anti-virus and other programs that prevents access to the disk.
HTH
I am installed the agent on source machine ,The successful completion of the conversion, thank you, but I still don't understand why, through the intermediate machine network conversion error.
Good news! 
There are thousand different problems with networking, if you can succeed to connect \\<ip>\ADMIN$ share, with given credentials, and upload a file(s) there, then the error is in converter, otherwise not 
HTH
Hello Support
I used kvm, but I need to migrate to VMware Workstation 11 and images of vmx
The kvm used qcow2 images.
I tried
qemu-img convert /media/Secure_HDD/images/Virtual_Client_for_Linux_Windows_7-KVM-2.qcow2 -O vmx win7.vmx
but the linux command returns..
Unknown file format 'vmx'
Is there any migration option?
Thank you!
Yes, you can convert your machine when it's powered, use 'Powered-on Machine' option.
HTH
the IP helper should be an IP that's on the same subnet as your vcenter but not in use (not pingable)
I have been reading and researching for days on how to convert a VM to another VM in same vmware cluster, with same name, IP, etc but just a different size disk. I am doing this for the purpose of reclaiming disk space on the SAN for VMS that were sized too large. The documentation ends before the necessary information is conveyed to be able to complete this. It ends abrubtly by saying "now select the destination system"..... however this is not straightforward information and as this is my first time doing a V2V conversion I more information.
For instance, I am prompted to select a location for the virtual machine which is a network path. I don't know what this is...I am assuming I would want the VM on my SAN, but we don't browse to our SAN on the the network. We only see it from the vcenter hosts. So, is this my vcenter IP address that is the location for the new virtual machine? I hope not since it is vcenter server I am hoping to resize. If I can't do this one its ok, I have others I need to do, but my same questions still apply.
Does anyone else know how I can resize a VM easily? I truly appreciate any help you can give me. As I said, the directions are not thorough, and having a very difficult time finding something on other sites.
I am vsphere 5.5 and converter 5.5
Hi Staciej0,
You can use the VMware Converter to go From your vCenter to your vCenter, the destination should be your vCenter not your SAN directly.
From there once you have selected your vCenter as a destination you will be able to see the datastores, select one of those.
You can clone your vCenter.
When you get to the disk options in the conversion process there will be a "Advanced" option this will allow to select Block Level or File Level Cloning of the disks you want File Level that way you can select your size.
Cheers
@iiToby
Hello Stacie,
I suppose you have read at the wrong place. Have a look at page 48, "Select a Destination for the New Virtual Machine", "Select a Managed Destination".
HTH
Plamen
Hello all,
As you know, Converter 6.0 is now GA. It now officially supports CentOS (v. 6 and 7). However there is more than that which is not in the docs.
As you probably also know, the tricky part in Linux P2V is reconfiguration. Which means the cloning itself would run successfully for virtually any Linux distro, but reconfiguration has specifics that vary across distros and versions, mostly (but not only) related to creating the initial ramfs.
Converter detects the source distro and version and uses this information to setup the appropriate reconfigurators. If it does not recognize it, it defaults to a predefined behavior and hopes for the best. For example, CentOS is so similar to RHEL, that if reconfiguration is done the RHEL way, that would be enough. However, Converter versions prior to 6.0 were not able to do it because of this logic.
In Converter 6.0 we have extended this logic - it recognizes a few other distros and uses the reconfiguration of the supported 'relative' distro. This is an approximation, the real logic is more complex. E.g dracut is becoming a de facto standard as a tool for creating the initial ramfs; Converter uses that, and if the source supports dracut, it uses it to create the initrams image regardless of the distro.
But basically these are:
Disclaimer: Only distros and versions mentioned in the User's Guide and Release Notes are officially supported!
All others have passed very limited testing (i.e. don't be surprised if anything doesn't work as expected). This post is aimed to improve the experience in the gray area of "this is not supported but sometimes it may work".
Thank you for your attention and best regards,
Plamen
Hello,
I've used the VMWare converter standalone on older PC's with out an issue.
When I tried to use this on a Lenovo Laptop running Windows 8.1 I get the following error when I select the destination.
The destination does not support EFI firmware.
I've selected destination type as VMWorkstation or other VMWare virtual machine.
I've selected the VMWare product as VMWare workstation 7.0.x
I'm not sure what I am doing incorrectly.
I've google for this but I don't seem to be getting any further forward with this one.
Can any one help?
Thank you.
Seamus
Hello exonio,
Now you can use "VMware vCenter Converter 6.0.0". I tested it on Ubuntu 14.04 Server 64bit and now it converts and boots without issue.
Cheers,
Munkhbayar Batkhuu
Hi All,
Now you can convert Ubuntu 14.04 Server with newly released VMware vCenter Converter 6.0.0.
I tested it personally and it converts and boots without issue.
Cheers,
Munkhbayar Batkhuu
Hi All,
Now you can convert Ubuntu 14.04 Server with newly released VMware vCenter Converter 6.0.0.
I tested it personally and it converts and boots without issue.
Cheers,
Munkhbayar Batkhuu
Hello
Select Workstation 8 or newer.
HTH
Plamen
Note: I've removed specific server names from the logs.
I've been working on a P2V for a few days with zero success. The error I am getting is: A general system error occurred platform-specific error 38. If I look into vCenter the VM will be created and then deleted within about 20 seconds and fail before 1%.
The specific server details are:
Windows Server 2008 x64.
VMware Converter Standalone 6.0 (I've tried versions 5.5.3 and 4.1 and the exact thing happens)
The first time I attempted to P2V this server it made it to 80ish percent and then rebooted. Ever since then I've been getting this failure. I had noticed there were some old folders in the vSAN datastore referencing this server so I removed that folder which did not resolve the problem.
This area of the log seems to be the portion where it fails:
2015-05-19T11:21:01.345-04:00 info vmware-converter-worker[05232] [Originator@6876 sub=task-1] GetManagedDiskName: Get virtual disk filebacking [vsanDatastore] ca545b55-ffc5-354a-c334-fc15b4132df0/<VMNAME>.vmdk
2015-05-19T11:21:01.345-04:00 info vmware-converter-worker[05232] [Originator@6876 sub=task-1] GetManagedDiskName: updating nfc port as 902
2015-05-19T11:21:01.345-04:00 info vmware-converter-worker[05232] [Originator@6876 sub=task-1] GetManagedDiskName: get protocol as vpxa-nfcssl
2015-05-19T11:21:01.345-04:00 info vmware-converter-worker[05232] [Originator@6876 sub=task-1] GetManagedDiskName: Get disklib file name as vpxa-nfcssl://[vsanDatastore] ca545b55-ffc5-354a-c334-fc15b4132df0/<VMNAME>.vmdk@<ESXiHOSTNAME>:902!52 a3 49 48 4d 8d f5 c1-cf 8a 14 3d 95 19 3b 78
2015-05-19T11:21:03.155-04:00 info vmware-converter-worker[05232] [Originator@6876 sub=Default] error 'Insufficient permission to access file' (error code:38) creating child in DiskLib
2015-05-19T11:21:03.264-04:00 info vmware-converter-worker[05232] [Originator@6876 sub=Default] error 'Insufficient permission to access file' (error code:38) creating child in DiskLib
2015-05-19T11:21:03.264-04:00 info vmware-converter-worker[05232] [Originator@6876 sub=Default] Error 38 opening disk vpxa-nfcssl://[vsanDatastore] ca545b55-ffc5-354a-c334-fc15b4132df0/<VMNAME>.vmdk@<ESXiHOSTNAME>:902!52 a3 49 48 4d 8d f5 c1-cf 8a 14 3d 95 19 3b 78.
2015-05-19T11:21:03.264-04:00 warning vmware-converter-worker[05232] [Originator@6876 sub=Default] ERROR 38 opening disk disk-2000.
2015-05-19T11:21:03.264-04:00 info vmware-converter-worker[05232] [Originator@6876 sub=Default] Attempt to opening disk disk-2000 again [rest 2] (sleep for 5 sec).
2015-05-19T11:21:08.272-04:00 info vmware-converter-worker[05232] [Originator@6876 sub=task-1] Reusing existing VIM connection to <VCENTERNAME>
2015-05-19T11:21:08.287-04:00 info vmware-converter-worker[05232] [Originator@6876 sub=task-1] GetManagedDiskName: Get virtual disk filebacking [vsanDatastore] ca545b55-ffc5-354a-c334-fc15b4132df0/<VMNAME>.vmdk
2015-05-19T11:21:08.287-04:00 info vmware-converter-worker[05232] [Originator@6876 sub=task-1] GetManagedDiskName: updating nfc port as 902
2015-05-19T11:21:08.287-04:00 info vmware-converter-worker[05232] [Originator@6876 sub=task-1] GetManagedDiskName: get protocol as vpxa-nfcssl
2015-05-19T11:21:08.287-04:00 info vmware-converter-worker[05232] [Originator@6876 sub=task-1] GetManagedDiskName: Get disklib file name as vpxa-nfcssl://[vsanDatastore] ca545b55-ffc5-354a-c334-fc15b4132df0/<VMNAME>.vmdk@<ESXiHOSTNAME>:902!52 c4 4f 5f 39 0c c3 12-18 2b 4c 44 77 75 63 ad
2015-05-19T11:21:10.035-04:00 info vmware-converter-worker[05232] [Originator@6876 sub=Default] error 'Insufficient permission to access file' (error code:38) creating child in DiskLib
2015-05-19T11:21:10.159-04:00 info vmware-converter-worker[05232] [Originator@6876 sub=Default] error 'Insufficient permission to access file' (error code:38) creating child in DiskLib
2015-05-19T11:21:10.159-04:00 info vmware-converter-worker[05232] [Originator@6876 sub=Default] Error 38 opening disk vpxa-nfcssl://[vsanDatastore] ca545b55-ffc5-354a-c334-fc15b4132df0/<VMNAME>.vmdk@<ESXiHOSTNAME>:902!52 c4 4f 5f 39 0c c3 12-18 2b 4c 44 77 75 63 ad.
2015-05-19T11:21:10.159-04:00 warning vmware-converter-worker[05232] [Originator@6876 sub=Default] ERROR 38 opening disk disk-2000.
2015-05-19T11:21:10.159-04:00 info vmware-converter-worker[05232] [Originator@6876 sub=Default] Attempt to opening disk disk-2000 again [rest 1] (sleep for 10 sec).
2015-05-19T11:21:20.175-04:00 info vmware-converter-worker[05232] [Originator@6876 sub=task-1] Reusing existing VIM connection to <VCENTERNAME>
2015-05-19T11:21:20.206-04:00 info vmware-converter-worker[05232] [Originator@6876 sub=task-1] GetManagedDiskName: Get virtual disk filebacking [vsanDatastore] ca545b55-ffc5-354a-c334-fc15b4132df0/<VMNAME>.vmdk
2015-05-19T11:21:20.206-04:00 info vmware-converter-worker[05232] [Originator@6876 sub=task-1] GetManagedDiskName: updating nfc port as 902
2015-05-19T11:21:20.206-04:00 info vmware-converter-worker[05232] [Originator@6876 sub=task-1] GetManagedDiskName: get protocol as vpxa-nfcssl
2015-05-19T11:21:20.206-04:00 info vmware-converter-worker[05232] [Originator@6876 sub=task-1] GetManagedDiskName: Get disklib file name as vpxa-nfcssl://[vsanDatastore] ca545b55-ffc5-354a-c334-fc15b4132df0/<VMNAME>.vmdk@<ESXiHOSTNAME>:902!52 71 6c db 92 78 8d bf-b8 f7 a0 f6 88 c8 3c dc
2015-05-19T11:21:21.969-04:00 info vmware-converter-worker[05232] [Originator@6876 sub=Default] error 'Insufficient permission to access file' (error code:38) creating child in DiskLib
2015-05-19T11:21:22.093-04:00 info vmware-converter-worker[05232] [Originator@6876 sub=Default] error 'Insufficient permission to access file' (error code:38) creating child in DiskLib
2015-05-19T11:21:22.093-04:00 info vmware-converter-worker[05232] [Originator@6876 sub=Default] Error 38 opening disk vpxa-nfcssl://[vsanDatastore] ca545b55-ffc5-354a-c334-fc15b4132df0/<VMNAME>.vmdk@<ESXiHOSTNAME>:902!52 71 6c db 92 78 8d bf-b8 f7 a0 f6 88 c8 3c dc.
2015-05-19T11:21:22.093-04:00 warning vmware-converter-worker[05232] [Originator@6876 sub=Default] ERROR 38 opening disk disk-2000.
2015-05-19T11:21:22.093-04:00 error vmware-converter-worker[05232] [Originator@6876 sub=task-1] [BaseDiskSetComputer::OpenDiskSet] OpenDisks failed, mntapi error: 609
2015-05-19T11:21:22.093-04:00 error vmware-converter-worker[05232] [Originator@6876 sub=task-1] [BaseDiskSetComputer::AnalyzeErrorAndThrow] Error occurred when opening disk set, MNTAPI_ERROR = 609 MNTAPI errorType = 1, errorCode = 38
2015-05-19T11:21:22.093-04:00 error vmware-converter-worker[05232] [Originator@6876 sub=task-1] AnalyzeErrorAndThrow(): Insufficient permissions to open file
2015-05-19T11:21:22.093-04:00 error vmware-converter-worker[05232] [Originator@6876 sub=task-1] AnalyzeErrorAndThrow(): Platform errorType 1, errorCode 38
2015-05-19T11:21:22.093-04:00 error vmware-converter-worker[05232] [Originator@6876 sub=task-1] TaskImpl has failed with std::Exception: Platform-specific error 38
Ensure you have the access to your ESX box at port 902.
HTH
If I telnet to the hosts on port 902 should I get a banner message or anything to indicate that I have access?
=~=~=~=~=~=~=~=~=~=~=~= PuTTY log 2015.05.19 13:16:09 =~=~=~=~=~=~=~=~=~=~=~=
220 VMware Authentication Daemon Version 1.10: SSL Required, ServerDaemonProtocol:SOAP, MKSDisplayProtocol:VNC , VMXARGS supported, NFCSSL supported
I believe I have access to all 4 hosts in the cluster on port 902 if this above is any indication.
Ensure all required ports are opened as in User's Manual.
Also use the latest converter - currently 6.0.
HTH