The correct xFusion server configuration depends on how your virtual machines use CPU, memory, storage, and network resources. A small office cluster, a VDI environment, and a storage-heavy virtualization platform may require completely different server designs even when they run a similar number of virtual machines.
Start With the VM Inventory
Before selecting a server, collect the workload information that will determine the configuration:
- Number of virtual machines
- vCPU and memory assigned to each VM
- Average and peak CPU utilization
- Database, VDI, file-service, and application workloads
- Required storage capacity, IOPS, and latency
- Backup, replication, and live-migration traffic
- High-availability or N+1 requirements
- Expected growth during the next two to three years
- Hypervisor and software version
VM count alone is not a reliable sizing metric. One hundred lightly loaded office VMs can require much less CPU, memory, and storage performance than one hundred database, VDI, or real-time application VMs.
You can review available platforms through the xFusion virtualization server range before preparing a final configuration request.
Compare xFusion Virtualization Server Models
The table below organizes the available xFusion platforms by virtualization role. The recommended use is a planning direction, not a fixed workload guarantee. The final configuration must be checked against the required CPU, memory, drive, RAID, NIC, power, and support options.
| Model | Platform Position | Recommended Use | Main Consideration |
|---|---|---|---|
| FusionServer 1158H V7 | Compact 1U, single-socket platform | Small virtualization, branch, or edge workloads | Limited single-socket expansion and failover capacity |
| FusionServer 1288H V7 | 1U, dual-socket platform | High-density virtualization where rack space matters | Less room for local storage and expansion than a 2U platform |
| FusionServer 1288 V8 | Newer 1U platform option | Compact enterprise and virtualization deployments | Confirm the exact processor, memory, storage, and hypervisor configuration |
| FusionServer 2288H V7 | 2U, dual-socket platform | General enterprise virtualization, VDI, and mixed workloads | CPU, memory, storage, and NICs should be balanced |
| FusionServer 2288 V7 | 2U general-purpose platform | Virtualization, cloud infrastructure, and enterprise applications | Compare drive layout, RAID or HBA, PCIe, and network options |
| FusionServer 2288 V8 | Newer 2U platform option | Virtualization and general-purpose server consolidation | Do not assume V8 is a direct replacement without checking the complete BOM |
| FusionServer 2488H V7 | High-density, multi-socket platform | Memory-intensive, scale-up, and high-density virtualization | Higher power, cooling, and licensing complexity |
| FusionServer 5288H V5/V6 | Storage-oriented rack platform | Storage-heavy virtualization and distributed storage | Check current availability, rack space, drive layout, and power requirements |
The official FusionServer 2288H V7 specifications describe a 2U dual-socket platform for virtualization, VDI, SDS, databases, and other enterprise workloads. The page also lists multiple CPU, DDR5 memory, storage, OCP 3.0 NIC, PCIe, RAID, and power-supply options.
Size CPU Capacity
CPU sizing should start with actual workload demand rather than the total number of vCPUs assigned to virtual machines.
| Planning Item | What to Check |
|---|---|
| Average utilization | Identify whether the current environment is normally idle, moderately loaded, or consistently busy. |
| Peak utilization | Review backup windows, login storms, batch processing, and application peaks. |
| NUMA topology | Check how VM memory and vCPU scheduling will be distributed across CPU sockets. |
| Failover capacity | Reserve sufficient capacity if one host must take over workloads from another host. |
| Future growth | Include planned VM growth instead of sizing only for the current inventory. |
A useful planning model is:
Avoid applying a universal vCPU-to-pCPU ratio. The correct ratio depends on workload type, CPU utilization, oversubscription policy, and the performance target of the environment.
Share your VM, storage, network, and HA requirements.
Size Memory for Consolidation
Memory is often the first constraint in a virtualized environment, especially when the cluster runs databases, VDI, caching, or in-memory applications.
Check more than the maximum supported memory. The practical configuration depends on DIMM size, memory-channel population, CPU population, NUMA locality, cost, and the planned upgrade path.
- Populate DIMMs evenly across the available memory channels.
- Consider NUMA locality in dual-socket and multi-socket systems.
- Reserve memory for host management and failover operations.
- Confirm whether the workload needs large-memory databases or VDI density.
- Check whether future memory expansion will require replacing existing DIMMs.
The official 2288H V7 specification lists 32 DDR5 DIMM slots and additional DIMM capacity through CXL in supported configurations. This describes platform capability, not a recommendation that every deployment should use the maximum configuration.
Select Storage by Performance
Virtualization storage should be planned by capacity, IOPS, latency, endurance, redundancy, and backup requirements. Capacity alone does not describe whether a datastore will perform well under load.
| Storage Area | Main Question |
|---|---|
| Hypervisor boot | Can the hypervisor boot independently from VM data? |
| VM datastore | What capacity, IOPS, and latency are required? |
| Local cache | Do performance-sensitive workloads need NVMe? |
| Backup and replica | Can backup traffic be separated from production VM traffic? |
Common Storage Choices
- SATA: Suitable for capacity-focused and cost-sensitive workloads.
- SAS: Useful for enterprise drive arrays and traditional RAID designs.
- NVMe: Better suited to high-IOPS and low-latency workloads.
- Shared storage or NVMe-oF: Useful for centralized cluster storage, but requires a properly designed storage network.
The storage controller, RAID level, cache protection, and backup design should be considered together. A large number of SSDs will not solve a bottleneck caused by an undersized RAID controller, insufficient network bandwidth, or an unsuitable RAID layout.
For storage-heavy virtualization, FusionServer 5288H V5/V6 platforms may be considered when the project requires more local drive capacity. Confirm the exact drive layout, controller, power, cooling, and current availability before including them in a final BOM.
Plan the Virtualization Network
Virtualization traffic should not be treated as a single data stream. At minimum, identify management, VM production, storage, live migration, backup, and replication traffic.
- Management network
- VM production network
- Storage network
- Live-migration network
- Backup and replication network
10GbE or 25GbE?
Redundant 10GbE may be sufficient for many general enterprise virtualization environments. Dense VM clusters, shared storage, and frequent live migration can justify evaluating 25GbE.
The decision should be connected to storage throughput, traffic isolation, migration frequency, backup windows, and switch uplink capacity. A faster NIC does not solve a bottleneck elsewhere in the storage or switching design.
Also confirm whether the server needs OCP 3.0 or PCIe network adapters, SR-IOV, RDMA/RoCE, redundant NIC ports, or dual-switch connectivity. These requirements should be checked together with the hypervisor driver and firmware matrix.
Select a Platform by Scenario
Small Branch or Edge Virtualization
Typical workloads include directory services, DNS, file services, monitoring, and a limited number of lightweight application VMs.
A compact platform such as the FusionServer 1158H V7 may be considered when the environment prioritizes a small chassis and moderate resource requirements. Its single-socket design should be checked carefully if future expansion or host-level failover is required.
General Enterprise Consolidation
ERP, application servers, file services, databases, and internal business systems usually require a balanced configuration rather than the highest specification in one component.
The FusionServer 2288H V7 is a practical starting point because a 2U dual-socket platform can provide room for additional memory, storage configurations, RAID controllers, OCP network adapters, PCIe devices, and redundant power supplies.
High-Density VM or VDI Deployment
In high-density environments, memory capacity and network design may become more important than maximum CPU frequency.
The FusionServer 1288H V7 is designed as a 1U dual-socket platform for high-density virtualization. It can improve rack efficiency, while a 2U platform may be more suitable when the deployment needs additional local storage, PCIe adapters, or future expansion.
Memory-Intensive or Scale-Up Workloads
The FusionServer 2488H V7 should be evaluated for high-density virtualization, large-memory applications, and scale-up workloads. It is not automatically the best choice for a standard virtualization cluster.
A multi-socket platform can introduce higher power, cooling, licensing, and NUMA-planning requirements. These factors should be compared with the cost of using more conventional dual-socket hosts.
Storage-Heavy Virtualization
When local storage capacity is more important than compute density, storage-oriented FusionServer platforms may be appropriate. Confirm rack space, rail compatibility, floor loading, power distribution, cooling capacity, drive type, RAID or HBA requirements, and storage-network bandwidth before selecting the chassis.
Information to Include in a BOM Request
A useful server quotation request should include more than the number of virtual machines. Provide the following information:
- Number of VMs and workload types
- Total and peak vCPU demand
- Total assigned and required memory
- Hypervisor and software version
- Required storage capacity, IOPS, and latency
- Boot, VM, backup, and replica storage requirements
- RAID or HBA preference
- 10GbE or 25GbE network requirement
- NIC and switch redundancy requirements
- HA and failover policy
- Rack space and power limits
- Expected expansion during the next two to three years
This information allows the server configuration to be evaluated as a complete system rather than as an isolated CPU, memory, or storage quote.
Frequently Asked Questions
Plan the Configuration Before Requesting a Quote
An xFusion virtualization server should be selected as part of a complete infrastructure design. The chassis, processors, memory, storage controller, drives, NICs, power supplies, and hypervisor plan all affect the final result.
Share your VM inventory and infrastructure requirements with Router-Switch for an xFusion configuration review and BOM quotation.