What Do I Do If a Windows Image File Is Not Pre-Configured When I Use It to Register a Private Image?

If an image file is not configured as instructed in Table 1 before it is exported from the original platform, configure it by referring to Figure 1.

Caution

The proper running of ECSs depends on the KVM Guest OS driver (UVP VMTools), without which the performance of ECSs will be affected and some functions will be unavailable. Ensure that the driver installation has been completed for the image file before it is exported from the original platform. Otherwise, the ECSs created from the image will fail to start.

For details about how to install UVP VMTools, see Installing UVP VMTools.

**Figure 1** Image creation process

Figure 1 Image creation process

Step 1: Upload the Image File

Upload the external image file to an OBS bucket. For details, see Uploading an External Image File.

Step 2 Register the Image File as a Private Image

On the management console, select the uploaded image file and register it as a private image. For details, see Registering an External Image File as a Private Image.

Step 3: Create an ECS

  1. Access the IMS console.

    1. Log in to the management console.

    2. Under Compute, click Image Management Service.

      The IMS console is displayed.

  2. Click the Private Images tab.

  3. Locate the row that contains the private image and click Apply for Server in the Operation column.

  4. Set parameters as promoted to create an ECS. Pay attention to the following:

    • Bind an EIP to the ECS so that you can upload installation packages to the ECS or download installation packages from the ECS.

    • You must add inbound rules for security groups of the ECS to ensure that the ECS can be accessed.

    • If the image file has Cloudbase-Init installed, set a password and log in to the ECS using the password as prompted. If Cloudbase-Init is not installed, use the password or certificate contained in the image file to log in the ECS.

    For details, see Elastic Cloud Server User Guide.

  5. Perform the following steps to check whether the private image has been pre-configured:

    1. Check whether the ECS can be successfully started. If the start succeeds, a Guest OS driver has been installed for the image file on the original platform or the driver has been automatically installed for the private image on the cloud platform. If the start failed, install a Guest OS driver for the image file on the original platform and start from Step 1: Upload the Image File again.

    2. Check whether you can log in to the ECS using your configured password or key. If you can, Cloudbase-Init has been installed. If you cannot, use the password or key contained in the image file to log in to the ECS and install Cloudbase-Init as instructed in Installing and Configuring Cloudbase-Init.

    3. Check whether NICs are set to DHCP by referring to 2 in Step 4: Configure the ECS.

    4. Use MSTSC to log in to the ECS. If the login is successful, remote desktop connection is enabled on the ECS. If the login fails, enable remote desktop connection by referring to 3 in Step 4: Configure the ECS.

    If the ECS meets the preceding requirements, the private image has been pre-configured. Skip Step 4: Configure the ECS and Step 5: Create a Private Image from the ECS.

Step 4: Configure the ECS

Remotely log in to the ECS created in Step 3: Create an ECS to configure it.

  1. Log in to the ECS.

  2. Check whether NICs are set to DHCP. If the ECS is configured with a static IP address, change its IP address assignment mode to DHCP as instructed in Setting the NIC to DHCP.

  3. Enable remote desktop connection for the ECS as needed. For details about how to enable this function, see Enabling Remote Desktop Connection.

  4. (Optional) Configure value-added functions.

Step 5: Create a Private Image from the ECS

For details, see Creating a System Disk Image from a Windows ECS.

(Optional) Clear the Environment

After the image registration is complete, delete the image file as well as the intermediate private image and ECS to prevent them from occupying storage and compute resources.