Overview
The Xloud Image Service accepts virtual machine disk images in several formats for use as boot sources when launching new instances. You can upload images directly from your workstation through the Dashboard or CLI, or trigger a server-side web download from a public URL. This guide covers both methods.Prerequisites
- An active Xloud account with appropriate permissions
- Access to the Xloud Dashboard (
https://connect.<your-domain>) or CLI configured with credentials - API credentials sourced (
source admin-openrc.sh)
Supported formats: QCOW2 (recommended), RAW, VHD/VHDX, and VMDK.
See the Image Formats guide for format selection guidance.
Upload from Local File
- Dashboard
- CLI
Navigate to Images
Log in to the Xloud Dashboard (
https://connect.<your-domain>) and navigate to
Project → Compute → Images. Click Create Image.Configure image metadata
| Field | Description |
|---|---|
| Image Name | Descriptive name (e.g., ubuntu-24.04-lts) |
| Image Description | Optional — displayed in the image list |
| Image Source | Select File to upload from your browser |
| Image File | Select the local .qcow2, .raw, .vhd, or .vmdk file |
| Format | Select the disk format matching your file |
| Visibility | Private (project only) or Public (all projects, admin only) |
| Min Disk (GB) | Minimum root disk size required to launch |
| Min RAM (MB) | Minimum memory required to launch |
Import from URL (Web Download)
The web download import method fetches image data server-side — no local storage needed for large images.- CLI
Upload Best Practices
Always set min_disk and min_ram
Always set min_disk and min_ram
Setting
--min-disk and --min-ram prevents instance launch failures on flavors
that are too small for the image. Set these to the actual OS requirements:| OS | Recommended min_disk | Recommended min_ram |
|---|---|---|
| Ubuntu 22.04+ | 10 GB | 1024 MB |
| CentOS/RHEL 9 | 15 GB | 1024 MB |
| Windows Server | 40 GB | 2048 MB |
Use private visibility for development images
Use private visibility for development images
Upload images as
private (project-scoped) during testing. Only promote to public
or shared after validation. Administrators must approve public images to prevent
unauthorized images from appearing in the shared catalog.Name images with version and date
Name images with version and date
Include OS version and build date in image names for easy identification:
ubuntu-24.04-lts-2026-03— OS, version, LTS flag, build monthwindows-2022-std-2026-03— OS, version, edition, build month This naming scheme makes it easy to identify outdated images and manage lifecycle.
Next Steps
Image Properties
Set hardware requirements and OS metadata on uploaded images.
Share Images
Share images with other projects in your organization.
Create a Snapshot
Capture running instances as golden images for cloning and backup.
Troubleshooting
Resolve upload failures, stuck images, and launch errors.