diff --git a/docs/ims/umn/en-us_topic_0030713189.html b/docs/ims/umn/en-us_topic_0030713189.html
index 08f697f9a..1bba6a6be 100644
--- a/docs/ims/umn/en-us_topic_0030713189.html
+++ b/docs/ims/umn/en-us_topic_0030713189.html
@@ -52,7 +52,7 @@
Other requirements
|
-- Currently, images with data disks cannot be created. The image file must contain only the system disk, and the system disk size must be [1 GB, 1024 GB].
- The initial password in the image file must contain uppercase letters, lowercase letters, digits, and special characters (!@$%^-_=+[{}]:,./?).
- The boot partition and system partition must be on the same disk.
- For an external image file, you need a tenant administrator account and password combination.
- Generally, the boot mode is BIOS in an image. Some OS images support the UEFI boot mode. For details, see OSs Supporting UEFI Boot Mode.
- The image file cannot be encrypted, or ECSs created from the registered image may not work properly.
+ | - Currently, images with data disks cannot be created. The image file must contain only the system disk, and the system disk size must be between 1 GB and 1024 GB.
- The initial password in the image file must contain uppercase letters, lowercase letters, digits, and special characters (!@$%^-_=+[{}]:,./?).
- The boot partition and system partition must be on the same disk.
- For an external image file, you need a tenant administrator account and password combination.
- Generally, the boot mode is BIOS in an image. Some OS images support the UEFI boot mode. For details, see OSs Supporting UEFI Boot Mode.
- The image file cannot be encrypted, or ECSs created from the registered image may not work properly.
|
diff --git a/docs/ims/umn/en-us_topic_0030713198.html b/docs/ims/umn/en-us_topic_0030713198.html
index 826662f7c..3abc96a8c 100644
--- a/docs/ims/umn/en-us_topic_0030713198.html
+++ b/docs/ims/umn/en-us_topic_0030713198.html
@@ -57,7 +57,7 @@
Other requirements
|
-- Currently, images with data disks cannot be created. The image file must contain only the system disk, and the system disk size must be [1 GB, 1024 GB].
- The initial password in the image file must contain uppercase letters, lowercase letters, digits, and special characters (!@$%^-_=+[{}]:,./?).
- The boot partition and system partition must be on the same disk.
- Generally, the boot mode is BIOS in an image. Some OS images support the UEFI boot mode. For details, see "OSs Supporting UEFI Boot Mode" in Image Service Management User Guide.
- The image file cannot be encrypted, or ECSs created from the registered image may not work properly.
- The /etc/fstab file cannot contain automatic mounting information of non-system disks. Otherwise, the login to the created ECS may fail.
- If the external image file uses LVM as the system disk, ECSs created from the private image do not support file injection.
- If the VM where the external image file is located has been shut down, it must be a graceful shutdown. Otherwise, a blue screen may occur when the ECS created from the private image is started.
+ | - Currently, images with data disks cannot be created. The image file must contain only the system disk, and the system disk size must be between 1 GB and 1024 GB.
- The initial password in the image file must contain uppercase letters, lowercase letters, digits, and special characters (!@$%^-_=+[{}]:,./?).
- The boot partition and system partition must be on the same disk.
- Generally, the boot mode is BIOS in an image. Some OS images support the UEFI boot mode. For details, see "OSs Supporting UEFI Boot Mode" in Image Service Management User Guide.
- The image file cannot be encrypted, or ECSs created from the registered image may not work properly.
- The /etc/fstab file cannot contain automatic mounting information of non-system disks. Otherwise, the login to the created ECS may fail.
- If the external image file uses LVM as the system disk, ECSs created from the private image do not support file injection.
- If the VM where the external image file is located has been shut down, it must be a graceful shutdown. Otherwise, a blue screen may occur when the ECS created from the private image is started.
|
diff --git a/docs/ims/umn/en-us_topic_0041178787.html b/docs/ims/umn/en-us_topic_0041178787.html
index cc51a03fa..2ccf7beb5 100644
--- a/docs/ims/umn/en-us_topic_0041178787.html
+++ b/docs/ims/umn/en-us_topic_0041178787.html
@@ -8,10 +8,17 @@
-2023-03-27
+ |
2023-04-19
+ |
+Modified the following content:
+Changed [1 GB, 1024 GB] to "between 1 GB and 1024 GB" in Preparing an Image File and Preparing an Image File.
+Optimized the description of qemu-img-hw in Converting the Image Format Using qemu-img-hw.
+ |
+
+2023-03-27
|
Added the following content:
-
+
|
2023-03-17
diff --git a/docs/ims/umn/en-us_topic_0171668652.html b/docs/ims/umn/en-us_topic_0171668652.html
index 02914d44d..6009a354f 100644
--- a/docs/ims/umn/en-us_topic_0171668652.html
+++ b/docs/ims/umn/en-us_topic_0171668652.html
@@ -14,7 +14,7 @@
|
qemu-img-hw
|
-qemu-img-hw is developed by Huawei and is used for converting image formats.
+ | 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
|