Users encounter PSOD due to Deep Security and ESXi timer-related stack overflow.
p>To resolve this issue, use the advanced setting for the Deep Security Filter Driver that controls whether or not the driver will multiplex a single kernel timer across all Virtual Machines.
These timers are used to perform minimal maintenance task on a default 30 second interval. These same tasks also take place periodically as the system processes packets. Thus, the tasks execute with or without a timer. Using a single timer across all VMs is complex to manage and appears to have created some stability issue that could result in ESXi host crash.
Since the tasks that the timers perform occur, Trend Micro recommends disabling the timer-based method using these steps:
- From the ESXi console, execute this command to find out the value that is configured for the Filter Driver heap memory size:
% esxcfg-module -g dvfilter-dsa
If the value for the "DSAFILTER_HEAP_MAX_SIZE" is adjusted from its default value then the outcome will be similar to:
dvfilter-dsa enabled = 1 options = 'DSAFILTER_HEAP_MAX_SIZE=134217728'
- Use this command to disable timer and preserve the configured value for the DSAFILTER_HEAP_MAX_SIZE:
% esxcfg-module -s "DSAFILTER_HEAP_MAX_SIZE= 134217728 DSAFILTER_MOD_TIMER_ENABLED=0" dvfilter-dsa
Set the DSAFILTER_HEAP_MAX_SIZE to the value that was observed after running the "esxcfg-module -g dvfilter-dsa" command.If the value for the "DSAFILTER_HEAP_MAX_SIZE" is not changed from its default value then the outcome will be similar to:
dvfilter-dsa enabled = 1 options = ' '
In this case you can use the following command to disable timers:
% esxcfg-module -s "DSAFILTER_MOD_TIMER_ENABLED=0" dvfilter-dsa
- Verify if the settings were successfully applied by executing this command:
% esxcfg-module -g dvfilter-dsa
- Reboot the ESXi server for the changes to take effect.
The setting will not take effect until the driver is reloaded. Reloading will require a reboot (best option) of ESXi or unloading/loading of the driver.
