VMware Cloud Community
arcolino1
Contributor
Contributor
Jump to solution

vmware vcenter converter standalone converting physical to virtual stuck at 81% completion for many days

hello all I have an interesting one, I am converting a physical to virtual pointing the new virtual straight to the esx server the conversion was going smoothly taking schedual for a day. But now it’s just stuck at 81 % and not going any further!? I am not getting any errors any ideas? questions are there logs I can look at to see what’s going on? Is there a way I can fix without starting over again. There is enough resources on the destination esx I did have to change hard drive space for destination and ram but nothing drastic actually made footprint smaller which I think should make it better.

0 Kudos
1 Solution

Accepted Solutions
patanassov
VMware Employee
VMware Employee
Jump to solution

That's an interesting case you've got here. I suppose either the conversion has finished but somehow you don't see it, or some deadlock has occurred.

Either way you probably won't be able to export the logs from the client. Go to the logs directory at %ALLUSERSPROFILE%\Application Data\VMware\VMware vCenter Converter Standalone\logs (for WP/W3K) or at %ALLUSERSPROFILE%\VMware\VMware vCenter Converter Standalone\logs (for Vista +) and find the last worker's log (vmware-converte-worker-###.log). The progress of the conversion is being logged. Have a look whether it has completed, is still running, or is stuck.

If it has completed you may try restarting the client and/or the converter server service. Do not stop the worker service unless you are sure there is no running conversion!!

HTH

Plamen

View solution in original post

0 Kudos
5 Replies
POCEH
VMware Employee
VMware Employee
Jump to solution

What changes you made and where? You must not edit destination VM while it's copied.

For errors - inspect the agent and worker logs.  HTH

0 Kudos
patanassov
VMware Employee
VMware Employee
Jump to solution

That's an interesting case you've got here. I suppose either the conversion has finished but somehow you don't see it, or some deadlock has occurred.

Either way you probably won't be able to export the logs from the client. Go to the logs directory at %ALLUSERSPROFILE%\Application Data\VMware\VMware vCenter Converter Standalone\logs (for WP/W3K) or at %ALLUSERSPROFILE%\VMware\VMware vCenter Converter Standalone\logs (for Vista +) and find the last worker's log (vmware-converte-worker-###.log). The progress of the conversion is being logged. Have a look whether it has completed, is still running, or is stuck.

If it has completed you may try restarting the client and/or the converter server service. Do not stop the worker service unless you are sure there is no running conversion!!

HTH

Plamen

0 Kudos
arcolino1
Contributor
Contributor
Jump to solution

the path I have for logs is

c:\programdata\vmware\vmware vcenter converter standalone\logs

it actually started going after 3 days! I did strink the orginal size of the drive

didnt need to have destination have same size. example source l drive

400gigs actually using 100gigs destination 200gigs that sort of thing

didnt know that would cause the program to go through major changes

I made those settings for two drives. I checked the logs. no errors.

see below.

Section for VMware vCenter Converter Standalone, pid=1728, version=5.0.1, build=build-875114, option=Release
2013-02-15T03:11:21.961-05:00 [01760 info 'Default'] Initialized channel manager
2013-02-15T03:11:21.961-05:00 [01760 info 'Default'] Current working directory: C:\Program Files (x86)\VMware\VMware vCenter Converter Standalone
2013-02-15T03:11:21.977-05:00 [01760 info 'Default'] Trying converter_agent
2013-02-15T03:11:22.944-05:00 [01760 info 'Default'] Trying converter_worker
2013-02-15T03:11:23.365-05:00 [01760 info 'Default'] Trying ufa_agent
2013-02-15T03:11:23.443-05:00 [01760 info 'Ufa'] Initializing SSL context
2013-02-15T03:11:24.644-05:00 [01760 info 'Default'] Vmacore::InitSSL: doVersionCheck = true, handshakeTimeoutUs = 20000000
2013-02-15T03:11:24.644-05:00 [01760 info 'Ufa'] Plugin initialized
2013-02-15T03:11:24.644-05:00 [01760 info 'Ufa'] SOAP pipe name: \\.\pipe\vmware-converter-worker-soap
2013-02-15T03:11:24.660-05:00 [01760 info 'Ufa.HTTPService'] Using default for nonChunkingAgents: 'VMware VI Client|VMware-client|VMware-client/3.*'
2013-02-15T03:11:24.660-05:00 [01760 info 'Ufa.HTTPService'] Using default for agentsNeedingContentLength: 'VMware-client'
2013-02-15T03:11:24.660-05:00 [01760 info 'Ufa.HTTPService'] Max buffered response size is 104857600 bytes
2013-02-15T03:11:24.660-05:00 [01760 info 'Ufa'] enableChunkedResponses: true
2013-02-15T03:11:24.660-05:00 [01760 info 'Libs'] UUID: SMBIOS UUID is reported as '56 4d e4 47 88 00 3d 2f-68 c8 55 05 48 9e 7f 08'.
2013-02-15T03:11:24.676-05:00 [01760 info 'Ufa.HTTPService'] Http Service started: [class Vmacore::Ssl::SSLServerSocketImpl:0284B560]
2013-02-15T03:11:24.676-05:00 [01760 info 'Ufa'] Soap (over Named Pipe) started on pipe \\.\pipe\vmware-converter-worker-soap. enableRemoteAccess = false, nonRootAccess = false, useSSL = true
2013-02-15T03:11:24.676-05:00 [01760 info 'Ufa'] Plugin started
2013-02-15T03:11:24.894-05:00 [01760 info 'Default'] [,0] DiskLibProvider init - OK
2013-02-15T03:1

0 Kudos
patanassov
VMware Employee
VMware Employee
Jump to solution

So, is everything all right now?

BTW the log snippet doesn't contain the task progress. I'd suggest, if you need further investigation, to attach the whole log.

0 Kudos
arcolino1
Contributor
Contributor
Jump to solution

hey patanassov thanks for responding, yes its working a matter of fact it finished 🙂 it took 4 days but it finished, thanks if I run it that issue again I'll make sure to attach the complete file info. 

0 Kudos