Known issues and limitations with VMware hosts

The VMware Knowledge Base information on the VMware Web site contains information about known issues and limitations that can help you verify and troubleshoot your attachment configurations.

To search for known issues and solutions, see the following VMware Web site:

www.vmware.com

Search the VMware support knowledge base for the following topics about possible symptoms and solutions:
  • Increasing the disk timeout values for a Linux 2.6 virtual machine (1009465)
    Issues occur when the guest operating system timeout values are exceeded for attached storage disks. Possible symptoms:
    • Inconsistent Linux operating system performance when disks are on SAN-based datastores.
    • The Linux guest operating system might experience intermittent issues when stored on SAN-based datastores.
    • During a host storage path failover, a Linux guest operating system reports a system error or file system error, encounters a kernel panic, or becomes unresponsive.
  • Inconsistent Windows virtual machine performance when disks are on SAN datastores (1014)

    Windows virtual machines might experience intermittent issues when stored on datastores that are presented from non-local storage. This issue might be encountered on virtual machines that use SAN, NFS, or iSCSI storage.

  • Fibre Channel switch outage leaves pending SCSI reservations on LUNs managed by an IBM SVC (2008333)
    Directions at the VMware Web site state that to enable the reset_on_attempted_reserve option on the claim rule for the IBM storage array, issue the esxcli command:
    • For ESXi 5.5:
      • esxcli storage nmp satp rule add --satp VMW_SATP_ALUA --psp VMW_PSP_RR --vendor IBM --model 2145 --option reset_on_attempted_reserve
    • For ESXi 5.0 or 5.1:
      • esxcli storage nmp satp rule add --satp VMW_SATP_SVC --psp VMW_PSP_FIXED --vendor IBM --model 2145 --option reset_on_attempted_reserve
  • Enabling or disabling VAAI ATS heartbeat
    You might experience the following symptoms:
    • An ESXi 5.5 Update 2 or ESXi 6.0 host loses connectivity to a VMFS5 datastore that resides on IBM Storwize based LUNs.
    • You see this message in /var/run/log/vobd.log and in Virtual Center Events: Lost access to volume <uuid><volume name> due to connectivity issues. Recovery attempt is in progress and the outcome will be reported shortly.
    • You see this message in /var/run/log/vmkernel.log: ATS Miscompare detected beween test and set HB images at offset XXX on vol YYY
Parent topic: Hosts that run the VMware operating system