UK’s trusted IT infrastructure partner since 2003
Servnet
ConfiguratorGet in Touch
Lenovo ThinkSystem SR650 V3 vs V4: choosing the right 2U virtualisation host (UK 2026) — analysisLenovo ThinkSystem SR650 V3 vs V4: choosing the right 2U virtualisation host (UK 2026) — analysis — reach
Server Infrastructure · Buyer Guide

Lenovo ThinkSystem SR650 V3 vs V4: choosing the right 2U virtualisation host (UK 2026)

Servnet Editorial · Server Infrastructure Practice10 min read

The ThinkSystem SR650 is Lenovo's 2U all-rounder, and for most UK buyers it is the default virtualisation host: enough drive bays, enough PCIe, enough memory to consolidate a serious number of virtual machines. With the V4 generation now alongside the established V3, the question is the same as ever in a 2U refresh: does the newer platform earn its premium, or is the abundant, well-proven V3 the better host for the money? This guide compares the two as virtualisation hosts and helps you decide which to standardise on.

SR650 V4 2U host, top down
5ResilienceDual PSU - XClarity - redundant fans4NetworkPCIe Gen5 NICs - 25GbE+ for VMs3StorageAll-NVMe - EDSFF - mirrored boot2MemoryBalanced DDR5 - the VM ceiling1ComputeDual Xeon 6 - sized to consolidation

Why the SR650 is the 2U default

The SR650 hits the sweet spot most buyers actually need. As a dual-socket 2U, it carries far more drive bays and PCIe expansion than a 1U, which makes it comfortable as a vSphere or Hyper-V host, an all-in-one for smaller sites, or a flexible box that can take a GPU or extra NICs later. That flexibility is precisely why it outsells narrower form factors for general virtualisation.

Both V3 and V4 keep that role intact. They share the 2U chassis approach, XClarity management and the same operational model, so the generational choice is about platform headroom rather than suitability. If the SR650 is already your standard host, neither generation changes that.

What the V4 brings to a virtualisation host

The V4 moves to the newer Intel Xeon 6 platform, with more cores available, additional memory channels, faster DDR5 and PCIe Gen5 across the slots. For a consolidation host the memory side is usually the headline: more channels and faster memory raise the ceiling on how many VMs a host can carry before bandwidth, not cores, becomes the limit. Gen5 lanes also matter if you intend to add accelerators or high-speed NICs over the host's life.

Storage in the V4 favours NVMe in volume, including EDSFF for dense, serviceable flash. If you are building an all-NVMe vSAN-style host or want the host to stay relevant for five years, the V4 has the runway. Size memory deliberately with our memory and RAM guidance, because on a virtualisation host RAM is almost always the first thing you run out of.

When the V3 is the better host for the money

The SR650 V3 is a known quantity that runs the vast majority of virtualisation workloads without breaking a sweat. For steady consolidation where you are not memory-bandwidth-starved, the V3 frequently delivers a better cost per VM, and its wide availability means you can buy now rather than queue for current-generation allocation.

There is also a strong standardisation argument in a 2U fleet. Matching V3 nodes keep your cluster homogeneous, which simplifies vMotion, firmware management and spares. For cross-vendor context on the 2U host decision, see our Dell vs HPE vs Lenovo comparison before you settle the generation.

SR650 V3 vs V4, 3-year cost as a VM host
£k40£k30£k20£k10£k0£k14£k18Y1£k22£k28Y2£k30£k38Y3SR650 V3SR650 V4

Sizing the SR650 as a VM host

Regardless of generation, size the host backwards from the VMs it will run. Count production vCPUs and committed RAM, apply a realistic consolidation ratio, and keep N+1 headroom so a node can be evacuated for patching without tipping the cluster. Populate DDR5 to balance every channel, and remember that going to higher capacity per channel can drop the clocked speed on either platform.

Keep the hypervisor on a separate mirrored boot device, put the VM workload on fast NVMe, and specify redundant power supplies and licensed XClarity for remote console. Build the exact host and request a quote in our Lenovo configurator.

  • Size from VM vCPU and committed RAM with N+1 cluster headroom
  • Balance memory channels; capacity-per-channel can cost you clock speed
  • Choose V4 for all-NVMe, Gen5 accelerators and a long horizon
  • Choose V3 for cost per VM, availability and a homogeneous cluster

The verdict

For greenfield clusters, memory-bandwidth-heavy consolidation, or hosts you want to last five years and take accelerators, the SR650 V4 is the platform to standardise on. For extending a proven estate, hitting a tight lead time, or squeezing the best cost per VM from a steady workload, the SR650 V3 remains an excellent 2U host. Either way, the sizing method in our how to spec a server guide applies unchanged.

Key takeaways
  • The SR650 is the default 2U virtualisation host; V3 and V4 share chassis, management and role.
  • The V4 adds newer Xeon 6 silicon, more memory channels, faster DDR5 and PCIe Gen5.
  • RAM bandwidth, not cores, usually limits how many VMs a host carries first.
  • Choose V4 for all-NVMe and a five-year horizon; choose V3 for cost per VM and availability.
  • Size from VM vCPU and committed RAM, keep N+1, and mirror the boot device separately.
Frequently asked

FAQs — Lenovo ThinkSystem SR650 V3 vs V4

Choosing

Is the SR650 V4 worth the premium over V3 for virtualisation?

If your consolidation is memory-bandwidth-heavy or you want all-NVMe and a five-year horizon, yes. For steady virtualisation the V3 often gives a better cost per VM and is more readily available. Compare platforms in our Dell vs HPE vs Lenovo piece.

How many VMs can an SR650 host run?

Plan from vCPU consolidation ratios and committed RAM rather than a fixed count, keeping N+1 headroom so a node can be evacuated. RAM is usually the first ceiling. Build a sized host in our Lenovo configurator.

Spec

What limits an SR650 virtualisation host first, CPU or RAM?

Almost always RAM. Size committed VM memory, add hypervisor overhead, and populate DIMMs to balance every channel for full bandwidth on either generation. Cores are rarely the binding constraint for general consolidation.

Related

Continue reading

More in Buyer Guides

Got a question this article didn't answer?

One conversation with an engineer who's done this before. No sales script.

Talk to Servnet →