Skip to main content
Version: 3.1

Import OS images or migrate VMs from other hypervisors

Overview​

Import OS images and virtual machines into CubeCOS using the web-based UI to support cloud images, VM migrations from VMware, Hyper-V, and other hypervisors, with options for both administrator and project-level image management.

Import Cloud Images (From Bigstack workflow)​

This action was executed via the Skyline. Administrators and project users can import QCOW2 files as either public or private image resources.

You can easily download cloud images from our website. Go to Downloads

Import images as an administrator​

This action was executed via the Skyline. Administrators import images as public resources. The image can be used by all users and in all projects.

Switch to CubeCOS administrator view​

Before starting the import, switch to the CubeCOS administrator view. See administrator view.

Import images​

  1. Navigate to Compute > Images > Create Image.
  2. Fill in the required fields.
    • Select image: Select the image file to be imported.
    • Specific image name: Provide a unique name for the image.
    • OS: Select the OS template for the current image.
    • Destination: Specify the target location and storage media type after the image import. The following options are available:
      • Internal: CubeStorage is the default, built-in, distributed Ceph storage cluster.
      • External: Import the image to an external storage device. For example, NFS, iSCSI. For more information, see external image.
    • Domain: Always select Default
  3. To make the image publicly visible to all users, click the checkbox public at Visibility.
  4. Click Confirm.

Import Images as an user​

This action was executed via the Skyline. Users import images only for their own use.

  1. Navigate to Compute > Images > Create Image.
  2. Fill in the required fields.
    • Select image: Select the image file to be imported.
    • Specific image name: Provide a unique name for the image.
    • OS: Select the OS template for the current image.
    • Destination: Specify the target location and storage media type after the image import. The following options are available:
      • Internal: Built-in Ceph distributed storage cluster.
      • External: Import the image to an external storage device. For example, NFS, iSCSI.
    • Domain: Always select Default
  3. To make the image visible only to the user, click the checkbox private at Visibility.
  4. Click Confirm.

Import virtual disk images from another hypervisor​

This option enables you to import VMs from other platforms as bootable volumes in the form of virtual disks, which can then be used to launch VMs. Use this workflow to migrate workloads from external platforms to CubeCOS.

info

The system strictly enforces isolation for disks imported from another hypervisor (such as VMDK or VHDX). These resources are Private and are stored only within the designated project, preventing cross-project sharing.

Prerequisites​

Before importing, prepare the source VM image:

  • For Windows hosts: Disable security features such as BitLocker, vTPM, and other endpoint protections.
  • For Linux hosts: Ensure the OS is configured for hardware compatibility (Linux typically requires fewer adjustments than Windows).

Workflow​

  1. Export the image from the source hypervisor in a supported format.
  2. Upload the image to CubeCOS and select the From another hypervisor option.
  3. Create the VM using the imported Cinder volume.

Import Images as an administrator​

This action is executed via the Skyline. Administrators import images for specific projects. The image can be used by all users in the project.

Switch to CubeCOS administrator view​

Before starting the import, switch to the CubeCOS administrator view. See administrator view.

Import images​
  1. Navigate to Compute > Images > Create Image.
  2. Fill in the required fields.
    • Select image: Select the image file to be imported.
    • Specific image name: Provide a unique name for the image.
    • OS: Select the OS template for the current image.
    • Destination: Specify the target location and storage media type after the image import. The following options are available:
      • Internal: Built-in Ceph distributed storage cluster.
      • External: Import the image to an external storage device. For example, NFS, iSCSI.
    • Domain: Always select Default
  3. To make the image visible to all the users in the project. Select the project from Owned project list.
  4. Click the checkbox From another hypervisor at Source.
  5. Click Confirm.

Import Images as an user​

This action is executed via Skyline. Users import images for use exclusively within the current project they are currently logged into. These resources are subject to strict tenant isolation, meaning they will not be visible or accessible to users in other projects.

  1. Navigate to Compute > Images > Create Image.
  2. Fill in the required fields.
    • Select image: Select the image file to be imported.
    • Specific image name: Provide a unique name for the image.
    • OS: Select the OS template for the current image.
    • Destination: Specify the target location and storage media type after the image import. The following options are available:
      • Internal: Built-in Ceph distributed storage cluster.
      • External: Import the image to an external storage device. For example, NFS, iSCSI.
    • Domain: Always select Default
  3. Click the checkbox From another hypervisor at Source.
  4. Click Confirm.

Troubleshooting​

The following are some common issues that may arise during the import process:

  • If the page does not automatically redirect after clicking Confirm, it is usually because the API has not yet received a response (common with large file uploads). You can manually click the sidebar to navigate back to Images or Volumes page to check the status of the upload.
  • Skyline cannot upload two identical image files simultaneously. Doing so will cause the status to get stuck at Saving with a file size of 0.
  • If there is insufficient space in /tmp or the target storage pool, The conversion process will fail during the "Copying disk" or "Importing" phase. Skyline will then display an error status.
Last updated on by Brian Su