Overview

Last Updated At: 2025-11-26 15:01:22

In addition to using the Create Custom Image feature, Converge Cloud also supports to import. You can import image files of local server system disk or other platform into the custom image of Cloud Virtual Machine (CVM). After you import, you can use the imported image to create the Cloud Virtual Machine or reinstall the system on an existing Cloud Virtual Machine.

Import Preparation

You need to prepare an image file that meets the import restrictions in advance.

  • Image limits of Linux system type:
Image Attribute Condition
OS - Images based on CentOS, Ubuntu, and Debian distributions.
- Supports 32-bit and 64-bit
Image Format - Support RAW, VHD, QCOW2, VMDK image formats
- Use qemu-img info imageName | grep 'file format' to view image format.
Image Size Use qemu-img info imageName | grep 'disk size' to check the actual size of the image.
Use qemu-img info imageName | grep 'virtual size' to view image vsize.
Note: When importing an image, the size is based on the image information after conversion to QCOW2 format.
Network - By default, eth0 network API is provided for the instance.
- IPv6 is not supported yet.
- Users can query the network configuration of an instance through the metadata service within the instance. For details, see Instance Metadata.
Drive - The image must be installed with the Virtio driver of the virtualization platform KVM. For details, see Import Image on Linux to Check Virtio Driver.
- It is recommended to install cloudinit in the image. For details, see Import Image on Linux to Install Cloudinit.
- If the image cannot be installed with cloudinit due to other reasons, use Forced Import Image to self-configure instance.
Kernel Limits The image should preferably be a native kernel. Modification may cause the Cloud Virtual Machine to fail to import.
  • Image limits of Windows system type:
Image Attribute Condition
OS - Windows Server 2008 related versions, Windows Server 2012 related versions, and Windows Server 2016 related versions.
- Supports 32-bit and 64-bit
Image Format - Support RAW, VHD, QCOW2, VMDK image formats
- Use qemu-img info imageName | grep 'file format' to view image format.
File System Type - Only NTFS file systems that use MBR partitions are supported
- GPT partitions are not supported.
- Logical Volume Management (LVM) is not supported.
Image Size Use qemu-img info imageName | grep 'disk size' to check the actual size of the image.
Use qemu-img info imageName | grep 'virtual size' to view image vsize.
Note: When importing an image, the size is based on the image information after conversion to qcow2 format.
Network By default, this version provides a local connection network API for the instance.
IPv6 is not supported by this version.
Users can query the network configuration of an instance through the metadata service within the instance. For details, see Instance Metadata.
Drive The image must be installed with the Virtio driver of the virtualization platform KVM. The Virtio driver is not installed by default in Windows. You can install the Windows Virtio driver and then export the local image.
Others The imported Windows system images do not provide Windows Activation service.

Import Steps

  1. Log in to the CVM Console.
  2. Click Image in the left sidebar.
  3. Select Custom Image and click Import Image.
  4. According to the requirements of the operation interface, activate COS first, then create a bucket, upload the image file to the bucket. On the image file details page, directly click the temporary link and copy the temporary link to obtain the image file URL.
  5. Check Preparations completed. Then click Next: Import Image.
  6. Enter the form according to the actual situation and click Start Importing.
    Ensure that the Cloud Object Storage file URL you enter is correct. Whether the import is successful or failed, you will be notified via message center.

Import Failed

After the image import operation is performed on the console, the task may fail due to some reasons. If the task fails, you can troubleshoot based on the following information.

Notes

Before troubleshooting the cause of the failure according to this document, make sure that you have subscribed to product and service related notifications in the Message Subscription column of the Message Center Management page to ensure that you can receive message center, short message service, and emails containing the cause of the failure.

Note:

If you do not subscribe to product and service related information in the message center, you will not be able to receive message center notifications about the success/failure of the import.

Troubleshooting Cause of Failure

For detailed error prompts and error descriptions, see the error code.

InvalidUrl: The Cloud Object Storage Link is Invalid

The InvalidUrl error is reported, error prompts: An incorrect Cloud Object Storage link was entered on the image import page. Possible reasons are as follows:

  • The image link entered is not an Cloud Object Storage service.

  • The access permission to the Cloud Object Storage file is private read, but the signature has expired. > Note:
    The Cloud Object Storage file link with a signature can be accessed only once.

  • A Cloud Object Storage link in another region was entered. > Note:
    Import image service accesses the Cloud Object Storage server in the local region through the private network.

  • The user's image file has been deleted.
    If you receive an error reporting that the Cloud Object Storage link is invalid, you can troubleshoot the problem based on the reasons listed above.

InvalidFormatSize: The format or Size does not Meet the Requirements

The InvalidFormatSize error is reported, error prompts: The format or size of the pre-imported image does not meet the limits of the import image feature. The limits are as follows:

  • Import image supports 4 image file formats: qcow2, vhd, vmdk, and raw.
  • The size of the system disk of the import image must not exceed 500 GB.
    After an error reporting that the format or size does not meet the requirements is received:
  • Based on the image format conversion content of Linux Image Creation, you can convert the image file to a suitable file format, condense the image content to meet the size limit, and then re-import the image.
  • You can also use Offline Instance Migration to migrate example. This feature supports migration of image files with a maximum size of 500 GB.

VirtioNotInstall: Virtio Driver is not Installed

The VirtioNotInstall error is reported, error prompts: The Virtio driver is not installed on the pre-imported image. Converge Cloud uses KVM virtualization technology, which requires the virtio driver to be installed in the image that the user imports. The Virtio driver has been installed on most Linux operating systems except a few user-customized Linux operating systems. For Windows operating system, you need to manually install the Virtio driver:

CloudInitNotInstalled: The Cloud-init Program is not Installed

The CloudInitNotInstalled error is reported, error prompts: The cloud-init driver is not installed on the pre-imported image. Converge Cloud uses the open source program cloud-init to initialize the sub-machine. Therefore, if the cloud-init program is not installed, the user's sub-machine initialization will fail.

PartitionNotPresent: Partition Information is Lost

The PartitionNotPresent error is reported, error prompts: The imported image is incomplete. Check whether the boot partition is included when making the image.

RootPartitionNotFound: The Root Partition is Lost

The RootPartitionNotFound error is reported, error prompts: The imported image is not detected to contain a root partition. Check the image file. The reasons that have occurred are as follows for reference:

  • The installation package file is uploaded.
  • The data disk image is uploaded.
  • The boot partition image is uploaded.
  • The wrong file is uploaded.

InternalError: Unknown Error

The InternalError error is reported, error prompts: The import image service does not include the error cause. Contact customer service to handle this problem, and the technician will solve the problem as soon as possible.

Error Code

Error Code Error Cause Suggested Handling Method
InvalidUrl COS link is invalid. Check if the COS link is the same as the import image link.
InvalidFormatSize The format or size does not meet the requirements. The image must meet the requirements of Image Format and Image Size in the import preparation.
VirtioNotInstall Virtio driver is not installed. The virtio driver needs to be installed for images. For details, see Driver section in the import preparation.
PartitionNotPresent Partition information is not found. The image is damaged, which may be caused by the wrong image creation method.
CloudInitNotInstalled cloud-init is not installed. The cloud-init needs to be installed for Linux images. For details, see Driver section in the import preparation.
RootPartitionNotFound Root partition is not detected. The image is damaged, which may be caused by the wrong image creation method.
InternalError Other Errors Contact customer service to handle the problem.