Page tree
Skip to end of metadata
Go to start of metadata

Here you can find frequently asked questions on SAP on VMware vSphere.


Which SAP Notes are related to VMware vSphere?

For a list of SAP Notes that are related to the use of SAP applications on VMware products, see SAP Notes Related to VMware.

What about HANA support on VMware vSphere?

For support information on SAP HANA and SAP HANA-related applications with VMware vSphere, see the page SAP HANA on VMware vSphere.

Where can I get more information about running SAP on VMware vSphere?

For information about running SAP on VMware vSphere, see the VMware documents regarding SAP products.

Are there any customer references for using SAP on VMware?

For more information, see the Customer Success Stories.

Which tools for p2v migration does SAP support for conversion of its systems?

SAP cannot test its software with every partner tool offered for physical to virtual conversion. Therefore, SAP cannot give a support statement for these tools. Nevertheless, you can use every p2v tool which is supported by the respective partner getting support from the partner during migration of your SAP system. SAP support will start after you have succesfully migrated your SAP application to the virtual environment and the system comes up.

Is VMware Distributed Resource Scheduling (VMware DRS) supported to run with SAP?

VMware DRS only works in combination with VMotion, which is not supported in a high-availability environment (see SAP note 1374671 - SMP login required). Therefore, VMware DRS is only supported in a non-high-availability environment.

Which Microsoft clustering solutions does VMware support on VMware vSphere?

For a list of supported configurations, see Microsoft Clustering on VMware vSphere: Guidelines for Supported Configurations (1037959).

Does SAP support using VMware Converter in a Microsoft failover cluster environment?

Since the tool is owned by VMware, VMware also provides support when using VMware Converter with SAP software. For supported Windows versions and information on how to use VMware Converter, see Using VMware Converter to convert Microsoft Cluster (MSCS) nodes to virtual machines (1002661).

Is this specific hardware supported to run SAP applications on Windows with VMware?

SAP supports its systems on hardware that is certified for SAP on Windows. For a list of SAP-certified hardware, see List of certified hardware. In addition, for SAP systems running on VMware, the hardware has to be listed in the VMware Compatibility Guide. For more information, see VMware Compatibility Guide.

Technical Questions

I need to upgrade to a new vSphere version. Is there any update needed inside the VM to qualify for full SAP support?

After an upgrade of the VMware vSphere version, you need to upgrade the VMware Tools on each virtual machine.

How can I automate the update of the VMware Tools version?

You can automate the update of the VMware tools version running in your virtual machine so that the VMware tools version is checked by default with every reboot of the virtual machine. For more information about automating the VMware Tools upgrade, see

Where can I find information on how the CPU clock rate and Hyperthreading might influence my performance?

Read the following documents for optimal hardware configuration and sizing of your SAP system:

  • SAP Note 1612283 - Hardware Configuration Standards and Guidance (SMP login required)
  • SAP Note 1501701 - Single Computing Unit Performance and Sizing (SMP login required)
  • (login required) - Virtualizing SAP: Design and Performance Management Guideline

Besides the generation of the physical processor type, the clock rate of the physical CPU, as well as enabling Hyperthreading, influences the performance of your SAP system.

As a rule:

  • The higher the CPU clock rate, the higher the single computing unit performance of a process
  • When over-provisioning resources, enabling Hyperthreading might lead to reduced performance of your SAP processes. In this case, most of the time it makes sense to enable Hyperthreading with dialogue mode and disable Hyperthreading with batch mode. In the event of performance problems, deactivating Hyperthreading for your single VM (not necessarily for the whole host) might improve performance.

When I configure the number of virtual processors of a VM, does it make a difference how I map the cores to sockets?

For example, when I choose 4 virtual processors, does it make a difference if the VM is created with:

  1. 1 socket - 4 cores?
  2. 2 sockets - 2 cores?
  3. 4 sockets - 1 core?

In most cases,choose option 1, mapping 4 cores to 1 socket, because:

  • In most cases, the ESX scheduler leaves the 4 CPUs on the same socket and therefore on the same NUMA node.
  • SAP application servers are not NUMA-aware, but they are NUMA-sensitive. Therefore, the SAP application server benefits when running on the same NUMA node.
  • When the SAP application server uses different NUMA nodes, the work processes would need to access the memory remotely, which leads to severe performance loss. When the SAP application server uses one NUMA node, the work processes have less L3 cache available than when running on different sockets, but the reduced L3 cache decreases performance less than the remote memory access.

You might find the following documentation helpful:



  • No labels