04-03-2016 03:32 AM - edited 03-01-2019 12:40 PM
i came today morning to find my ucs c220 m35 has crashed over the weekend , i hard reset it and it went up fine along with all the vm "it had four solarwinds windows vm" , the problem is now im asked to find the root cause of the crash and frankly i dont know where to start , i attached the image of the crash screen i found , the ucs was showing high memory usage before the crash on solarwind , please help?
Solved! Go to Solution.
04-03-2016 04:15 AM
Please take a look at https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2059053
The workarounds include changing the e1000 adapter to vmxnet3.
There also should be a vmware patch that resolves the psod using the e1000.
Thanks,
Kirk
04-03-2016 04:15 AM
Please take a look at https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2059053
The workarounds include changing the e1000 adapter to vmxnet3.
There also should be a vmware patch that resolves the psod using the e1000.
Thanks,
Kirk
04-03-2016 04:49 AM
thanks for the great response , it is most likely this is the cause of the crash correct? also why is e1000e is causing the crash exactly??? like if i want to describe this issue how can i say it?
04-03-2016 05:01 AM
Yes, the bug is with vmware code, and is related to the use of e1000 (and RSS capabilities of the guestVM host OS).
This is a pretty common issue we used to get a lot of tickets for.
Thanks,
Kirk...
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide