CnicNV
asked on
Cannot live migrate, cold migrate, copy or clone virtual machine to another host.
Not a major problem because the resident VM isn't that important, but I am having an issue where I cannot extricate a VM from a host, a host which in general seems to be causing problems in the past such as a VM freezing and entire host freezing soon afterwards.
Now I am having issues with an entirely different VM resident on this problem host, but the problem now is not the VM and then host crashing (unless I attempt to move it), but rather, I cannot live migrate, cold migrate, copy and paste VM files to NAS datastore, or clone the VM to another host. It's like it is absolutely stuck on that server's local data store.
None of the VCenter GUI event errors are helpful. I have been able to live migrate to and from this host before without issue as well as with other hosts with the exact same hardware configuration (they are in fact the exact same model).
Before I go combing through the various low level server log dumps, I am just wondering if anyone may have already had this exact same issue and are like "ahhh yeah, that, you need to do xyz"
I am on ESXI 5.5u2 and thanks for the help:-)
Now I am having issues with an entirely different VM resident on this problem host, but the problem now is not the VM and then host crashing (unless I attempt to move it), but rather, I cannot live migrate, cold migrate, copy and paste VM files to NAS datastore, or clone the VM to another host. It's like it is absolutely stuck on that server's local data store.
None of the VCenter GUI event errors are helpful. I have been able to live migrate to and from this host before without issue as well as with other hosts with the exact same hardware configuration (they are in fact the exact same model).
Before I go combing through the various low level server log dumps, I am just wondering if anyone may have already had this exact same issue and are like "ahhh yeah, that, you need to do xyz"
I am on ESXI 5.5u2 and thanks for the help:-)
FOX
Have you tried to export the vms to one file .ova templates so you can import them on another host?
check the datastore for errors ?
check the logs for errors ?
what are the errors on the datastore if you try a manual copy/clone ?
check the logs for errors ?
what are the errors on the datastore if you try a manual copy/clone ?
ASKER
Yes I can try that. It was the last thing I picked, simply because it takes soo long, but definitely worth a shot.
Thanks for reminding me. I will report back tomorrow.
Thanks for reminding me. I will report back tomorrow.
Sounds good. When you export you have 2 options after you click ovf template...hit the dropdown and click ova template. It will be one file for the whole vm. Do one, import it in to the other host, and see if your successful
yes, see here...
Part 10: HOW TO: Backup (Export) and Restore (Import) virtual machines to VMware vSphere Hypervisor 5.1 for FREE
If the VM Power's UP, why not just use "VM Converter" and create a V2V?
Part 10: HOW TO: Backup (Export) and Restore (Import) virtual machines to VMware vSphere Hypervisor 5.1 for FREE
If the VM Power's UP, why not just use "VM Converter" and create a V2V?
ASKER
So, yeah. The export to OVF process failed as well. Well I guess technically it didn't, but the estimated time went from 340 minutes to 3890 minutes. Peculiarly, when I looked at the host performance data charts, there were a bunch of time intervals, where the line was broken (on and off) for all measures, including CPU, RAM, Disk etc. It was like the host was freezing or every so often not communicating with the vcenter server and then reestablishing communication.
Additionally,when I tried to cancel the process, the command would not execute and it kept exporting (or at least appearing to). I could not restart the host via VCenter server and had to force restart the computer and as well as the VCenter Server to get it to show that it was no longer exporting and so that I could power on the VM again.
I am thinking there is something wrong with the host, either physically (which is not a big deal) or more worrisome, I am wondering if it is problem related to upgrading ESXI from 5.1 to 5.5u2 ? Like it has some how made the hypervisor unstable.
I have upgraded a few other hosts so far and they seem to running fine without these issues.
Thanks Andrew for the tips, but where specifically do I look in VCenter for information about datastore errors? Also, do you have suggestions as for which logs to check for overall hypervisor stability, if applicable?
Additionally,when I tried to cancel the process, the command would not execute and it kept exporting (or at least appearing to). I could not restart the host via VCenter server and had to force restart the computer and as well as the VCenter Server to get it to show that it was no longer exporting and so that I could power on the VM again.
I am thinking there is something wrong with the host, either physically (which is not a big deal) or more worrisome, I am wondering if it is problem related to upgrading ESXI from 5.1 to 5.5u2 ? Like it has some how made the hypervisor unstable.
I have upgraded a few other hosts so far and they seem to running fine without these issues.
Thanks Andrew for the tips, but where specifically do I look in VCenter for information about datastore errors? Also, do you have suggestions as for which logs to check for overall hypervisor stability, if applicable?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Ok thanks a lot Andrew:-) I will comb through these logs when I get the time to troubleshoot this host again.