Why Can't I Find My Private Image When I Want to Use It to Create an ECS or Change the OS of an ECS?
When I create an ECS or change the OS of an ECS, some of my private images are invisible to me. The possible cause is that the x86 and ARM architectures are incompatible with each other, or the UEFI and BIOS boot modes are incompatible with each other. The details are as follows:
- If a private image is created from a x86 ECS, this image will be invisible to you when you create an ARM (Kunpeng) ECS or change the OS of an ARM (Kunpeng) ECS. Similarly, a private image created from an ARM (Kunpeng) ECS will be invisible to you when you create a x86 server or change the OS of a x86 server.
- If you use an external image file to create a private image and select the x86 architecture, this image will be invisible to you when you create an ARM (Kunpeng) ECS or change the OS of an ARM (Kunpeng) ECS. Similarly, if you select the ARM architecture, this image will be invisible to you when you create a x86 ECS or change the OS of a x86 ECS.
- If a private image is created from an ECS in BIOS boot mode, this image will be invisible to you when you create an ECS in UEFI boot mode or change the OS of an ECS in UEFI boot mode. Similarly, a private image created from an ECS in UEFI boot mode will be invisible to you when you create an ECS in BIOS boot mode or change the OS of an ECS in BIOS boot mode.
- If you use an external image file to create a private image and select the BIOS boot mode, this image will be invisible to you when you create an ECS in UEFI boot mode or change the OS of an ECS in UEFI boot mode. Similarly, if you select the UEFI boot mode, the image will be invisible to you when you create an ECS in BIOS boot mode or change the OS of an ECS in BIOS boot mode.
Did this article solve your problem?
Thank you for your score!Your feedback would help us improve the website.