What Do I Do If the Initial Configurations of a Linux External Image File Are Not Completed Before the File Is Exported?
The ECS where the external image file is located is not configured as instructed in Linux image file requirements before the image file is exported. You are advised to follow the process in Figure 1 to configure the ECS.
The proper running of ECSs depends on the XEN and KVM drivers. If the drivers are not installed, the performance of ECSs will be affected and some functions will be unavailable. Ensure that the two drivers have been installed for the image file before it is exported from the original platform. Otherwise, the ECSs created from the image will fail to start and cannot be configured.
For details, see Installing Native Xen and KVM Drivers.
Step 1: Upload the Image File
Upload the external image file to the OBS bucket. For details, see Uploading an External Image File (Linux).
Step 2 Register the External Image File as a Private Image
On the management console, select the uploaded image file and register it as an uninitialized private image. For details, see Registering an External Image File as a Private Image (Linux).
Step 3: Create an ECS
Create an ECS from the uninitialized private image.
- Log in to the management console.
- Under Computing, click Image Management Service.
The IMS console is displayed.
- Click the Private Images tab to display the image list.
- Locate the row that contains the uninitialized private image and click Apply for Server in the Operation column.
- Set parameters as promoted to create the ECS. Pay attention to the following:
- You are advised to select Pay-per-use for Billing Mode because the ECS will be deleted when you finish with it.
- You must add inbound rules for security groups of the ECS to ensure that the ECS can be accessed.
- If Cloud-Init has been installed in the image file, set a login password as prompted. If Cloud-Init is not installed, use the password or certificate contained in the image file to log in.
For details, see Purchasing an ECS with Customized Configurations.
- Perform the following steps to check whether the private image is available:
- Check whether the ECS can be successfully started. If the start succeeds, the XEN and KVM drivers have been installed for the external image file on the original platform or the drivers have been automatically installed for the private image on the cloud platform. If the start failed, install the XEN and KVM drivers for the image file and register it as a private image again.
- Check whether you can log in to the ECS using your configured password or key. If yes, Cloud-Init has been installed. If no, use the password or key contained in the image file to log in to the ECS and install Cloud-Init as instructed in Installing Cloud-Init.
- Check the network configuration by referring to Step 4: Configure the ECS.
If the ECS meets the preceding requirements, the private image is available. You can clear the environment as instructed in (Optional) Clear the Environment.
Step 4: Configure the ECS
Remotely log in to the ECS created in Step 3: Create an ECS to configure the network and install software.
- Log in to the ECS.
- Configuring the network.
- Run the ifconfig command to check whether the private IP address of the ECS is the same as that displayed on the console. If they are inconsistent, delete files in the network rule directory as instructed in Deleting Files in the Network Rule Directory.
- Check whether the 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.
- Run the service sshd status command to check whether SSH is enabled. If it is disabled, run the service sshd start command to enable it. Ensure that your firewall (for example, Linux iptables) allows SSH access.
- Configure a file system.
- Change the disk identifier in the GRUB configuration file to UUID. For details, see Changing the Disk Identifier in the GRUB Configuration File to UUID.
- Change the disk identifier in the fstab file to UUID. For details, see Changing the Disk Identifier in the fstab File to UUID.
- Clear the automatic attachment information of non-system disks in the /etc/fstab file to prevent impacts on subsequent data disk attachment. For details, see Detaching Data Disks from an ECS.
- (Optional) Configure value-added functions.
- Install and configure Cloud-Init. For details, see Installing Cloud-Init and Configuring Cloud-Init.
- Enable NIC multi-queue. For details, see How Do I Set NIC Multi-Queue for an Image?
- Configure an IPv6 address. For details, see How Do I Configure an ECS to Dynamically Acquire IPv6 Addresses?
Step 5: Create an Image from the ECS
Create a private image from the ECS. For details, see Creating a System Disk Image from a Linux ECS.
(Optional) Clear the Environment
In the preceding steps, storage fees are charged for the uninitialized image file, and extra fees are charged for the created ECS. Therefore, you are advised to clear the environment after the image is registered.
- Delete the uninitialized image registered in Step 2 Register the External Image File as a Private Image.
- Delete the ECS created in Step 3: Create an ECS.
- Delete the image files stored in the OBS bucket.

Did this article solve your problem?
Thank you for your score!Your feedback would help us improve the website.