VMware vSphere vs SUSE KVM for SAP HANA with Hitachi Vantara Advanced Servers and VSP One Block Storage

By Akshay Gandhi posted 6 hours ago

Like

VMware vSphere vs SUSE KVM for SAP HANA with Hitachi Vantara Advanced Servers and VSP One Block Storage

Choosing a hypervisor for SAP HANA is a decision that carries significant long-term implications for cost, operations, and supportability. VMware vSphere and SUSE KVM (Kernel-based Virtual Machine) are both production-ready virtualization platforms for SAP HANA deployments on Hitachi Vantara Advanced Servers. Hitachi Vantara provides validated reference architectures across multiple server generations, including the HA820 G3, HA840 G3, and DS7000, on Hitachi VSP One storage platforms. This blog draws on that validation work to provide a straightforward technical comparison to help you make the right choice for your environment.

The VMware Licensing Shift: Why This Decision Matters More Now

Broadcom acquired VMware in late 2023 and restructured the licensing model significantly. Perpetual licenses were retired and the portfolio was consolidated into per-core subscription bundles, most notably VMware Cloud Foundation (VCF) and vSphere Foundation (VVF). For many organizations, this transition has resulted in substantially higher licensing costs compared to previous agreements.

This shift has prompted many enterprises to evaluate KVM as a serious alternative, not because KVM is a new technology, but because the cost differential now warrants a structured assessment. KVM is a mature, production-capable hypervisor. The key question is whether it aligns with your environment, your SAP HANA workloads, and your operational capabilities.

SAP HANA Support: Understanding the Certification Landscape

VMware vSphere has the broadest SAP HANA certification coverage and is the hypervisor used in Hitachi Vantara vHANA (virtualized SAP HANA) reference architecture. vSphere 8 is documented in SAP Note 3372365 and supports VMs up to 4 TB. vSphere 9 / VCF 9 (SAP Note 3663150) is the latest certification as of early 2026.

SUSE KVM is equally a production-supported platform for SAP HANA, and Hitachi Vantara provides a validated KVM reference architecture for SAP HANA deployments. SAP certifies HANA on SLES-based KVM, using SUSE Linux Enterprise Server for SAP Applications as the hypervisor host (SAP Note 3538596). Current certified configurations support virtual machines up to 4 TiB on Sapphire Rapids and Emerald Rapids systems.

For both hypervisors, verify your specific server and OS combination is listed as certified in the SAP HANA Hardware Directory, under Certified and Supported SAP HANA Hardware for your target platform.

Side-by-Side Comparison

Category	VMware vSphere	SUSE KVM
License Cost	Commercial. VMware by Broadcom per-core subscription, available in bundles including VCF and VVF. Licensing costs have increased significantly since the 2023 Broadcom acquisition.	Open source. Included with SLES for SAP Applications. No hypervisor license fee.
SAP HANA Support	Broadly certified. vSphere 8 (SAP Note 3372365) and vSphere 9 / VCF 9 (SAP Note 3663150). Supports VMs up to 4 TB on 2-socket systems and up to 16 TB on 8-socket systems.	Production supported on SLES-based KVM (SAP Note 3538596). Current certified configurations support VMs up to 4 TiB on Sapphire Rapids and Emerald Rapids systems.
Guest OS for HANA	RHEL for SAP Applications and SLES for SAP Applications are both fully supported by SAP.	SLES for SAP Applications is the primary validated guest OS by SAP for SAP HANA on SLES KVM.
Management	vCenter provides a mature, GUI-driven enterprise toolset with centralized management of the full virtualization stack.	Managed via virsh, libvirt, and virt-manager. Well suited for Linux-native teams and integrates naturally into existing Linux administration workflows.
Vendor Support	Enterprise support provided by Broadcom. Includes dedicated TAM options, extensive knowledge base, and long-standing ISV ecosystem. Support contracts are bundled with the VCF/VVF subscription	Enterprise support provided by SUSE through SLES for SAP Applications subscription. SUSE offers dedicated SAP support, long-term service packs (up to 4 years), and direct escalation paths with SAP.

Live Migration: An Operationally Critical Difference

One of the most operationally significant differences between vSphere and KVM for SAP HANA is live migration: the ability to move a running HANA virtual machine from one physical host to another without incurring downtime.

VMware vSphere:

vMotion is fully SAP-validated for SAP HANA virtual machines
Host maintenance, firmware updates, and hardware replacement can be performed without scheduling a HANA downtime window
SAP and VMware conducted joint testing confirming the HANA instance remains operational throughout the migration. For details, refer to the VMware announcement on SAP HANA 16 TB VM support and SAP HANA on VMware vSphere in VCF
Note: vMotion requires virtualized storage such as VMFS datastores. VMs configured with PCIe passthrough devices are not compatible with vMotion.

