The VMkernel log reports the log spew:lsuv2-lsi-drivers-plugin-util plugin and generates suv2-lsi-drivers-plugin-util-zdump

Products

• VMware vSphere ESXi 7.0

Issue/Introduction

Symptoms:

• The vmkernel.log file (located at /var/log/)contains a log spew similar to, sometimes it may generate a dump as well.

2024-09-06T17:48:21.426Z cpu18:47259141)Admission failure in path: host/vim/vmvisor/lsud:lsuv2-lsi-drivers-plugin-util.47259141:uw.47259141
2024-09-06T17:48:21.426Z cpu18:47259141)UserWorld 'lsuv2-lsi-drivers-plugin-util' with cmdline '/usr/lib64/vmware/lsuv2_plugins/lsiv2-drivers-plugin/lsuv2-lsi-drivers-plugin-util -I -p 100 -r lsi_mr3 -c 1 -t 124 -l 0'
2024-09-06T17:48:21.426Z cpu18:47259141)Admission failure in path: host/vim/vmvisor/lsud:lsuv2-lsi-drivers-plugin-util.47259141:uw.47259141
2024-09-06T17:48:21.426Z cpu18:47259141)UserWorld 'lsuv2-lsi-drivers-plugin-util' with cmdline '/usr/lib64/vmware/lsuv2_plugins/lsiv2-drivers-plugin/lsuv2-lsi-drivers-plugin-util -I -p 100 -r lsi_mr3 -c 1 -t 124 -l 0'

 

Environment

vSphere ESXi 7.0U3

Cause

This issue occurs when using the lsi_msgpt3, lsi_msgpt35 and lsi_mr3 controllers, there is a potential risk to see dump file lsuv2-lsi-drivers-plugin-util-zdump. There is an issue when exiting the storelib used in this plugin utility. 

Resolution

There is no impact on ESXi operations, you can ignore the dump file. We can safely ignore this message

The workaround and suggestion for the plugin dump is by removing the plugin or disabling the lsud framework

Workaround: . You can remove the lsuv2-lsi-drivers-plugin with the following command 

esxcli software vib remove -n lsuv2-lsiv2-drivers-plugin (Reboot is required)

 

Additional Information

Ref: https://docs.vmware.com/en/VMware-vSphere/7.0/rn/vsphere-esxi-70u3q-release-notes/index.html