Link to home
Start Free TrialLog in
Avatar of LemonCalvin
LemonCalvin

asked on

Cloning VM Fails - The Operation is Not Supported On The Object.

I've been attempting this for a few weeks now (browsing various outlets for answers) to no avail and I'm hoping someone here can help me.

Attempting to clone VM to template or another host using vCenter Server v6.0 I get the error "The Operation is Not Supported On The Object". This message is displayed in the console of vCenter Server.

1. The VM is Exchange Server 2010 (vmdk file = 564gb Server 2008r2 x64) VM version 8.
2. The esxi host It resides on is vSphere 5.0. with 1.36 tb storage with 8.11 gb free space
3. I'm attempting to clone it using vCenter Server 6.0.
4. The destination host is esxi vSphere 5.5 with 4.5 tb available space and no other VMs on it.

Please let me know if I need to provide any additional information to help with resolving this.
Thank you all in advance for your help.
ASKER CERTIFIED SOLUTION
Avatar of Luciano Patrão
Luciano Patrão
Flag of Portugal image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Is the VM Powered Up ?

I would agree with my colleague Luciano Patrão, 8GB is very low on a datastore, we try and keep at least 20-30% FREE.
Avatar of LemonCalvin
LemonCalvin

ASKER

Where do I get those logs from. I did a log retrieval from the vCenter console for that exchange host but they showed empty. Where on the host can I find those? I've looked around but nadda, cant find where they might be.
The VM is powered on. I will check that location when I return from lunch.
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Logs attached. There are no other VMs on this host. There are files from old VMs but I'm unable to delete the files.
vpxa-logs-1.txt
vpxa-logs-2.txt
Hi,

Add also vmkernel log and the name of the VM that you are trying to clone. If not, will be very difficult to find the proper log entries for that task.

Jail
The VM is Ex2010. Log is attached.
Ex2010-vmkernelLog.txt
I agree with the other experts on the low free space on the datastore. I also noticed the following error in the hostd logs

Truncating <FD c533 r138> failed: Address temporarily unmapped



 Is this VM sharing the datstore with other VMs? If so are you able to clone one of them as a test?
Previously, there were other vm's using the same datastore, they were removed but some of their files remain as I cant/it will not let me delete them. This vm has been the only one on there for several months.
do you require any additional help to close this question?
I do, I am in the process of setting up another host (with ample space) where I will try to vMotion or clone the vm to this host and see if that works. That's why I haven't closed this out.
I setup a host with an additional 4TB of storage and configured iSCSI SANs on both the new and problem hosts. On the host with the problem VM and low space, I was able to move (vMotion) the problem VM to the new host. The problem WAS as you stated... the reason I could not move the VM. Thanks for your insight on this guys. I can now add more hard drives to the host and totally reinstall a newer version of esxi.