Cool Solution - Migration of an OVA archives (virtual appliance) to UVMM
From Univention Wiki
This article describes the migration of an OVA virtual appliance to a UVMM machine.
It must be ensured that all drivers used in the virtual appliance are also supported in QEMU. Especially windows system must be prepared accordingly (see Migrating a native Windows installation to UVMM).
Unpack the OVA archive
The first step is to unpack the OVA archive.
tar -xvf image.ova
Convert the disk image
The image (a vmdk image in this example) must be converted to the appropriate format. The input format is automatically detected, but can also be passed as option -f vmdk.
qemu-img is able to convert many image formats besides vmdk. Take a look at qemu-img --help for other supported formats.
qemu-img convert -O qcow2 <disk name>.vmdk <disk name>.qcow2
Create an UVMM machine
First, the image must be copied to the UVMM default pool (/var/lib/libvirt/images/).
cp <disk name>.qcow2 /var/lib/libvirt/images/
Then an UVMM machine can be created with the UMC module UVMM.
When creating the machine a profile has to be selected. For paravirtual machines choose "UCS 3.0" (3.1) as profile and "Other" for full virtualization.
Select the previously copied disk image as hard drive from the default pool ("Drives" -> "Add" -> "Hard Drive" -> "Choose existing image").
Hardware information for the system, such as number of CPUs, architecture and amount of memory can be set when creating the machine (according to the settings from the OVF file of the OVA archive).
Para/full virtual driver
If supported by the operating system, paravirtual driver for the hard drive and the network interface can be used.
Please consider our Documentation, if you need help installing these on a Windows system.