Difference between revisions of "Cool Solution - Migration of an OVA archives (virtual appliance) to UVMM"
From Univention Wiki
| Line 5: | Line 5: | ||
{{Version|UCS=3.1}} | {{Version|UCS=3.1}} | ||
| − | This article describes the migration of an OVA virtual appliance to a UVMM | + | This article describes the migration of an OVA virtual appliance to a UVMM machine (XEN or KVM). |
= Precondition = | = Precondition = | ||
| Line 31: | Line 31: | ||
= Para- or full-virtualization of the system (XEN only) = | = Para- or full-virtualization of the system (XEN only) = | ||
| − | Whether para- or full-virtualization can be used for the XEN | + | Whether para- or full-virtualization can be used for the XEN machine depends on the operating system. UCS (from 3.0) supports para-virtualization with the amd64 and i386 pae kernel. Windows system must be operated fully virtualized. |
| − | Furthermore, the system must be supported by the bootloader for paravirtual XEN | + | Furthermore, the system must be supported by the bootloader for paravirtual XEN machines "pygrub". This can be tested as follows: |
pygrub -n image-disk1.raw | pygrub -n image-disk1.raw | ||
| − | = Create an UVMM | + | = Create an UVMM machine = |
First, the image must be copied to the UVMM default pool (/var/lib/libvirt/images/). | First, the image must be copied to the UVMM default pool (/var/lib/libvirt/images/). | ||
| Line 43: | Line 43: | ||
cp image-disk1.raw /var/lib/libvirt/images/ | cp image-disk1.raw /var/lib/libvirt/images/ | ||
| − | Then an UVMM | + | Then an UVMM machine can be created with the UMC module UVMM. |
| − | When creating the | + | 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"). | 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 | + | 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 = | = Para/full virtual driver = | ||
| − | If supported by the operating system, paravirtual driver for the hard drive and the network interface can be used (UVMM -> | + | If supported by the operating system, paravirtual driver for the hard drive and the network interface can be used (UVMM -> Machine -> "Devices" -> "Drives/Network Interface" -> "Paravirtual drive"), see [[UVMM-Migration einer nativen Windows-Installation]] for more information. |
= Network = | = Network = | ||
| − | The mac address of the network interface can also be set in UVMM, | + | The mac address of the network interface can also be set in UVMM, Machine -> "Devices" -> "Network Interface" -> "MAC address". |
[[Category:Virtualisierung]] | [[Category:Virtualisierung]] | ||
Revision as of 15:39, 14 March 2013
This article describes the migration of an OVA virtual appliance to a UVMM machine (XEN or KVM).
Contents
Precondition
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 UVMM-Migration einer nativen Windows-Installation).
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 fmt" (see ""qemu-img --help" for the supported formats).
KVM
qemu-img convert -O qcow2 image-disk1.vmdk image-disk1.qcow2
XEN
qemu-img convert -O raw image-disk1.vmdk image-disk1.raw
Para- or full-virtualization of the system (XEN only)
Whether para- or full-virtualization can be used for the XEN machine depends on the operating system. UCS (from 3.0) supports para-virtualization with the amd64 and i386 pae kernel. Windows system must be operated fully virtualized.
Furthermore, the system must be supported by the bootloader for paravirtual XEN machines "pygrub". This can be tested as follows:
pygrub -n image-disk1.raw
Create an UVMM machine
First, the image must be copied to the UVMM default pool (/var/lib/libvirt/images/).
cp image-disk1.raw /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 (UVMM -> Machine -> "Devices" -> "Drives/Network Interface" -> "Paravirtual drive"), see UVMM-Migration einer nativen Windows-Installation for more information.
Network
The mac address of the network interface can also be set in UVMM, Machine -> "Devices" -> "Network Interface" -> "MAC address".
