Solved

VM's shutting down after alarm "Virtual CPU Usage' and "Virtual Machine memory Usage"

Posted on 2012-04-12
6
4,396 Views
Last Modified: 2013-06-14
Our VMs are shutting down after these alarms appear in the logs.


Alarm 'Virtual machine total disk latency' on
LANWSRV03 changed from Green to Gray
info
4/9/2012 11:45:27 AM
Alarm 'Virtual machine memory usage' on
LANWSRV03 changed from Green to Gray
info
4/9/2012 11:45:27 AM
Alarm 'Virtual machine cpu usage' on
LANWSRV03 changed from Green to Gray
info
4/9/2012 11:45:27 AM
Changed resource allocation for LANWSRV03
info
4/9/2012 11:45:27 AM

The VM then powers off and need to manually turn it back on. Can not seem to isolate the cause as all the other VMs seem unaffected.
0
Comment
Question by:WohlsenIT
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 3
  • 2
6 Comments
 
LVL 121
ID: 37837427
check the contents of the vmware.log in the virtual machine folder?

what is the guest, any snapshots, datastore out of space...
0
 

Author Comment

by:WohlsenIT
ID: 37837596
Apr 09 11:38:38.812: vcpu-0| SymBacktrace[11] 0x1e271178 eip 0xa828fda in function (null) in object /usr/lib/vmware/bin/vmware-vmx loaded at 0xa759000
Apr 09 11:38:38.812: vcpu-0| SymBacktrace[12] 0x1e2b2218 eip 0xa977244 in function (null) in object /usr/lib/vmware/bin/vmware-vmx loaded at 0xa759000
Apr 09 11:38:38.812: vcpu-0| Unrecoverable memory allocation failure at bora/lib/user/msg.c:220
Apr 09 11:38:38.812: vcpu-0| Panic loop
Apr 09 11:38:38.812: vcpu-0| Backtrace:
Apr 09 11:38:38.812: vcpu-0| Backtrace[0] 0x1e270168 eip 0xabb98cd
Apr 09 11:38:38.812: vcpu-0| Backtrace[1] 0x1e2705a8 eip 0xa7b80e4
Apr 09 11:38:38.813: vcpu-0| Backtrace[2] 0x1e270678 eip 0xabb394a
Apr 09 11:38:38.813: vcpu-0| Backtrace[3] 0x1e270698 eip 0xabb3ef4
Apr 09 11:38:38.813: vcpu-0| Backtrace[4] 0x1e270ad8 eip 0xabbaee9
Apr 09 11:38:38.813: vcpu-0| Backtrace[5] 0x1e270f18 eip 0xa7b8073
Apr 09 11:38:38.813: vcpu-0| Backtrace[6] 0x1e270f68 eip 0xabb80f7
Apr 09 11:38:38.813: vcpu-0| Backtrace[7] 0x1e270f88 eip 0xa7b9b14
Apr 09 11:38:38.813: vcpu-0| Backtrace[8] 0x1e270fd8 eip 0xabb471f
Apr 09 11:38:38.813: vcpu-0| Backtrace[9] 0x1e271008 eip 0xa7b99cb
Apr 09 11:38:38.814: vcpu-0| Backtrace[10] 0x1e271038 eip 0xa7b9e6b
Apr 09 11:38:38.814: vcpu-0| Backtrace[11] 0x1e271078 eip 0xa7c8741
Apr 09 11:38:38.814: vcpu-0| Backtrace[12] 0x1e2710a8 eip 0xa7c5b9b
Apr 09 11:38:38.814: vcpu-0| Backtrace[13] 0x1e2710f8 eip 0xa7c4ec8
Apr 09 11:38:38.814: vcpu-0| Backtrace[14] 0x1e271148 eip 0xa7c82ed
Apr 09 11:38:38.814: vcpu-0| Backtrace[15] 0x1e271178 eip 0xa828fda
Apr 09 11:38:38.814: vcpu-0| Backtrace[16] 0x1e2b2218 eip 0xa977244
Apr 09 11:38:38.814: vcpu-0| SymBacktrace[0] 0x1e270168 eip 0xabb98cd in function (null) in object /usr/lib/vmware/bin/vmware-vmx loaded at 0xa759000
Apr 09 11:38:38.815: vcpu-0| SymBacktrace[1] 0x1e2705a8 eip 0xa7b80e4 in function Panic in object /usr/lib/vmware/bin/vmware-vmx loaded at 0xa759000
Apr 09 11:38:38.815: vcpu-0| SymBacktrace[2] 0x1e270678 eip 0xabb394a in function (null) in object /usr/lib/vmware/bin/vmware-vmx loaded at 0xa759000
Apr 09 11:38:38.815: vcpu-0| SymBacktrace[3] 0x1e270698 eip 0xabb3ef4 in function (null) in object /usr/lib/vmware/bin/vmware-vmx loaded at 0xa759000
Apr 09 11:38:38.815: vcpu-0| SymBacktrace[4] 0x1e270ad8 eip 0xabbaee9 in function (null) in object /usr/lib/vmware/bin/vmware-vmx loaded at 0xa759000
Apr 09 11:38:38.815: vcpu-0| SymBacktrace[5] 0x1e270f18 eip 0xa7b8073 in function Panic in object /usr/lib/vmware/bin/vmware-vmx loaded at 0xa759000
Apr 09 11:38:38.815: vcpu-0| SymBacktrace[6] 0x1e270f68 eip 0xabb80f7 in function (null) in object /usr/lib/vmware/bin/vmware-vmx loaded at 0xa759000
Apr 09 11:38:38.815: vcpu-0| SymBacktrace[7] 0x1e270f88 eip 0xa7b9b14 in function (null) in object /usr/lib/vmware/bin/vmware-vmx loaded at 0xa759000
Apr 09 11:38:38.815: vcpu-0| SymBacktrace[8] 0x1e270fd8 eip 0xabb471f in function (null) in object /usr/lib/vmware/bin/vmware-vmx loaded at 0xa759000
Apr 09 11:38:38.816: vcpu-0| SymBacktrace[9] 0x1e271008 eip 0xa7b99cb in function (null) in object /usr/lib/vmware/bin/vmware-vmx loaded at 0xa759000
Apr 09 11:38:38.816: vcpu-0| SymBacktrace[10] 0x1e271038 eip 0xa7b9e6b in function (null) in object /usr/lib/vmware/bin/vmware-vmx loaded at 0xa759000
Apr 09 11:38:38.816: vcpu-0| SymBacktrace[11] 0x1e271078 eip 0xa7c8741 in function (null) in object /usr/lib/vmware/bin/vmware-vmx loaded at 0xa759000
Apr 09 11:38:38.816: vcpu-0| SymBacktrace[12] 0x1e2710a8 eip 0xa7c5b9b in function (null) in object /usr/lib/vmware/bin/vmware-vmx loaded at 0xa759000
Apr 09 11:38:38.816: vcpu-0| SymBacktrace[13] 0x1e2710f8 eip 0xa7c4ec8 in function (null) in object /usr/lib/vmware/bin/vmware-vmx loaded at 0xa759000
Apr 09 11:38:38.816: vcpu-0| SymBacktrace[14] 0x1e271148 eip 0xa7c82ed in function (null) in object /usr/lib/vmware/bin/vmware-vmx loaded at 0xa759000
Apr 09 11:38:38.817: vcpu-0| SymBacktrace[15] 0x1e271178 eip 0xa828fda in function (null) in object /usr/lib/vmware/bin/vmware-vmx loaded at 0xa759000
Apr 09 11:38:38.817: vcpu-0| SymBacktrace[16] 0x1e2b2218 eip 0xa977244 in
0
 

