Problem starting Virtual Machines after upgrade 4.0 --> 5.1

[RemkoDeKoning]

Hi guys,

Recently I upgrade my ESXi box from 4.0 to 5.1.

After some vague problems (see: http://communities.vmware.com/message/2179808#2179808 ) the server seems to be running stable now.

This morning I discovered that one of my virtual test machines was not running.

I tried to power in on and got the message

"A general system error occured: The Virtual machine could not start"

After playing around a bit with this and turning off some other machines the virtual machine did start.

So far so good i thought but then I discovered that my machine that was running previously, is not starting anymore.

I have 20 GB of memory installed and only have 4 machines running

VM1     :     1024 MB

VM2     :     2500 MB

VM3     :     2048 MB

VM4     :     1680 MB

Total     :     7252 MB

There should be more than enough memory available.

Also on disk there is more than 100 GB of free disk space.

What could be the source of this? When I was running 4.0 I could run these machines simultanous without any problems.

Anything that I can check to see what is causing this?

Any thoughts are appreciated

Remko

[Sreec]

Hi ,

      Can you please post the virtual machine /kernal logs.Error message which you have posted wont help to figure out whats going wrong.

[RemkoDeKoning]

I just tried, it looks like my problem from yesterday is acting up again.

See thread: http://communities.vmware.com/message/2179808#2179808

This morning I could browse the datastores just fine. Now I cannot download any more files (logfiles)

Also going into the "security profile" of the configuration tab is throwing in an error now while it did not this morning.

Call "HostImageConfigManager.QueryHostAcceptanceLevel" for object "ha-image-config-manager" on ESXi "164.89.48.27" failed.

Starting and stopping services is also not working anymore

I am starting to believe there is seriously something wrong with my ESXI machine after the upgrade.

Problem is that I do not have the deep knowledge yet to troubleshoot this.

I guess I need an expert to take a look at this to see whats wrong.

In the realtime log on the server itself I am seeing the same error/warning returning

cpu:5:4129)Warning: World: 2349 Could not allocate new world handle

It gives this message for various CPU's

I have tried a google search on this but to no reveal.

Any suggestions were to start looking?

Remko

[RemkoDeKoning]

In the shell environment were I could normally browse the folders and type "LS" for a directory listing, I am now getting the message "Can't fork"

I am not a Linux expert but I believe this has something to do with resources.

[RemkoDeKoning]

Shutting down some VM's is fixing the problem. So it looks like a resource problem.

What can I do to prevent this from happening again?

[tjw82]

Was there ever a final solution for this issue?  I am having similar issues