Problem z Vmware ESX

I1ve checked the logs you sent us and here is the result of analysis:



The hostd log contain entries which shows the reason of the hung was causes=

by a process called Pegasus:



[2009-12-05 12:51:40.322 'Memory checker' 25045936 warning] Current value 1=

46908 exceeds soft limit 122880.

[2009-12-05 12:52:10.324 'Memory checker' 32680880 warning] Current value 1=

46908 exceeds soft limit 122880.

[2009-12-05 12:52:40.342 'Memory checker' 23989168 warning] Current value 1=

46908 exceeds soft limit 122880.

[2009-12-05 12:53:10.362 'Memory checker' 23722928 warning] Current value 1=

46908 exceeds soft limit 122880.

[2009-12-05 12:53:40.392 'Memory checker' 32680880 warning] Current value 1=

46908 exceeds soft limit 122880.

[2009-12-05 12:54:10.405 'Memory checker' 114621360 warning] Current value =

146908 exceeds soft limit 122880.

[2009-12-05 12:54:40.422 'Memory checker' 41872304 warning] Current value 1=

46908 exceeds soft limit 122880.

[2009-12-05 12:55:10.452 'Memory checker' 13888432 warning] Current value 1=

46908 exceeds soft limit 122880.

[2009-12-05 12:55:40.524 'Memory checker' 23989168 warning] Current value 1=

46908 exceeds soft limit 122880.

[2009-12-05 12:56:10.542 'Memory checker' 23722928 warning] Current value 1=

46908 exceeds soft limit 122880



I1ve checked the top output as well:

09:59:48 up 1 day, 55 min, 2 users, load average: 1.03, 0.27, 0.09

265 processes: 263 sleeping, 2 running, 0 zombie, 0 stopped

CPU states: cpu user nice system irq softirq iowait idle

total 0.9% 0.0% 0.0% 0.0% 0.0% 72.5% 26.4%

Mem: 268572k av, 258860k used, 9712k free, 0k shrd, 16220k bu=

ff

185324k actv, 31500k in_d, 3040k in_c

Swap: 1052216k av, 46784k used, 1005432k free 74480k ca=

ched



As you can see as well, all of the physical memory is used already within 1=

day uptime, which indicates there is not enough memory assigned to the ser=

vice console.



I would have two suggestions to solve this issue:



- Increase the service console memory to 512MB with this procedure:

http://kb.vmware.com/kb/1003501



- Do an upgrade to ESX3.5 U5 which contains the patch for this issue:

https://www.vmware.com/mysupport/download/

In here select the 3.5 version and download the ESX Server 3.5.0 Update 5