Author Comment

by:WohlsenIT
ID: 37837606
There are no snapshots currently and the datastore appears to be working fine.
0
10 Questions to Ask when Buying Backup Software

Choosing the right backup solution for your organization can be a daunting task. To make the selection process easier, ask solution providers these 10 key questions.

 

Author Comment

by:WohlsenIT
ID: 37837611
Guest OS is 2003 R2
0
 
LVL 121

Accepted Solution

by:
Andrew Hancock (VMware vExpert / EE MVE^2) earned 500 total points
ID: 37837612
is the host on the HCL, could be a hardware memory fault, check host memory.
0
 

Expert Comment

by:messaging_expert
ID: 39247576
xxx
0

Featured Post

Get free NFR key for Veeam Availability Suite 9.5

Veeam is happy to provide a free NFR license (1 year, 2 sockets) to all certified IT Pros. The license allows for the non-production use of Veeam Availability Suite v9.5 in your home lab, without any feature limitations. It works for both VMware and Hyper-V environments

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Will try to explain how to use the VMware feature TAGs in the VMs and create Veeam Backup Jobs using TAGs. Since this article is too long, I will create second article for the Veeam tasks.
This article outlines why you need to choose a backup solution that protects your entire environment – including your VMware ESXi and Microsoft Hyper-V virtualization hosts – not just your virtual machines.
Teach the user how to use vSphere Update Manager to update the VMware Tools and virtual machine hardware version Open vSphere Client: Review manual processes for updating VMware Tools and virtual hardware versions: Create a new baseline group in vSp…
Advanced tutorial on how to run the esxtop command to capture a batch file in csv format in order to export the file and use it for performance analysis. He demonstrates how to download the file using a vSphere web client (or vSphere client) and exp…
Suggested Courses

623 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question