Migration Validation Guide for Closed Hypervisor Environments

When this guide is needed

• The source virtualization platform is closed or legacy and cannot export standard images directly, yet migration to PVE (Proxmox VE, Proxmox Virtual Environment) must be evaluated.
• Original vendor support is discontinued or unavailable, and third-party feasibility validation is required.
• Common source constraints include backup-only export paths, proprietary image formats, no control-plane agent support, or hardware-bound licensing.

Pre-assessment and risk definition

1. Asset inventory: record VM count, OS versions, disk sizes, partition types, NIC models, and critical service dependencies.
2. Backup-type verification: determine whether available artifacts are full-image, file-level, or snapshot-chain backups.
3. Consistency target definition: define which attributes must remain stable post-migration (for example MAC, IP, service ports, boot window).
4. Risk register: flag high-risk items early (legacy kernels, private storage drivers, hardware-bound licensing, UEFI/legacy mismatch).

Repeatable migration validation workflow

1. Acquire operable backup set: export minimal reconstructable dataset without mutating source environment, with SHA256 checksums.
2. Intermediate restore: restore in a neutral environment and verify filesystem mount, key service startup, system time, and network stack.
3. Format conversion: convert with qemu-img (or equivalent) into PVE-friendly format (qcow2/raw) and record block/cache/sparse parameters.
4. PVE import: attach converted image to test VM with conservative hardware settings (host-compatible CPU, virtio-scsi, matching NIC model); for legacy Windows workloads, pre-plan boot mode and storage-controller compatibility before first boot.
5. Boot and service checks: verify boot logs, disk mounting, network service, and application dependency behavior against intermediate baseline.
6. Data-consistency validation: run sampled critical-folder and database checksum checks plus application health endpoints.

Common technical issues and triage order

1. Boot succeeds but networking fails: inspect legacy udev NIC rules, interface renaming (eth0 to ens*), and netplan/network-script mappings.
2. Disk mount errors: compare fstab UUID entries with migrated disk UUIDs and repair in rescue mode if needed.
3. System stuck in initramfs: usually storage-controller driver or rootfs UUID mismatch; rebuild initramfs and retest.
4. Application starts but licensing fails: check hardware-fingerprint binding (MAC/UUID/CPU ID) and plan controlled rebinding window.
5. Performance below source baseline: evaluate cache mode, IO scheduler, vCPU topology, NUMA, and memory-balloon settings.

Windows legacy boot-disk note (IDE)

1. Identify source-generation behavior first: older Windows VMs from legacy hypervisor or P2V paths may only have stable boot support on IDE/SATA.
2. Keep IDE system disk for first validation pass: start with i440fx and IDE system disk to confirm baseline boot before controller optimization.
3. Validate system and data disk separately: ensure system-disk bootability first, then migrate data disks to virtio-scsi in staged tests.
4. Switch controller only after driver readiness: install required guest drivers, reboot verification, then move system disk from IDE to VirtIO.
5. Preserve full rollback point: before each controller switch, create full backup. If boot failure occurs, restore full machine state (config plus data), because some OS self-repair paths may prevent clean rollback by settings-only reversion.

Technical validation checklist

1. Source and converted image checksums match and integrity is confirmed.
2. Intermediate and PVE test results are consistent for service behavior.
3. Critical applications run and complete minimal business workflow on PVE.
4. Recovery steps are reproducible with at least one full backup-to-boot rehearsal.
5. Performance baselines (CPU, memory, disk IO, network latency) are recorded for comparison.

References

• Proxmox VE Documentation
  https://pve.proxmox.com/pve-docs/
• qemu-img Manual
  https://www.qemu.org/docs/master/tools/qemu-img.html
• QCOW2 Image Format
  https://qemu.readthedocs.io/en/latest/interop/qcow2.html