VMware Cloud Community
IvenUA
Contributor
Contributor

vmware's error

111.jpg

couldnt connect to vmware some times

need to restart power

finally was able to see the error


advice ?

0 Kudos
6 Replies
ScreamingSilenc

From the screenshot it seem like this Assert is caused by memory overcommitment have you been running Memory Intensive workload on the host ?

Please consider marking this answer "correct" or "helpful" if you found it useful.
0 Kudos
IvenUA
Contributor
Contributor

do u mean - resource - memory - shares - high ?

0 Kudos
ScreamingSilenc

do u mean - resource - memory - shares - high ?

Yes

Please consider marking this answer "correct" or "helpful" if you found it useful.
0 Kudos
IvenUA
Contributor
Contributor

it is posible that it was turn on

I thought it was smart function of using free memory from all virtual machines

did not think that could cause a conflict


is high resources cpu and disk normal ? or can be problems too ?

0 Kudos
ScreamingSilenc

I'm not saying you shouldn't use these features but it has caused this Assert which you have observed.

I would suggest you to file a case with VMware Support team this can be a potential issue or a bug.

Please consider marking this answer "correct" or "helpful" if you found it useful.
0 Kudos
MarVista
Enthusiast
Enthusiast

Hello,

This is a known issue in VMware ESXi 5.1 and is resolved in patch ESXi510-201212401-BG (Build 914609).  Hope this will resolve your issue.

http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=203876...

Yours,
Mar Vista

0 Kudos