How to boot a virtual machine from an ISO image
Coming from another cloud?
▸AWS·Amazon Machine Images (AMIs)
Amazon Machine Images (AMIs)
- Managed via EC2 APIs, not Glance.
- Region-specific with cross-region copy.
- Marketplace AMIs may charge hourly fees.
- Includes block device mapping in AMI.
▸Azure·Compute Gallery image definitions and versions
Azure Compute Gallery image definitions and versions
- Organized in galleries with image definitions and versioned images (Microsoft.Compute/galleries/images/versions), more structured than flat Glance images.
- Supports global replication to regions with replicas (up to 100), ZRS storage, unlike OpenStack's store-only model.
- Sharing via RBAC, community galleries, or direct share; requires gallery setup vs simple OpenStack image sharing.
- New features like Trusted Launch only in Gallery, legacy managed images deprecated.
▸Google Cloud·Machine Images (full VM state capture)
OS images
- Public images shareable across projects (e.g. debian-cloud); OpenStack typically tenant-private.
- Image families point to latest version; no OpenStack equivalent.
- Custom images stored in Cloud Storage with licensing fees for premium OS.
How to boot a virtual machine from an ISO image
Install a custom operating system on Quake AI by booting from an ISO image. This process uses two volumes: a blank root drive and an ISO-backed drive. After the installation completes, you can snapshot the root volume and use it to launch new instances.
Overview:
- Create a blank volume (root drive A)
- Create a volume from the ISO image (volume B)
- Boot a VM with both volumes attached: A as the root drive, B as the ISO
- Install the OS from the ISO to the blank volume
- Detach and delete the ISO volume
- Snapshot or image the root volume for reuse
Prerequisites
- ConsoleLogged in to the Quake AI console
- CLIOpenStack CLI installed and authenticated (
clouds.yamloropenrcsourced)
Windows: CLI examples use bash. Set up a Linux CLI environment on Windows before proceeding.
- A Quake AI account with a project
- An ISO image uploaded to your project with disk format
ISO
Step 1. Create a blank root volume#
Step 2. Create a volume from the ISO image#
Step 3. Launch a VM with both volumes#
Boot an instance with iso-root-drive as the primary volume and iso-boot-media as a secondary drive. The VM boots from the ISO volume first.
Step 4. Install the operating system#
- Go to Compute > Instances and select
iso-installer. - Select Console to open the web-based VNC console.
- Complete the OS installation using the installer on the ISO. When prompted to select an installation target, choose the blank root drive (typically the larger volume,
vdbor/dev/sdb). - Shut down the instance from within the OS once installation completes.
Step 5. Detach and delete the ISO volume#
After the installation is done, remove the ISO volume:
Step 6. Boot from the installed volume#
Start the instance; it now boots from iso-root-drive with the installed OS:
Access the instance via the web console (Compute > Instances > iso-installer > Console) or via SSH if you configured SSH access during installation.
Reuse the installed image#
To create other instances from the same installation, take a snapshot of the root volume:
See also#
Usage Guidelines
The sample code, software libraries, command line tools, proofs of concept, templates, and other related technology on this page (including any of the foregoing that is provided by Quake AI personnel) is provided to you as Quake AI Content under the Quake AI Customer Agreement, or the relevant written agreement between you and Quake AI (whichever applies). Do not use this Quake AI Content in your production accounts, or on production or other critical data. You are responsible for testing, securing, and optimizing the Quake AI Content (such as sample code) as appropriate for production grade use based on your specific quality control practices and standards. Deploying Quake AI Content may incur Quake AI charges for creating or using Quake AI chargeable resources, such as running Compute instances or storing data in Object Storage. Your use is also subject to the Acceptable Use Policy.
For the full policy, see Usage Guidelines.
Last validated: 22.06.2026
Quick answers
- Why does `openstack image save` write a 0-byte file for my boot-from-volume instance?CLI
- Why does `openstack server create` fail with "Only volume-backed servers are allowed for flavors with zero disk"?CLIAPITerraform
- Why does my project still have a 10 GiB Cinder volume after I deleted my instance?CLIAPI