P2V migration — a physical server becomes a virtual machine
P2V (Physical-to-Virtual) migration is the process of moving an entire operating system, applications and data from a physical server (bare-metal) into a virtual machine running on a virtualisation platform — in our case Proxmox VE. As a result of P2V migration:
- The physical server is replicated as a virtual machine (QEMU/KVM) with the identical OS, applications and data.
- Multiple physical servers can run on a single Proxmox host — 10:1 consolidation is the norm (a single host provides no HA — that requires a cluster of at least 3 nodes).
- Virtual machines have full isolation — a failure in one VM does not affect the others.
- Live migration is possible — moving running VMs between cluster nodes without downtime.
- VM backup is simpler and faster than physical server backup — snapshots, deduplication, encryption.
There is also a P2P (Physical-to-Physical) variant — migrating a system between physical servers without virtualisation. Details: physical-to-physical server migration. We deliver both variants depending on your needs — with Proxmox VE consolidation as the recommended end state. For existing VMware ESXi estates, see our vmware to proxmox migration technical guide.
Migrating physical servers to virtual machines — consolidation benefits on Proxmox
Moving workloads from bare-metal to virtual machines cuts energy costs, simplifies backup and speeds up recovery after failures. Below is a comparison of a typical environment before and after virtualisation.
| Area | Physical servers | After virtualisation (Proxmox) |
|---|---|---|
| Hardware utilisation | 5–15% average CPU/RAM utilisation | 70–90% through consolidation and overcommit |
| Energy costs | Many servers × 300–800 W | Up to 75% energy cost savings |
| Backup and recovery | Physical backup — slow, complex | VM snapshots, PBS — fast backup and restore |
| Failure downtime | Hardware replacement — hours or days | HA failover (cluster of at least 3 nodes) — automatic VM restart on another node, typically about 2 minutes including failure detection and watchdog fencing |
| Scaling | Buy a new physical server | Add CPU/RAM resources to a VM in minutes |
| Management | Multiple consoles, multiple systems | One Proxmox panel for all VMs |
| Data-centre space | Many rack units | Dramatic reduction — 10 servers → 1 host (no HA; HA from 3 nodes) |
How much you save after physical server consolidation
Example calculation for 10 physical servers migrated onto 1 Proxmox host (a single host provides no HA — that requires a cluster of at least 3 nodes):
| Cost category | 10 physical servers | 1 Proxmox host | Saving / year |
|---|---|---|---|
| OPEX · Energy (600W/server) | ~€33,000 / year | ~€7,700 / year | ~€25,300 |
| OPEX · Maintenance / support | ~€12,000 / year | ~€2,400 / year | ~€9,600 |
| CAPEX · Hardware refresh (3-year total) | ~€140,000 (10 × €14k) | ~€28,000 (1 × €28k) | ~€37,000 |
Use our physical server consolidation calculator — enter your server count and OPEX/CAPEX per machine, and the calculator will work out the exact savings for your environment.
Our physical server migration process
Our P2V migration services include driver mapping, pilot runs and UAT on every server. P2V migration requires careful analysis and the right tools — especially for systems with non-standard drivers, hardware RAID or specific BIOS/UEFI configurations. Our proven process:
- Hardware inventory and analysis: identifying each server's configuration — CPU, RAM, disks, RAID, network, drivers, OS, installed applications.
- Driver mapping: identifying hardware drivers that will need to be replaced with virtual equivalents (virtio, para-virtualisation drivers).
- P2V tool selection: depending on the OS we use
virt-p2v(then virt-v2v),Clonezilla,dd+ disk conversion, or manual engineering for legacy systems. - Proxmox host preparation: Proxmox VE cluster installation and configuration on target hardware, storage, network and backup configuration.
- Pilot — test migration: migrating the first, less critical server. Verifying correct operation of OS and applications in the virtual environment.
- Production migration: batch migration of all servers according to schedule. Every system is tested post-migration (UAT). Old servers remain as fallback.
- Handover and documentation: full technical documentation, IT team training, 30–90 days of hypercare.
Legacy system note: Servers running Windows Server 2003/2008, old RedHat versions or 32-bit systems require additional analysis before P2V migration. We have experience migrating legacy systems — ask for details.
P2V migration tools for Proxmox
Tool selection depends on the OS and configuration of the server being migrated. We use proven, open-source solutions:
| Tool | Use case | Operating systems |
|---|---|---|
| virt-p2v | Capture of the physical server, then virt-v2v conversion and virtio drivers | Windows and the Linux families virt-v2v supports (RHEL, SUSE, Debian/Ubuntu and relatives) |
| Clonezilla | Used-block clone (partclone); sector-by-sector is an option | Linux, Windows, BSD, any OS |
| dd + qemu-img | Low-level disk copy + format conversion | Linux, Windows and other systems from rescue media |
| qm disk import | Import ready disk image into Proxmox VM | Any — converted on the fly from any format qemu-img can read (vmdk, vhdx, qcow2, raw) |
| Manual engineering | Legacy systems, hardware RAID, non-standard configs | Windows 2003/2008, old RHEL, 32-bit systems |
After P2V migration we install virtio drivers (para-virtualisation) in the guest OS — this can improve disk and network IO performance in the virtual environment by 30–50% compared to full hardware emulation.
When P2V migration makes sense
Migrating physical servers to virtual machines is particularly worthwhile in the following situations:
- Hardware refresh — instead of buying many new physical servers, buy 1 powerful Proxmox host and virtualise everything (if you need HA — a cluster of at least 3 nodes).
- High data-centre OPEX — many physical servers generate large energy, cooling and rack-space costs. Consolidation cuts them dramatically.
- No HA or backup — physical servers have no automatic failover. After P2V, in a Proxmox cluster of at least 3 nodes with shared or replicated storage, HA automatically restarts VMs on another node if a node fails.
- Difficult management — many independent physical machines = many independent environments to manage. One Proxmox panel simplifies administration.
- No rack space for expansion — no room for more physical servers? Consolidation frees up multiple rack units.
P2V migration is especially popular with companies that built their infrastructure on physical servers before the virtualisation era and now want to modernise without rewriting their applications.
Virtualise your physical servers
We'll analyse your physical servers free of charge, draw up a P2V migration plan and calculate CAPEX/OPEX savings. Our engineer will contact you within 24 hours.
⚡ Free P2V migration quote→ Physical server calculator