sam.hadow/website-hadow.fr
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

article fix

Browse Source
This commit is contained in:
Sam Hadow
2025-11-24 16:31:35 +01:00
parent c7a786735e
commit 1dced1ffd8
1 changed files with 4 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

5
_posts/2025-11-24-kvm-import-ova-appliance.md
View File

@@ -1,4 +1,7 @@
---
layout: post
author: Sam Hadow
---
When downloading virtual machines they're usually packaged in an OVA file (Open Virtual Appliance). An OVA file is actually just a single file archive with an OVF package inside. When downloading virtual machines they're usually packaged in an OVA file (Open Virtual Appliance). An OVA file is actually just a single file archive with an OVF package inside.
An OVF package contains the metadata decribing the virtual machine (usually a .ovf file) and the virtual disks. The OVF standard doesn't specify a disk image format. An OVF package contains the metadata decribing the virtual machine (usually a .ovf file) and the virtual disks. The OVF standard doesn't specify a disk image format.
Virtual machines made using vmware, virtualbox or Microsoft hyper-V are usually using disks in the vmdk, vdi or vhd/vhdx formats respectively, which are then packaged in the OVA file. However, while QEMU/KVM can read them, there are not the prefered formats. We'll see here how to convert them to a more appropriate format. Virtual machines made using vmware, virtualbox or Microsoft hyper-V are usually using disks in the vmdk, vdi or vhd/vhdx formats respectively, which are then packaged in the OVA file. However, while QEMU/KVM can read them, there are not the prefered formats. We'll see here how to convert them to a more appropriate format.