Hello,
This is my situation.
I have 4 servers with ESXi 5.0 managed by vCenter 5.5 VM.
I received a new server is not compatible with ESXi 5.0 and 5.5.
I installed ESXi 6.0 and vCenter 6.0 on it on VM.
I imported the new Datacenter 4 Host 5.0.
The problem is that I can not migrate / clone vm from hosts 5.0 to 6.0 new host.
The error is the following:
"The operation is not supported on the object."
What should I do?
Tell me where I'm wrong like I was a baby because I'm not an expert in this area.
Thank you.
Nicolò
No, I did not find any explanation to my error in the links that you suggested.
I repeat that I can add the hosts in the data center created in vCenter 6 but I can not clone / migrate vm .
The error is always 'The operation is not supported on the object'.
Nicolò
If you are running this operation through a script,please check that you are calling the script against vcenter server & not against vcenter server.
Also can you please check manually if you can clone from esxi 5.0 to esxi 6.0 in the datacenter
Some discussion regarding this might help you
Help Please: CloneVM_Task gets created but fails with: Operation not supported on the object
I'm no expert in vSphere, so I only use the manual procedure within vCenter.
For example try to clone the vm 'COPIA ERMES OTTOBRE 2015' by the host esxi 5.0 (ip 10.23.154.12) in host esxi 6.0 (ip 10.23.154.19).
See image list ...
The result is the following:
What I'm not considering properly? What am I doing wrong?
I forgot to add that during the installation of vCenter 6.0 on vm Datacenter6 I left Postgres database management engine as default.
Can you please post vpxd.log when you are doing the clone operation
I apologize if I did not answer quickly, but the problem is that I can not find the file vpxd.log you asked. I reinstalled vsphere but the result has not changed. The user used to log in is Administrator@vsphere.local that I think has all the required privileges ....
Can you try below steps and see if it helps ?
1.Poweroff the VM
2. RightClick->Upgrade Virtual Hardware
3, Poweron the VM
4. Clone the VM
can you try unregistering VM on the source host(5.0) and reregister on the destination (6.0)
i have the same problem