Migrating Enterprise Virtualization Environments from VMware vSphere to Proxmox VE Cluster Infrastructures

ประเด็นสำคัญ

• Inventory the VMware environment. Document VMs, networks, storage, and dependencies before planning.
• Choose a migration strategy. Cold migration is simpler; hot migration requires replication and cutover.
• Convert VM disks. Use qemu-img to convert VMDK to QCOW2 or raw format.
• Reconfigure networking. Map VMware port groups to Proxmox bridges and VLANs.
• Set up storage. Configure Proxmox storage backends to match or exceed VMware performance.
• Test thoroughly. Run VMs on Proxmox in isolated networks before cutover.
• Plan the cutover. Schedule a maintenance window and communicate downtime to users.
• Validate post-migration. Check performance, backups, and monitoring after cutover.

Architecture

VMware VMs are converted to Proxmox format and imported into a Proxmox cluster. Storage is configured on Proxmox backends. Networking is mapped from VMware port groups to Proxmox bridges. VMs are tested in isolation before production cutover.

Production configuration

qemu-img convert -f vmdk -O qcow2 vm-disk.vmdk vm-disk.qcow2
qemu-img info vm-disk.qcow2
qm importdisk 100 vm-disk.qcow2 local-lvm

qm create 100 --name migrated-vm --memory 4096 --cores 4 --net0 virtio,bridge=vmbr0
qm set 100 --scsi0 local-lvm:vm-100-disk-0
qm set 100 --boot order=scsi0
qm set 100 --ostype l26
qm start 100
qm status 100

auto vmbr0
iface vmbr0 inet static
    address 10.0.0.1/24
    bridge-ports eth0
    bridge-stp off
    bridge-fd 0
    bridge-vlan-aware yes

ifreload -a

Edge cases from production

• VMware tools must be replaced with QEMU guest agent for full integration.
• Some VMs have hardware dependencies that do not translate; test before migration.
• Storage performance may differ; benchmark before and after.
• Licensing for guest OS may need reactivation after hardware change.

คำถามที่พบบ่อย