The Dell PowerEdge R660 is the server most UK virtualisation estates are quietly built on: a dual-socket 1U box that packs two current Xeon CPUs, a full set of DDR5 memory channels and a row of NVMe into a single rack unit. It is not glamorous and it is not specialised, and that is precisely the point. The R660 is the default consolidation host, the one you reach for when you want the most VMs per rack unit without paying for capabilities you will never use. This guide covers how to spec one well, where its limits are, and when a different chassis is the smarter buy.
Where the R660 fits in the line
The R660 is Dell's mainstream dual-socket 1U server, built around two current-generation Intel Xeon processors and a full complement of DDR5 channels. Its job is density: maximum compute and memory in one rack unit, which makes it the natural host for general virtualisation, container platforms and consolidation workloads where you want many VMs per U and a clean, repeatable building block.
It sits between two siblings worth knowing. The 2U R760 trades rack density for far more drive bays and the riser space to host GPUs and add-in cards, while the single-socket R670 drops to one CPU for edge and licence-sensitive roles. The R660 is the middle path: two sockets for consolidation, one rack unit for density, and enough NVMe for the storage a virtualisation host actually needs.
CPU: licence-aware, not maximum core
With two Xeon sockets, the R660 can carry a lot of cores, but core count is now a recurring cost rather than a one-off, because hypervisor and guest licensing is largely per-core. For most consolidation workloads a pair of mid-bin CPUs with a strong per-core clock beats two top-bin parts you pay to licence and rarely saturate, a point we make in detail in how to spec a server in 2026.
Size the cores from the consolidation ratio and the licences you will buy, not from the spec sheet. Keep the workload NUMA-aware so VMs stay local to a socket where possible, and favour the clock and cache that keep per-VM latency low. The processor choice is where the R660's running cost is really set, and our processors range covers the options.
Memory and storage in 1U
Memory is usually the real ceiling on a virtualisation host, so populate the R660's DDR5 channels in a balanced pattern to keep full bandwidth, and size committed VM memory plus hypervisor overhead with headroom for a node failure. An unbalanced fill silently throttles memory bandwidth, so the population map matters as much as the total capacity, a subject we cover in DIMM population rules.
On storage, the R660 takes a row of front NVMe or SAS/SATA drives, which is plenty for a virtualisation host using either local datastores or, more often, a small local footprint with capacity on shared storage or vSAN. Boot belongs on a separate mirrored device such as Dell BOSS rather than the data tier, so a boot-drive failure never takes the host down and rebuilds stay trivial.
- •Populate DDR5 channels in a balanced map for full bandwidth, not just total capacity
- •Size committed VM memory plus hypervisor overhead with N+1 headroom
- •A row of front NVMe suits local datastores or a thin local footprint over shared storage
- •Boot on a separate mirrored BOSS device, never on the data tier
Networking, resilience and management
A modern virtualisation host wants redundant NICs sized to role. On the R660 an OCP 3.0 mezzanine NIC keeps the PCIe slots free and is hot-serviceable on most configurations, with 2x 25GbE a sensible mainstream baseline for combined VM, vMotion and management traffic, and storage or vSAN traffic on its own pair where used.
Resilience is table stakes for anything running production VMs: dual power supplies on separate feeds, redundant fans, and iDRAC out-of-band management licensed for remote console so the host can be managed and recovered without a trip to the rack. These are not the place to economise on a consolidation host that may carry dozens of workloads.
When the R660 is the wrong answer
The R660 stops being the right choice when the workload needs what a 1U cannot give. If you need GPUs, many more drives, or a lot of add-in cards, the 2U R760 has the riser and bay space the R660 lacks, and forcing a GPU-heavy or storage-dense role into 1U leads to compromise. The 2U all-rounder is covered in our R760 buyer's guide.
If a role genuinely needs only one socket, for edge sites or licence-bound single-socket workloads, the R670 avoids paying for a second CPU and its licences. And for scale-up in-memory databases that want four sockets and very large memory, the R660 is simply the wrong class of machine. The R660 is the default, not the universal answer, and knowing its edges is part of speccing it well.
Putting it together
Spec the R660 as a consolidation host: licence-aware cores, balanced DDR5 sized to your VMs with N+1, a thin NVMe footprint with mirrored boot, redundant 25GbE and full resilience. Then build the exact configuration and request a quote in our Dell server configurator. For the platform-level choice between vendors see Dell vs HPE vs Lenovo, and explore the wider range on our Dell servers hub.