Specify a server for virtual machines from the guests that must run together and the work they perform at peak periods. Record the hypervisor and guest versions first, then assess processor demand, memory, storage and networking. Server virtualization requirements also include compatibility, licensing and recovery decisions that a component list cannot settle.
“A server for ten VMs” is incomplete. Ten lightly used test guests and ten busy production systems create different requirements. Give procurement a workload inventory and an accepted operating scenario before asking suppliers to propose hardware.
Inventory each guest and its busy periods
Create one row per virtual machine. Record its purpose, operating system and version, application owner, current vCPU allocation, memory allocation, data size and dependencies. Identify requirements such as an application-supported guest platform or a peripheral that needs specialist compatibility review.
Add normal operating hours, peak tasks and tasks that overlap. For example, report generation, imports, maintenance and backups may share the same period. Record which guests can be stopped and which must remain available. Do not assume that “usually idle” means a guest consumes no resources.
Use measured observations where an existing environment is available. Collect representative host and guest data through busy periods, with timestamps and the operations being performed. If the system is new, mark the workload values as estimates and identify the pilot needed to validate them.
The inventory should also expose business consequences. A noncritical test guest and a production database may need different restart priorities and recovery arrangements even when their assigned memory matches.
Check the exact hypervisor and hardware combination
Select the intended hypervisor version and support requirements before accepting a server model. Ask IT to verify the proposed processor, firmware, storage controller, network adapters and drivers against that platform's current compatibility guidance.
For Hyper-V, Microsoft's hardware requirements include a 64-bit processor with second-level address translation, VM Monitor Mode extensions and enabled virtualization and data-execution protection support. Those are eligibility checks. They do not say that an eligible host has enough capacity for your production guests.
Record the exact host operating-system edition and guest versions in the request. If using another hypervisor, use its own current supported-hardware and guest requirements. Features such as device assignment can introduce extra conditions, so identify them explicitly instead of treating ordinary VM support as proof.
Review the host workload across all resources
Assess simultaneous CPU demand, guest memory and the host's own needs together. A vCPU allocation is a scheduling input, not a direct physical-core purchase rule. Avoid a universal vCPU-to-core ratio: the workload pattern and measured contention determine what the technical reviewer can accept.
Microsoft's Hyper-V configuration guidance separates host and guest memory needs, storage capacity and I/O bandwidth. It also identifies Hyper-V performance counters for measuring physical CPU use. Ask your administrator to select appropriate measurements rather than adding guest CPU percentages without context.
For storage, record usable capacity, growth, temporary files and any planned checkpoint or backup working space. Then describe concurrent read/write activity, latency requirements and backup windows. A large disk capacity does not prove that a shared storage path can handle the busiest operations.
For networking, list required interfaces, switch connectivity and traffic purposes, including management, guest access, backup and migration where applicable. The network owner should approve the design and any required separation or resilience.
Work through an illustrative VM capacity worksheet
Illustrative assumptions only, not tested sizing or a recommended configuration: An IT team plans four guests and assumes that all remain running during the reporting window. The numbers below are provisional allocations and usable storage budgets requiring technical validation.
| Guest | Assigned vCPU | Assumed guest RAM | Assumed storage budget | Concurrent peak task |
|---|---|---|---|---|
| Directory services | 2 | 8 GB | 100 GB | Normal office authentication |
| Business application | 4 | 16 GB | 250 GB | End-of-day processing |
| Reporting database | 4 | 24 GB | 500 GB | Report query and import |
| Test environment | 2 | 8 GB | 150 GB | Planned test run |
| Guest totals | 12 assigned | 56 GB | 1,000 GB | Overlap requires validation |
Suppose the reviewer provisionally reserves 8 GB for host operations and agents and 16 GB for agreed near-term growth. The memory planning subtotal is 56 + 8 + 16 = 80 GB. This arithmetic records assumptions; it does not establish a safe host configuration or a standard percentage of spare capacity.
The 12 assigned vCPUs do not establish a requirement for 12 physical cores. IT still needs evidence of simultaneous CPU demand and acceptable response times. Likewise, the 1,000 GB guest storage total excludes any additional host, protection and temporary-space needs until those are recorded.
If test work can be moved outside the reporting window, document and enforce that scheduling decision. Do not reduce the capacity brief on an informal promise that teams may ignore.
Separate capacity, availability, backup and licences
Capacity asks whether the host can run the approved workload. Availability asks what happens when a host or dependency is unavailable. A single host with spare memory does not provide another host for failover; clustering and recovery architecture need their own review.
Backup asks what data can be restored and within what agreed time and loss limits. Record the protection method, destination, retention and restore-test owner. Microsoft's checkpoint guidance warns that a standard snapshot is not a full backup. Do not accept the existence of checkpoints as the recovery plan.
Licensing is another approval. Microsoft's Windows Server licensing guidance distinguishes physical-core and eligible per-VM licensing, with different virtualization rights and access-licence considerations. Have the customer's licence owner review the actual host, guests and applications against applicable terms. Hardware rental does not establish those rights.
Validate the brief before ordering
Set pilot tasks and acceptance criteria with application owners. Test the agreed simultaneous workload, observe resource behaviour and record exceptions. Include backup activity and recovery testing where they form part of the accepted operating plan.
Attach the result to the physical server quotation brief, alongside room fit, quantities, start date and duration. Monthly rentals require at least one month. Identify the customer team responsible for hypervisor installation, guest deployment, security and ongoing operation; agree any additional supplier duties in writing.
Frequently asked questions
How much RAM does a virtual machine host need?
Plan from guests that run simultaneously, their validated memory needs, host overhead and documented growth. Check startup behaviour and any memory-management assumptions during the pilot. The illustrative 80 GB subtotal above belongs only to its stated assumptions and is not a universal recommendation.
Can I size the processor from the total vCPU count?
No. Assigned vCPUs do not express the complete simultaneous demand on physical processors. Review workload timing, measured CPU behaviour and application response. Use those observations to approve a host configuration rather than applying one fixed conversion ratio.
Does one virtualization server provide high availability?
A single host remains a shared dependency for its guests. Define acceptable interruption and recovery requirements separately, then have IT assess the necessary architecture. Extra memory or redundant components do not by themselves establish host failover.
Does a server rental include hypervisor and guest deployment?
Include only duties explicitly agreed in the quotation and contract. Record who supplies licences, installs the platform, deploys guests, protects data and operates the environment. The hardware specification and rental term do not assign those responsibilities automatically.