Boot Images

Use this page to register or upload boot image media for install workflows.

Quick User Steps

When to Use:

Use this page when you need installation media for VM bootstrap workflows.

Purpose:

Confirm Boot Images are ready and available in the target zone for provisioning.

Steps:

  1. Open Control Center -> Storage -> Boot Images.

  2. Register or upload one Boot Image.

  3. Verify state transitions to Ready.

  4. Use the image in Compute -> Virtual Machines create flow.

Expected Outcome:

  • At least one boot image is Ready and selectable for VM install workflows.

If this fails:

  1. Confirm Boot Image source URL or uploaded file is valid and reachable.

  2. Verify architecture, OS type, and zone values match the target VM plan.

  3. Review related events in Observability.

Boot Images

UI path: Control Center -> Storage -> Boot Images

Purpose

The Boot Images Dashboard provides a centralized view of all Boot Images available in Control Center. Use it to browse bootable installation media, manage Boot Image availability, and provision new virtual machines.

When to Use Boot Images

Use this module when you need to:

  • Publish or validate OS installation media.

  • Confirm architecture and zone compatibility before VM provisioning.

  • Manage visibility and bootable flags for shared media catalogs.

Overview

Boot Images are installation or utility media used during VM bootstrap and recovery workflows. The dashboard tracks readiness, visibility, architecture compatibility, and zone availability.

Boot Images Table

Column

Description

Boot Image Name

Unique identifier or name of the Boot Image. Click to view details.

Architecture

Processor architecture (for example x86_64, i386, or ARM64). Determines VM compatibility.

OS Type

Operating system type associated with the Boot Image.

Status

Current state (for example Ready, Downloading, Failed, Allocated).

Visibility

Access level (Public or Private).

Bootable

Whether the Boot Image can boot/install an OS (Yes or No).

Size

Boot Image file size.

Zone

Zone where the Boot Image is available. Can show - for global scope.

Actions

Delete action for removing Boot Images.

Boot Image Status Indicators

Status Badges

Status

Meaning

Ready

Fully downloaded and available for use.

Downloading

Boot Image is currently being downloaded from source.

Failed

Download or preparation failed; image cannot be used.

Allocated

Boot Image has been allocated but is not yet ready.

Visibility Badges

Visibility

Meaning

Public

Accessible to all users in Control Center.

Private

Restricted to owner/account scope.

Bootable Badges

Bootable

Meaning

Yes

Bootable media for OS install/boot workflows.

No

Not intended for VM boot; used for data/tools payloads.

Boot Image Types

Operating System Boot Images

Pre-built bootable images for OS installation:

  • Windows Server installation media.

  • Linux distribution installation media.

  • Virtio/tools media for guest integration and driver support.

Use cases:

  • Install Windows Server variants on new VMs.

  • Bootstrap Linux VMs with selected distribution media.

  • Install guest integration tools for better VM performance and management.

Tool and Utility Boot Images

Specialized utility images for operations and platform tooling:

  • vmware-tools.iso

  • xs-tools.iso

  • Kubernetes/CaaS utility images

Use cases:

  • Install guest tools and utilities.

  • Distribute system diagnostics/support media.

  • Support platform Bootstrap workflows.

Quick Actions

Use the trash icon in Actions to delete a Boot Image.

Warning

Deleting a Public Boot Image can impact all users that depend on it. Verify dependencies before confirming deletion.

Creating and Uploading Boot Images

Use + Add Boot Image (top-right) to publish new Boot Images. Typical fields include:

  • Boot Image name

  • File selection (upload)

  • OS type

  • Architecture

  • Visibility

  • Zone

  • Bootable flag

Size and Performance Considerations

Size range

Typical use

Transfer profile

Characteristics

< 1 GB

Minimal/live images

Quick

Minimal OS footprint and limited functionality.

1-5 GB

Standard OS images

Moderate

Full OS with common tools.

5-10 GB

Feature-rich OS images

Slow

OS with broader package/tool coverage.

> 10 GB

Specialized images

Very slow

Complex stacks and large preloaded payloads.

Boot Image Management Tips

  • Ensure Boot Images exist in the zone where VMs will be provisioned.

  • Use descriptive naming with OS, version, and architecture.

  • Keep sensitive/internal media Private; publish only approved standard media.

  • Set Bootable = Yes only for valid boot/install media.

  • Remove unused large Boot Images to reclaim storage.

  • Track versioned media explicitly in naming for clarity.

  • Check visibility settings regularly to maintain access control alignment.

Step: Review Boot Images Dashboard

When to Use: Use this when performing Review Boot Images Dashboard in the active storage workflow.

Purpose: Execute Review Boot Images Dashboard and confirm the expected UI/state outcome for this storage resource.

Steps:

  1. Open Control Center -> Storage -> Boot Images.

  2. Use search and filters for status/visibility/storage.

  3. Review table rows and verify Status and Bootable values.

