The virtual machine on ESXi 6.0 crashes because MONITOR PANIC occurs
search cancel

The virtual machine on ESXi 6.0 crashes because MONITOR PANIC occurs

book

Article ID: 334754

calendar_today

Updated On:

Products

VMware vSphere ESXi

Issue/Introduction

Symptoms:
  • The virtual machine crashes while deleting or integrating snapshots.
    • At that time, in /vmfs/volumes/Datastore/VM-name/vmware.log, you see entries similar to:
  20xx-xx-xxTxx:xx:xx.xxxZ| vmx| I125: GuestRpcSendTimedOut: message to toolbox-dnd timed out.
 20xx-xx-xxTxx:xx:xx.xxxZ| vmx| I125: GuestRpcSendTimedOut: message to toolbox-dnd timed out.
 20xx-xx-xxTxx:xx:xx.xxxZ| vmx| I125: GuestRpcSendTimedOut: message to toolbox-dnd timed out.
 20xx-xx-xxTxx:xx:xx.xxxZ| vcpu-0| W115: MONITOR PANIC: vcpu-0:VERIFY devices/lsilogic/lsilogic_monitorVMK.c:896 bugNr=133423
 20xx-xx-xxTxx:xx:xx.xxxZ| vcpu-0| I125: Core dump with build build-5251623
  • Also, in /var/run/log/vmkernel.log, you see entries similar to:
20xx-xx-xxTxx:xx:xx.xxxZ cpu32:128715)FSS: 6249: Failed to open file '*****flat.vmdk'; Requested flags 0x4008, world: 128715 [vmx-vcpu-0:******], (Existing flags 0x4001, world: 2927675 [sdrsInjector]): Busy
20xx-xx-xxTxx:xx:xx.xxxZ cpu32:128715)FSS: 6249: Failed to open file '*****flat.vmdk'; Requested flags 0x4008, world: 128715 [vmx-vcpu-0:******], (Existing flags 0x4001, world: 2927675 [sdrsInjector]): Busy
20xx-xx-xxTxx:xx:xx.xxxZ cpu32:128715)FSS: 6249: Failed to open file '*****flat.vmdk'; Requested flags 0x4008, world: 128715 [vmx-vcpu-0:******], (Existing flags 0x4001, world: 2927675 [sdrsInjector]): Busy


Environment

VMware vSphere ESXi 6.0

Cause

This issue occurs because there is a failure in the processing to release the lock between hostd and sdrsinjector.

Resolution

This issue is resolved in ESXi 6.0 Patch 06 or later.



Workaround:
To work around this issue stop sdrsinjector.
  • Run the following command with ESX Shell or SSH, and then stop sdrsinjector.
 
# /etc/init.d/sdrsinjector stop
 
Note: By default, the automatic startup of sdrsinjector is enabled upon the startup of ESXi. After ESXi is restarted, you need to stop sdrsinjector again.
  • The automatic startup of sdrsinjector can be disabled by the following command.
 # chkconfig sdrsInjector off
  • After disabling sdrsinjector, check the setting with the following command. You can see the configuration is changed to 'sdrsInjector  off'
 # chkconfig sdrsInjector 

  sdrsInjector    off