Virtual machines might experience slow performance in vSAN 6.5 while running certain NVMe drivers

Symptoms

In rare occasions, under high input/output processing conditions you may observe the vSAN disk group going offline.
In the /var/log/vmkernel file, you see message similar to:

2020-03-30T15:48:43.044Z cpu7:21644947)nvme:scsiIoCompleteCommand:459:vmkCmd 0x43a194105f00[28h I:0x4307df218480 SN:0x168418e0] UNDERRUN 8192/32768

Note: The preceding log excerpts are only examples. Date, time, and environmental variables may vary depending on your environment.

Cause

This issue is caused in the inbox driver.

Note:This is only observed when using the following NVMe devices in vSAN cluster:

Intel NVMe P4800X
Intel NVMe P4600/P4500
Intel NVMe P4610/ P4510

Resolution

This issue is resolved in VMware ESXi 6.5 EP20 Patch Release ESXi650-202006001, available at VMware Patch Downloads.
For more information on downloading patch, see How to download patches in MyVMWare (1021623).

Comments

Troubleshooting vpxd service on Windows vCenter Server

Symptoms You cannot connect to VMware vCenter Server with the vSphere Client. You cannot see the VMware vCenter Server in the inventory in the vSphere Web Client. You see a Microsoft Windows Event error associated with IIS similar to: Event properties - Event 7024, Service Control Manager The VMware VirtualCenter Server service terminated with service-specific error The system cannot find the file specified.. Log Name: System Source: Service Control Event ID: 7024 Level: Error Note : A windows Event ID 1000 may also be reported in relation to this issue. Connecting to vCenter Server fails with the error: Cannot connect to host server_name : No connection could be made because the target machine actively refused it. Attempting to start the VMware VirtualCenter Server service fails. You see this error: Windows could not start the VMware VirtualCenter Server service on...

Investigating virtual machine file locks on ESXi

Details Adding an existing virtual machine disk (VMDK) to a virtual machine that is already powered on fails. Failed to add disk scsi0:1. Failed to power on scsi0:1 Powering on the virtual machine results in the power on task remaining at 95% indefinitely. Cannot power on the virtual machine after deploying it from a template. Powering on a virtual machine fails with an error: Unable to open Swap File Unable to access a file since it is locked Unable to access a file <filename> since it is locked Unable to access Virtual machine configuration In the /var/log/vmkernel log file, you see entries similar to: WARNING: World: VM xxxx: xxx: Failed to open swap file <path>: Lock was not free WARNING: World: VM xxxx: xxx: Failed to initialize swap file <path> When opening a console to the virtual machine, you may receive ...

"Failed to configure vAPI Endpoint Service at the firstboot time" while installing Windows VC 6.5

Symptoms While configuring the vAPI EndPoint Service, you experience these symptoms: Windows vCenter Server 6.5 installation fails while configuring the vAPI EndPoint Service vCenter Server 6.5 installation on a Windows Server fails during the vAPI EndPoint Service during the firstboot time. You see the error: Error: An error occurred while starting service 'vapi-endpoint'. Failed to start the vAPI Endpoint Service. Failed to configure vAPI Endpoint Service at the firstboot time. Please file a bug against VAPI In vapi_firstboot.py_2948_stderr.log file, you see entries similar to: No valid files with pathname: C:\ProgramData\VMware\vCenterServer\logs\vapi\endpoint* found. ERROR starting vapi-endpoint rc: 2, stdout: , stderr: Start service request failed. Error: Service crashed while starting^M vapi firstboot failed Traceback (most recent call last): File "C:\Program Files\VMware\vCenter Server\firstbo...

thatwaskube

Search This Blog