SUSE KVM:

High availability is achieved through OS-level clustering using Pacemaker and STONITH
Pacemaker continuously monitors node health, SAP HANA process health, and System Replication state
In the event of a primary node failure, it automatically promotes the standby and redirects client connections
STONITH ensures data integrity by fencing failed nodes before failover
For detailed guidance, refer to the SUSE SAP HANA System Replication HA Guide and SUSE overview of supported HA solutions for SAP

Performance Tuning for SAP HANA: Key Configuration Requirements

VMware vSphere:

VMware and SAP have published a comprehensive best practices guide covering all recommended vSphere configuration settings for SAP HANA deployments. Refer to the SAP HANA on VMware vSphere Best Practices Guide and SAP Note 2161991 for the full list of configuration guidelines.

SUSE KVM:

KVM delivers performance comparable to vSphere for SAP HANA workloads. The following configuration steps are standard practice for production SAP HANA deployments on KVM and are well-documented by SAP and SUSE:

• CPU Pinning: Pinning vCPUs to physical cores on the same NUMA node as the VM memory ensures optimal NUMA locality and consistent query performance for SAP HANA workloads.

• Hugepages: Pre-allocating 1 GB hugepages on the KVM host before the VM starts ensures that SAP HANA has access to large contiguous memory pages, which is a standard SAP HANA memory configuration requirement.

• vhostmd: The vhostmd daemon runs on the KVM host and enables SAP HANA VMs to report hypervisor metrics to the SAP support infrastructure, as required by SAP (SAP Note 1522993).

• Storage Configuration: For production storage I/O, presenting block storage directly to the HANA VM keeps the I/O path close to bare metal characteristics when properly configured.

These configuration steps are well-documented by both SAP and SUSE, and are standard practice for Linux-native infrastructure teams. Refer to the SUSE Best Practices for SAP HANA on KVM for detailed guidance. Each platform has its own operational model; the right choice depends on your team and existing infrastructure.

VSP One Block Storage The Validated Storage Foundation for Both Hypervisors

Regardless of which hypervisor you choose, Hitachi VSP One Block Storage is the validated storage platform for SAP HANA deployments. Hitachi VSP One Block models are certified for SAP HANA TDI deployments under SAP's Enterprise Storage certification program, and integrate with both vSphere and KVM deployments.

The difference between the two hypervisors is in how block storage reaches the virtual machine:

• VMware vSphere: Storage is presented to the virtual machine via VMFS datastores, which is the approach used in Hitachi Vantara validated vSphere reference architectures. Refer to the Hitachi Vantara Documentation Portal for the validated RA for your server platform.

• SUSE KVM: Storage is presented directly to the guest VM, keeping the I/O path close to bare metal characteristics when properly configured. Refer to the SUSE Best Practices guide for SAP HANA on KVM for detailed storage configuration guidance.

In both cases, VSP One Block delivers the same enterprise data services. For product details, visit the VSP One Block product page.

Which One Is Right for You?

VMware vSphere may be the right fit if:

• You need the widest SAP HANA certification coverage, especially for large VMs or newer CPUs such as Intel Xeon 6 Granite Rapids.

• You need SAP-validated live migration via vMotion for non-disruptive host maintenance.

• Your organization already runs VMware and has existing vCenter skills and infrastructure.

• Your organization requires centralized, GUI-driven management across SAP and non-SAP workloads through vCenter.

SUSE KVM may be the right fit if:

• Your organization is looking to reduce hypervisor licensing costs and operates a Linux-native environment based on SLES for SAP Applications.

• Your SAP HANA workload is well suited to virtualized scale-up deployments on SLES-based KVM.

• You prefer open-source infrastructure with enterprise support from SUSE.

• Your team is comfortable with Linux-based administration tools such as virsh and libvirt for day-to-day hypervisor operations.

Final Thoughts

Both VMware vSphere and SUSE KVM are proven, production-grade virtualization options for SAP HANA, and Hitachi Vantara has validated solutions for both. Whether you are running vSphere with VMFS-based storage or SUSE KVM with direct block storage access, VSP One Block Storage provides the same certified, high-performance foundation underneath.

Hitachi Vantara has published validated reference architectures for both hypervisors across multiple server generations, including the HA820 G3, HA840 G3, and DS7000, on Hitachi VSP storage platforms. These are available on the Hitachi Vantara Documentation Portal. If you are evaluating which virtualization path is right for your SAP HANA environment, your Hitachi Vantara account team can help you assess your options and connect you with the right reference architecture for your platform.