diff --git a/docs/ims/umn/en-us_topic_0030713142.html b/docs/ims/umn/en-us_topic_0030713142.html index 9cac4f71..8c9d2941 100644 --- a/docs/ims/umn/en-us_topic_0030713142.html +++ b/docs/ims/umn/en-us_topic_0030713142.html @@ -2,7 +2,7 @@
This section describes the OSs supported by different types of ECSs.
-General-purpose S2, S3
+General-purpose S2, S3
Dedicated general-purpose C3, C4
Memory-optimized M3, M4
Disk-intensive D2
diff --git a/docs/ims/umn/en-us_topic_0030713143.html b/docs/ims/umn/en-us_topic_0030713143.html index ee3beb2c..558ca902 100644 --- a/docs/ims/umn/en-us_topic_0030713143.html +++ b/docs/ims/umn/en-us_topic_0030713143.html @@ -6,7 +6,7 @@When you upload an external image file to an OBS bucket on the management console, the OS contained in the image file will be checked. Table 1 lists the OSs supported by external image files.
If the OS cannot be identified or is not supported:
-This parameter is optional. The value can be BIOS or UEFI. For details about the differences between them, see How Is BIOS Different from UEFI?
For details about which OSs support UEFI boot, see OSs Supporting UEFI Boot Mode.
-The boot mode must be the same as that in the image file. You need to confirm which boot mode is used in the image file. After you select the correct boot mode, the boot mode will be configured for the image at the background. Select the right boot mode, or ECSs created using the image will not be able to boot up.
+The boot mode must be the same as that in the image file. You need to confirm which boot mode is used in the image file. After you select the right boot mode, the boot mode will be configured for the image at the background. Select the right boot mode, or ECSs created using the image will not be able to boot up.
OS
To ensure that the image can be created and used properly, select an OS consistent with that in the image file. If you do not select an OS, the system attempts to automatically identify the OS in the image file.
-System Disk (GB)
The system disk capacity (value range: 40 GB to 1024 GB). Ensure that this value is at least equal to the system disk capacity in the image file.
+The system disk capacity (value range: 40 GB to 1024 GB). Ensure that this value is not less than the system disk capacity in the image file.
If the uploaded VHD image is generated using qemu-img or similar tools, check the system disk capacity based on Why Did My VHD Upload Fail? Why Does the System Say the System Disk in the VHD Image File Is Larger Than What I Specified on the Management Console?
This parameter is optional. The value can be BIOS or UEFI. For details about the differences between them, see How Is BIOS Different from UEFI?
For details about which OSs support UEFI boot, see OSs Supporting UEFI Boot Mode.
-The boot mode must be the same as that in the image file. You need to confirm which boot mode is used in the image file. After you select the correct boot mode, the boot mode will be configured for the image at the background. Select the right boot mode, or ECSs created using the image will not be able to boot up.
+The boot mode must be the same as that in the image file. You need to confirm which boot mode is used in the image file. After you select the right boot mode, the boot mode will be configured for the image at the background. Select the right boot mode, or ECSs created using the image will not be able to boot up.
OS
To ensure that the image can be created and used properly, select an OS consistent with that in the image file. If you do not select an OS, the system attempts to automatically identify the OS in the image file.
-System Disk (GB)
The system disk capacity (value range: 40 GB to 1024 GB). Ensure that this value is at least equal to the system disk capacity in the image file.
+The system disk capacity (value range: 40 GB to 1024 GB). Ensure that this value is not less than the system disk capacity in the image file.
If the uploaded VHD image is generated using qemu-img or similar tools, check the system disk capacity based on Why Did My VHD Upload Fail? Why Does the System Say the System Disk in the VHD Image File Is Larger Than What I Specified on the Management Console?
The version number shown in the figure is for reference only.
The version number shown in the figure is for reference only.
[openstack] add_metadata_private_ip_route=False
Change the value of user_password_length to customize the password length.
+The registry entry RealTimeIsUniversal=1 allows the system to synchronize time from BIOS. If real_time_clock_utc=true is not configured, Cloudbase-Init will revert RealTimeIsUniversal back to 0. As a result, the system cannot synchronize time from BIOS after a restart.
quick-import-tools
https://obs-20181128.ims.obs.eu-de.otc.t-systems.com/DT-image-convert-tools.zip
+https://obs-20181128-ims.obs.eu-de.otc.t-systems.com/DT-image-convert-tools.zip
make
make install
-The following information is displayed when you run the qemu-img-hw command:
+The following information is displayed when you run the qemu-img-hw command:
./qemu-img-hw: error while loading shared libraries: libaio.so.1: cannot open shared object file: No such file or directory
Solution: Run the yum install libaio command first.
qemu-img-hw is used for converting image formats.
You can obtain it from:
-https://obs-20181128.ims.obs.eu-de.otc.t-systems.com/DT-image-convert-tools.zip
+https://obs-20181128-ims.obs.eu-de.otc.t-systems.com/DT-image-convert-tools.zip
Free
quick-import-tools
https://obs-20181128.ims.obs.eu-de.otc.t-systems.com/DT-image-convert-tools.zip
+https://obs-20181128-ims.obs.eu-de.otc.t-systems.com/DT-image-convert-tools.zip
quick-import-tools
https://obs-20181128.ims.obs.eu-de.otc.t-systems.com/DT-image-convert-tools.zip
+https://obs-20181128-ims.obs.eu-de.otc.t-systems.com/DT-image-convert-tools.zip