Skip to main content

​
Overview

The Xloud Image Service supports multiple virtual disk formats. Selecting the right format affects launch performance, storage efficiency, and compatibility with your source environment. This guide compares supported formats, explains conversion workflows, and provides recommendations for common use cases.
Prerequisites
  • Basic familiarity with virtual disk concepts
  • qemu-img installed locally for format conversion (optional)

​
Format Comparison

​
Format Details

QCOW2 — Recommended

RAW images are unformatted disk dumps. There is zero overhead from the format layer. When Xloud Distributed Storage (Ceph RBD) is the image and volume backend, RBD handles copy-on-write natively — making RAW the optimal format.
On Ceph-backed deployments, instance launches from RAW images use zero-copy RBD clones — resulting in near-instantaneous boot times regardless of image size.
VHD and VHDX are the native disk formats for Microsoft Hyper-V. Import them directly into Xloud when migrating workloads from a Hyper-V environment.
Convert VHD/VHDX to QCOW2 after import for optimal performance and Xloud snapshot support.
VMDK is the native disk format for VMware ESXi and Workstation. Import VMDKs directly when migrating virtual machines from a VMware environment.
Convert VMDKs to QCOW2 after import to enable Xloud snapshot and resize operations.

​
Convert Between Formats

Use qemu-img to convert images locally before upload:
Verify the converted image:
Verify converted image

​
Next Steps

Upload an Image

Upload your converted image to the Xloud Image Service.

Image Properties

Set hardware properties matching your image format and source platform.

Image Admin Guide — Storage Backends

Configure the storage backend where images are stored after upload.

Troubleshooting

Resolve format-related launch failures and image upload errors.