{"id":309,"date":"2026-09-05T19:15:39","date_gmt":"2026-09-05T22:15:39","guid":{"rendered":"https:\/\/www.linuxpro.com.br\/2026\/09\/ova2xva\/"},"modified":"2026-09-08T11:40:31","modified_gmt":"2026-09-08T14:40:31","slug":"ova2xva","status":"publish","type":"post","link":"https:\/\/www.linuxpro.com.br\/en\/2026\/09\/ova2xva\/","title":{"rendered":"ova2xva: migrate VMs from VMware\/VirtualBox to XCP-ng with one command"},"content":{"rendered":"

\"Mascote<\/p>\n

Moving a VM from VirtualBox<\/a> or VMware to XCP-ng<\/a> (or XenServer<\/a>) usually turns into a ritual: export OVA, convert the disk manually, wrestle with xe<\/code>. The ova2xva<\/strong> is a CLI in Go<\/strong> (MIT) that handles both directions in a single binary \u2014 it converts OVA or a standalone disk to XVA, validates it, imports it via XAPI and, if needed, returns a portable OVA. Without the xe<\/code> binary in the process.<\/p>\n

The code and releases are at github.com\/jniltinho\/ova2xva<\/a>. The current version of the official binaries is v0.4.0<\/strong> (August 1\u00ba, 2026).<\/p>\n

What it does<\/h2>\n\n\n\n\n\n\n\n\n
Command<\/th>\nFunction<\/th>\n<\/tr>\n<\/thead>\n
convert<\/code><\/td>\nOVA or standalone disk (.vmdk<\/code>, .qcow2<\/code>, .vhdx<\/code>\u2026) \u2192 .xva<\/code> (compression zstd<\/code> by default)<\/td>\n<\/tr>\n
to-ova<\/code><\/td>\nThe reverse: .xva<\/code> or disk \u2192 .ova<\/code> (OVF 1.0 + stream-optimized VMDK + SHA-256 manifest). Requires qemu-img<\/code><\/td>\n<\/tr>\n
validate<\/code><\/td>\nChecks the structure and SHA1 of .xva<\/code><\/td>\n<\/tr>\n
import<\/code><\/td>\nUploads to XCP-ng\/XenServer with HTTP PUT \/import<\/code> (XAPI) \u2014 without xe<\/code><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

VMDK, QCOW2, and VHDX decoding is native in Go<\/strong>. The qemu-img<\/code> is used as a fallback and is required<\/strong> in to-ova<\/code> (it generates the VMDK). Classic VHD and VDI also go exclusively through qemu-img<\/code>; .raw<\/code>\/.img<\/code> use direct copying.<\/p>\n

In practice<\/h2>\n
# OVA do VirtualBox\/VMware \u2192 XVA\nova2xva convert -o app.xva --name \"App Server\" app.ova\n\n# Disco solto, sem OVA\nova2xva convert -o app.xva --name \"App Server\" --memory 4096 --vcpus 2 disk.vmdk\n\n# Validar (opcional)\nova2xva validate app.xva\n\n# Importar no XCP-ng e j\u00e1 ligar a VM\nexport OVA2XVA_HOST=xcp.example.com OVA2XVA_USER=root OVA2XVA_PASSWORD='...'\nova2xva import --start app.xva\n\n# O caminho contr\u00e1rio: sair do Xen com um OVA port\u00e1til\nova2xva to-ova -o app.ova app.xva<\/code><\/pre>\n
Two details the README makes explicit that save you from surprises:<\/p>\n