V2K MigrateProxmox VE is now a migration destination, not a disk drop
V2K builds complete Proxmox VMs through the API on NFS/QCOW2 and Ceph/RBD, with cold migration and controlled warm CBT flows implemented.
Engineering Journal / Archive
All articles
Architecture, product changes and evidence from the lab.
6 articles / Newest first RSS feed
September 2026
When the migration database is gone, what survives?
V2K Migrate keeps full migration history in PostgreSQL, but also stores a small recovery record against the source VM in vCenter. Here is what that record can rebuild, and what it cannot.
Why preserving a Windows IP is not an import parameter
A Windows static IP is recorded inside the guest and in CloudStack. V2K Migrate has to keep both records in sync during migration.
At 50,000 VMs, one inventory query took 8.7 seconds
We tested the database, API and real UI with a large synthetic inventory. A PostgreSQL query reached 8.7 seconds. After the fix, its measured p95 was 183 ms.
Source vTPM detection added to preflight
V2K Migrate detects a VirtualTPM device in the source VM hardware and warns before cutover. It records device presence only; source TPM state is never migrated.
VMware-to-KVM migration is not a disk conversion problem
How V2K Migrate reads VMware disks, prepares the guest and creates the destination VM. The main design decisions, with their limits.