Can't add a VM to the inventory > Operation timed out

[mrovide]

Hi there,

I've been trying to add a VM to my VIC inventory but I keep getting the error "Operation timed out".

Do you have any idea what should I do to be able to do it from the GUI ?

Tips :

• it worked before, but not with this specific VM

• the same request made from the console works fine

Thanks in advance,

Ovide

[chrisAMS]

try this command service mgmt-vmware restart

and re try to add your vm in the inventory

[mrovide]

Thank you for your answer. Unfortunately the command service mgmt-vmware restart didn't work.

I tried to reboot the whole ESX but I'm still not able to add the VM to the inventory (same error).

Any idea ?

Thanks in advance

[chrisAMS]

sure you have enough space ?

could you verify with: df -vh

[mrovide]

Yes, I've got about 600GB freespace on my datastore...

[chrisAMS]

i was speaking about ESX partitions

dont you have another ESX just to test if it is coming from ESX or you VM ?

[mrovide]

Oh ok I didn't understand...

Here's my output :

myaccount@myesx myaccount$ df -vh

Filesystem Size Used Avail Use% Mounted on

/dev/sda2 4.9G 1.5G 3.2G 32% /

/dev/sda1 194M 30M 155M 16% /boot

/dev/sda6 2.0G 74M 1.8G 4% /opt

none 250M 0 250M 0% /dev/shm

/dev/sda5 2.0G 33M 1.9G 2% /tmp

/dev/sda8 2.0G 78M 1.8G 5% /var/log

You're right, I'll try to add the same VM to another datastore or ESX just to see what happens.

[Rubeck]

Have you tried to create a new VM using the same disks? Just to generate a new .vmx file..

Maybe the existing .vmx file contains something that the VIclient dosn't like..

Just an idea..

/Rubeck

[Leafy911]

I just built an ESX server with update 2 and I couldn't get any VMs to work on it until I added the latest critical patches. Are you fully patched up?

Regards

Leafy911

(Dont forget you recieve points when you award points)

[mrovide]

Our version is 3.02 build 63195. Unfortunately we cannot add the latest patches especially for this ESX because our policy is to evolve the ESX altogether.

Anyway, I tried to move the VM from one datastore to another, then I had the same error. Later I even tried to add the VM to another ESX but nothing better...

Maybe the problem came for the VirtualCenter...so I tried to reboot the Oracle database (well, actually I had to reboot the whole server) but I still got the timeout.

I haven't tried to create a new VM yet because I tried to delete/add another VM from the inventory and I got the same error as my first VM...

Thanks for your help

[Rubeck]

Alot of funny issues are .vmx file related, and can easily be verfied by creating a new one...

Just create a new custom VM and use existing disks.... Easy to try out..

/Rubeck.

[mrovide]

After I posted my last message, I tried to deploy a VM from a template and to create a new VM but I got the same error...

I wonder if the problem doesn't come from the VirtualCenter now.

[mrovide]

OK the problem is solved...at last !

The only way I found to make it work was to upgrade the ESX to 3.0.3 build 107381 (which means, upgrade from 3.0.2 to 3.0.3 + patches for the 3.0.3)

Hope this will help someone in the future...