VM suspend without intervention

[sjuanlu]

Hi!

The past 5 of July an vm was suspended without to do anyting in the ESXi or vCenter.  The rest of the esxi vms were not affected.

I'm checking the logs and I see this:

- vmware.log

2018-07-05T10:00:08.305Z| vcpu-3| I120: VMSAMPLE: cs=0x10, rip=0xffffffff8102b370 halted progress=22927962

2018-07-05T10:00:09.305Z| vcpu-1| I120: VMSAMPLE: cs=0x10, rip=0xffffffff81359463 progress=15014680

2018-07-05T10:00:09.305Z| vcpu-0| I120: VMSAMPLE: cs=0x10, rip=0xffffffff811b5c08 progress=33157648

2018-07-05T10:00:09.305Z| vcpu-3| I120: VMSAMPLE: cs=0x10, rip=0xffffffff8102b370 halted progress=45583087

2018-07-05T10:00:09.305Z| vcpu-2| I120: VMSAMPLE: cs=0x10, rip=0xffffffff8102b370 halted progress=11549935

2018-07-05T10:00:10.305Z| vcpu-2| I120: VMSAMPLE: cs=0x10, rip=0xffffffff8102b370 halted progress=3055556

2018-07-05T10:00:10.305Z| vcpu-3| I120: VMSAMPLE: cs=0x10, rip=0xffffffff8102b370 halted progress=10239605

2018-07-05T10:00:10.305Z| vcpu-1| I120: VMSAMPLE: cs=0x10, rip=0xffffffff8102b370 halted progress=7204515

2018-07-05T10:00:10.305Z| vcpu-0| I120: VMSAMPLE: cs=0x10, rip=0xffffffff8102b370 halted progress=20317859

2018-07-05T10:00:11.305Z| vcpu-2| I120: VMSAMPLE: cs=0x10, rip=0xffffffff8102b370 halted progress=27985311

2018-07-05T10:00:11.305Z| vcpu-0| I120: VMSAMPLE: cs=0x10, rip=0xffffffff8102b370 halted progress=2640222

2018-07-05T10:00:11.305Z| vcpu-1| I120: VMSAMPLE: cs=0x10, rip=0xffffffff8102b370 halted progress=3070393

2018-07-05T10:00:11.305Z| vcpu-3| I120: VMSAMPLE: cs=0x10, rip=0xffffffff8102b370 halted progress=17303737

2018-07-05T10:00:12.305Z| vcpu-3| I120: VMSAMPLE: cs=0x10, rip=0xffffffff8102b370 halted progress=32413003

2018-07-05T10:00:12.305Z| vcpu-2| I120: VMSAMPLE: cs=0x10, rip=0xffffffff8102b370 halted progress=9906710

2018-07-05T10:00:12.305Z| vcpu-0| I120: VMSAMPLE: cs=0x10, rip=0xffffffff8102b370 halted progress=12189961

2018-07-05T10:00:12.305Z| vcpu-1| I120: VMSAMPLE: cs=0x10, rip=0xffffffff8102b370 halted progress=13080786

2018-07-05T10:00:13.305Z| vcpu-3| I120: VMSAMPLE: cs=0x10, rip=0xffffffff8102b370 halted progress=14169782

2018-07-05T10:00:13.305Z| vcpu-0| I120: VMSAMPLE: cs=0x10, rip=0xffffffff8102b370 halted progress=3037673

2018-07-05T10:00:13.305Z| vcpu-2| I120: VMSAMPLE: cs=0x10, rip=0xffffffff8102b370 halted progress=9502378

2018-07-05T10:00:13.305Z| vcpu-1| I120: VMSAMPLE: cs=0x10, rip=0xffffffff8102b370 halted progress=3745327

2018-07-05T10:00:14.203Z| vmx| I120: Setting log_vmsample: 0

2018-07-05T10:00:14.531Z| vmx| I120: VMXVmdbCbVmVmxExecState: Exec state change requested to state suspended without reset, hard, softOptionTimeout: 0.

2018-07-05T10:00:14.531Z| vmx| I120: SUSPEND: Start (flags=0 prog=0 progData=0 cb=A409220 cbData=0)

2018-07-05T10:00:14.531Z| vcpu-0| I120: Destroying virtual dev for scsi0:0 vscsi=14439

2018-07-05T10:00:14.531Z| vcpu-0| I120: VMMon_VSCSIStopVports: No such target on adapter

2018-07-05T10:00:14.532Z| vcpu-0| I120: Destroying virtual dev for scsi0:1 vscsi=14440

2018-07-05T10:00:14.532Z| vcpu-0| I120: VMMon_VSCSIStopVports: No such target on adapter

2018-07-05T10:00:14.532Z| vcpu-0| I120: Destroying virtual dev for scsi0:2 vscsi=14441

2018-07-05T10:00:14.532Z| vcpu-0| I120: VMMon_VSCSIStopVports: No such target on adapter

2018-07-05T10:00:14.540Z| vcpu-0| I120: Closing all the disks of the VM.

2018-07-05T10:00:14.540Z| vcpu-0| I120: Closing disk scsi0:2

2018-07-05T10:00:14.540Z| vcpu-0| I120: DISKLIB-CBT : Shutting down change tracking for untracked fid 1016656812.

20

- ESXi Log:

Jul 5 09:58:51 S00749PB kernel: [3720430.691911] Uhhuh. NMI received for unknown reason 30 on CPU 0.

Jul 5 09:58:51 S00749PB kernel: [3720430.692110] Do you have a strange power saving mode enabled?

Jul 5 09:58:51 S00749PB kernel: [3720430.692162] Dazed and confused, but trying to continue

Jul 5 10:00:15 S00749PB kernel: [3720513.343515] [0]: VMCI: Updating context from (ID=0xa31d648a) to (ID=0xa31d648a) on event (type=0).

what is the problem? Is it a vm or SO problem or a ESXi problem?

Thanks in advanced.

[Kaustubhambulka]

Check if datastore have enough free space. Seems to storage issue.

[sjuanlu]

Thanks for your reply.

The vm has two disk in two different datastores but each one has more than 3 TB free.

Other idea?

[sjuanlu]

Is  it possible that the problem is the SO?

[Kaustubhambulka]

As per log I think . your guest system goes to standby after a specific time of inactivity.

Check in

Start -> control panel -> Power option . suspend system after 30 min of inactivity.

[sjuanlu]

I thought that, but Power Option is configured as never suspend.

[sjuanlu]

Attach the extract of the host log where the vm is located if you can provide more information. Thanks.

[luwenwei]

Is the problem solved? Friend?

[sjuanlu]

Not yet

[kalago]

rWe are having a similar error.

[amarsico]

In case it is still helpful... This event can be triggered when extracting the logs (vm-support.cgi) from vSphere. Standing in the VM, when running the extraction (Actions/Export System Logs..), vSphere warns us about this with the following message 'This option is used to troubleshoot unresponsive virtual machines, and will suspend or crash the VM. If you are unsure whether or not the virtual machine is responsive, see KB 1007802: http://kb.vmware.com/kb/1007802 for guidance. Proceed with caution.' Maybe this will help you! Regards