Hello
It is possible the source machine has gone out of memory and the tar process used in the conversion has been chosen as a victim. Ensure the source has enough memory and retry the conversion.
HTH
Plamen
Hello
It is possible the source machine has gone out of memory and the tar process used in the conversion has been chosen as a victim. Ensure the source has enough memory and retry the conversion.
HTH
Plamen
@patanassovPlamen Thank for the reply i don't thinks so its a memory issue
The following error occurred at 97%: and please see attached file for reference physical current resources.
Thanks,
I still believe it is a process killed by OOM killer (because of the error code 137). Let me give some details: the process of volume cloning runs a tar process on the source and another one in the helper. The error message you have posted contains "$TAR_CMD" 2243 Killed so I assumed it is the source machine but it could be the destination (the message is ambiguous). There have been issues whit out of memory in the helper during the reconfiguration process; I have no recollection for this to have happened during cloning, but the 97% progress suggest the end of cloning. tar does some additional job like link creation at the end, so perhaps it is possible.
Have a look at this KB about how to hack the helper with more memory: VMware KB: VMware vCenter Converter Standalone fails with the error: Vmacore::TimeoutException(Operation timed out) … . Hope this will do.
Regards,
Plamen
@patanassovPlamen so you mean to say should I crease memory Virtual machine before start conversion like same configuration physical and VM.
Thanks,
Farhan Khan Mughal.
Not exactly but what you say should also do.
The helper VM (which is the destination but during the conversion) is setup with 512MB memory, half of which is used as RAM disk. Increasing it to to 1GB should be enough (though more would not harm)
Regards,
Plamen
@patanassovPlamen
I have tried this increase memory 5GB but still same error found on 97%.
Please let me know what is the next step.
Thanks,
Farhan Khan Mughal.
Not good
Can you export and upload the task log bundle? May be there are some other clues
Hello Farhan,
unfortunately the helper log doesn't contain more details about this error. There might be in the kernel log, which however is not in the bundle.
One way to go is to continue with the investigation (this is an error I have never seen before, there have been similar issues with untar-ing but not the process being killed by the kernel). For this you need to enable logging in the helper (see this KB: VMware KB: Enabling Logging in to Helper Virtual Machine During Conversion of Powered-On Linux Sources with Converte…). Then, after the conversion finishes, log in the destination VM (still running the helper), grab the whole /var/log directory (there is scp client in the helper) and post it here for further examination. If there is something valuable in these logs, it may help both with your specific issue and improving the product in the future.
The other way is a workaround. Since it is the /home volume that fails and it is not crucial for the conversion, you may convert without it (uncheck it in options -> data-to-copy wizard page). Then manually add a volume in the destination VM and copy the data.
HTH and regards,
Plamen
Hi, @patanassovPlamen
Thank you so much for with me on this and i will follow this step and will let you know after the result.
Thanks,
Farhan Khan Mughal.
Hello @Plamen,
This is to inform you I try this step and follow. Deselect Home (Volume) and successfully converted this is the good news and bad news is after converted VM started show me error.
I have attached logs file and VMhelper logs please see.
Thanks,
Farhan Khan Mughal.
Hello @Plamen,
I am waiting your response.
Thanks,
Your error is:
2016-01-28T15:34:05.312+08:00 info vmware-converter-worker[06304] [Originator@6876 sub=Default] GetManagedDiskName: Get disklib file name as vpxa-nfcssl://[VADSCES9XENDS] vadsacs03.ASTRO.AMDOCS.ASTRO/vadsacs03.ASTRO.AMDOCS.ASTRO.vmdk@vadcesesxnpxa01:902!52 68 22 3d 8e 31 be 28-96 3b ae f7 69 00 68 e4
2016-01-28T15:34:12.593+08:00 warning vmware-converter-worker[06304] [Originator@6876 sub=Default] [,0] [NFC ERROR] NfcNewAuthdConnectionEx: Failed to connect to peer. Error: Host address lookup for server vadcesesxnpxa01 failed: No such host is known
The host is not visible from the source computer.
Hello,
I am trying to migrate my Virtual machine from Esx 4.1 to Esx 5.5. This is completely on new vCenter. However, when i trying to migrate using VM Ware vCenter Converter Standalone, i am getting error "A File I/O error occurred while Accessing." This error shows when i click "finish" on the summary. Attached the diagnose file. Any expert, please advise.
Hi Farhan
These are the old logs.
Was the whole conversion completely successful, I mean including reconfiguration? Are there any warnings? What is the the behaviour of the GOS starting? Did it stop before GRUB, did the kernel load, etc. ("Error loading operating system" is not very informative)
Let me have a look at the new logs for start. It will be good to also check the file system for corruption on the source machine.
Regards
Plamen
@patanassovPlamen
I am totally new on this centos and VMware tell me where I find out the new logs and what is the GRUB ?
Thanks,
Farhan Khan Mughal.
Hi,patanassov,
Today I have started again the task with Home drive and found error again please see the log i have attached.
Thanks,
Farhan Khan Mughal.
This is the worker log. There is a line that reads
...failed to reconfigure target vm.
Go to the conversion task in converter client, right click and select "export logs" to get the whole bundle.
I also notice there are more than 2 hours between cloning has finished and the failure. That is way too much (the usual time is less than 10min).
There is something unusual with that source machine. Did you check the source file system?
Regards,
Plamen
Dear patanassov,
Please see attached log files may it's help with us.I have no idea why it's take 2 hours and i am also new on Centos.
Thanks,
Farhan Khan Mughal.
Sorry about these 2 hours, that was a mistake (I was looking at minutes:seconds)
Now the helper log contains:
Copying files from 192.168.0.17:/home to /mnt/p2v-src-root/home
...
2231 Killed | $UNTAR_CMD