VMware Communities: Message List - Converter Standalone

You can find the coverter log files in the attachment.

The machine in question doesn't use a software raid.

Then try to resize disk in order to run file-level cloning instead of block-level cloning. HTH

Could you attach the log bundle?

Also ensure connectivity with ESX server too.

Thanks. I've attached the logfile. I have tested connectivity to/from the ESXi server to the source and back. Ping works fine. Other physical servers have been able to convert although this is first time from the location of this server. Could this be something to do with not detecting the "heartbeat"? I understand that detecting the ESXi heartbeat occurs very early in the conversion process and since this fails exactly at 1% (about 1minute into the process) I'm wondering if the source failed to find the heartbeat.

Unfortunatly logs are GUI one, we need a converter-worker or converter-agent logs.

The 1% fail probably means that you can not connect to the ESX:902 from the source machine.

Changing from block-level to file-level did the trick. Thanks a bunch.

sorry. will provide agent logs soon

sorry it took so long. I've added the worker and agent files. I could not find any "logs" but did find the XML files. Hope that is what you wanted.

Nope these are configuration files...

find the corresponding log files in: %localappdata%\vmware\...

I'll look for the logs on Tuesday after the holidays.

btw...one question. The source server is on a subnet that other servers that were previously successfully P2v'd. Doesn't this imply that the 443 and 902 ports are already opened?

I don't know, the ports and/or connection settigs could be changed after previsous P2V... check out the connection settings, consult with manual.

Unfortunately there are no worker logs in the log bundle. They are the ones that contain the most useful information. There was some error with generating worker log bundle:

2013-08-29T16:08:35.957+02:00 [09704 warning 'Default'] [diagnosticManager,487] CRC mismatch in worker source related logs. Worker logs will not be added to server log bundle.

Can you provide worker logs manually? They should be under %ALLUSERSPROFILE%\Application Data\VMware\VMware vCenter Converter Standalone\logs (or under ProgramData on Vista and above).

you were right on. Port 902 was closed. I did a telnet and discovered there was no access to the port. Called our WAN guys and they confirmed. They will setup policy to open it. Thanks much.

Hi, I have tried to convert a VPC 2007 VHD of a win2000 VM and it seems to convert OK with no errors.

But, as soon as I start the converted vm in VMPlayer I get an error message along the lines of "error in first line," or "error in line 1"

Sorry, I forgot to write it down and I am now at work.

Is there anything I can do to fix the conversion?

Thanks

Once the conversion finished fine you should ask for the specific error in Workstation/Player forum.

I asked the networking guys to open port 902 between the source subnet address to the IP address of the vCenter server. They did so. Yet, I still cannot perform a P2V. I still get the same message about error 2338. Anyone have any advice?

You need an access and port 902 to the ESX host. HTH

Thanks for reply. Since the hosts on vCenter are in a HA/DRS cluster, even as I select a host, it will assign the VM to the one that DRS deems most suitable. So, to open port 902 I would have to request it be open to all the hosts on the cluster, correct? With our DRS cluster, I can assign a host but whether it is placed on that host or not is the decision of resource scheduling. Very often I see that I assign to a specific host but immediately it is assigned to another host in the cluster. So, I had hoped by directing the port to vCenter that it would allow conversion to any of the hosts in the cluster. Guess not.

misabreton , through convertor you can perform this task , please let us knwo which convertor you are using or any error time of converting .

If at first you don't succeed; call it version 1.0"

Hi Marius - Roma , this generally happen if something wrong with physical mouse , have tested with any other mouse, if the previous mouse working fine on other system please check the compatibility driver or usb tool for vmware .

If at first you don't succeed; call it version 1.0"

Re: Unable to detect disk or volumes on the source machine (Ubuntu 10.04 LTS)

Re: Failed: Unable to find the system volume, reconfiguration is not possible

Re: P2V error: FAILED: An error occurred during the conversion: 'Platform-specific error 2338'

Re: P2V error: FAILED: An error occurred during the conversion: 'Platform-specific error 2338'

Re: P2V error: FAILED: An error occurred during the conversion: 'Platform-specific error 2338'

Re: Failed: Unable to find the system volume, reconfiguration is not possible

Re: P2V error: FAILED: An error occurred during the conversion: 'Platform-specific error 2338'

Re: P2V error: FAILED: An error occurred during the conversion: 'Platform-specific error 2338'

Re: P2V error: FAILED: An error occurred during the conversion: 'Platform-specific error 2338'

Re: P2V error: FAILED: An error occurred during the conversion: 'Platform-specific error 2338'

Re: P2V error: FAILED: An error occurred during the conversion: 'Platform-specific error 2338'

Re: Unable to detect disk or volumes on the source machine (Ubuntu 10.04 LTS)

Re: P2V error: FAILED: An error occurred during the conversion: 'Platform-specific error 2338'

Converting a VirtualPC 2007 VHD - problem

Re: Converting a VirtualPC 2007 VHD - problem

Re: P2V error: FAILED: An error occurred during the conversion: 'Platform-specific error 2338'

Re: P2V error: FAILED: An error occurred during the conversion: 'Platform-specific error 2338'

Re: P2V error: FAILED: An error occurred during the conversion: 'Platform-specific error 2338'

Re: Can you convert vh to vm ware files

Re: Mouse pointer jumping to the upper left corner (VMware Tools issue?)