-
Title
VMware restore fails with “The operation is not supported on the object” -
Description
From binary log:
Error 2012/05/08 10:39:24 92 Data Plugin BACKUP Failed to add VM to target server's inventory
Binary log sub text
VMWVIM :01124 116 0 65727 Fault string is 'The operation is not supported on the object.'
VMWVIM :01124 117 0 65727 Fault type is 3227
VMWVIM :01124 605 0 65727 Failed wait for CreateVM_Task
VMWVIM :01124 617 0 65727 Failed to create VM from config info
VMWRESTR:01124 105 0 65727 Failed to add VM to server inventory
Restore VM using the restore to files option edit the VMX file and the video card setting are as below:
svga.autodetect = "true"
svga.vramSize = "16777216"
-
Cause
This problem happens because the hostd component of ESX does not support modifying the Video Card RAM size if it is already set to Auto Detect Video Setting. In the hostd log sample in the Symptoms section, you see that the virtual machine Video Card RAM size settings are:
svga.autodetect = "true"
svga.vramSize = "16777216"
-
Resolution
1)Restore the VM-system to files
2) Copy the restore folder to you SAN or ESX local storage
3) In Virtual Center browse the data store that you copied the folder to and Open the folder for the VM you want to restore and right click the .vmx file. Choose Add to Inventory
4) A dialog will open. Complete the wizard by specifying an ESX host
5) Right click the newly added VM and choose Edit Settings
6) Set the Network Adapter VLAN to the correct Network Label
7) Document the number of hard drives. As you will notice the restored drives do not show up with the correct space at first. You will need to re-add each drive one by one as shown in the next step
8) Click Remove on each of the hard drives.
9) Click Add
10) Choose Hard Disk
12) Select “Use an existing virtual disk”
13) Browse to the data store where this VM lives and locate the vmdk.
Click OK on all open Windows.
14)Repeat this process to add each drive if there was more than one in step 7.
15) Now clone the VM with a new name. This cloning process restores all the 2GB VCB backup files into a single VMDK.
16) Power up the clone and the VM-system should work as before.
Note:
This Generally happens to VM-system that have been converted from physical to Virtual systems So it would be advisable to check these system to see if they have Auto-detect Video selected.
If they have, To Avoid this restore problem happening to other VM-systems Video Ram setup needs to be modified so that the Auto-detect Video settings is not selected and the total video Ram is set to 4MB.
This needs to be done with the VM powered down. On power up you may find that the total video Ram has increased to 8MB, if this is the case do not worry the VM-system will backup and restore normally.