Quantcast
Channel: VirtualBoy
Viewing all articles
Browse latest Browse all 35

Why VM VM-A went into suspended state automatically.

$
0
0
Analysis:

- At 12/6/2013 12:41:36 PM ,VM VM-A went into suspended state and we donot notice any user assigned to it in events.

Cause:

- The event is observed in hostd logs and Send_NMI_To_Guest is part of Support Bundle Collection functionality. Log into VI Client, select a VM, and go to File / Export / System Logs to access the functionality. 

- Support bundle collection including Sending NMI to Guest are done directly between the VI Client and the hosts. The operations do not show up in vpxd logs because VC do not have control over them.

hostd.log

2013-12-06T07:05:34.094Z [4250AB90 info 'TaskManager' opID=B1607BD8-00000225-65] Task Created : haTask--vim.SessionManager.acquireGenericServiceTicket-266352563
2013-12-06T07:05:34.095Z [41C89B90 verbose 'HaCgiServiceManagerImpl' opID=B1607BD8-00000225-65] Ticket created: ((null) https://ESXi-A.vmware.local/cgi-bin/vm-support.cgi?manifests=HungVM:Coredump_VM HungVM:Send_NMI_To_Guest HungVM:Suspend_VM&vm=/vmfs/volumes/4dde2ab6-451eb2e8-062a-14feb5d05ab9/VM-A/VM-A.vmx) - ***64a6e
2013-12-06T07:05:34.095Z [41C89B90 info 'TaskManager' opID=B1607BD8-00000225-65] Task Completed : haTask--vim.SessionManager.acquireGenericServiceTicket-266352563 Status success
2013-12-06T07:05:34.135Z [425C9B90 verbose 'Proxysvc Req81975'] New proxy client SSL(TCP(local=10.1.16.115:443, peer=10.1.46.206:54910))
2013-12-06T07:05:34.143Z [4250AB90 verbose 'HaCgiServiceManagerImpl'] Ticket valid: ***64a6e: (GET http://localhost/cgi-bin/vm-support.cgi?manifests=HungVM:Coredump_VM HungVM:Send_NMI_To_Guest HungVM:Suspend_VM&vm=/vmfs/volumes/4dde2ab6-451eb2e8-062a-14feb5d05ab9/VM-A/VM-A.vmx) == ((null) https://ESXi-A.vmware.local/cgi-bin/vm-support.cgi?manifests=HungVM:Coredump_VM HungVM:Send_NMI_To_Guest HungVM:Suspend_VM&vm=/vmfs/volumes/4dde2ab6-451eb2e8-062a-14feb5d05ab9/VM-A/VM-A.vmx)

- vmdumper log also confirms the fact that a NMI interrupt was send to crash the VM for collecting the logs.vmdumper.log is located in VM directory.

Running /sbin/vmdumper 45732157 screenshot
Grabbing screenshot...
Running /sbin/vmdumper 45732157 samples_on
Turning VM samples on...
Running /sbin/vmdumper 45732157 samples_off
Turning VM samples off...
Running /sbin/vmdumper 45732157 unsync
Dumping unsync cores...
Running /sbin/vmdumper 45732157 sync
Dumping sync cores...
Running /sbin/vmdumper 45732157 vmx
Dumping vmx core...
Running /sbin/vmdumper 45732157 vmx_force
Dumping vmx core (force)...
Running /sbin/vmdumper 45732157 screenshot
Grabbing screenshot...
Running /sbin/vmdumper 45732157 samples_on
Turning VM samples on...
Running /sbin/vmdumper 45732157 samples_off
Turning VM samples off...
Running /sbin/vmdumper 45732157 nmi
Sending NMI to guest...
Running /sbin/vmdumper 45732157 screenshot
Grabbing screenshot...
Running /sbin/vmdumper 45732157 screenshot
Grabbing screenshot...
Running /sbin/vmdumper 45732157 samples_on
Turning VM samples on...
Running /sbin/vmdumper 45732157 samples_off
Turning VM samples off...
Running /sbin/vmdumper 45732157 suspend_vm
Suspending VM...

Recommendation: 

- Advice to Use  "Home/Administration/Export System Logs" for collecting the logs normally.


Viewing all articles
Browse latest Browse all 35

Trending Articles