Add an Image

The name must be 1 to 128 characters in length and can contain Chinese characters, English letters, digits, hyphens (-), underscores (_), periods (.), parenthesis (), colons (:), and plus signs (+).

• URL: Enter a specified URL to add an image. You can enter a URL by using either of the following syntax:
  • A URL that starts with http or https:
    • Syntax: http://host[:port]/path/file or https://host[:port]/path/file.
  • A URL that starts with ftp:
    • Syntax that does not specifies the user: ftp://hostname[:port]/path/file.
    • Syntax that specifies the user: ftp://user:password@hostname[:port]/path/file.
  • A URL that starts with sftp:
    • Syntax that specifies the user identity: sftp://user:password@hostname[:port]/path/file
    • User-identity-free syntax: sftp://user@hostname[:port]/path/file.
  • The absolute path of an image file that is stored on a backup storage. The backup storage that stores the image file can be an ImageStore backup storage.

    Syntax: file:///path/file

  Note:

  • The image file to be added to the destination backup storage must exist and the backup storage needs to have access to the URL of the image file.
  • If you enter a URL that starts with sftp and does not specify user identity, make sure that you enable password-free SSH login to the server that stores the image file.
  • For the progress bar and resumption from breakpoint features:
    • If you use an ImageStore backup storage, a progress bar will appear to display the upload progress. In addition, upload resumption from breakpoints is also supported.
    • If you use a Ceph backup storage, a progress bar will appear to display the upload progress. However, upload resumption from breakpoints is not supported.
  • If you specify a URL with the file:/// syntax to add an image:
    • Ceph backup storage does not support the file:/// syntax.
    • The three forward slashes (/) in file:/// represents the absolute path of a file on a backup storage. For example, if you specify the URL file:///opt/dvd/image-1.4.qcow2, you add the image file named image-1.4.qcow2 in the /opt/dvd path of a backup storage to the Cloud.
• Local File: Select a local image file that the current browser can access and upload the image file to the specified backup storage. The backup storage that stores the image file can be an ImageStore or Ceph backup storage.
  Note: If you upload a local image file, the local browser serves as a transfer station. Do not refresh or close the browser or stop management node services. Otherwise, the image addition may fail.

• Legacy: This mode supports all operating systems (OSs) and ensures stable operation. We recommend you select this mode.
• UEFI: This mode supports Windows and CentOS. Note that the Compatibility Support Module (CSM) must be enabled for Windows 7 and Windows Server 2008 R2.

Note: Mode mismatch may cause VM instances unable to work as expected. Select a mode based on your business needs:

• If you add an image in qcow2 or raw format, select the mode consistent with the mode used when the image was created.
• If you add an image in iso format, you can select either of the two modes. OS will be boot based on the selected mode.
• If you want to boot the OS of a VM instance in UEFI mode, we recommend that you select a VM image that is created from one of the OS listed in the following table.

  OS	BIOS Mode	Supported Versions
  Windows	UEFI	Windows 8 or later
  	UEFI with CSM	Windows 7 Windows Server 2008 R2
  Linux	UEFI	CentOS 7.2 CentOS 7.3 CentOS 7.4 or later

• As mentioned in the preceding table, you can create a Linux-based VM instance by using an image that is created from CentOS 7.4 or later and that uses the UEFI mode. However, if the VM instance is restarted, the system may enter the UEFI Shell. To avoid this situation, you can use one of the following methods to boot the OS:
  • Use a script to skip the UEFI Shell and directly load the OS.
    In the installed OS, run the vim /boot/efi/startup.nsh command to create a file, enter the following content in the file, and save the file. Then when you restart the VM instance, the UEFI Shell is skipped and the OS is boot.

    FS0:
    CD EFI
    CD centos
    shimx64-centos.efi

  • Manually exit the UEFI Shell.
    If you have entered the UEFI Shell, run the following commands to exit the UEFI Shell:

    Shell> fs0:
    FS0:\> cd EFI
    FS0:\EFI\> cd centos
    FS0:\EFI\centos\> shimx64-centos.efi

• If you use a Window-based VM instance such as Windows Server 2012 R2, Windows Server 2016, or Windows 10 that has its OS boot in UEFI mode, the following figure will display after you start the VM instance. In this case, press any key to continue the installation of the OS. Otherwise, the system will enter the UEFI Shell.

  
  
  

  If you have entered the UEFI Shell, run the following commands to exit the UEFI Shell:

  Shell> fs0:
  FS0:\> dir
  FS0:\> cd EFI
  FS0:\EFI\> cd BOOT
  FS0:\EFI\BOOT\> BOOTX64.EFI

  Then press any key in a timely manner. Otherwise, the system will reenter the UEFI Shell.

The CSM can only be used for devices that can only work in Legacy mode and OSs that do not support or partially support the UEFI mode.

Note: For Windows 7 and Windows Server 2008 R2, you must enable the CSM.