Boot Images dashboard

Boot Images dashboard.

Expected Outcome:

  • Boot Images dashboard loads with rows, status, and bootable metadata visible.

If this fails:

  1. Verify backend health and available capacity for the target storage resource (pool/store/endpoint and zone scope).

  2. Check blocking dependencies for this action (attachments, snapshots, templates, buckets, object locks, or maintenance state).

  3. Review Observability Events/Alerts for the storage object and retry only after resolving the root cause.

Step: Open Boot Images Help Panel

When to Use: Use this after opening Boot Images when you need definitions for page fields and actions.

Purpose: Open contextual help separately from dashboard review and media operations.

Steps:

  1. Open Control Center -> Storage -> Boot Images.

  2. Click the help icon in the top-right corner.

  3. Review help guidance for Boot Images fields and controls.

Boot Images help panel

Boot Images help panel.

Expected Outcome:

  • The Boot Images help panel opens with page-specific guidance.

If this fails:

  1. Verify backend health and available capacity for the target storage resource (pool/store/endpoint and zone scope).

  2. Check blocking dependencies for this action (attachments, snapshots, templates, buckets, object locks, or maintenance state).

  3. Review Observability Events/Alerts for the storage object and retry only after resolving the root cause.

Step: Register Boot Image from URL

When to Use: Use this when performing Register Boot Image from URL in the active storage workflow.

Purpose: Execute Register Boot Image from URL and confirm the expected UI/state outcome for this storage resource.

Steps:

  1. Click + Add Boot Image.

  2. In Register Boot Image tab, fill required fields:

  • Name

  • URL

  • Zone

  • OS Type

  1. Configure toggles as needed:

  • Bootable

  • Public

  • Featured

  • Direct Download

  1. Click Register.

Register Boot Image form

Register Boot Image form.

Expected Outcome:

  • Boot-image row is created with selected zone/OS metadata.

  • Boot image transitions to a usable state after fetch/import processing.

If this fails:

  1. Verify backend health and available capacity for the target storage resource (pool/store/endpoint and zone scope).

  2. Check blocking dependencies for this action (attachments, snapshots, templates, buckets, object locks, or maintenance state).

  3. Review Observability Events/Alerts for the storage object and retry only after resolving the root cause.

Step: Upload Boot Image File

When to Use: Use this when performing Upload Boot Image File in the active storage workflow.

Purpose: Execute Upload Boot Image File and confirm the expected UI/state outcome for this storage resource.

Steps:

  1. In the same panel, switch to Upload Boot Image tab.

  2. Select the boot-image file.

  3. Fill required fields:

  • Name

  • Architecture

  • Zone

  • OS Type

  1. Confirm Format matches your artifact type.

  2. Optional: set Bootable toggle.

  3. Click Upload.

Upload Boot Image form

Upload Boot Image form.

Expected Outcome:

  • Uploaded boot image is cataloged in the list with provided metadata.

  • Boot image becomes usable when status indicates readiness.

If this fails:

  1. Verify backend health and available capacity for the target storage resource (pool/store/endpoint and zone scope).

  2. Check blocking dependencies for this action (attachments, snapshots, templates, buckets, object locks, or maintenance state).

  3. Review Observability Events/Alerts for the storage object and retry only after resolving the root cause.

Step: Delete Boot Image

When to Use: Use this when performing Delete Boot Image in the active storage workflow.

Purpose: Execute Delete Boot Image and confirm the expected UI/state outcome for this storage resource.

Steps:

  1. In the Boot Images dashboard, locate the target row.

  2. Complete Pre-Delete Safety Checklist (Use Before Any Delete).

  3. Click the trash icon in Actions.

  4. Confirm deletion and verify row removal.

  5. If deleted by mistake, re-register/upload the same boot image and wait for Ready.

Expected Outcome:

  • Task completes and the related storage view updates as expected.

If this fails:

  1. Verify backend health and available capacity for the target storage resource (pool/store/endpoint and zone scope).

  2. Check blocking dependencies for this action (attachments, snapshots, templates, buckets, object locks, or maintenance state).

  3. Review Observability Events/Alerts for the storage object and retry only after resolving the root cause.

Tool Tips

  • Keep boot images private unless broad access is explicitly required.

  • Use consistent naming (OS, version, architecture).

Warnings

  • Deleting a boot image in active use is blocked until workloads use a different boot source.

  • Deleting a Public Boot Image can impact all users; coordinate before removal.

  • Deleting a Private Boot Image removes it from owner/account scope.

  • Deleted Boot Images are not recoverable from Control Center; confirm before deletion.

  • Public visibility should be used only with approved media.

If this fails:

  1. If a boot image remains Not Ready, validate storage path and upload/URL source.

  2. If register action fails, verify source URL and zone mapping.

  3. If upload action fails, re-check file integrity and selected architecture.