Skip to Content
Author's profile photo Claudia Baur

Known Issues with SAP Applications on VMware vSphere – Update 09/17/2018

Check carefully and make sure that you have implemented the required versions in your SAP on VMware vSphere environment.

VMware Tools Version 10.3.0 Recall and Workaround Recommendations. 09/17/2018
VMware has been made aware of issues in some vSphere ESXi 6.5 configurations with the VMXNET3 network driver for Windows that was released with VMware Tools 10.3.0. As a result, VMware has recalled the VMware Tools 10.3.0 release. This release has been removed from the VMware Downloads page. VMware KB 57796.

Speculative-Execution Vulnerability CVE-2018-3646 08/14/2018
Intel published details on a new class of CPU speculative-execution vulnerabilities known as “L1 Terminal Fault” that can occur on current and past Intel processors. For VMware’s mitigation strategy, see SAP Note 2680466.

Windows Server 2008 (R2) vNIC incompabilities 03/17/2018
The Security Updates KB4088875 and KB4088878 for Windows Server 2008 (R2) have incompatibility issues with VMs running on VMware vSphere. These patches replace the existing virtual network card (vNIC) with a new one, hide the pre-existing vNIC and do not persist or transfer the existing IP Address configuration to the new vNIC. For details, check this blog.

Meltdown and Spectre Vulnerabilities 01/05/2018
Like most other vendors, also VMware has released patches for the recently identified vulnerabilities in microprocessors, code named Spectre (CVE-2017-5753, CVE-2017-5715) and Meltdown (CVE-2017-5754).

Please see VMware Advisory page for further instructions in particular to the Spectre vulnerability, whereas the following blog confirms that ESXi and related VMware products are not affected by Meltdown vulnerability:

Applications fail to start when using Open VMware Tools with SLES and RHEL  07/10/2017
If you use the Open VMware tools and your applications which depend on VMware APIs fail to start, check SAP Note 2501545.

Incompatibility issues may lead to increased network latency and performance degradation on Windows 05/19/2017
If you use Windows Server 2012, 2012 R2 or 2016 guests and you experience an increased rate of “Received Dropped Packets”, check VMware Compatibility Issues may lead to Performance Degradation on Windows.
Update 05/19/2017: VMware published VMware Tools version 10.1.7 which fixes the issue.

VMware FT 6.0 may lead to increased network latency 11/23/2016
If you use FT 6.0 (with more than one vCPU) and you experience high latency and low throughput, check

VMware Virtual Machines hanging with VMware ESXi 5.5 p08 and p09  01/09/2017
After upgrading or installing VMware ESXi 5.5 p08 or p09, you encounter unpredictable hangs, stops or moves and crashes of virtual machines. Therefore your SAP application running inside these virtual machines might be interrupted unexpectedly.
For details, check and SAP Note 2381942.
VMware has patched this issue with VMware ESXi 5.5 p10.

VMware NSX for vSphere 6.2.x with ESXi 6.0 P03  10/14/2016
Due to a known issue affecting VMware NSX for vSphere 6.2.x with ESXi 6.0 P03 (Build 4192238) we recommend to consult VMware support before upgrading to the affected combination of products.
See VMware KB article 2146873 for further information.

ESXi 5.5U3 and 6.0: Unpredictable Hangs, Stops, Moves, Crashes of VMs 02/02/2016
After upgrading or installing VMware ESXi 5.5 Update 3 (also U3 versions with letters like U3x) and VMware ESXi 6.0, you encounter unpredictable hangs, stops or moves and crashes of virtual machines. Therefore your SAP application running inside these virtual machines might be interrupted unexpectedly.
Check SAP Note 2237937 for further information.

VMware vSphere 6: Possible Data Corruption 10/14/2015
Backing up a virtual machine with Changed Block Tracking (CBT) enabled fails after upgrading to or installing VMware ESXi 6.0. If you attempt this, you might encounter issues such as:

  • Database running inside VM becomes corrupted
  • Powering on the virtual machines fails
  • Expanding the size of a virtual disk fails
  • Taking virtual machine quiesced snapshots fails

Check SAP Note 2229228 for further information.

VMware vSphere 6: Performance Degradation due to High Network Latency 08/09/2016
You are using VMware vSphere 6.0. After changing the virtual machine hardware version to 11, you experience performance degradation of different intensity in network dependent workloads (this includes database access). Every network packet has up to a 0.5 second delay over the expected arrival in the application.

SAP observed a high degree of performance degradation when running SAP systems with MS SQL Server, even if the root cause of this issue is not related to MS SQL Server.
Check SAP Note 2293740 for further information.

Issue in Windows Server 2008 R2 SP1 Guest OS Causing Network Issues 2015
A new Ethernet virtual Network Interface Card (vNIC) may be created with default settings in place of the previously existing vNIC, causing network issues. Any custom settings on the previous vNIC are still persisted in the registry but unused.For details and solutions, see Microsoft KB 3125574.

For a collection of recent issues related to the operation of SAP applications in virtual environments, check the 1DX community topic page for virtualization or the recent support issues.

Assigned Tags

      1 Comment
      You must be Logged on to comment or reply to a post.
      Author's profile photo James Elliott
      James Elliott

      Hello - Are you aware of any Microsoft OS patch issues or incompatibility warnings with SAP on Windows servers, VMware, and VMWare tools for 2019?

      We're experiencing bad SAP performance issues after the latest Microsoft OS patching and suddenly our SAP production systems in all regions are now having enterprise wide bad performance.


      After troublshooting with SAP support..the VMWare support recommended changing the BIOS settings to HIGH performance on the ESX host level.

      Here are some logs:

      • Snapshot CPU Thu Dec 05 01:25:23 2019
        Interval 60 sec.
        |Monitoring Category |Description | Value|Unit|
        |Info |Operating system | Windows NT 6.1.7601 SP 1| |
        |Info |Timestamp |Thu Dec 05 01:25:23 2019 | |
        |Info |Hostname | USDCA138| |
        |CPU Virtualization Virtual System|Virtual CPUs | 8| |
        |CPU Virtualization Virtual System|Guaranteed Capacity | 0,00|CPUs|
        |CPU Virtualization Virtual System|Capacity Limit | 0,00|CPUs|
        |CPU Virtualization Virtual System|Capacity Maximum | 8,00|CPUs|
        |CPU Virtualization Virtual System|Capacity Consumed | 1,49|CPUs|
        |CPU Virtualization Virtual System|Ready Time | 22,1|% |
        |CPU Virtualization Virtual System|CPU Contention Time | 177,6|% |
        |CPU Virtualization Virtual System|Memory Contention Time | 0,0|% |

        They also identified VVMWare NIC card and firmware is outdated, but not sure if that is causing the immediate CPU contention.

        *** ERROR => NiIRead: SiRecv failed for hdl 57/sock 3100    (SI_ECONN_BROKEN/10053; I4; ST;=; L= [nixxi.cpp    5098] DpModState: change server state from STARTING to ACTIVE

        Are you aware of any known issues in this regard?