Configuration errors in a virtual machine with Kaspersky Sandbox installed
Issue
The article describes errors you may encounter while running a virtual machine (VM) with Kaspersky Sandbox installed.
Cause
The issue may occur due to improper configuration of your VM.
Solution
Before getting started, check whether the Kaspersky Sandbox app is configured correctly for operating in a virtual infrastructure. For more information about configuration settings, see Online Help.
You can check the VM settings using:
- VMware ESXi hypervisor. See reference screenshots with proper resource reservation below.
- VMX format file. See correct parameter settings below.
Please do not exceed the recommended size of dedicated resources for your virtual machine, as it may cause errors. To increase the performance of the VM with Kaspersky Sandbox installed, you should deploy additional VMs, allocate the necessary resources between them and combine these servers into a cluster.
What to do if the issue persists
If the issue persists, submit a request to Kaspersky Technical Support via Kaspersky CompanyAccount. When submitting the request, include your screenshots of the resource reservation settings from the VMware ESXi hypervisor or provide a VMX file of the respective VM. Before contacting the support, see the guide on creating a request in the Knowledge Base.
Resource reservation in VMware ESXi (the reference screenshots)
The reference screenshots with proper resource reservation in VMware ESXi are presented below. In case of problems with the VM, compare your current settings with those on the screenshot below or submit a request to Kaspersky Technical Support with the screenshots of your settings attached.
Checking the parameter settings in a VMX file
- Open VSphere Client.
- Go to the tab and select the VMX file for your virtual machine.
- Click Download.
- Open the file with any text editor.
All settings in the VMX file should be as follows:
numvcpus = "12"
cpuid.coresPerSocket = "2"
sched.cpu.units = "mhz"
sched.cpu.min = "26400"
memSize = "32768"
sched.mem.min = "32768"
vhv.enable = "TRUE"
sched.cpu.latencySensitivity = "high"
uefi.secureBoot.enabled = "FALSE"
ethernet0.present = "TRUE"
ethernet1.present = "TRUE"
Exclusions:
- The line sched.cpu.min. The CPU clock rate can be higher than 26400 MHz. See the formula for calculating the CPU clock rate in Online Help.
- The line uefi.secureBoot.enabled may be absent.