diff --git a/docs/ims/umn/ALL_META.TXT.json b/docs/ims/umn/ALL_META.TXT.json new file mode 100644 index 000000000..2751a0792 --- /dev/null +++ b/docs/ims/umn/ALL_META.TXT.json @@ -0,0 +1,1502 @@ +[ + { + "uri":"en-us_topic_0013901623.html", + "product_code":"ims", + "code":"1", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"usermanual", + "kw":"Overview", + "title":"Overview", + "githuburl":"" + }, + { + "uri":"en-us_topic_0013901609.html", + "product_code":"ims", + "code":"2", + "des":"An image is a server or disk template that contains an operating system (OS) or service data and necessary software, such as database software. IMS provides public, priva", + "doc_type":"usermanual", + "kw":"Supported OSs,OS compatibility,Supported images,Public image,Private image,Shared image,What Is Imag", + "title":"What Is Image Management Service?", + "githuburl":"" + }, + { + "uri":"en-us_topic_0030713146.html", + "product_code":"ims", + "code":"3", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"usermanual", + "kw":"Supported OSs", + "title":"Supported OSs", + "githuburl":"" + }, + { + "uri":"en-us_topic_0030713142.html", + "product_code":"ims", + "code":"4", + "des":"This section describes the OSs supported by different types of ECSs.Table 1 lists the OSs supported by the following ECSs:General-purpose T6General computing S2, S3, S6, ", + "doc_type":"usermanual", + "kw":"Supported OSs,OS compatibility,Supported images,OSs Supported by Different Types of ECSs,Supported O", + "title":"OSs Supported by Different Types of ECSs", + "githuburl":"" + }, + { + "uri":"en-us_topic_0030713143.html", + "product_code":"ims", + "code":"5", + "des":"Image files in VMDK, VHD, QCOW2, RAW, VHDX, QED, VDI, QCOW, ZVHD2, or ZVHD format can be used to create private images. Select whichever format best meeting your requirem", + "doc_type":"usermanual", + "kw":"Supported OSs,OS compatibility,Supported images,External File Formats,Supported OSs,External Image F", + "title":"External Image File Formats and Supported OSs", + "githuburl":"" + }, + { + "uri":"en-us_topic_0170853315.html", + "product_code":"ims", + "code":"6", + "des":"The ECS boot mode can be BIOS or UEFI. For details about the differences between the two modes, see How Is BIOS Different from UEFI?Table 1 lists the OSs that support the", + "doc_type":"usermanual", + "kw":"Supported OSs,OS compatibility,Supported images,OSs Supporting UEFI Boot Mode,Supported OSs,User Gui", + "title":"OSs Supporting UEFI Boot Mode", + "githuburl":"" + }, + { + "uri":"en-us_topic_0194137262.html", + "product_code":"ims", + "code":"7", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"usermanual", + "kw":"Basic Concepts", + "title":"Basic Concepts", + "githuburl":"" + }, + { + "uri":"en-us_topic_0171754221.html", + "product_code":"ims", + "code":"8", + "des":"A region and availability zone (AZ) identify the location of a data center. You can create resources in a specific region and AZ.A region is a physical data center, which", + "doc_type":"usermanual", + "kw":"Region,Region and AZ,Basic Concepts,User Guide", + "title":"Region and AZ", + "githuburl":"" + }, + { + "uri":"en-us_topic_0089615820.html", + "product_code":"ims", + "code":"9", + "des":"IMS supports multiple image formats, but the system uses ZVHD or ZVHD2 by default.Table 1 lists the common image formats.", + "doc_type":"usermanual", + "kw":"image formats,Common Image Formats,Basic Concepts,User Guide", + "title":"Common Image Formats", + "githuburl":"" + }, + { + "uri":"en-us_topic_0030713148.html", + "product_code":"ims", + "code":"10", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"usermanual", + "kw":"Related Services,Overview,User Guide", + "title":"Related Services", + "githuburl":"" + }, + { + "uri":"en-us_topic_0130878289.html", + "product_code":"ims", + "code":"11", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"usermanual", + "kw":"Creating a Private Image", + "title":"Creating a Private Image", + "githuburl":"" + }, + { + "uri":"en-us_topic_0013901628.html", + "product_code":"ims", + "code":"12", + "des":"A private image is an image available only to the user who created it. It contains an OS, preinstalled public applications, and a user's personal applications. A private ", + "doc_type":"usermanual", + "kw":"Create image,Create OS,Introduction,Creating a Private Image,User Guide", + "title":"Introduction", + "githuburl":"" + }, + { + "uri":"en-us_topic_0030713149.html", + "product_code":"ims", + "code":"13", + "des":"If you have created and configured a Windows ECS based on your service requirements (for example, by installing software and setting up an application environment), you c", + "doc_type":"usermanual", + "kw":"Use ECS to create image,Create system disk image,Creating a System Disk Image from a Windows ECS,Cre", + "title":"Creating a System Disk Image from a Windows ECS", + "githuburl":"" + }, + { + "uri":"en-us_topic_0030713180.html", + "product_code":"ims", + "code":"14", + "des":"If you have created and configured a Linux ECS based on your service requirements (for example, by installing software and setting up an application environment), you can", + "doc_type":"usermanual", + "kw":"Creating a System Disk Image from a Linux ECS,Creating a Private Image,User Guide", + "title":"Creating a System Disk Image from a Linux ECS", + "githuburl":"" + }, + { + "uri":"en-us_topic_0030713181.html", + "product_code":"ims", + "code":"15", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"usermanual", + "kw":"Creating a Windows System Disk Image from an External Image File", + "title":"Creating a Windows System Disk Image from an External Image File", + "githuburl":"" + }, + { + "uri":"en-us_topic_0030713182.html", + "product_code":"ims", + "code":"16", + "des":"You can import a local image or a system disk image from another cloud platform to the current cloud. After an image is imported, you can use it to create ECSs or reinsta", + "doc_type":"usermanual", + "kw":"Use external image file to create image,Import image,Overview,Creating a Windows System Disk Image f", + "title":"Overview", + "githuburl":"" + }, + { + "uri":"en-us_topic_0030713189.html", + "product_code":"ims", + "code":"17", + "des":"You need to prepare an image file that meets the platform requirements.You are advised to complete the network, tool, and driver configurations in Table 1 on the ECS and ", + "doc_type":"usermanual", + "kw":"Preparing an Image File,Creating a Windows System Disk Image from an External Image File,User Guide", + "title":"Preparing an Image File", + "githuburl":"" + }, + { + "uri":"en-us_topic_0030713183.html", + "product_code":"ims", + "code":"18", + "des":"You are advised to use OBS Browser to upload external image files to OBS buckets. For details, see Object Storage Service User Guide.Only unencrypted external image files", + "doc_type":"usermanual", + "kw":"Standard,Uploading an External Image File,Creating a Windows System Disk Image from an External Imag", + "title":"Uploading an External Image File", + "githuburl":"" + }, + { + "uri":"en-us_topic_0030713184.html", + "product_code":"ims", + "code":"19", + "des":"Register an image file uploaded to the OBS bucket as a private image.Log in to the management console.Under Compute, click Image Management Service.The IMS console is dis", + "doc_type":"usermanual", + "kw":"Registering an External Image File as a Private Image,Creating a Windows System Disk Image from an E", + "title":"Registering an External Image File as a Private Image", + "githuburl":"" + }, + { + "uri":"en-us_topic_0030713188.html", + "product_code":"ims", + "code":"20", + "des":"After registering an external image file as a private image on the cloud platform, you can use the image to create ECSs or change the OSs of existing ECSs.This section de", + "doc_type":"usermanual", + "kw":"Creating a Windows ECS from an Image,Creating a Windows System Disk Image from an External Image Fil", + "title":"Creating a Windows ECS from an Image", + "githuburl":"" + }, + { + "uri":"en-us_topic_0030713190.html", + "product_code":"ims", + "code":"21", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"usermanual", + "kw":"Creating a Linux System Disk Image from an External Image File", + "title":"Creating a Linux System Disk Image from an External Image File", + "githuburl":"" + }, + { + "uri":"en-us_topic_0030713191.html", + "product_code":"ims", + "code":"22", + "des":"You can import a local image or a system disk image from another cloud platform to the current cloud. After an image is imported, you can use it to create ECSs or reinsta", + "doc_type":"usermanual", + "kw":"Use external image file to create image,Import image,Overview,Creating a Linux System Disk Image fro", + "title":"Overview", + "githuburl":"" + }, + { + "uri":"en-us_topic_0030713198.html", + "product_code":"ims", + "code":"23", + "des":"You need to prepare an image file that meets the platform requirements.You are advised to complete the file system, network, and driver configurations in Table 1 on the V", + "doc_type":"usermanual", + "kw":"Preparing an Image File,Creating a Linux System Disk Image from an External Image File,User Guide", + "title":"Preparing an Image File", + "githuburl":"" + }, + { + "uri":"en-us_topic_0030713192.html", + "product_code":"ims", + "code":"24", + "des":"You are advised to use OBS Browser to upload external image files to OBS buckets. For details, see Object Storage Service User Guide.Only unencrypted external image files", + "doc_type":"usermanual", + "kw":"Standard,Uploading an External Image File,Creating a Linux System Disk Image from an External Image ", + "title":"Uploading an External Image File", + "githuburl":"" + }, + { + "uri":"en-us_topic_0030713193.html", + "product_code":"ims", + "code":"25", + "des":"Register an image file uploaded to the OBS bucket as a private image.Log in to the management console.Under Compute, click Image Management Service.The IMS console is dis", + "doc_type":"usermanual", + "kw":"Registering an External Image File as a Private Image,Creating a Linux System Disk Image from an Ext", + "title":"Registering an External Image File as a Private Image", + "githuburl":"" + }, + { + "uri":"en-us_topic_0030713197.html", + "product_code":"ims", + "code":"26", + "des":"After registering an external image file as a private image on the cloud platform, you can use the image to create ECSs or change the OSs of existing ECSs.This section de", + "doc_type":"usermanual", + "kw":"Creating a Linux ECS from an Image,Creating a Linux System Disk Image from an External Image File,Us", + "title":"Creating a Linux ECS from an Image", + "githuburl":"" + }, + { + "uri":"en-us_topic_0095084510.html", + "product_code":"ims", + "code":"27", + "des":"For how to create a BMS private image, see Bare Metal Server User Guide.", + "doc_type":"usermanual", + "kw":"Creating a BMS System Disk Image,Creating a Private Image,User Guide", + "title":"Creating a BMS System Disk Image", + "githuburl":"" + }, + { + "uri":"en-us_topic_0102644450.html", + "product_code":"ims", + "code":"28", + "des":"A data disk image contains only service data. You can create a data disk image from an ECS and then use the image to create new EVS disks. This is a convenient way to mig", + "doc_type":"usermanual", + "kw":"data disk image,Creating a Data Disk Image from an ECS,Creating a Private Image,User Guide", + "title":"Creating a Data Disk Image from an ECS", + "githuburl":"" + }, + { + "uri":"en-us_topic_0084064672.html", + "product_code":"ims", + "code":"29", + "des":"A data disk image contains only service data. You can create a data disk image using a local image file or an external image file (image file on another cloud platform). ", + "doc_type":"usermanual", + "kw":"data disk image,external image file,Creating a Data Disk Image from an External Image File,Creating ", + "title":"Creating a Data Disk Image from an External Image File", + "githuburl":"" + }, + { + "uri":"en-us_topic_0116125142.html", + "product_code":"ims", + "code":"30", + "des":"You can create an image of an entire ECS, including not just the OS, but also the software and all the service data. You can then use this image to migrate data by quickl", + "doc_type":"usermanual", + "kw":"SAN policies,Creating a Full-ECS Image from an ECS,Creating a Private Image,User Guide", + "title":"Creating a Full-ECS Image from an ECS", + "githuburl":"" + }, + { + "uri":"en-us_topic_0093344231.html", + "product_code":"ims", + "code":"31", + "des":"Create a full-ECS image from a CSBS backup. This image can then be used to create ECSs.When creating a full-ECS image from a CSBS backup, ensure that the source ECS of th", + "doc_type":"usermanual", + "kw":"CSBS backup,Creating a Full-ECS Image from a CSBS Backup,Creating a Private Image,User Guide", + "title":"Creating a Full-ECS Image from a CSBS Backup", + "githuburl":"" + }, + { + "uri":"en-us_topic_0176812699.html", + "product_code":"ims", + "code":"32", + "des":"You can use a Cloud Backup and Recovery (CBR) backup to create a full-ECS image, which can be used to create ECSs.The Cloud Backup and Recovery (CBR) service provides bac", + "doc_type":"usermanual", + "kw":"Use backup to create image,full-ECS image,Creating a Full-ECS Image from a CBR Backup,Creating a Pri", + "title":"Creating a Full-ECS Image from a CBR Backup", + "githuburl":"" + }, + { + "uri":"en-us_topic_0030713151.html", + "product_code":"ims", + "code":"33", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"usermanual", + "kw":"Quickly Importing an Image File", + "title":"Quickly Importing an Image File", + "githuburl":"" + }, + { + "uri":"en-us_topic_0133773658.html", + "product_code":"ims", + "code":"34", + "des":"If an image file is larger than 128 GB, you can import it using fast import. Only the RAW and ZVHD2 formats support fast import. The image file to be imported cannot exce", + "doc_type":"usermanual", + "kw":"Overview,Quickly Importing an Image File,User Guide", + "title":"Overview", + "githuburl":"" + }, + { + "uri":"en-us_topic_0133773660.html", + "product_code":"ims", + "code":"35", + "des":"This section describes how to convert the format of an image file on a Linux server and then quickly import it to the cloud platform. You are advised to use an EulerOS EC", + "doc_type":"usermanual", + "kw":"Quickly Importing an Image File (Linux),Quickly Importing an Image File,User Guide", + "title":"Quickly Importing an Image File (Linux)", + "githuburl":"" + }, + { + "uri":"en-us_topic_0174703579.html", + "product_code":"ims", + "code":"36", + "des":"This section describes how to convert the format of an image file on a Windows server and then quickly import it to the cloud platform. You are advised to use a local Win", + "doc_type":"usermanual", + "kw":"Quickly Importing an Image File (Windows),Quickly Importing an Image File,User Guide", + "title":"Quickly Importing an Image File (Windows)", + "githuburl":"" + }, + { + "uri":"en-us_topic_0013901608.html", + "product_code":"ims", + "code":"37", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"usermanual", + "kw":"Managing Private Images", + "title":"Managing Private Images", + "githuburl":"" + }, + { + "uri":"en-us_topic_0030713199.html", + "product_code":"ims", + "code":"38", + "des":"You can modify the following attributes of a private image:NameDescriptionMinimum MemoryMaximum MemoryNIC Multi-QueueNIC multi-queue enables multiple CPUs to process NIC ", + "doc_type":"usermanual", + "kw":"Change,Image name,Image memory,NIC multi-queue,Name,Description,Minimum Memory,Maximum Memory,NIC Mu", + "title":"Modifying an Image", + "githuburl":"" + }, + { + "uri":"en-us_topic_0090099339.html", + "product_code":"ims", + "code":"39", + "des":"You can export the public or private image list in the current region as a CSV file to your local PC.For public images, the file describes the image name, image status, O", + "doc_type":"usermanual", + "kw":"Exporting Image List,Managing Private Images,User Guide", + "title":"Exporting Image List", + "githuburl":"" + }, + { + "uri":"en-us_topic_0300978092.html", + "product_code":"ims", + "code":"40", + "des":"You can check the disk capacity of a private image.To check the disk capacity of a system disk image, data disk image, or ISO image, see Check the Disk Capacity of a Syst", + "doc_type":"usermanual", + "kw":"Checking the Disk Capacity of an Image,Managing Private Images,User Guide", + "title":"Checking the Disk Capacity of an Image", + "githuburl":"" + }, + { + "uri":"en-us_topic_0030713200.html", + "product_code":"ims", + "code":"41", + "des":"You can use a public, private, or shared image to create an ECS.If you use a public image, the created ECS contains an OS and pre-installed public applications. You need ", + "doc_type":"usermanual", + "kw":"Creating an ECS from an Image,Managing Private Images,User Guide", + "title":"Creating an ECS from an Image", + "githuburl":"" + }, + { + "uri":"en-us_topic_0030713201.html", + "product_code":"ims", + "code":"42", + "des":"You can delete private images that will no longer be used.Access the IMS console.Log in to the management console.Under Compute, click Image Management Service.The IMS co", + "doc_type":"usermanual", + "kw":"Deleting Images,Managing Private Images,User Guide", + "title":"Deleting Images", + "githuburl":"" + }, + { + "uri":"en-us_topic_0032042416.html", + "product_code":"ims", + "code":"43", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"usermanual", + "kw":"Sharing Images", + "title":"Sharing Images", + "githuburl":"" + }, + { + "uri":"en-us_topic_0032042417.html", + "product_code":"ims", + "code":"44", + "des":"You can share your private images with other tenants. The tenants who accept the shared images can use the images to create ECSs of the same specifications.You can share ", + "doc_type":"usermanual", + "kw":"share,Overview,Sharing Images,User Guide", + "title":"Overview", + "githuburl":"" + }, + { + "uri":"en-us_topic_0032042418.html", + "product_code":"ims", + "code":"45", + "des":"Before a tenant shares an image with you, you need to provide your project ID.Access the IMS console.Log in to the management console.Under Compute, click Image Managemen", + "doc_type":"usermanual", + "kw":"Obtaining the Project ID,Sharing Images,User Guide", + "title":"Obtaining the Project ID", + "githuburl":"" + }, + { + "uri":"en-us_topic_0032042419.html", + "product_code":"ims", + "code":"46", + "des":"After obtaining the project ID from a tenant, you can share specified private images with the tenant. You can share a single image or multiple images as needed.You have o", + "doc_type":"usermanual", + "kw":"share a single image,Share multiple images,Share a single image,Sharing Specified Images,Sharing Ima", + "title":"Sharing Specified Images", + "githuburl":"" + }, + { + "uri":"en-us_topic_0032042420.html", + "product_code":"ims", + "code":"47", + "des":"After another tenant shares images with you, you will receive a message. You can choose to accept or reject all or some of the shared images.If you are not in the same re", + "doc_type":"usermanual", + "kw":"Accepting or Rejecting Shared Images,Sharing Images,User Guide", + "title":"Accepting or Rejecting Shared Images", + "githuburl":"" + }, + { + "uri":"en-us_topic_0032042421.html", + "product_code":"ims", + "code":"48", + "des":"You can reject accepted images if you no longer need them.After an image is rejected, it will not be displayed on the Images Shared with Me page.You have accepted images ", + "doc_type":"usermanual", + "kw":"Rejecting Accepted Images,Sharing Images,User Guide", + "title":"Rejecting Accepted Images", + "githuburl":"" + }, + { + "uri":"en-us_topic_0075730699.html", + "product_code":"ims", + "code":"49", + "des":"If you want to use the shared images you have rejected, you can accept them from the list of rejected images.You have rejected the images shared by others.The image owner", + "doc_type":"usermanual", + "kw":"shared image,Accepting Rejected Images,Sharing Images,User Guide", + "title":"Accepting Rejected Images", + "githuburl":"" + }, + { + "uri":"en-us_topic_0032042422.html", + "product_code":"ims", + "code":"50", + "des":"You can stop sharing images. After you stop sharing an image:The image will be invisible to the recipient on the management console and no data will be returned when the ", + "doc_type":"usermanual", + "kw":"stop sharing images,Stopping Sharing Images,Sharing Images,User Guide", + "title":"Stopping Sharing Images", + "githuburl":"" + }, + { + "uri":"en-us_topic_0032042423.html", + "product_code":"ims", + "code":"51", + "des":"In addition to the tenants you have shared images with, you can add more tenants who can use the shared images.You have shared private images.You have obtained the projec", + "doc_type":"usermanual", + "kw":"add more tenants,Adding Tenants Who Can Use Shared Images,Sharing Images,User Guide", + "title":"Adding Tenants Who Can Use Shared Images", + "githuburl":"" + }, + { + "uri":"en-us_topic_0032087324.html", + "product_code":"ims", + "code":"52", + "des":"This section describes how to delete image recipients who can use shared images.You have shared private images.You have obtained project IDs of the image recipients.Acces", + "doc_type":"usermanual", + "kw":"delete image recipients who can use shared images,Deleting Image Recipients Who Can Use Shared Image", + "title":"Deleting Image Recipients Who Can Use Shared Images", + "githuburl":"" + }, + { + "uri":"en-us_topic_0000001175697174.html", + "product_code":"ims", + "code":"53", + "des":"IMS provides multiple methods for importing images. You can select a method based on the image file type, format, or size.To import a data disk image file, follow the ins", + "doc_type":"usermanual", + "kw":"Importing an Image,Managing Private Images,User Guide", + "title":"Importing an Image", + "githuburl":"" + }, + { + "uri":"en-us_topic_0034011241.html", + "product_code":"ims", + "code":"54", + "des":"You can export a private image to a standard OBS bucket and then download it to your local PC.You can reproduce cloud servers and their running environments in on-promise", + "doc_type":"usermanual", + "kw":"Exporting an Image,Managing Private Images,User Guide", + "title":"Exporting an Image", + "githuburl":"" + }, + { + "uri":"en-us_topic_0130878748.html", + "product_code":"ims", + "code":"55", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"usermanual", + "kw":"Optimizing a Windows Private Image", + "title":"Optimizing a Windows Private Image", + "githuburl":"" + }, + { + "uri":"en-us_topic_0047501112.html", + "product_code":"ims", + "code":"56", + "des":"ECSs require Xen Guest OS driver (PV driver) and KVM Guest OS driver (UVP VMTools) for proper running. To ensure that ECSs support both Xen and KVM and to improve network", + "doc_type":"usermanual", + "kw":"Optimization Process,Optimizing a Windows Private Image,User Guide", + "title":"Optimization Process", + "githuburl":"" + }, + { + "uri":"en-us_topic_0125075471.html", + "product_code":"ims", + "code":"57", + "des":"Open the cmd window and run the following command to query the virtualization type of the ECS:systeminfoIf the values of System Manufacturer and BIOS Version are Xen, the", + "doc_type":"usermanual", + "kw":"virtualization type,Viewing the Virtualization Type of a Windows ECS,Optimizing a Windows Private Im", + "title":"Viewing the Virtualization Type of a Windows ECS", + "githuburl":"" + }, + { + "uri":"en-us_topic_0037352059.html", + "product_code":"ims", + "code":"58", + "des":"Table 1 lists the PV driver software packages required for optimizing Windows private images.Table 2 lists the UVP VMTools software packages required for optimizing Windo", + "doc_type":"usermanual", + "kw":"PV driver,UVP VMTools,Obtaining Required Software Packages,Optimizing a Windows Private Image,User G", + "title":"Obtaining Required Software Packages", + "githuburl":"" + }, + { + "uri":"en-us_topic_0037352182.html", + "product_code":"ims", + "code":"59", + "des":"When using an ECS or external image file to create a private image, ensure that the PV driver has been installed in the OS to enable Xen virtualization for subsequently c", + "doc_type":"usermanual", + "kw":"PV driver,Installing the PV Driver,Optimizing a Windows Private Image,User Guide", + "title":"Installing the PV Driver", + "githuburl":"" + }, + { + "uri":"en-us_topic_0037352061.html", + "product_code":"ims", + "code":"60", + "des":"Before using an ECS or external image file to create a private image, ensure that UVP VMTools has been installed in the OS to enable subsequently created ECSs to support ", + "doc_type":"usermanual", + "kw":"UVP VMTools,KVM virtualization,UVP VMTools,Installing UVP VMTools,Optimizing a Windows Private Image", + "title":"Installing UVP VMTools", + "githuburl":"" + }, + { + "uri":"en-us_topic_0125075472.html", + "product_code":"ims", + "code":"61", + "des":"After installing the PV driver and UVP VMTools, perform the following operations to clear system logs:For Windows Server 2008 and Windows Server 2012, right-click Compute", + "doc_type":"usermanual", + "kw":"Clearing System Logs,Optimizing a Windows Private Image,User Guide", + "title":"Clearing System Logs", + "githuburl":"" + }, + { + "uri":"en-us_topic_0130878749.html", + "product_code":"ims", + "code":"62", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"usermanual", + "kw":"Optimizing a Linux Private Image", + "title":"Optimizing a Linux Private Image", + "githuburl":"" + }, + { + "uri":"en-us_topic_0047501133.html", + "product_code":"ims", + "code":"63", + "des":"A Linux ECS can be switched from Xen to KVM if xen-pv and VirtIO drivers run on the ECS. Before changing a Xen-based ECS to a KVM-based ECS, ensure that the required driv", + "doc_type":"usermanual", + "kw":"Optimization Process,Optimizing a Linux Private Image,User Guide", + "title":"Optimization Process", + "githuburl":"" + }, + { + "uri":"en-us_topic_0037352185.html", + "product_code":"ims", + "code":"64", + "des":"You can run the following command to query the virtualization type of an ECS:lscpuIf the value of Hypervisor vendor is Xen, the ECS uses Xen. If KVM is required, perform ", + "doc_type":"usermanual", + "kw":"Viewing the Virtualization Type of a Linux ECS,Optimizing a Linux Private Image,User Guide", + "title":"Viewing the Virtualization Type of a Linux ECS", + "githuburl":"" + }, + { + "uri":"en-us_topic_0037352186.html", + "product_code":"ims", + "code":"65", + "des":"When optimizing a Linux private image, you need to change the UUID in the fstab and GRUB configuration files, and install native Xen and KVM drivers on the ECS. To ensure", + "doc_type":"usermanual", + "kw":"uvp-monitor,Uninstalling the PV Driver from a Linux ECS,Optimizing a Linux Private Image,User Guide", + "title":"Uninstalling the PV Driver from a Linux ECS", + "githuburl":"" + }, + { + "uri":"en-us_topic_0086020895.html", + "product_code":"ims", + "code":"66", + "des":"When optimizing a Linux private image, you need to change the disk identifier to UUID in the GRUB configuration file of the ECS.Modify the menu.lst or grub.cfg configurat", + "doc_type":"usermanual", + "kw":"Changing the Disk Identifier in the GRUB Configuration File to UUID,Optimizing a Linux Private Image", + "title":"Changing the Disk Identifier in the GRUB Configuration File to UUID", + "githuburl":"" + }, + { + "uri":"en-us_topic_0086024961.html", + "product_code":"ims", + "code":"67", + "des":"When optimizing a Linux private image, you need to change the disk identifier to UUID in the fstab configuration file of the ECS.Take CentOS 7.0 as an example. Run blkid ", + "doc_type":"usermanual", + "kw":"UUIDs,Changing the Disk Identifier in the fstab File to UUID,Optimizing a Linux Private Image,User G", + "title":"Changing the Disk Identifier in the fstab File to UUID", + "githuburl":"" + }, + { + "uri":"en-us_topic_0000001120952155.html", + "product_code":"ims", + "code":"68", + "des":"When optimizing a Linux private image, you need to install native KVM drivers on the ECS.If you do not install KVM drivers, NICs of the ECS may not be detected and the EC", + "doc_type":"usermanual", + "kw":"native KVM drivers,Installing Native KVM Drivers,Optimizing a Linux Private Image,User Guide", + "title":"Installing Native KVM Drivers", + "githuburl":"" + }, + { + "uri":"en-us_topic_0125076462.html", + "product_code":"ims", + "code":"69", + "des":"Delete log files and historical records, and stop the ECS.Run the following commands to delete redundant key files:echo > /$path/$to/$root/.ssh/authorized_keysAn example ", + "doc_type":"usermanual", + "kw":"Delete log files,Clearing System Logs,Optimizing a Linux Private Image,User Guide", + "title":"Clearing System Logs", + "githuburl":"" + }, + { + "uri":"en-us_topic_0046588153.html", + "product_code":"ims", + "code":"70", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"usermanual", + "kw":"Encrypting Images", + "title":"Encrypting Images", + "githuburl":"" + }, + { + "uri":"en-us_topic_0046588154.html", + "product_code":"ims", + "code":"71", + "des":"IMS allows you to create encrypted images to ensure data security.To use the image encryption function, you must apply for KMS Administrator permissions.KMS must be enabl", + "doc_type":"usermanual", + "kw":"image encryption,Encrypted images,Overview,Encrypting Images,User Guide", + "title":"Overview", + "githuburl":"" + }, + { + "uri":"en-us_topic_0046588155.html", + "product_code":"ims", + "code":"72", + "des":"You can create an encrypted image using an external image file or an encrypted ECS.Create an encrypted image using an external image file.When you register the external i", + "doc_type":"usermanual", + "kw":"encrypted image,Creating Encrypted Images,Encrypting Images,User Guide", + "title":"Creating Encrypted Images", + "githuburl":"" + }, + { + "uri":"en-us_topic_0049177180.html", + "product_code":"ims", + "code":"73", + "des":"You can convert encrypted and unencrypted images into each other or enable some advanced features (such as fast ECS creation from an image) using the image replication fu", + "doc_type":"usermanual", + "kw":"replicate an image,Replicating Images,Managing Private Images,User Guide", + "title":"Replicating Images", + "githuburl":"" + }, + { + "uri":"en-us_topic_0068002265.html", + "product_code":"ims", + "code":"74", + "des":"You can use tags to classify images. You can add, modify, or delete image tags, or search for required images by tag in the image list.When adding predefined tags to an i", + "doc_type":"usermanual", + "kw":"image tags,Tagging an Image,Managing Private Images,User Guide", + "title":"Tagging an Image", + "githuburl":"" + }, + { + "uri":"en-us_topic_0107462580.html", + "product_code":"ims", + "code":"75", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"usermanual", + "kw":"Auditing Key Operations", + "title":"Auditing Key Operations", + "githuburl":"" + }, + { + "uri":"en-us_topic_0107462581.html", + "product_code":"ims", + "code":"76", + "des":"Cloud Trace Service (CTS) is a log audit service provided by the public cloud and intended for cloud security. It allows you to collect, store, and query cloud resource o", + "doc_type":"usermanual", + "kw":"IMS Operations Recorded by CTS,Auditing Key Operations,User Guide", + "title":"IMS Operations Recorded by CTS", + "githuburl":"" + }, + { + "uri":"en-us_topic_0107462582.html", + "product_code":"ims", + "code":"77", + "des":"Once CTS is enabled, it starts recording IMS operations. You can view operations recorded in the last seven days on the CTS management console.This section describes how ", + "doc_type":"usermanual", + "kw":"Viewing Traces,Auditing Key Operations,User Guide", + "title":"Viewing Traces", + "githuburl":"" + }, + { + "uri":"en-us_topic_0117262219.html", + "product_code":"ims", + "code":"78", + "des":"You can import an image file in VHD, VMDK, QCOW2, RAW, VHDX, QCOW, VDI, QED, ZVHD, or ZVHD2 format to the cloud platform. Image files in other formats need to be converte", + "doc_type":"usermanual", + "kw":"qemu-img,Converting the Image Format Using qemu-img,Managing Private Images,User Guide", + "title":"Converting the Image Format Using qemu-img", + "githuburl":"" + }, + { + "uri":"en-us_topic_0171668652.html", + "product_code":"ims", + "code":"79", + "des":"You can import an image file in VHD, VMDK, QCOW2, RAW, VHDX, QCOW, VDI, QED, ZVHD, or ZVHD2 format to the cloud platform. Image files in other formats need to be converte", + "doc_type":"usermanual", + "kw":"Converting the Image Format Using qemu-img-hw,Managing Private Images,User Guide", + "title":"Converting the Image Format Using qemu-img-hw", + "githuburl":"" + }, + { + "uri":"en-us_topic_0199394934.html", + "product_code":"ims", + "code":"80", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"usermanual", + "kw":"Windows Operations", + "title":"Windows Operations", + "githuburl":"" + }, + { + "uri":"en-us_topic_0030713152.html", + "product_code":"ims", + "code":"81", + "des":"If a private image is created from an ECS or external image file and the VM where the ECS or external image file is located is configured with a static IP address, you ne", + "doc_type":"usermanual", + "kw":"NIC DHCP,Enable remote desktop connection,Setting the NIC to DHCP,Windows Operations,User Guide", + "title":"Setting the NIC to DHCP", + "githuburl":"" + }, + { + "uri":"en-us_topic_0030713155.html", + "product_code":"ims", + "code":"82", + "des":"If you want to remotely access an ECS, enable remote desktop connection for the source ECS when creating a private image. This function must be enabled for GPU-accelerate", + "doc_type":"usermanual", + "kw":"Use ECS to create image,remote desktop connection,Enabling Remote Desktop Connection,Windows Operati", + "title":"Enabling Remote Desktop Connection", + "githuburl":"" + }, + { + "uri":"en-us_topic_0030730602.html", + "product_code":"ims", + "code":"83", + "des":"To ensure that you can use the user data injection function to inject initial custom information into ECSs created from a private image (such as setting the ECS login pas", + "doc_type":"usermanual", + "kw":"Cloudbase-Init,Installing and Configuring Cloudbase-Init,Windows Operations,User Guide", + "title":"Installing and Configuring Cloudbase-Init", + "githuburl":"" + }, + { + "uri":"en-us_topic_0093887081.html", + "product_code":"ims", + "code":"84", + "des":"Running Sysprep ensures that an ECS has a unique SID after it is added to a domain.After installing Cloudbase-Init on an ECS, you need to decide whether the ECS needs to ", + "doc_type":"usermanual", + "kw":"Sysprep,Running Sysprep,Windows Operations,User Guide", + "title":"Running Sysprep", + "githuburl":"" + }, + { + "uri":"en-us_topic_0081795392.html", + "product_code":"ims", + "code":"85", + "des":"Before using some types of ECSs to create private images, you need to install special drivers on the ECSs.If you want to use the created private image to create GPU-accel", + "doc_type":"usermanual", + "kw":"Installing Special Windows Drivers,Windows Operations,User Guide", + "title":"Installing Special Windows Drivers", + "githuburl":"" + }, + { + "uri":"en-us_topic_0199394935.html", + "product_code":"ims", + "code":"86", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"usermanual", + "kw":"Linux Operations", + "title":"Linux Operations", + "githuburl":"" + }, + { + "uri":"en-us_topic_0030713176.html", + "product_code":"ims", + "code":"87", + "des":"If a private image is created from an ECS or external image file and the VM where the ECS or external image file is located is configured with a static IP address, you ne", + "doc_type":"usermanual", + "kw":"Setting the NIC to DHCP,Linux Operations,User Guide", + "title":"Setting the NIC to DHCP", + "githuburl":"" + }, + { + "uri":"en-us_topic_0069904570.html", + "product_code":"ims", + "code":"88", + "des":"To prevent NIC name drift when you use a private image to create ECSs, you need to delete files from the network rule directory of the VM where the ECS or image file is l", + "doc_type":"usermanual", + "kw":"Delete network rule files,Disable NetworkManager,Deleting Files from the Network Rule Directory,Linu", + "title":"Deleting Files from the Network Rule Directory", + "githuburl":"" + }, + { + "uri":"en-us_topic_0030730603.html", + "product_code":"ims", + "code":"89", + "des":"To ensure that you can use the user data injection function to inject initial custom information into ECSs created from a private image (such as setting the ECS login pas", + "doc_type":"usermanual", + "kw":"Check whether Cloud-Init is installed,Cloud-Init,Installing Cloud-Init,Linux Operations,User Guide", + "title":"Installing Cloud-Init", + "githuburl":"" + }, + { + "uri":"en-us_topic_0122876047.html", + "product_code":"ims", + "code":"90", + "des":"You need to configure Cloud-Init after it is installed.Cloud-Init has been installed.An EIP has been bound to the ECS.You have logged in to the ECS.The IP address obtaini", + "doc_type":"usermanual", + "kw":"Cloud-Init,Configuring Cloud-Init,Linux Operations,User Guide", + "title":"Configuring Cloud-Init", + "githuburl":"" + }, + { + "uri":"en-us_topic_0082002007.html", + "product_code":"ims", + "code":"91", + "des":"Before using some types of ECSs to create private images, you need to install special drivers on the ECSs.If you want to use the private image to create P1 ECSs, install ", + "doc_type":"usermanual", + "kw":"Installing Special Linux Drivers,Linux Operations,User Guide", + "title":"Installing Special Linux Drivers", + "githuburl":"" + }, + { + "uri":"en-us_topic_0030713179.html", + "product_code":"ims", + "code":"92", + "des":"If multiple data disks are attached to the ECS used to create a private image, ECSs created from the image may be unavailable. Therefore, you need to detach all data disk", + "doc_type":"usermanual", + "kw":"Detaching Data Disks from an ECS,Linux Operations,User Guide", + "title":"Detaching Data Disks from an ECS", + "githuburl":"" + }, + { + "uri":"en-us_topic_0057450886.html", + "product_code":"ims", + "code":"93", + "des":"If you want to use the ECS console logging function, you need to configure related parameters on the ECS.Currently, ECSs running the following OSs are supported: CentOS 6", + "doc_type":"usermanual", + "kw":"Configuring Console Logging,Linux Operations,User Guide", + "title":"Configuring Console Logging", + "githuburl":"" + }, + { + "uri":"en-us_topic_0030713202.html", + "product_code":"ims", + "code":"94", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"usermanual", + "kw":"FAQs", + "title":"FAQs", + "githuburl":"" + }, + { + "uri":"en-us_topic_0138455714.html", + "product_code":"ims", + "code":"95", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"usermanual", + "kw":"Image Consulting", + "title":"Image Consulting", + "githuburl":"" + }, + { + "uri":"en-us_topic_0195253327.html", + "product_code":"ims", + "code":"96", + "des":"When creating an ECS or BMS, you can select an image based on the following factors:Region and AZImage TypeOSAn image is a regional resource. You cannot use an image to c", + "doc_type":"usermanual", + "kw":"How Do I Select an Image?,Image Consulting,User Guide", + "title":"How Do I Select an Image?", + "githuburl":"" + }, + { + "uri":"en-us_topic_0153114116.html", + "product_code":"ims", + "code":"97", + "des":"Quotas can limit the number or amount of resources available to users, such as the maximum number of ECSs or EVS disks that can be created.If the existing resource quota ", + "doc_type":"usermanual", + "kw":"How Do I Increase the Image Quota?,Image Consulting,User Guide", + "title":"How Do I Increase the Image Quota?", + "githuburl":"" + }, + { + "uri":"en-us_topic_0173986473.html", + "product_code":"ims", + "code":"98", + "des":"Yes.Other tenants can share a private image with you. You can use it after accepting it. For details about image sharing, see Sharing Specified Images.", + "doc_type":"usermanual", + "kw":"Can I Use Private Images of Other Tenants?,Image Consulting,User Guide", + "title":"Can I Use Private Images of Other Tenants?", + "githuburl":"" + }, + { + "uri":"en-us_topic_0193137621.html", + "product_code":"ims", + "code":"99", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"usermanual", + "kw":"Image Creation", + "title":"Image Creation", + "githuburl":"" + }, + { + "uri":"en-us_topic_0193146244.html", + "product_code":"ims", + "code":"100", + "des":"Currently, you can create a maximum of 100 private images under an account in a region.No. You can create an image from a running ECS. However, if data is written to the ", + "doc_type":"usermanual", + "kw":"Image Creation FAQs,Image Creation,User Guide", + "title":"Image Creation FAQs", + "githuburl":"" + }, + { + "uri":"en-us_topic_0106444267.html", + "product_code":"ims", + "code":"101", + "des":"An ECS used to create a Windows full-ECS image cannot have a spanned volume. If you attempt to create an image from an ECS with a spanned volume, when the image is used t", + "doc_type":"usermanual", + "kw":"How Do I Create a Full-ECS Image Using an ECS That Has a Spanned Volume?,Image Creation,User Guide", + "title":"How Do I Create a Full-ECS Image Using an ECS That Has a Spanned Volume?", + "githuburl":"" + }, + { + "uri":"en-us_topic_0030742197.html", + "product_code":"ims", + "code":"102", + "des":"For a user that needs to be added to a domain and uses the domain account to log in to Windows, Sysprep is required before a private image is created. Otherwise, the imag", + "doc_type":"usermanual", + "kw":"Why Is Sysprep Required for Creating a Private Image from a Windows ECS?,Image Creation,User Guide", + "title":"Why Is Sysprep Required for Creating a Private Image from a Windows ECS?", + "githuburl":"" + }, + { + "uri":"en-us_topic_0096558549.html", + "product_code":"ims", + "code":"103", + "des":"When you create a ZVHD2 image using an API, the image is created in the ZVHD format.Check whether your token contains the op_gated_lld role (op_gated_lld is the OBT tag, ", + "doc_type":"usermanual", + "kw":"What Do I Do If I Cannot Create an Image in ZVHD2 Format Using an API?,Image Creation,User Guide", + "title":"What Do I Do If I Cannot Create an Image in ZVHD2 Format Using an API?", + "githuburl":"" + }, + { + "uri":"en-us_topic_0171668653.html", + "product_code":"ims", + "code":"104", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"usermanual", + "kw":"Image Sharing", + "title":"Image Sharing", + "githuburl":"" + }, + { + "uri":"en-us_topic_0183293890.html", + "product_code":"ims", + "code":"105", + "des":"128There is no limit.No.No.Yes. After sharing an image with other tenants, you can still use the image to create an ECS and use the created ECS to create a private image.", + "doc_type":"usermanual", + "kw":"Image Sharing FAQs,Image Sharing,User Guide", + "title":"Image Sharing FAQs", + "githuburl":"" + }, + { + "uri":"en-us_topic_0037352060.html", + "product_code":"ims", + "code":"106", + "des":"Cause 1: Some images cannot be shared in any cases (the Share button in the Operation column for these images is unavailable), such as:Encrypted imagesFull-ECS images cre", + "doc_type":"usermanual", + "kw":"What Do I Do If I Cannot Share My Images?,Image Sharing,User Guide", + "title":"What Do I Do If I Cannot Share My Images?", + "githuburl":"" + }, + { + "uri":"en-us_topic_0133773782.html", + "product_code":"ims", + "code":"107", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"usermanual", + "kw":"OS", + "title":"OS", + "githuburl":"" + }, + { + "uri":"en-us_topic_0113533721.html", + "product_code":"ims", + "code":"108", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"usermanual", + "kw":"How Is BIOS Different from UEFI?,OS,User Guide", + "title":"How Is BIOS Different from UEFI?", + "githuburl":"" + }, + { + "uri":"en-us_topic_0093842586.html", + "product_code":"ims", + "code":"109", + "des":"The target ECS has had an EIP bound.You have obtained the driver installation package required for an OS. For details, see Table 1.The procedure for installing the NVIDIA", + "doc_type":"usermanual", + "kw":"How Do I Install the NVIDIA Driver on a P1 ECS?,OS,User Guide", + "title":"How Do I Install the NVIDIA Driver on a P1 ECS?", + "githuburl":"" + }, + { + "uri":"en-us_topic_0106312064.html", + "product_code":"ims", + "code":"110", + "des":"Press Win+R. In the displayed dialog box, enter regedit and press Enter to open the registry editor.Open the following registry key:HKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\", + "doc_type":"usermanual", + "kw":"How Do I Delete Redundant Network Connections from a Windows ECS?,OS,User Guide", + "title":"How Do I Delete Redundant Network Connections from a Windows ECS?", + "githuburl":"" + }, + { + "uri":"en-us_topic_0117142739.html", + "product_code":"ims", + "code":"111", + "des":"If an ECS starts slowly, you can change the default timeout duration to speed up the startup.Log in to the ECS.Run the following command to switch to user root:sudo susud", + "doc_type":"usermanual", + "kw":"What Do I Do If an ECS Starts Slowly?,OS,User Guide", + "title":"What Do I Do If an ECS Starts Slowly?", + "githuburl":"" + }, + { + "uri":"en-us_topic_0081802526.html", + "product_code":"ims", + "code":"112", + "des":"When the 20.4.1 driver package downloaded at Intel website https://downloadcenter.intel.com/search?keyword=Intel++Ethernet+Connections+CD was installed in a Windows 7 64b", + "doc_type":"usermanual", + "kw":"What Do I Do If a Windows 7 ECS Equipped with an Intel 82599 NIC Reports an Error in SR-IOV Scenario", + "title":"What Do I Do If a Windows 7 ECS Equipped with an Intel 82599 NIC Reports an Error in SR-IOV Scenarios?", + "githuburl":"" + }, + { + "uri":"en-us_topic_0030713195.html", + "product_code":"ims", + "code":"113", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"usermanual", + "kw":"Image Importing", + "title":"Image Importing", + "githuburl":"" + }, + { + "uri":"en-us_topic_0030713217.html", + "product_code":"ims", + "code":"114", + "des":"No. Currently, only the VMDK, VHD, RAW, QCOW2, VHDX, QED, VDI, QCOW, ZVHD2, and ZVHD formats are supported.Images of the -flat.vmdk format and image file packages contain", + "doc_type":"usermanual", + "kw":"Can I Use Images in Formats Other Than the Specified Ones?,Image Importing,User Guide", + "title":"Can I Use Images in Formats Other Than the Specified Ones?", + "githuburl":"" + }, + { + "uri":"en-us_topic_0030713216.html", + "product_code":"ims", + "code":"115", + "des":"Before using an ECS or external image file to create a private image, you need to pre-configure the ECS or the source VM of the image file. If you do not perform the pre-", + "doc_type":"usermanual", + "kw":"What Are the Impacts If I Do Not Pre-configure an ECS Used to Create a Private Image?,Image Importin", + "title":"What Are the Impacts If I Do Not Pre-configure an ECS Used to Create a Private Image?", + "githuburl":"" + }, + { + "uri":"en-us_topic_0118990097.html", + "product_code":"ims", + "code":"116", + "des":"Open Virtualization Appliance (OVA) is a single file (with the .ova extension) that archives all the files making up an Open Virtualization Format (OVF). OVF is a folder ", + "doc_type":"usermanual", + "kw":"How Do I Import an OVF or OVA File to the Cloud Platform?,Image Importing,User Guide", + "title":"How Do I Import an OVF or OVA File to the Cloud Platform?", + "githuburl":"" + }, + { + "uri":"en-us_topic_0030713213.html", + "product_code":"ims", + "code":"117", + "des":"If you selected an incorrect OS, ECSs may fail to be created from the private image. If the configured system disk size is less than the one in the image file, image regi", + "doc_type":"usermanual", + "kw":"What Do I Do If I Configured an Incorrect OS or System Disk Size During Private Image Registration U", + "title":"What Do I Do If I Configured an Incorrect OS or System Disk Size During Private Image Registration Using an Image File?", + "githuburl":"" + }, + { + "uri":"en-us_topic_0058841396.html", + "product_code":"ims", + "code":"118", + "des":"The possible causes may be:You have specified a small value.Check the system disk size in the VHD image file. Specify a value no less than this size when you use the VHD ", + "doc_type":"usermanual", + "kw":"What Do I Do If the System Disk Size in a VHD Image File Exceeds the One I Have Specified on the Man", + "title":"What Do I Do If the System Disk Size in a VHD Image File Exceeds the One I Have Specified on the Management Console When I Use This File to Register a Private Image?", + "githuburl":"" + }, + { + "uri":"en-us_topic_0030713222.html", + "product_code":"ims", + "code":"119", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"usermanual", + "kw":"Image Exporting", + "title":"Image Exporting", + "githuburl":"" + }, + { + "uri":"en-us_topic_0249675952.html", + "product_code":"ims", + "code":"120", + "des":"Yes. You can download private images in VMDK, VHD, QCOW2, or ZVHD format as instructed in Exporting an Image.", + "doc_type":"usermanual", + "kw":"Can I Download My Private Images to a Local PC?,Image Exporting,User Guide", + "title":"Can I Download My Private Images to a Local PC?", + "githuburl":"" + }, + { + "uri":"en-us_topic_0030713153.html", + "product_code":"ims", + "code":"121", + "des":"No. The system disk image of an ECS is a VM file that contains a system running environment and does not have an installation boot program. Therefore, it cannot be used o", + "doc_type":"usermanual", + "kw":"Can I Use the System Disk Image of an ECS on a Physical Server After I Export It from the Cloud Plat", + "title":"Can I Use the System Disk Image of an ECS on a Physical Server After I Export It from the Cloud Platform?", + "githuburl":"" + }, + { + "uri":"en-us_topic_0274352601.html", + "product_code":"ims", + "code":"122", + "des":"After a private image is exported to an OBS bucket, the image size in the bucket is different from that displayed in IMS. For example, the size of a private image is 1.04", + "doc_type":"usermanual", + "kw":"Why Is the Image Size in an OBS Bucket Different from That Displayed in IMS?,Image Exporting,User Gu", + "title":"Why Is the Image Size in an OBS Bucket Different from That Displayed in IMS?", + "githuburl":"" + }, + { + "uri":"en-us_topic_0030713186.html", + "product_code":"ims", + "code":"123", + "des":"Currently, you cannot directly download a public image. You can use the public image to create an ECS, use the ECS to create a private image, export the private image to ", + "doc_type":"usermanual", + "kw":"Can I Download a Public Image to My Local PC?,Image Exporting,User Guide", + "title":"Can I Download a Public Image to My Local PC?", + "githuburl":"" + }, + { + "uri":"en-us_topic_0199451475.html", + "product_code":"ims", + "code":"124", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"usermanual", + "kw":"What Are the Differences Between Import/Export and Fast Import/Export?,Image Exporting,User Guide", + "title":"What Are the Differences Between Import/Export and Fast Import/Export?", + "githuburl":"" + }, + { + "uri":"en-us_topic_0199396601.html", + "product_code":"ims", + "code":"125", + "des":"Some images cannot be exported. Therefore, the Export option is not provided for them in the Operation column. The following images cannot be exported:Public imagesFull-E", + "doc_type":"usermanual", + "kw":"What Do I Do If the Export Option Is Unavailable for My Image?,Image Exporting,User Guide", + "title":"What Do I Do If the Export Option Is Unavailable for My Image?", + "githuburl":"" + }, + { + "uri":"en-us_topic_0030713203.html", + "product_code":"ims", + "code":"126", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"usermanual", + "kw":"Image Optimization", + "title":"Image Optimization", + "githuburl":"" + }, + { + "uri":"en-us_topic_0030713214.html", + "product_code":"ims", + "code":"127", + "des":"Installing Guest OS drivers on an ECS improves your experience in using the ECS. In addition, it also ensures high reliability and stability of ECSs.Windows ECSs: Install", + "doc_type":"usermanual", + "kw":"Must I Install Guest OS Drivers on an ECS?,Image Optimization,User Guide", + "title":"Must I Install Guest OS Drivers on an ECS?", + "githuburl":"" + }, + { + "uri":"en-us_topic_0032307025.html", + "product_code":"ims", + "code":"128", + "des":"You are advised to enable automatic configuration when registering a private image using an image file. Then, the system will perform the following operations:Check wheth", + "doc_type":"usermanual", + "kw":"What Will the System Do to an Image File When I Use the File to Register a Private Image?,Image Opti", + "title":"What Will the System Do to an Image File When I Use the File to Register a Private Image?", + "githuburl":"" + }, + { + "uri":"en-us_topic_0040740508.html", + "product_code":"ims", + "code":"129", + "des":"When registering an external image file as a private image, you are advised to perform the preceding operations on the VM where the external image file is located.When re", + "doc_type":"usermanual", + "kw":"How Do I Configure an ECS, BMS, or Image File Before I Use It to Create an Image?,Image Optimization", + "title":"How Do I Configure an ECS, BMS, or Image File Before I Use It to Create an Image?", + "githuburl":"" + }, + { + "uri":"en-us_topic_0030713185.html", + "product_code":"ims", + "code":"130", + "des":"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.The proper running of ", + "doc_type":"usermanual", + "kw":"What Do I Do If a Windows Image File Is Not Pre-Configured When I Use It to Register a Private Image", + "title":"What Do I Do If a Windows Image File Is Not Pre-Configured When I Use It to Register a Private Image?", + "githuburl":"" + }, + { + "uri":"en-us_topic_0030713211.html", + "product_code":"ims", + "code":"131", + "des":"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.The proper running of ", + "doc_type":"usermanual", + "kw":"What Do I Do If a Linux Image File Is Not Pre-Configured When I Use It to Register a Private Image?,", + "title":"What Do I Do If a Linux Image File Is Not Pre-Configured When I Use It to Register a Private Image?", + "githuburl":"" + }, + { + "uri":"en-us_topic_0085214115.html", + "product_code":"ims", + "code":"132", + "des":"With the increase of network I/O bandwidth, a single vCPU cannot meet the requirement of processing NIC interruptions. NIC multi-queue allows multiple vCPUs to process NI", + "doc_type":"usermanual", + "kw":"How Do I Enable NIC Multi-Queue for an Image?,Image Optimization,User Guide", + "title":"How Do I Enable NIC Multi-Queue for an Image?", + "githuburl":"" + }, + { + "uri":"en-us_topic_0187108863.html", + "product_code":"ims", + "code":"133", + "des":"Fast Create greatly reduces the time required for creating ECSs from a system disk image. Currently, this feature is supported by all newly created system disk images by ", + "doc_type":"usermanual", + "kw":"How Do I Make a System Disk Image Support Fast ECS Creation?,Image Optimization,User Guide", + "title":"How Do I Make a System Disk Image Support Fast ECS Creation?", + "githuburl":"" + }, + { + "uri":"en-us_topic_0030713215.html", + "product_code":"ims", + "code":"134", + "des":"Possible causes:Your image file was exported from a VMware VM, and VMware Tools was not uninstalled or not completely uninstalled.You have downloaded the Guest OS driver ", + "doc_type":"usermanual", + "kw":"What Is the Cause of the Failure to Install a Guest OS Driver on a Windows ECS?,Image Optimization,U", + "title":"What Is the Cause of the Failure to Install a Guest OS Driver on a Windows ECS?", + "githuburl":"" + }, + { + "uri":"en-us_topic_0086020894.html", + "product_code":"ims", + "code":"135", + "des":"When optimizing a Linux private image, you need to install native Xen and KVM drivers for the image.If you do not install Xen drivers for the image, the network performan", + "doc_type":"usermanual", + "kw":"native Xen and KVM drivers,How Do I Install Native Xen and KVM Drivers?,Image Optimization,User Guid", + "title":"How Do I Install Native Xen and KVM Drivers?", + "githuburl":"" + }, + { + "uri":"en-us_topic_0049196765.html", + "product_code":"ims", + "code":"136", + "des":"If you want to store an unencrypted image in an encrypted way, you can select an encryption key when you replicate the image. Then, the system will generate an encrypted ", + "doc_type":"usermanual", + "kw":"Image Encryption,FAQs,User Guide", + "title":"Image Encryption", + "githuburl":"" + }, + { + "uri":"en-us_topic_0138479468.html", + "product_code":"ims", + "code":"137", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"usermanual", + "kw":"Cloud-Init", + "title":"Cloud-Init", + "githuburl":"" + }, + { + "uri":"en-us_topic_0148873774.html", + "product_code":"ims", + "code":"138", + "des":"Cloud-Init is an open-source tool for cloud instance initialization. When creating ECSs from an image with Cloud-Init, you can use user data injection to inject customize", + "doc_type":"usermanual", + "kw":"What Can I Do with a Cloud-Init ECS?,Cloud-Init,User Guide", + "title":"What Can I Do with a Cloud-Init ECS?", + "githuburl":"" + }, + { + "uri":"en-us_topic_0113992021.html", + "product_code":"ims", + "code":"139", + "des":"A major cause is that the version of Cloud-Init is incompatible with that of NetworkManager. In Debian 9.0 and later versions, NetworkManager is incompatible with Cloud-I", + "doc_type":"usermanual", + "kw":"What Do I Do If Injecting the Key or Password Using Cloud-Init Failed After NetworkManager Is Instal", + "title":"What Do I Do If Injecting the Key or Password Using Cloud-Init Failed After NetworkManager Is Installed?", + "githuburl":"" + }, + { + "uri":"en-us_topic_0078454810.html", + "product_code":"ims", + "code":"140", + "des":"growpart for SUSE and openSUSE is an independent toolkit that does not start with cloud-*. Perform operations in this section to install growpart.Run the following comman", + "doc_type":"usermanual", + "kw":"How Do I Install growpart for SUSE 11 SP4?,Cloud-Init,User Guide", + "title":"How Do I Install growpart for SUSE 11 SP4?", + "githuburl":"" + }, + { + "uri":"en-us_topic_0076880304.html", + "product_code":"ims", + "code":"141", + "des":"An image whose root partition file system is xfs cannot automatically expand its partitions.An image that has the LVM partition cannot automatically expand its partitions", + "doc_type":"usermanual", + "kw":"How Do I Configure a Linux Private Image to Make It Automatically Expand Its Root Partition?,Cloud-I", + "title":"How Do I Configure a Linux Private Image to Make It Automatically Expand Its Root Partition?", + "githuburl":"" + }, + { + "uri":"en-us_topic_0030713220.html", + "product_code":"ims", + "code":"142", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"usermanual", + "kw":"ECS Creation", + "title":"ECS Creation", + "githuburl":"" + }, + { + "uri":"en-us_topic_0030713209.html", + "product_code":"ims", + "code":"143", + "des":"Yes. You can specify the CPU, memory, bandwidth, data disks of the new ECSs if necessary. You can also specify their system disk size. The value must be smaller than 1024", + "doc_type":"usermanual", + "kw":"Can I Use a Private Image to Create ECSs with Different Hardware Specifications from the ECS Used to", + "title":"Can I Use a Private Image to Create ECSs with Different Hardware Specifications from the ECS Used to Create the Private Image?", + "githuburl":"" + }, + { + "uri":"en-us_topic_0030713221.html", + "product_code":"ims", + "code":"144", + "des":"Yes. However, the value must be smaller than 30,768 GB but no less than the system disk size in the image.Ensure that your ECS OS supports the system disk size you specif", + "doc_type":"usermanual", + "kw":"Can I Specify the System Disk Size When I Create an ECS Using an Image?,ECS Creation,User Guide", + "title":"Can I Specify the System Disk Size When I Create an ECS Using an Image?", + "githuburl":"" + }, + { + "uri":"en-us_topic_0034220644.html", + "product_code":"ims", + "code":"145", + "des":"This may be caused by a disk partition ID change after the cross-platform image import. As a result, no partition can be found based on the original disk partition ID in ", + "doc_type":"usermanual", + "kw":"What Do I Do If No Partition Is Found During the Startup of an ECS Created from an Imported Private ", + "title":"What Do I Do If No Partition Is Found During the Startup of an ECS Created from an Imported Private Image?", + "githuburl":"" + }, + { + "uri":"en-us_topic_0030713219.html", + "product_code":"ims", + "code":"146", + "des":"Generally, this is because the xen-blkfront.ko module is not loaded during the startup. You need to modify OS kernel startup parameters. Figure 1 shows the startup screen", + "doc_type":"usermanual", + "kw":"What Do I Do If the Disks of an ECS Created from a CentOS Image Cannot Be Found?,ECS Creation,User G", + "title":"What Do I Do If the Disks of an ECS Created from a CentOS Image Cannot Be Found?", + "githuburl":"" + }, + { + "uri":"en-us_topic_0113403127.html", + "product_code":"ims", + "code":"147", + "des":"This issue is probably caused by the failure of offline VirtIO driver injection.When you inject the VirtIO driver for a Windows ECS offline, there are some restrictions:I", + "doc_type":"usermanual", + "kw":"What Do I Do If an ECS Created from a Windows Image Failed to Start When I Have Enabled Automatic Co", + "title":"What Do I Do If an ECS Created from a Windows Image Failed to Start When I Have Enabled Automatic Configuration During Image Registration?", + "githuburl":"" + }, + { + "uri":"en-us_topic_0161870891.html", + "product_code":"ims", + "code":"148", + "des":"An ECS created from a private image using the UEFI boot mode cannot start.The image OS uses the UEFI boot mode, but the uefi attribute is not added to the image.Delete th", + "doc_type":"usermanual", + "kw":"What Do I Do If an Exception Occurs When I Start an ECS Created from an Image Using the UEFI Boot Mo", + "title":"What Do I Do If an Exception Occurs When I Start an ECS Created from an Image Using the UEFI Boot Mode?", + "githuburl":"" + }, + { + "uri":"en-us_topic_0041178787.html", + "product_code":"ims", + "code":"149", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"usermanual", + "kw":"Change History,User Guide", + "title":"Change History", + "githuburl":"" + }, + { + "uri":"en-us_topic_0047898081.html", + "product_code":"ims", + "code":"150", + "des":"For details about the terms involved in this document, see Glossary.", + "doc_type":"usermanual", + "kw":"Glossary,User Guide", + "title":"Glossary", + "githuburl":"" + } +] \ No newline at end of file diff --git a/docs/ims/umn/CLASS.TXT.json b/docs/ims/umn/CLASS.TXT.json index 60fb2bebd..67d3e5d5f 100644 --- a/docs/ims/umn/CLASS.TXT.json +++ b/docs/ims/umn/CLASS.TXT.json @@ -1,11 +1,1352 @@ [ - { - "desc":"Demo", - "product_code":"ims", - "title":"Overview", - "uri":"index.html", - "doc_type":"usermanual", - "p_code":"", - "code":"1" - } -] + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"ims", + "title":"Overview", + "uri":"en-us_topic_0013901623.html", + "doc_type":"usermanual", + "p_code":"", + "code":"1" + }, + { + "desc":"An image is a server or disk template that contains an operating system (OS) or service data and necessary software, such as database software. IMS provides public, priva", + "product_code":"ims", + "title":"What Is Image Management Service?", + "uri":"en-us_topic_0013901609.html", + "doc_type":"usermanual", + "p_code":"1", + "code":"2" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"ims", + "title":"Supported OSs", + "uri":"en-us_topic_0030713146.html", + "doc_type":"usermanual", + "p_code":"1", + "code":"3" + }, + { + "desc":"This section describes the OSs supported by different types of ECSs.Table 1 lists the OSs supported by the following ECSs:General-purpose T6General computing S2, S3, S6, ", + "product_code":"ims", + "title":"OSs Supported by Different Types of ECSs", + "uri":"en-us_topic_0030713142.html", + "doc_type":"usermanual", + "p_code":"3", + "code":"4" + }, + { + "desc":"Image files in VMDK, VHD, QCOW2, RAW, VHDX, QED, VDI, QCOW, ZVHD2, or ZVHD format can be used to create private images. Select whichever format best meeting your requirem", + "product_code":"ims", + "title":"External Image File Formats and Supported OSs", + "uri":"en-us_topic_0030713143.html", + "doc_type":"usermanual", + "p_code":"3", + "code":"5" + }, + { + "desc":"The ECS boot mode can be BIOS or UEFI. For details about the differences between the two modes, see How Is BIOS Different from UEFI?Table 1 lists the OSs that support the", + "product_code":"ims", + "title":"OSs Supporting UEFI Boot Mode", + "uri":"en-us_topic_0170853315.html", + "doc_type":"usermanual", + "p_code":"3", + "code":"6" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"ims", + "title":"Basic Concepts", + "uri":"en-us_topic_0194137262.html", + "doc_type":"usermanual", + "p_code":"1", + "code":"7" + }, + { + "desc":"A region and availability zone (AZ) identify the location of a data center. You can create resources in a specific region and AZ.A region is a physical data center, which", + "product_code":"ims", + "title":"Region and AZ", + "uri":"en-us_topic_0171754221.html", + "doc_type":"usermanual", + "p_code":"7", + "code":"8" + }, + { + "desc":"IMS supports multiple image formats, but the system uses ZVHD or ZVHD2 by default.Table 1 lists the common image formats.", + "product_code":"ims", + "title":"Common Image Formats", + "uri":"en-us_topic_0089615820.html", + "doc_type":"usermanual", + "p_code":"7", + "code":"9" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"ims", + "title":"Related Services", + "uri":"en-us_topic_0030713148.html", + "doc_type":"usermanual", + "p_code":"1", + "code":"10" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"ims", + "title":"Creating a Private Image", + "uri":"en-us_topic_0130878289.html", + "doc_type":"usermanual", + "p_code":"", + "code":"11" + }, + { + "desc":"A private image is an image available only to the user who created it. It contains an OS, preinstalled public applications, and a user's personal applications. A private ", + "product_code":"ims", + "title":"Introduction", + "uri":"en-us_topic_0013901628.html", + "doc_type":"usermanual", + "p_code":"11", + "code":"12" + }, + { + "desc":"If you have created and configured a Windows ECS based on your service requirements (for example, by installing software and setting up an application environment), you c", + "product_code":"ims", + "title":"Creating a System Disk Image from a Windows ECS", + "uri":"en-us_topic_0030713149.html", + "doc_type":"usermanual", + "p_code":"11", + "code":"13" + }, + { + "desc":"If you have created and configured a Linux ECS based on your service requirements (for example, by installing software and setting up an application environment), you can", + "product_code":"ims", + "title":"Creating a System Disk Image from a Linux ECS", + "uri":"en-us_topic_0030713180.html", + "doc_type":"usermanual", + "p_code":"11", + "code":"14" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"ims", + "title":"Creating a Windows System Disk Image from an External Image File", + "uri":"en-us_topic_0030713181.html", + "doc_type":"usermanual", + "p_code":"11", + "code":"15" + }, + { + "desc":"You can import a local image or a system disk image from another cloud platform to the current cloud. After an image is imported, you can use it to create ECSs or reinsta", + "product_code":"ims", + "title":"Overview", + "uri":"en-us_topic_0030713182.html", + "doc_type":"usermanual", + "p_code":"15", + "code":"16" + }, + { + "desc":"You need to prepare an image file that meets the platform requirements.You are advised to complete the network, tool, and driver configurations in Table 1 on the ECS and ", + "product_code":"ims", + "title":"Preparing an Image File", + "uri":"en-us_topic_0030713189.html", + "doc_type":"usermanual", + "p_code":"15", + "code":"17" + }, + { + "desc":"You are advised to use OBS Browser to upload external image files to OBS buckets. For details, see Object Storage Service User Guide.Only unencrypted external image files", + "product_code":"ims", + "title":"Uploading an External Image File", + "uri":"en-us_topic_0030713183.html", + "doc_type":"usermanual", + "p_code":"15", + "code":"18" + }, + { + "desc":"Register an image file uploaded to the OBS bucket as a private image.Log in to the management console.Under Compute, click Image Management Service.The IMS console is dis", + "product_code":"ims", + "title":"Registering an External Image File as a Private Image", + "uri":"en-us_topic_0030713184.html", + "doc_type":"usermanual", + "p_code":"15", + "code":"19" + }, + { + "desc":"After registering an external image file as a private image on the cloud platform, you can use the image to create ECSs or change the OSs of existing ECSs.This section de", + "product_code":"ims", + "title":"Creating a Windows ECS from an Image", + "uri":"en-us_topic_0030713188.html", + "doc_type":"usermanual", + "p_code":"15", + "code":"20" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"ims", + "title":"Creating a Linux System Disk Image from an External Image File", + "uri":"en-us_topic_0030713190.html", + "doc_type":"usermanual", + "p_code":"11", + "code":"21" + }, + { + "desc":"You can import a local image or a system disk image from another cloud platform to the current cloud. After an image is imported, you can use it to create ECSs or reinsta", + "product_code":"ims", + "title":"Overview", + "uri":"en-us_topic_0030713191.html", + "doc_type":"usermanual", + "p_code":"21", + "code":"22" + }, + { + "desc":"You need to prepare an image file that meets the platform requirements.You are advised to complete the file system, network, and driver configurations in Table 1 on the V", + "product_code":"ims", + "title":"Preparing an Image File", + "uri":"en-us_topic_0030713198.html", + "doc_type":"usermanual", + "p_code":"21", + "code":"23" + }, + { + "desc":"You are advised to use OBS Browser to upload external image files to OBS buckets. For details, see Object Storage Service User Guide.Only unencrypted external image files", + "product_code":"ims", + "title":"Uploading an External Image File", + "uri":"en-us_topic_0030713192.html", + "doc_type":"usermanual", + "p_code":"21", + "code":"24" + }, + { + "desc":"Register an image file uploaded to the OBS bucket as a private image.Log in to the management console.Under Compute, click Image Management Service.The IMS console is dis", + "product_code":"ims", + "title":"Registering an External Image File as a Private Image", + "uri":"en-us_topic_0030713193.html", + "doc_type":"usermanual", + "p_code":"21", + "code":"25" + }, + { + "desc":"After registering an external image file as a private image on the cloud platform, you can use the image to create ECSs or change the OSs of existing ECSs.This section de", + "product_code":"ims", + "title":"Creating a Linux ECS from an Image", + "uri":"en-us_topic_0030713197.html", + "doc_type":"usermanual", + "p_code":"21", + "code":"26" + }, + { + "desc":"For how to create a BMS private image, see Bare Metal Server User Guide.", + "product_code":"ims", + "title":"Creating a BMS System Disk Image", + "uri":"en-us_topic_0095084510.html", + "doc_type":"usermanual", + "p_code":"11", + "code":"27" + }, + { + "desc":"A data disk image contains only service data. You can create a data disk image from an ECS and then use the image to create new EVS disks. This is a convenient way to mig", + "product_code":"ims", + "title":"Creating a Data Disk Image from an ECS", + "uri":"en-us_topic_0102644450.html", + "doc_type":"usermanual", + "p_code":"11", + "code":"28" + }, + { + "desc":"A data disk image contains only service data. You can create a data disk image using a local image file or an external image file (image file on another cloud platform). ", + "product_code":"ims", + "title":"Creating a Data Disk Image from an External Image File", + "uri":"en-us_topic_0084064672.html", + "doc_type":"usermanual", + "p_code":"11", + "code":"29" + }, + { + "desc":"You can create an image of an entire ECS, including not just the OS, but also the software and all the service data. You can then use this image to migrate data by quickl", + "product_code":"ims", + "title":"Creating a Full-ECS Image from an ECS", + "uri":"en-us_topic_0116125142.html", + "doc_type":"usermanual", + "p_code":"11", + "code":"30" + }, + { + "desc":"Create a full-ECS image from a CSBS backup. This image can then be used to create ECSs.When creating a full-ECS image from a CSBS backup, ensure that the source ECS of th", + "product_code":"ims", + "title":"Creating a Full-ECS Image from a CSBS Backup", + "uri":"en-us_topic_0093344231.html", + "doc_type":"usermanual", + "p_code":"11", + "code":"31" + }, + { + "desc":"You can use a Cloud Backup and Recovery (CBR) backup to create a full-ECS image, which can be used to create ECSs.The Cloud Backup and Recovery (CBR) service provides bac", + "product_code":"ims", + "title":"Creating a Full-ECS Image from a CBR Backup", + "uri":"en-us_topic_0176812699.html", + "doc_type":"usermanual", + "p_code":"11", + "code":"32" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"ims", + "title":"Quickly Importing an Image File", + "uri":"en-us_topic_0030713151.html", + "doc_type":"usermanual", + "p_code":"11", + "code":"33" + }, + { + "desc":"If an image file is larger than 128 GB, you can import it using fast import. Only the RAW and ZVHD2 formats support fast import. The image file to be imported cannot exce", + "product_code":"ims", + "title":"Overview", + "uri":"en-us_topic_0133773658.html", + "doc_type":"usermanual", + "p_code":"33", + "code":"34" + }, + { + "desc":"This section describes how to convert the format of an image file on a Linux server and then quickly import it to the cloud platform. You are advised to use an EulerOS EC", + "product_code":"ims", + "title":"Quickly Importing an Image File (Linux)", + "uri":"en-us_topic_0133773660.html", + "doc_type":"usermanual", + "p_code":"33", + "code":"35" + }, + { + "desc":"This section describes how to convert the format of an image file on a Windows server and then quickly import it to the cloud platform. You are advised to use a local Win", + "product_code":"ims", + "title":"Quickly Importing an Image File (Windows)", + "uri":"en-us_topic_0174703579.html", + "doc_type":"usermanual", + "p_code":"33", + "code":"36" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"ims", + "title":"Managing Private Images", + "uri":"en-us_topic_0013901608.html", + "doc_type":"usermanual", + "p_code":"", + "code":"37" + }, + { + "desc":"You can modify the following attributes of a private image:NameDescriptionMinimum MemoryMaximum MemoryNIC Multi-QueueNIC multi-queue enables multiple CPUs to process NIC ", + "product_code":"ims", + "title":"Modifying an Image", + "uri":"en-us_topic_0030713199.html", + "doc_type":"usermanual", + "p_code":"37", + "code":"38" + }, + { + "desc":"You can export the public or private image list in the current region as a CSV file to your local PC.For public images, the file describes the image name, image status, O", + "product_code":"ims", + "title":"Exporting Image List", + "uri":"en-us_topic_0090099339.html", + "doc_type":"usermanual", + "p_code":"37", + "code":"39" + }, + { + "desc":"You can check the disk capacity of a private image.To check the disk capacity of a system disk image, data disk image, or ISO image, see Check the Disk Capacity of a Syst", + "product_code":"ims", + "title":"Checking the Disk Capacity of an Image", + "uri":"en-us_topic_0300978092.html", + "doc_type":"usermanual", + "p_code":"37", + "code":"40" + }, + { + "desc":"You can use a public, private, or shared image to create an ECS.If you use a public image, the created ECS contains an OS and pre-installed public applications. You need ", + "product_code":"ims", + "title":"Creating an ECS from an Image", + "uri":"en-us_topic_0030713200.html", + "doc_type":"usermanual", + "p_code":"37", + "code":"41" + }, + { + "desc":"You can delete private images that will no longer be used.Access the IMS console.Log in to the management console.Under Compute, click Image Management Service.The IMS co", + "product_code":"ims", + "title":"Deleting Images", + "uri":"en-us_topic_0030713201.html", + "doc_type":"usermanual", + "p_code":"37", + "code":"42" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"ims", + "title":"Sharing Images", + "uri":"en-us_topic_0032042416.html", + "doc_type":"usermanual", + "p_code":"37", + "code":"43" + }, + { + "desc":"You can share your private images with other tenants. The tenants who accept the shared images can use the images to create ECSs of the same specifications.You can share ", + "product_code":"ims", + "title":"Overview", + "uri":"en-us_topic_0032042417.html", + "doc_type":"usermanual", + "p_code":"43", + "code":"44" + }, + { + "desc":"Before a tenant shares an image with you, you need to provide your project ID.Access the IMS console.Log in to the management console.Under Compute, click Image Managemen", + "product_code":"ims", + "title":"Obtaining the Project ID", + "uri":"en-us_topic_0032042418.html", + "doc_type":"usermanual", + "p_code":"43", + "code":"45" + }, + { + "desc":"After obtaining the project ID from a tenant, you can share specified private images with the tenant. You can share a single image or multiple images as needed.You have o", + "product_code":"ims", + "title":"Sharing Specified Images", + "uri":"en-us_topic_0032042419.html", + "doc_type":"usermanual", + "p_code":"43", + "code":"46" + }, + { + "desc":"After another tenant shares images with you, you will receive a message. You can choose to accept or reject all or some of the shared images.If you are not in the same re", + "product_code":"ims", + "title":"Accepting or Rejecting Shared Images", + "uri":"en-us_topic_0032042420.html", + "doc_type":"usermanual", + "p_code":"43", + "code":"47" + }, + { + "desc":"You can reject accepted images if you no longer need them.After an image is rejected, it will not be displayed on the Images Shared with Me page.You have accepted images ", + "product_code":"ims", + "title":"Rejecting Accepted Images", + "uri":"en-us_topic_0032042421.html", + "doc_type":"usermanual", + "p_code":"43", + "code":"48" + }, + { + "desc":"If you want to use the shared images you have rejected, you can accept them from the list of rejected images.You have rejected the images shared by others.The image owner", + "product_code":"ims", + "title":"Accepting Rejected Images", + "uri":"en-us_topic_0075730699.html", + "doc_type":"usermanual", + "p_code":"43", + "code":"49" + }, + { + "desc":"You can stop sharing images. After you stop sharing an image:The image will be invisible to the recipient on the management console and no data will be returned when the ", + "product_code":"ims", + "title":"Stopping Sharing Images", + "uri":"en-us_topic_0032042422.html", + "doc_type":"usermanual", + "p_code":"43", + "code":"50" + }, + { + "desc":"In addition to the tenants you have shared images with, you can add more tenants who can use the shared images.You have shared private images.You have obtained the projec", + "product_code":"ims", + "title":"Adding Tenants Who Can Use Shared Images", + "uri":"en-us_topic_0032042423.html", + "doc_type":"usermanual", + "p_code":"43", + "code":"51" + }, + { + "desc":"This section describes how to delete image recipients who can use shared images.You have shared private images.You have obtained project IDs of the image recipients.Acces", + "product_code":"ims", + "title":"Deleting Image Recipients Who Can Use Shared Images", + "uri":"en-us_topic_0032087324.html", + "doc_type":"usermanual", + "p_code":"43", + "code":"52" + }, + { + "desc":"IMS provides multiple methods for importing images. You can select a method based on the image file type, format, or size.To import a data disk image file, follow the ins", + "product_code":"ims", + "title":"Importing an Image", + "uri":"en-us_topic_0000001175697174.html", + "doc_type":"usermanual", + "p_code":"37", + "code":"53" + }, + { + "desc":"You can export a private image to a standard OBS bucket and then download it to your local PC.You can reproduce cloud servers and their running environments in on-promise", + "product_code":"ims", + "title":"Exporting an Image", + "uri":"en-us_topic_0034011241.html", + "doc_type":"usermanual", + "p_code":"37", + "code":"54" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"ims", + "title":"Optimizing a Windows Private Image", + "uri":"en-us_topic_0130878748.html", + "doc_type":"usermanual", + "p_code":"37", + "code":"55" + }, + { + "desc":"ECSs require Xen Guest OS driver (PV driver) and KVM Guest OS driver (UVP VMTools) for proper running. To ensure that ECSs support both Xen and KVM and to improve network", + "product_code":"ims", + "title":"Optimization Process", + "uri":"en-us_topic_0047501112.html", + "doc_type":"usermanual", + "p_code":"55", + "code":"56" + }, + { + "desc":"Open the cmd window and run the following command to query the virtualization type of the ECS:systeminfoIf the values of System Manufacturer and BIOS Version are Xen, the", + "product_code":"ims", + "title":"Viewing the Virtualization Type of a Windows ECS", + "uri":"en-us_topic_0125075471.html", + "doc_type":"usermanual", + "p_code":"55", + "code":"57" + }, + { + "desc":"Table 1 lists the PV driver software packages required for optimizing Windows private images.Table 2 lists the UVP VMTools software packages required for optimizing Windo", + "product_code":"ims", + "title":"Obtaining Required Software Packages", + "uri":"en-us_topic_0037352059.html", + "doc_type":"usermanual", + "p_code":"55", + "code":"58" + }, + { + "desc":"When using an ECS or external image file to create a private image, ensure that the PV driver has been installed in the OS to enable Xen virtualization for subsequently c", + "product_code":"ims", + "title":"Installing the PV Driver", + "uri":"en-us_topic_0037352182.html", + "doc_type":"usermanual", + "p_code":"55", + "code":"59" + }, + { + "desc":"Before using an ECS or external image file to create a private image, ensure that UVP VMTools has been installed in the OS to enable subsequently created ECSs to support ", + "product_code":"ims", + "title":"Installing UVP VMTools", + "uri":"en-us_topic_0037352061.html", + "doc_type":"usermanual", + "p_code":"55", + "code":"60" + }, + { + "desc":"After installing the PV driver and UVP VMTools, perform the following operations to clear system logs:For Windows Server 2008 and Windows Server 2012, right-click Compute", + "product_code":"ims", + "title":"Clearing System Logs", + "uri":"en-us_topic_0125075472.html", + "doc_type":"usermanual", + "p_code":"55", + "code":"61" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"ims", + "title":"Optimizing a Linux Private Image", + "uri":"en-us_topic_0130878749.html", + "doc_type":"usermanual", + "p_code":"37", + "code":"62" + }, + { + "desc":"A Linux ECS can be switched from Xen to KVM if xen-pv and VirtIO drivers run on the ECS. Before changing a Xen-based ECS to a KVM-based ECS, ensure that the required driv", + "product_code":"ims", + "title":"Optimization Process", + "uri":"en-us_topic_0047501133.html", + "doc_type":"usermanual", + "p_code":"62", + "code":"63" + }, + { + "desc":"You can run the following command to query the virtualization type of an ECS:lscpuIf the value of Hypervisor vendor is Xen, the ECS uses Xen. If KVM is required, perform ", + "product_code":"ims", + "title":"Viewing the Virtualization Type of a Linux ECS", + "uri":"en-us_topic_0037352185.html", + "doc_type":"usermanual", + "p_code":"62", + "code":"64" + }, + { + "desc":"When optimizing a Linux private image, you need to change the UUID in the fstab and GRUB configuration files, and install native Xen and KVM drivers on the ECS. To ensure", + "product_code":"ims", + "title":"Uninstalling the PV Driver from a Linux ECS", + "uri":"en-us_topic_0037352186.html", + "doc_type":"usermanual", + "p_code":"62", + "code":"65" + }, + { + "desc":"When optimizing a Linux private image, you need to change the disk identifier to UUID in the GRUB configuration file of the ECS.Modify the menu.lst or grub.cfg configurat", + "product_code":"ims", + "title":"Changing the Disk Identifier in the GRUB Configuration File to UUID", + "uri":"en-us_topic_0086020895.html", + "doc_type":"usermanual", + "p_code":"62", + "code":"66" + }, + { + "desc":"When optimizing a Linux private image, you need to change the disk identifier to UUID in the fstab configuration file of the ECS.Take CentOS 7.0 as an example. Run blkid ", + "product_code":"ims", + "title":"Changing the Disk Identifier in the fstab File to UUID", + "uri":"en-us_topic_0086024961.html", + "doc_type":"usermanual", + "p_code":"62", + "code":"67" + }, + { + "desc":"When optimizing a Linux private image, you need to install native KVM drivers on the ECS.If you do not install KVM drivers, NICs of the ECS may not be detected and the EC", + "product_code":"ims", + "title":"Installing Native KVM Drivers", + "uri":"en-us_topic_0000001120952155.html", + "doc_type":"usermanual", + "p_code":"62", + "code":"68" + }, + { + "desc":"Delete log files and historical records, and stop the ECS.Run the following commands to delete redundant key files:echo > /$path/$to/$root/.ssh/authorized_keysAn example ", + "product_code":"ims", + "title":"Clearing System Logs", + "uri":"en-us_topic_0125076462.html", + "doc_type":"usermanual", + "p_code":"62", + "code":"69" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"ims", + "title":"Encrypting Images", + "uri":"en-us_topic_0046588153.html", + "doc_type":"usermanual", + "p_code":"37", + "code":"70" + }, + { + "desc":"IMS allows you to create encrypted images to ensure data security.To use the image encryption function, you must apply for KMS Administrator permissions.KMS must be enabl", + "product_code":"ims", + "title":"Overview", + "uri":"en-us_topic_0046588154.html", + "doc_type":"usermanual", + "p_code":"70", + "code":"71" + }, + { + "desc":"You can create an encrypted image using an external image file or an encrypted ECS.Create an encrypted image using an external image file.When you register the external i", + "product_code":"ims", + "title":"Creating Encrypted Images", + "uri":"en-us_topic_0046588155.html", + "doc_type":"usermanual", + "p_code":"70", + "code":"72" + }, + { + "desc":"You can convert encrypted and unencrypted images into each other or enable some advanced features (such as fast ECS creation from an image) using the image replication fu", + "product_code":"ims", + "title":"Replicating Images", + "uri":"en-us_topic_0049177180.html", + "doc_type":"usermanual", + "p_code":"37", + "code":"73" + }, + { + "desc":"You can use tags to classify images. You can add, modify, or delete image tags, or search for required images by tag in the image list.When adding predefined tags to an i", + "product_code":"ims", + "title":"Tagging an Image", + "uri":"en-us_topic_0068002265.html", + "doc_type":"usermanual", + "p_code":"37", + "code":"74" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"ims", + "title":"Auditing Key Operations", + "uri":"en-us_topic_0107462580.html", + "doc_type":"usermanual", + "p_code":"37", + "code":"75" + }, + { + "desc":"Cloud Trace Service (CTS) is a log audit service provided by the public cloud and intended for cloud security. It allows you to collect, store, and query cloud resource o", + "product_code":"ims", + "title":"IMS Operations Recorded by CTS", + "uri":"en-us_topic_0107462581.html", + "doc_type":"usermanual", + "p_code":"75", + "code":"76" + }, + { + "desc":"Once CTS is enabled, it starts recording IMS operations. You can view operations recorded in the last seven days on the CTS management console.This section describes how ", + "product_code":"ims", + "title":"Viewing Traces", + "uri":"en-us_topic_0107462582.html", + "doc_type":"usermanual", + "p_code":"75", + "code":"77" + }, + { + "desc":"You can import an image file in VHD, VMDK, QCOW2, RAW, VHDX, QCOW, VDI, QED, ZVHD, or ZVHD2 format to the cloud platform. Image files in other formats need to be converte", + "product_code":"ims", + "title":"Converting the Image Format Using qemu-img", + "uri":"en-us_topic_0117262219.html", + "doc_type":"usermanual", + "p_code":"37", + "code":"78" + }, + { + "desc":"You can import an image file in VHD, VMDK, QCOW2, RAW, VHDX, QCOW, VDI, QED, ZVHD, or ZVHD2 format to the cloud platform. Image files in other formats need to be converte", + "product_code":"ims", + "title":"Converting the Image Format Using qemu-img-hw", + "uri":"en-us_topic_0171668652.html", + "doc_type":"usermanual", + "p_code":"37", + "code":"79" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"ims", + "title":"Windows Operations", + "uri":"en-us_topic_0199394934.html", + "doc_type":"usermanual", + "p_code":"", + "code":"80" + }, + { + "desc":"If a private image is created from an ECS or external image file and the VM where the ECS or external image file is located is configured with a static IP address, you ne", + "product_code":"ims", + "title":"Setting the NIC to DHCP", + "uri":"en-us_topic_0030713152.html", + "doc_type":"usermanual", + "p_code":"80", + "code":"81" + }, + { + "desc":"If you want to remotely access an ECS, enable remote desktop connection for the source ECS when creating a private image. This function must be enabled for GPU-accelerate", + "product_code":"ims", + "title":"Enabling Remote Desktop Connection", + "uri":"en-us_topic_0030713155.html", + "doc_type":"usermanual", + "p_code":"80", + "code":"82" + }, + { + "desc":"To ensure that you can use the user data injection function to inject initial custom information into ECSs created from a private image (such as setting the ECS login pas", + "product_code":"ims", + "title":"Installing and Configuring Cloudbase-Init", + "uri":"en-us_topic_0030730602.html", + "doc_type":"usermanual", + "p_code":"80", + "code":"83" + }, + { + "desc":"Running Sysprep ensures that an ECS has a unique SID after it is added to a domain.After installing Cloudbase-Init on an ECS, you need to decide whether the ECS needs to ", + "product_code":"ims", + "title":"Running Sysprep", + "uri":"en-us_topic_0093887081.html", + "doc_type":"usermanual", + "p_code":"80", + "code":"84" + }, + { + "desc":"Before using some types of ECSs to create private images, you need to install special drivers on the ECSs.If you want to use the created private image to create GPU-accel", + "product_code":"ims", + "title":"Installing Special Windows Drivers", + "uri":"en-us_topic_0081795392.html", + "doc_type":"usermanual", + "p_code":"80", + "code":"85" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"ims", + "title":"Linux Operations", + "uri":"en-us_topic_0199394935.html", + "doc_type":"usermanual", + "p_code":"", + "code":"86" + }, + { + "desc":"If a private image is created from an ECS or external image file and the VM where the ECS or external image file is located is configured with a static IP address, you ne", + "product_code":"ims", + "title":"Setting the NIC to DHCP", + "uri":"en-us_topic_0030713176.html", + "doc_type":"usermanual", + "p_code":"86", + "code":"87" + }, + { + "desc":"To prevent NIC name drift when you use a private image to create ECSs, you need to delete files from the network rule directory of the VM where the ECS or image file is l", + "product_code":"ims", + "title":"Deleting Files from the Network Rule Directory", + "uri":"en-us_topic_0069904570.html", + "doc_type":"usermanual", + "p_code":"86", + "code":"88" + }, + { + "desc":"To ensure that you can use the user data injection function to inject initial custom information into ECSs created from a private image (such as setting the ECS login pas", + "product_code":"ims", + "title":"Installing Cloud-Init", + "uri":"en-us_topic_0030730603.html", + "doc_type":"usermanual", + "p_code":"86", + "code":"89" + }, + { + "desc":"You need to configure Cloud-Init after it is installed.Cloud-Init has been installed.An EIP has been bound to the ECS.You have logged in to the ECS.The IP address obtaini", + "product_code":"ims", + "title":"Configuring Cloud-Init", + "uri":"en-us_topic_0122876047.html", + "doc_type":"usermanual", + "p_code":"86", + "code":"90" + }, + { + "desc":"Before using some types of ECSs to create private images, you need to install special drivers on the ECSs.If you want to use the private image to create P1 ECSs, install ", + "product_code":"ims", + "title":"Installing Special Linux Drivers", + "uri":"en-us_topic_0082002007.html", + "doc_type":"usermanual", + "p_code":"86", + "code":"91" + }, + { + "desc":"If multiple data disks are attached to the ECS used to create a private image, ECSs created from the image may be unavailable. Therefore, you need to detach all data disk", + "product_code":"ims", + "title":"Detaching Data Disks from an ECS", + "uri":"en-us_topic_0030713179.html", + "doc_type":"usermanual", + "p_code":"86", + "code":"92" + }, + { + "desc":"If you want to use the ECS console logging function, you need to configure related parameters on the ECS.Currently, ECSs running the following OSs are supported: CentOS 6", + "product_code":"ims", + "title":"Configuring Console Logging", + "uri":"en-us_topic_0057450886.html", + "doc_type":"usermanual", + "p_code":"86", + "code":"93" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"ims", + "title":"FAQs", + "uri":"en-us_topic_0030713202.html", + "doc_type":"usermanual", + "p_code":"", + "code":"94" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"ims", + "title":"Image Consulting", + "uri":"en-us_topic_0138455714.html", + "doc_type":"usermanual", + "p_code":"94", + "code":"95" + }, + { + "desc":"When creating an ECS or BMS, you can select an image based on the following factors:Region and AZImage TypeOSAn image is a regional resource. You cannot use an image to c", + "product_code":"ims", + "title":"How Do I Select an Image?", + "uri":"en-us_topic_0195253327.html", + "doc_type":"usermanual", + "p_code":"95", + "code":"96" + }, + { + "desc":"Quotas can limit the number or amount of resources available to users, such as the maximum number of ECSs or EVS disks that can be created.If the existing resource quota ", + "product_code":"ims", + "title":"How Do I Increase the Image Quota?", + "uri":"en-us_topic_0153114116.html", + "doc_type":"usermanual", + "p_code":"95", + "code":"97" + }, + { + "desc":"Yes.Other tenants can share a private image with you. You can use it after accepting it. For details about image sharing, see Sharing Specified Images.", + "product_code":"ims", + "title":"Can I Use Private Images of Other Tenants?", + "uri":"en-us_topic_0173986473.html", + "doc_type":"usermanual", + "p_code":"95", + "code":"98" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"ims", + "title":"Image Creation", + "uri":"en-us_topic_0193137621.html", + "doc_type":"usermanual", + "p_code":"94", + "code":"99" + }, + { + "desc":"Currently, you can create a maximum of 100 private images under an account in a region.No. You can create an image from a running ECS. However, if data is written to the ", + "product_code":"ims", + "title":"Image Creation FAQs", + "uri":"en-us_topic_0193146244.html", + "doc_type":"usermanual", + "p_code":"99", + "code":"100" + }, + { + "desc":"An ECS used to create a Windows full-ECS image cannot have a spanned volume. If you attempt to create an image from an ECS with a spanned volume, when the image is used t", + "product_code":"ims", + "title":"How Do I Create a Full-ECS Image Using an ECS That Has a Spanned Volume?", + "uri":"en-us_topic_0106444267.html", + "doc_type":"usermanual", + "p_code":"99", + "code":"101" + }, + { + "desc":"For a user that needs to be added to a domain and uses the domain account to log in to Windows, Sysprep is required before a private image is created. Otherwise, the imag", + "product_code":"ims", + "title":"Why Is Sysprep Required for Creating a Private Image from a Windows ECS?", + "uri":"en-us_topic_0030742197.html", + "doc_type":"usermanual", + "p_code":"99", + "code":"102" + }, + { + "desc":"When you create a ZVHD2 image using an API, the image is created in the ZVHD format.Check whether your token contains the op_gated_lld role (op_gated_lld is the OBT tag, ", + "product_code":"ims", + "title":"What Do I Do If I Cannot Create an Image in ZVHD2 Format Using an API?", + "uri":"en-us_topic_0096558549.html", + "doc_type":"usermanual", + "p_code":"99", + "code":"103" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"ims", + "title":"Image Sharing", + "uri":"en-us_topic_0171668653.html", + "doc_type":"usermanual", + "p_code":"94", + "code":"104" + }, + { + "desc":"128There is no limit.No.No.Yes. After sharing an image with other tenants, you can still use the image to create an ECS and use the created ECS to create a private image.", + "product_code":"ims", + "title":"Image Sharing FAQs", + "uri":"en-us_topic_0183293890.html", + "doc_type":"usermanual", + "p_code":"104", + "code":"105" + }, + { + "desc":"Cause 1: Some images cannot be shared in any cases (the Share button in the Operation column for these images is unavailable), such as:Encrypted imagesFull-ECS images cre", + "product_code":"ims", + "title":"What Do I Do If I Cannot Share My Images?", + "uri":"en-us_topic_0037352060.html", + "doc_type":"usermanual", + "p_code":"104", + "code":"106" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"ims", + "title":"OS", + "uri":"en-us_topic_0133773782.html", + "doc_type":"usermanual", + "p_code":"94", + "code":"107" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"ims", + "title":"How Is BIOS Different from UEFI?", + "uri":"en-us_topic_0113533721.html", + "doc_type":"usermanual", + "p_code":"107", + "code":"108" + }, + { + "desc":"The target ECS has had an EIP bound.You have obtained the driver installation package required for an OS. For details, see Table 1.The procedure for installing the NVIDIA", + "product_code":"ims", + "title":"How Do I Install the NVIDIA Driver on a P1 ECS?", + "uri":"en-us_topic_0093842586.html", + "doc_type":"usermanual", + "p_code":"107", + "code":"109" + }, + { + "desc":"Press Win+R. In the displayed dialog box, enter regedit and press Enter to open the registry editor.Open the following registry key:HKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\", + "product_code":"ims", + "title":"How Do I Delete Redundant Network Connections from a Windows ECS?", + "uri":"en-us_topic_0106312064.html", + "doc_type":"usermanual", + "p_code":"107", + "code":"110" + }, + { + "desc":"If an ECS starts slowly, you can change the default timeout duration to speed up the startup.Log in to the ECS.Run the following command to switch to user root:sudo susud", + "product_code":"ims", + "title":"What Do I Do If an ECS Starts Slowly?", + "uri":"en-us_topic_0117142739.html", + "doc_type":"usermanual", + "p_code":"107", + "code":"111" + }, + { + "desc":"When the 20.4.1 driver package downloaded at Intel website https://downloadcenter.intel.com/search?keyword=Intel++Ethernet+Connections+CD was installed in a Windows 7 64b", + "product_code":"ims", + "title":"What Do I Do If a Windows 7 ECS Equipped with an Intel 82599 NIC Reports an Error in SR-IOV Scenarios?", + "uri":"en-us_topic_0081802526.html", + "doc_type":"usermanual", + "p_code":"107", + "code":"112" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"ims", + "title":"Image Importing", + "uri":"en-us_topic_0030713195.html", + "doc_type":"usermanual", + "p_code":"94", + "code":"113" + }, + { + "desc":"No. Currently, only the VMDK, VHD, RAW, QCOW2, VHDX, QED, VDI, QCOW, ZVHD2, and ZVHD formats are supported.Images of the -flat.vmdk format and image file packages contain", + "product_code":"ims", + "title":"Can I Use Images in Formats Other Than the Specified Ones?", + "uri":"en-us_topic_0030713217.html", + "doc_type":"usermanual", + "p_code":"113", + "code":"114" + }, + { + "desc":"Before using an ECS or external image file to create a private image, you need to pre-configure the ECS or the source VM of the image file. If you do not perform the pre-", + "product_code":"ims", + "title":"What Are the Impacts If I Do Not Pre-configure an ECS Used to Create a Private Image?", + "uri":"en-us_topic_0030713216.html", + "doc_type":"usermanual", + "p_code":"113", + "code":"115" + }, + { + "desc":"Open Virtualization Appliance (OVA) is a single file (with the .ova extension) that archives all the files making up an Open Virtualization Format (OVF). OVF is a folder ", + "product_code":"ims", + "title":"How Do I Import an OVF or OVA File to the Cloud Platform?", + "uri":"en-us_topic_0118990097.html", + "doc_type":"usermanual", + "p_code":"113", + "code":"116" + }, + { + "desc":"If you selected an incorrect OS, ECSs may fail to be created from the private image. If the configured system disk size is less than the one in the image file, image regi", + "product_code":"ims", + "title":"What Do I Do If I Configured an Incorrect OS or System Disk Size During Private Image Registration Using an Image File?", + "uri":"en-us_topic_0030713213.html", + "doc_type":"usermanual", + "p_code":"113", + "code":"117" + }, + { + "desc":"The possible causes may be:You have specified a small value.Check the system disk size in the VHD image file. Specify a value no less than this size when you use the VHD ", + "product_code":"ims", + "title":"What Do I Do If the System Disk Size in a VHD Image File Exceeds the One I Have Specified on the Management Console When I Use This File to Register a Private Image?", + "uri":"en-us_topic_0058841396.html", + "doc_type":"usermanual", + "p_code":"113", + "code":"118" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"ims", + "title":"Image Exporting", + "uri":"en-us_topic_0030713222.html", + "doc_type":"usermanual", + "p_code":"94", + "code":"119" + }, + { + "desc":"Yes. You can download private images in VMDK, VHD, QCOW2, or ZVHD format as instructed in Exporting an Image.", + "product_code":"ims", + "title":"Can I Download My Private Images to a Local PC?", + "uri":"en-us_topic_0249675952.html", + "doc_type":"usermanual", + "p_code":"119", + "code":"120" + }, + { + "desc":"No. The system disk image of an ECS is a VM file that contains a system running environment and does not have an installation boot program. Therefore, it cannot be used o", + "product_code":"ims", + "title":"Can I Use the System Disk Image of an ECS on a Physical Server After I Export It from the Cloud Platform?", + "uri":"en-us_topic_0030713153.html", + "doc_type":"usermanual", + "p_code":"119", + "code":"121" + }, + { + "desc":"After a private image is exported to an OBS bucket, the image size in the bucket is different from that displayed in IMS. For example, the size of a private image is 1.04", + "product_code":"ims", + "title":"Why Is the Image Size in an OBS Bucket Different from That Displayed in IMS?", + "uri":"en-us_topic_0274352601.html", + "doc_type":"usermanual", + "p_code":"119", + "code":"122" + }, + { + "desc":"Currently, you cannot directly download a public image. You can use the public image to create an ECS, use the ECS to create a private image, export the private image to ", + "product_code":"ims", + "title":"Can I Download a Public Image to My Local PC?", + "uri":"en-us_topic_0030713186.html", + "doc_type":"usermanual", + "p_code":"119", + "code":"123" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"ims", + "title":"What Are the Differences Between Import/Export and Fast Import/Export?", + "uri":"en-us_topic_0199451475.html", + "doc_type":"usermanual", + "p_code":"119", + "code":"124" + }, + { + "desc":"Some images cannot be exported. Therefore, the Export option is not provided for them in the Operation column. The following images cannot be exported:Public imagesFull-E", + "product_code":"ims", + "title":"What Do I Do If the Export Option Is Unavailable for My Image?", + "uri":"en-us_topic_0199396601.html", + "doc_type":"usermanual", + "p_code":"119", + "code":"125" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"ims", + "title":"Image Optimization", + "uri":"en-us_topic_0030713203.html", + "doc_type":"usermanual", + "p_code":"94", + "code":"126" + }, + { + "desc":"Installing Guest OS drivers on an ECS improves your experience in using the ECS. In addition, it also ensures high reliability and stability of ECSs.Windows ECSs: Install", + "product_code":"ims", + "title":"Must I Install Guest OS Drivers on an ECS?", + "uri":"en-us_topic_0030713214.html", + "doc_type":"usermanual", + "p_code":"126", + "code":"127" + }, + { + "desc":"You are advised to enable automatic configuration when registering a private image using an image file. Then, the system will perform the following operations:Check wheth", + "product_code":"ims", + "title":"What Will the System Do to an Image File When I Use the File to Register a Private Image?", + "uri":"en-us_topic_0032307025.html", + "doc_type":"usermanual", + "p_code":"126", + "code":"128" + }, + { + "desc":"When registering an external image file as a private image, you are advised to perform the preceding operations on the VM where the external image file is located.When re", + "product_code":"ims", + "title":"How Do I Configure an ECS, BMS, or Image File Before I Use It to Create an Image?", + "uri":"en-us_topic_0040740508.html", + "doc_type":"usermanual", + "p_code":"126", + "code":"129" + }, + { + "desc":"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.The proper running of ", + "product_code":"ims", + "title":"What Do I Do If a Windows Image File Is Not Pre-Configured When I Use It to Register a Private Image?", + "uri":"en-us_topic_0030713185.html", + "doc_type":"usermanual", + "p_code":"126", + "code":"130" + }, + { + "desc":"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.The proper running of ", + "product_code":"ims", + "title":"What Do I Do If a Linux Image File Is Not Pre-Configured When I Use It to Register a Private Image?", + "uri":"en-us_topic_0030713211.html", + "doc_type":"usermanual", + "p_code":"126", + "code":"131" + }, + { + "desc":"With the increase of network I/O bandwidth, a single vCPU cannot meet the requirement of processing NIC interruptions. NIC multi-queue allows multiple vCPUs to process NI", + "product_code":"ims", + "title":"How Do I Enable NIC Multi-Queue for an Image?", + "uri":"en-us_topic_0085214115.html", + "doc_type":"usermanual", + "p_code":"126", + "code":"132" + }, + { + "desc":"Fast Create greatly reduces the time required for creating ECSs from a system disk image. Currently, this feature is supported by all newly created system disk images by ", + "product_code":"ims", + "title":"How Do I Make a System Disk Image Support Fast ECS Creation?", + "uri":"en-us_topic_0187108863.html", + "doc_type":"usermanual", + "p_code":"126", + "code":"133" + }, + { + "desc":"Possible causes:Your image file was exported from a VMware VM, and VMware Tools was not uninstalled or not completely uninstalled.You have downloaded the Guest OS driver ", + "product_code":"ims", + "title":"What Is the Cause of the Failure to Install a Guest OS Driver on a Windows ECS?", + "uri":"en-us_topic_0030713215.html", + "doc_type":"usermanual", + "p_code":"126", + "code":"134" + }, + { + "desc":"When optimizing a Linux private image, you need to install native Xen and KVM drivers for the image.If you do not install Xen drivers for the image, the network performan", + "product_code":"ims", + "title":"How Do I Install Native Xen and KVM Drivers?", + "uri":"en-us_topic_0086020894.html", + "doc_type":"usermanual", + "p_code":"126", + "code":"135" + }, + { + "desc":"If you want to store an unencrypted image in an encrypted way, you can select an encryption key when you replicate the image. Then, the system will generate an encrypted ", + "product_code":"ims", + "title":"Image Encryption", + "uri":"en-us_topic_0049196765.html", + "doc_type":"usermanual", + "p_code":"94", + "code":"136" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"ims", + "title":"Cloud-Init", + "uri":"en-us_topic_0138479468.html", + "doc_type":"usermanual", + "p_code":"94", + "code":"137" + }, + { + "desc":"Cloud-Init is an open-source tool for cloud instance initialization. When creating ECSs from an image with Cloud-Init, you can use user data injection to inject customize", + "product_code":"ims", + "title":"What Can I Do with a Cloud-Init ECS?", + "uri":"en-us_topic_0148873774.html", + "doc_type":"usermanual", + "p_code":"137", + "code":"138" + }, + { + "desc":"A major cause is that the version of Cloud-Init is incompatible with that of NetworkManager. In Debian 9.0 and later versions, NetworkManager is incompatible with Cloud-I", + "product_code":"ims", + "title":"What Do I Do If Injecting the Key or Password Using Cloud-Init Failed After NetworkManager Is Installed?", + "uri":"en-us_topic_0113992021.html", + "doc_type":"usermanual", + "p_code":"137", + "code":"139" + }, + { + "desc":"growpart for SUSE and openSUSE is an independent toolkit that does not start with cloud-*. Perform operations in this section to install growpart.Run the following comman", + "product_code":"ims", + "title":"How Do I Install growpart for SUSE 11 SP4?", + "uri":"en-us_topic_0078454810.html", + "doc_type":"usermanual", + "p_code":"137", + "code":"140" + }, + { + "desc":"An image whose root partition file system is xfs cannot automatically expand its partitions.An image that has the LVM partition cannot automatically expand its partitions", + "product_code":"ims", + "title":"How Do I Configure a Linux Private Image to Make It Automatically Expand Its Root Partition?", + "uri":"en-us_topic_0076880304.html", + "doc_type":"usermanual", + "p_code":"137", + "code":"141" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"ims", + "title":"ECS Creation", + "uri":"en-us_topic_0030713220.html", + "doc_type":"usermanual", + "p_code":"94", + "code":"142" + }, + { + "desc":"Yes. You can specify the CPU, memory, bandwidth, data disks of the new ECSs if necessary. You can also specify their system disk size. The value must be smaller than 1024", + "product_code":"ims", + "title":"Can I Use a Private Image to Create ECSs with Different Hardware Specifications from the ECS Used to Create the Private Image?", + "uri":"en-us_topic_0030713209.html", + "doc_type":"usermanual", + "p_code":"142", + "code":"143" + }, + { + "desc":"Yes. However, the value must be smaller than 30,768 GB but no less than the system disk size in the image.Ensure that your ECS OS supports the system disk size you specif", + "product_code":"ims", + "title":"Can I Specify the System Disk Size When I Create an ECS Using an Image?", + "uri":"en-us_topic_0030713221.html", + "doc_type":"usermanual", + "p_code":"142", + "code":"144" + }, + { + "desc":"This may be caused by a disk partition ID change after the cross-platform image import. As a result, no partition can be found based on the original disk partition ID in ", + "product_code":"ims", + "title":"What Do I Do If No Partition Is Found During the Startup of an ECS Created from an Imported Private Image?", + "uri":"en-us_topic_0034220644.html", + "doc_type":"usermanual", + "p_code":"142", + "code":"145" + }, + { + "desc":"Generally, this is because the xen-blkfront.ko module is not loaded during the startup. You need to modify OS kernel startup parameters. Figure 1 shows the startup screen", + "product_code":"ims", + "title":"What Do I Do If the Disks of an ECS Created from a CentOS Image Cannot Be Found?", + "uri":"en-us_topic_0030713219.html", + "doc_type":"usermanual", + "p_code":"142", + "code":"146" + }, + { + "desc":"This issue is probably caused by the failure of offline VirtIO driver injection.When you inject the VirtIO driver for a Windows ECS offline, there are some restrictions:I", + "product_code":"ims", + "title":"What Do I Do If an ECS Created from a Windows Image Failed to Start When I Have Enabled Automatic Configuration During Image Registration?", + "uri":"en-us_topic_0113403127.html", + "doc_type":"usermanual", + "p_code":"142", + "code":"147" + }, + { + "desc":"An ECS created from a private image using the UEFI boot mode cannot start.The image OS uses the UEFI boot mode, but the uefi attribute is not added to the image.Delete th", + "product_code":"ims", + "title":"What Do I Do If an Exception Occurs When I Start an ECS Created from an Image Using the UEFI Boot Mode?", + "uri":"en-us_topic_0161870891.html", + "doc_type":"usermanual", + "p_code":"142", + "code":"148" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"ims", + "title":"Change History", + "uri":"en-us_topic_0041178787.html", + "doc_type":"usermanual", + "p_code":"", + "code":"149" + }, + { + "desc":"For details about the terms involved in this document, see Glossary.", + "product_code":"ims", + "title":"Glossary", + "uri":"en-us_topic_0047898081.html", + "doc_type":"usermanual", + "p_code":"", + "code":"150" + } +] \ No newline at end of file diff --git a/docs/ims/umn/PARAMETERS.txt b/docs/ims/umn/PARAMETERS.txt new file mode 100644 index 000000000..6da8d5f07 --- /dev/null +++ b/docs/ims/umn/PARAMETERS.txt @@ -0,0 +1,3 @@ +version="" +language="en-us" +type="" \ No newline at end of file diff --git a/docs/ims/umn/en-us_image_0000001082321842.png b/docs/ims/umn/en-us_image_0000001082321842.png new file mode 100644 index 000000000..1f8bc73a3 Binary files /dev/null and b/docs/ims/umn/en-us_image_0000001082321842.png differ diff --git a/docs/ims/umn/en-us_image_0000001147047376.png b/docs/ims/umn/en-us_image_0000001147047376.png new file mode 100644 index 000000000..3e2aa6039 Binary files /dev/null and b/docs/ims/umn/en-us_image_0000001147047376.png differ diff --git a/docs/ims/umn/en-us_image_0000001211409095.png b/docs/ims/umn/en-us_image_0000001211409095.png new file mode 100644 index 000000000..04a5b6a9e Binary files /dev/null and b/docs/ims/umn/en-us_image_0000001211409095.png differ diff --git a/docs/ims/umn/en-us_image_0030714279.png b/docs/ims/umn/en-us_image_0030714279.png new file mode 100644 index 000000000..67c1f65b6 Binary files /dev/null and b/docs/ims/umn/en-us_image_0030714279.png differ diff --git a/docs/ims/umn/en-us_image_0030714282.png b/docs/ims/umn/en-us_image_0030714282.png new file mode 100644 index 000000000..8b0dfdfa8 Binary files /dev/null and b/docs/ims/umn/en-us_image_0030714282.png differ diff --git a/docs/ims/umn/en-us_image_0030714285.png b/docs/ims/umn/en-us_image_0030714285.png new file mode 100644 index 000000000..97123d4e5 Binary files /dev/null and b/docs/ims/umn/en-us_image_0030714285.png differ diff --git a/docs/ims/umn/en-us_image_0030714288.png b/docs/ims/umn/en-us_image_0030714288.png new file mode 100644 index 000000000..a67640d2e Binary files /dev/null and b/docs/ims/umn/en-us_image_0030714288.png differ diff --git a/docs/ims/umn/en-us_image_0085074510.png b/docs/ims/umn/en-us_image_0085074510.png new file mode 100644 index 000000000..64789aaa5 Binary files /dev/null and b/docs/ims/umn/en-us_image_0085074510.png differ diff --git a/docs/ims/umn/en-us_image_0087083593.png b/docs/ims/umn/en-us_image_0087083593.png new file mode 100644 index 000000000..409a3dd44 Binary files /dev/null and b/docs/ims/umn/en-us_image_0087083593.png differ diff --git a/docs/ims/umn/en-us_image_0089766015.png b/docs/ims/umn/en-us_image_0089766015.png new file mode 100644 index 000000000..c4bf203d9 Binary files /dev/null and b/docs/ims/umn/en-us_image_0089766015.png differ diff --git a/docs/ims/umn/en-us_image_0099872706.png b/docs/ims/umn/en-us_image_0099872706.png new file mode 100644 index 000000000..84d438e80 Binary files /dev/null and b/docs/ims/umn/en-us_image_0099872706.png differ diff --git a/docs/ims/umn/en-us_image_0099872707.png b/docs/ims/umn/en-us_image_0099872707.png new file mode 100644 index 000000000..84d438e80 Binary files /dev/null and b/docs/ims/umn/en-us_image_0099872707.png differ diff --git a/docs/ims/umn/en-us_image_0099872708.png b/docs/ims/umn/en-us_image_0099872708.png new file mode 100644 index 000000000..04716d1bb Binary files /dev/null and b/docs/ims/umn/en-us_image_0099872708.png differ diff --git a/docs/ims/umn/en-us_image_0115573259.png b/docs/ims/umn/en-us_image_0115573259.png new file mode 100644 index 000000000..49c271dd8 Binary files /dev/null and b/docs/ims/umn/en-us_image_0115573259.png differ diff --git a/docs/ims/umn/en-us_image_0118549088.png b/docs/ims/umn/en-us_image_0118549088.png new file mode 100644 index 000000000..1e9d829cf Binary files /dev/null and b/docs/ims/umn/en-us_image_0118549088.png differ diff --git a/docs/ims/umn/en-us_image_0120595879.png b/docs/ims/umn/en-us_image_0120595879.png new file mode 100644 index 000000000..d1f94c13c Binary files /dev/null and b/docs/ims/umn/en-us_image_0120595879.png differ diff --git a/docs/ims/umn/en-us_image_0120595887.png b/docs/ims/umn/en-us_image_0120595887.png new file mode 100644 index 000000000..d1f94c13c Binary files /dev/null and b/docs/ims/umn/en-us_image_0120595887.png differ diff --git a/docs/ims/umn/en-us_image_0120595964.png b/docs/ims/umn/en-us_image_0120595964.png new file mode 100644 index 000000000..96d747aab Binary files /dev/null and b/docs/ims/umn/en-us_image_0120595964.png differ diff --git a/docs/ims/umn/en-us_image_0122875972.png b/docs/ims/umn/en-us_image_0122875972.png new file mode 100644 index 000000000..c815e9fc4 Binary files /dev/null and b/docs/ims/umn/en-us_image_0122875972.png differ diff --git a/docs/ims/umn/en-us_image_0122875976.png b/docs/ims/umn/en-us_image_0122875976.png new file mode 100644 index 000000000..5fd277afd Binary files /dev/null and b/docs/ims/umn/en-us_image_0122875976.png differ diff --git a/docs/ims/umn/en-us_image_0125146639.png b/docs/ims/umn/en-us_image_0125146639.png new file mode 100644 index 000000000..925e763e5 Binary files /dev/null and b/docs/ims/umn/en-us_image_0125146639.png differ diff --git a/docs/ims/umn/en-us_image_0125154453.png b/docs/ims/umn/en-us_image_0125154453.png new file mode 100644 index 000000000..274b95971 Binary files /dev/null and b/docs/ims/umn/en-us_image_0125154453.png differ diff --git a/docs/ims/umn/en-us_image_0125452070.png b/docs/ims/umn/en-us_image_0125452070.png new file mode 100644 index 000000000..9050cc49b Binary files /dev/null and b/docs/ims/umn/en-us_image_0125452070.png differ diff --git a/docs/ims/umn/en-us_image_0125511073.png b/docs/ims/umn/en-us_image_0125511073.png new file mode 100644 index 000000000..de1962339 Binary files /dev/null and b/docs/ims/umn/en-us_image_0125511073.png differ diff --git a/docs/ims/umn/en-us_image_0125515202.png b/docs/ims/umn/en-us_image_0125515202.png new file mode 100644 index 000000000..48072e341 Binary files /dev/null and b/docs/ims/umn/en-us_image_0125515202.png differ diff --git a/docs/ims/umn/en-us_image_0127506675.png b/docs/ims/umn/en-us_image_0127506675.png new file mode 100644 index 000000000..7b0eacb21 Binary files /dev/null and b/docs/ims/umn/en-us_image_0127506675.png differ diff --git a/docs/ims/umn/en-us_image_0141888758.png b/docs/ims/umn/en-us_image_0141888758.png new file mode 100644 index 000000000..ee46a4ca5 Binary files /dev/null and b/docs/ims/umn/en-us_image_0141888758.png differ diff --git a/docs/ims/umn/en-us_image_0142360062.png b/docs/ims/umn/en-us_image_0142360062.png new file mode 100644 index 000000000..f5a39cdd6 Binary files /dev/null and b/docs/ims/umn/en-us_image_0142360062.png differ diff --git a/docs/ims/umn/en-us_image_0144424631.png b/docs/ims/umn/en-us_image_0144424631.png new file mode 100644 index 000000000..f5a39cdd6 Binary files /dev/null and b/docs/ims/umn/en-us_image_0144424631.png differ diff --git a/docs/ims/umn/en-us_image_0152727234.png b/docs/ims/umn/en-us_image_0152727234.png new file mode 100644 index 000000000..35e283157 Binary files /dev/null and b/docs/ims/umn/en-us_image_0152727234.png differ diff --git a/docs/ims/umn/en-us_image_0180986761.png b/docs/ims/umn/en-us_image_0180986761.png new file mode 100644 index 000000000..d41a5694a Binary files /dev/null and b/docs/ims/umn/en-us_image_0180986761.png differ diff --git a/docs/ims/umn/en-us_image_0180992674.png b/docs/ims/umn/en-us_image_0180992674.png new file mode 100644 index 000000000..d48cc79b4 Binary files /dev/null and b/docs/ims/umn/en-us_image_0180992674.png differ diff --git a/docs/ims/umn/en-us_image_0184026531.png b/docs/ims/umn/en-us_image_0184026531.png new file mode 100644 index 000000000..1303a51c2 Binary files /dev/null and b/docs/ims/umn/en-us_image_0184026531.png differ diff --git a/docs/ims/umn/en-us_image_0187517327.png b/docs/ims/umn/en-us_image_0187517327.png new file mode 100644 index 000000000..484e614b7 Binary files /dev/null and b/docs/ims/umn/en-us_image_0187517327.png differ diff --git a/docs/ims/umn/en-us_image_0196045691.png b/docs/ims/umn/en-us_image_0196045691.png new file mode 100644 index 000000000..8a64c3072 Binary files /dev/null and b/docs/ims/umn/en-us_image_0196045691.png differ diff --git a/docs/ims/umn/en-us_image_0196045692.png b/docs/ims/umn/en-us_image_0196045692.png new file mode 100644 index 000000000..cced0a1ea Binary files /dev/null and b/docs/ims/umn/en-us_image_0196045692.png differ diff --git a/docs/ims/umn/en-us_image_0203204308.png b/docs/ims/umn/en-us_image_0203204308.png new file mode 100644 index 000000000..71bf71ddb Binary files /dev/null and b/docs/ims/umn/en-us_image_0203204308.png differ diff --git a/docs/ims/umn/en-us_image_0203204309.png b/docs/ims/umn/en-us_image_0203204309.png new file mode 100644 index 000000000..951ae4b4d Binary files /dev/null and b/docs/ims/umn/en-us_image_0203204309.png differ diff --git a/docs/ims/umn/en-us_image_0203254718.png b/docs/ims/umn/en-us_image_0203254718.png new file mode 100644 index 000000000..3ad15a7d4 Binary files /dev/null and b/docs/ims/umn/en-us_image_0203254718.png differ diff --git a/docs/ims/umn/en-us_image_0207581512.png b/docs/ims/umn/en-us_image_0207581512.png new file mode 100644 index 000000000..526264df6 Binary files /dev/null and b/docs/ims/umn/en-us_image_0207581512.png differ diff --git a/docs/ims/umn/en-us_image_0207619456.png b/docs/ims/umn/en-us_image_0207619456.png new file mode 100644 index 000000000..f2629e80b Binary files /dev/null and b/docs/ims/umn/en-us_image_0207619456.png differ diff --git a/docs/ims/umn/en-us_image_0207619609.jpg b/docs/ims/umn/en-us_image_0207619609.jpg new file mode 100644 index 000000000..7cb9e6f72 Binary files /dev/null and b/docs/ims/umn/en-us_image_0207619609.jpg differ diff --git a/docs/ims/umn/en-us_image_0208136139.png b/docs/ims/umn/en-us_image_0208136139.png new file mode 100644 index 000000000..d9b94ee59 Binary files /dev/null and b/docs/ims/umn/en-us_image_0208136139.png differ diff --git a/docs/ims/umn/en-us_image_0208136140.png b/docs/ims/umn/en-us_image_0208136140.png new file mode 100644 index 000000000..92a464842 Binary files /dev/null and b/docs/ims/umn/en-us_image_0208136140.png differ diff --git a/docs/ims/umn/en-us_image_0208136141.png b/docs/ims/umn/en-us_image_0208136141.png new file mode 100644 index 000000000..f74901175 Binary files /dev/null and b/docs/ims/umn/en-us_image_0208136141.png differ diff --git a/docs/ims/umn/en-us_image_0208252825.png b/docs/ims/umn/en-us_image_0208252825.png new file mode 100644 index 000000000..895cf31e2 Binary files /dev/null and b/docs/ims/umn/en-us_image_0208252825.png differ diff --git a/docs/ims/umn/en-us_image_0208476701.png b/docs/ims/umn/en-us_image_0208476701.png new file mode 100644 index 000000000..e45912c0e Binary files /dev/null and b/docs/ims/umn/en-us_image_0208476701.png differ diff --git a/docs/ims/umn/en-us_image_0208552567.jpg b/docs/ims/umn/en-us_image_0208552567.jpg new file mode 100644 index 000000000..dcf70d7e2 Binary files /dev/null and b/docs/ims/umn/en-us_image_0208552567.jpg differ diff --git a/docs/ims/umn/en-us_image_0210189238.png b/docs/ims/umn/en-us_image_0210189238.png new file mode 100644 index 000000000..c2ca06d9a Binary files /dev/null and b/docs/ims/umn/en-us_image_0210189238.png differ diff --git a/docs/ims/umn/en-us_image_0210206922.png b/docs/ims/umn/en-us_image_0210206922.png new file mode 100644 index 000000000..9822f6e59 Binary files /dev/null and b/docs/ims/umn/en-us_image_0210206922.png differ diff --git a/docs/ims/umn/en-us_image_0210228327.png b/docs/ims/umn/en-us_image_0210228327.png new file mode 100644 index 000000000..c92bf1a9c Binary files /dev/null and b/docs/ims/umn/en-us_image_0210228327.png differ diff --git a/docs/ims/umn/en-us_image_0214265355.png b/docs/ims/umn/en-us_image_0214265355.png new file mode 100644 index 000000000..895cf31e2 Binary files /dev/null and b/docs/ims/umn/en-us_image_0214265355.png differ diff --git a/docs/ims/umn/en-us_image_0219481382.png b/docs/ims/umn/en-us_image_0219481382.png new file mode 100644 index 000000000..0f7dfd5ca Binary files /dev/null and b/docs/ims/umn/en-us_image_0219481382.png differ diff --git a/docs/ims/umn/en-us_image_0251959651.png b/docs/ims/umn/en-us_image_0251959651.png new file mode 100644 index 000000000..2e3cc3ca6 Binary files /dev/null and b/docs/ims/umn/en-us_image_0251959651.png differ diff --git a/docs/ims/umn/en-us_image_0254928267.png b/docs/ims/umn/en-us_image_0254928267.png new file mode 100644 index 000000000..65904d8d4 Binary files /dev/null and b/docs/ims/umn/en-us_image_0254928267.png differ diff --git a/docs/ims/umn/en-us_image_0254963039.png b/docs/ims/umn/en-us_image_0254963039.png new file mode 100644 index 000000000..4a17b5f55 Binary files /dev/null and b/docs/ims/umn/en-us_image_0254963039.png differ diff --git a/docs/ims/umn/en-us_image_0254985106.png b/docs/ims/umn/en-us_image_0254985106.png new file mode 100644 index 000000000..c27055e4c Binary files /dev/null and b/docs/ims/umn/en-us_image_0254985106.png differ diff --git a/docs/ims/umn/en-us_image_0255035033.png b/docs/ims/umn/en-us_image_0255035033.png new file mode 100644 index 000000000..a56ce0946 Binary files /dev/null and b/docs/ims/umn/en-us_image_0255035033.png differ diff --git a/docs/ims/umn/en-us_image_0255101497.png b/docs/ims/umn/en-us_image_0255101497.png new file mode 100644 index 000000000..9e9c2e9a6 Binary files /dev/null and b/docs/ims/umn/en-us_image_0255101497.png differ diff --git a/docs/ims/umn/en-us_image_0275513364.png b/docs/ims/umn/en-us_image_0275513364.png new file mode 100644 index 000000000..1909444d2 Binary files /dev/null and b/docs/ims/umn/en-us_image_0275513364.png differ diff --git a/docs/ims/umn/en-us_image_0285376505.png b/docs/ims/umn/en-us_image_0285376505.png new file mode 100644 index 000000000..12e570b77 Binary files /dev/null and b/docs/ims/umn/en-us_image_0285376505.png differ diff --git a/docs/ims/umn/en-us_topic_0000001120952155.html b/docs/ims/umn/en-us_topic_0000001120952155.html new file mode 100644 index 000000000..ac2855280 --- /dev/null +++ b/docs/ims/umn/en-us_topic_0000001120952155.html @@ -0,0 +1,199 @@ + + +
When optimizing a Linux private image, you need to install native KVM drivers on the ECS.
+
If you do not install KVM drivers, NICs of the ECS may not be detected and the ECS cannot communicate with other resources.
+This section describes how to install native KVM drivers.
+Modify the configuration file based on the OS version.
+ +OS + |
+Configuration + |
+Reference + |
+
|---|---|---|
CentOS/EulerOS + |
+Take CentOS 7.0 as an example. +
|
++ | +
Ubuntu/Debian + |
+
|
++ | +
SUSE and openSUSE + |
+If the OS version is earlier than SUSE 12 SP1 or openSUSE 13: +
|
++ | +
If the OS version is SUSE 12 SP1: +
|
++ | +|
If the OS version is later than SUSE 12 SP1 or openSUSE 13: +
|
++ | +
vi /etc/dracut.conf
+[root@CTU10000xxxxx ~]# vi /etc/dracut.conf +# additional kernel modules to the default +add_drivers+="virtio_blk virtio_scsi virtio_net virtio_pci virtio_ring virtio" +....+
dracut -f /boot/initramfs-2.6.32-573.8.1.el6.x86_64.img
+If the virtual file system is not the default initramfs, run the dracut -f Name of the initramfs or initrd file actually used command. The actual initramfs or initrd file name can be obtained from the grub.cfg file, which can be /boot/grub/grub.cfg, /boot/grub2/grub.cfg, or /boot/grub/grub.conf depending on the OS.
+lsinitrd /boot/initramfs-`uname -r`.img | grep virtio
+If the virtual file system is initrd, run the following command to check whether native KVM drivers have been loaded:
+lsinitrd /boot/initrd-`uname -r` | grep virtio
+Assume that the virtual file system is initramfs. The following command output will be displayed:
+[root@CTU10000xxxxx home]# lsinitrd /boot/initramfs-`uname -r`.img | grep virtio +-rwxr--r-- 1 root root 23448 Jul 16 17:53 lib/modules/2.6.32-573.8.1.el6.x86_64/kernel/drivers/block/virtio_blk.ko +-rwxr--r-- 1 root root 50704 Jul 16 17:53 lib/modules/2.6.32-573.8.1.el6.x86_64/kernel/drivers/net/virtio_net.ko +-rwxr--r-- 1 root root 28424 Jul 16 17:53 lib/modules/2.6.32-573.8.1.el6.x86_64/kernel/drivers/scsi/virtio_scsi.ko +drwxr-xr-x 2 root root 0 Jul 16 17:53 lib/modules/2.6.32-573.8.1.el6.x86_64/kernel/drivers/virtio +-rwxr--r-- 1 root root 14544 Jul 16 17:53 lib/modules/2.6.32-573.8.1.el6.x86_64/kernel/drivers/virtio/virtio.ko +-rwxr--r-- 1 root root 21040 Jul 16 17:53 lib/modules/2.6.32-573.8.1.el6.x86_64/kernel/drivers/virtio/virtio_pci.ko +-rwxr--r-- 1 root root 18016 Jul 16 17:53 lib/modules/2.6.32-573.8.1.el6.x86_64/kernel/drivers/virtio/virtio_ring.ko+
If you add built-in drivers to the initrd or initramfs file, the ECS will not be affected. This makes it easy to modify the drivers. However, you cannot check the drivers by running the lsinitrd command. You can run the following command to check whether the drivers are built-in ones in the kernel:
+cat /boot/config-`uname -r` | grep CONFIG_VIRTIO | grep y
+vi /etc/initramfs-tools/modules
+[root@CTU10000xxxxx ~]#vi /etc/initramfs-tools/modules +... +# Examples: +# +# raid1 +# sd_mOd +virtio_blk +virtio_scsi +virtio_net +virtio_pci +virtio_ring +virtio+
lsinitramfs /boot/initrd.img-`uname -r` |grep virtio
+[root@ CTU10000xxxxx home]# lsinitramfs /boot/initrd.img-`uname -r` |grep virtio +lib/modules/3.5.0-23-generic/kernel/drivers/scsi/virtio_scsi.ko+
If you add built-in drivers to the initrd or initramfs file, the ECS will not be affected. This makes it easy to modify the drivers. However, you cannot check the drivers by running the lsinitrd command. You can run the following command to check whether the drivers are built-in ones in the kernel:
+[root@ CTU10000xxxxx home]# cat /boot/config-`uname -r` | grep CONFIG_VIRTIO | grep y +CONFIG_VIRTIO_BLK=y +CONFIG_VIRTIO_NET=y +CONFIG_VIRTIO=y +CONFIG_VIRTIO_RING=y +CONFIG_VIRTIO_PCI=y +CONFIG_VIRTIO_MMIO_CMDLINE_DEVICES=y+
vi etc/sysconfig/kernel
+SIA10000xxxxx:~ # vi /etc/sysconfig/kernel +# (like drivers for scsi-controllers, for lvm or reiserfs) +# +INITRD_MODULES="ata_piix ata_generic virtio_blk virtio_scsi virtio_net virtio_pci virtio_ring virtio"+
If the virtual file system is not the default initramfs or initrd, run the dracut -f Name of the initramfs or initrd file actually used command. The actual initramfs or initrd file name can be obtained from the menu.lst or grub.cfg file (/boot/grub/menu.lst, /boot/grub/grub.cfg, or /boot/grub2/grub.cfg).
+The following is an example initrd file of SUSE 11 SP4:
+default 0 +timeout 10 +gfxmenu (hd0,0)/boot/message +title sles11sp4_001_[_VMX_] +root (hd0,0) +kernel /boot/linux.vmx vga=0x314 splash=silent console=ttyS0,115200n8 console=tty0 net.ifnames=0 NON_PERSISTENT_DEVICE_NAMES=1 showopts +initrd /boot/initrd.vmx +title Failsafe_sles11sp4_001_[_VMX_] +root (hd0,0) +kernel /boot/linux.vmx vga=0x314 splash=silent ide=nodma apm=off noresume edd=off powersaved=off nohz=off highres=off processsor.max+cstate=1 nomodeset x11failsafe console=ttyS0,115200n8 console=tty0 net.ifnames=0 NON_PERSISTENT_DEVICE_NAMES=1 showopts +initrd /boot/initrd.vmx+
/boot/initrd.vmx in the initrd line is the initrd file actually used. Run the dracut -f /boot/initrd.vmx command. If the initrd file does not contain the /boot directory, such as /initramfs-xxx, run the dracut -f /boot/initramfs-xxx command.
+SIA10000xxxxx:~ # lsinitrd /boot/initrd-`uname -r` | grep virtio +-rwxr--r-- 1 root root 19248 Jun 22 2012 lib/modules/2.6.32-279.el6.x86_64/kernel/drivers/scsi/virtio_scsi.ko +-rwxr--r-- 1 root root 23856 Jun 22 2012 lib/modules/2.6.32-279.el6.x86_64/kernel/drivers/block/virtio_blk.ko +drwxr-xr-x 2 root root 0 Jul 12 14:53 lib/modules/2.6.32-279.el6.x86_64/kernel/drivers/virtio +-rwxr--r-- 1 root root 15848 Jun 22 2012 lib/modules/2.6.32-279.el6.x86_64/kernel/drivers/virtio/virtio_ring.ko +-rwxr--r-- 1 root root 20008 Jun 22 2012 lib/modules/2.6.32-279.el6.x86_64/kernel/drivers/virtio/virtio_pci.ko +-rwxr--r-- 1 root root 12272 Jun 22 2012 lib/modules/2.6.32-279.el6.x86_64/kernel/drivers/virtio/virtio.ko +-rwxr--r-- 1 root root 38208 Jun 22 2012 lib/modules/2.6.32-279.el6.x86_64/kernel/drivers/net/virtio_net.ko+
lsinitrd /boot/initrd-`uname -r` | grep virtio
+SIA10000xxxxx:~ # lsinitrd /boot/initrd-`uname -r` | grep virtio +-rwxr--r-- 1 root root 19248 Jun 22 2012 lib/modules/2.6.32-279.el6.x86_64/kernel/drivers/scsi/virtio_scsi.ko +-rwxr--r-- 1 root root 23856 Jun 22 2012 lib/modules/2.6.32-279.el6.x86_64/kernel/drivers/block/virtio_blk.ko +drwxr-xr-x 2 root root 0 Jul 12 14:53 lib/modules/2.6.32-279.el6.x86_64/kernel/drivers/virtio +-rwxr--r-- 1 root root 15848 Jun 22 2012 lib/modules/2.6.32-279.el6.x86_64/kernel/drivers/virtio/virtio_ring.ko +-rwxr--r-- 1 root root 20008 Jun 22 2012 lib/modules/2.6.32-279.el6.x86_64/kernel/drivers/virtio/virtio_pci.ko +-rwxr--r-- 1 root root 12272 Jun 22 2012 lib/modules/2.6.32-279.el6.x86_64/kernel/drivers/virtio/virtio.ko +-rwxr--r-- 1 root root 38208 Jun 22 2012 lib/modules/2.6.32-279.el6.x86_64/kernel/drivers/net/virtio_net.ko+
If you add built-in drivers to the initrd or initramfs file, the ECS will not be affected. This makes it easy to modify the drivers. However, you cannot check the drivers by running the lsinitrd command. You can run the following command to check whether the drivers are built-in ones in the kernel:
+cat /boot/config-`uname -r` | grep CONFIG_VIRTIO | grep y
+vi /etc/dracut.conf
+[root@CTU10000xxxxx ~]# vi /etc/dracut.conf +# additional kernel modules to the default +add_drivers+="ata_piix ata_generic virtio_blk virtio_scsi virtio_net virtio_pci virtio_ring virtio"+
dracut -f /boot/initramfs-File name
+If the virtual file system is not the default initramfs, run the dracut -f Name of the initramfs or initrd file actually used command. The actual initramfs or initrd file name can be obtained from the grub.cfg file, which can be /boot/grub/grub.cfg, /boot/grub2/grub.cfg, or /boot/grub/grub.conf depending on the OS.
+lsinitrd /boot/initramfs-`uname -r`.img | grep virtio
+If the virtual file system is initrd, run the following command to check whether native KVM drivers have been loaded:
+lsinitrd /boot/initrd-`uname -r` | grep virtio
+Modify the /etc/dracut.conf file.
+vi /etc/dracut.conf
+[root@CTU10000xxxxx ~]# vi /etc/dracut.conf +# additional kernel modules to the default +add_drivers+="ata_piix ata_generic virtio_blk virtio_scsi virtio_net virtio_pci virtio_ring virtio"+
dracut -f /boot/initramfs-File name
+If the virtual file system is not the default initramfs, run the dracut -f Name of the initramfs or initrd file actually used command. The actual initramfs or initrd file name can be obtained from the grub.cfg file, which can be /boot/grub/grub.cfg, /boot/grub2/grub.cfg, or /boot/grub/grub.conf depending on the OS.
+lsinitrd /boot/initramfs-`uname -r`.img | grep virtio
+If the virtual file system is initrd, run the following command to check whether native KVM drivers have been loaded:
+lsinitrd /boot/initrd-`uname -r` | grep virtio
+Assume that the virtual file system is initrd. The following command output will be displayed:
+sluo-ecs-30dc:~ # lsinitrd /boot/initrd-`uname -r` | grep virtio +-rw-r--r-- 1 root root 29335 Oct 26 2016 lib/modules/4.4.21-69-default/kernel/drivers/block/virtio_blk.ko +-rw-r--r-- 1 root root 57007 Oct 26 2016 lib/modules/4.4.21-69-default/kernel/drivers/net/virtio_net.ko +-rw-r--r-- 1 root root 32415 Oct 26 2016 lib/modules/4.4.21-69-default/kernel/drivers/scsi/virtio_scsi.ko +drwxr-xr-x 2 root root 0 Sep 28 10:21 lib/modules/4.4.21-69-default/kernel/drivers/virtio +-rw-r--r-- 1 root root 19623 Oct 26 2016 lib/modules/4.4.21-69-default/kernel/drivers/virtio/virtio.ko +-rw-r--r-- 1 root root 38943 Oct 26 2016 lib/modules/4.4.21-69-default/kernel/drivers/virtio/virtio_pci.ko +-rw-r--r-- 1 root root 24431 Oct 26 2016 lib/modules/4.4.21-69-default/kernel/drivers/virtio/virtio_ring.ko+
If you add built-in drivers to the initrd or initramfs file, the ECS will not be affected. This makes it easy to modify the drivers. However, you cannot check the drivers by running the lsinitrd command. You can run the following command to check whether the drivers are built-in ones in the kernel:
+cat /boot/config-`uname -r` | grep CONFIG_VIRTIO | grep y
+IMS provides multiple methods for importing images. You can select a method based on the image file type, format, or size.
+File Format + |
+File Size + |
+Reference + |
+
|---|---|---|
VMDK, VHD, QCOW2, VHDX, QED, VDI, QCOW, or ZVHD + |
+Not larger than 128 GB + |
++ | +
RAW or ZVHD2 + |
+No larger than 1 TB + |
++ | +
An image is a server or disk template that contains an operating system (OS) or service data and necessary software, such as database software. IMS provides public, private, and shared images.
+Image Management Service (IMS) allows you to manage the entire lifecycle of your images. You can create ECSs or BMSs from public, private, or shared images. You can also create a private image from a cloud server or an external image file to make it easier to migrate workloads to the cloud or on the cloud.
+Images are classified as public, private, and shared. Public images are provided by the cloud platform, private images are those you created yourself, and shared images are private images that other tenants have shared with you.
+ +Image Type + |
+Description + |
+
|---|---|
Public image + |
+A public image is a standard, widely used image. It contains an OS and preinstalled public applications and is available to all users. Public images are very stable and their OS and any included software have been officially authorized for use. If a public image does not contain the application environments or software you need, you can use a public image to create an ECS and then deploy required software as needed. + |
+
Private image + |
+A private image contains an OS or service data, preinstalled public applications, and a user's personal applications. Private images are only available to the users who created them. +A private image can be a system disk image, data disk image, or full-ECS image. +
|
+
Shared image + |
+A shared image is a private image another user has shared with you. + |
+
IMS provides:
+The public cloud provides a web-based service management platform (a management console). You can access the IMS service through HTTPS APIs or from the management console.
+ +A private image is an image available only to the user who created it. It contains an OS, preinstalled public applications, and a user's personal applications. A private image can be a system disk image, data disk image, or full-ECS image. It can be created from a cloud server or an external image file.
+Creating a private image does not affect the running of services on the cloud server or cause data loss.
+This section describes the OSs supported by different types of ECSs.
+General-purpose T6
+General computing S2, S3, S6, and SN3
+General computing-plus C3 and C6
+Memory-optimized M2, M3, and M6
+High-performance computing HC2 and H3
+Disk-intensive D2 and D3
+General computing-plus C3ne, C6, and C6s
+Memory-optimized M3ne
+Large-memory E3
+Ultra-high I/O I3 and IR3
+
OS + |
+OS Version + |
+
|---|---|
Windows + |
+Windows Server 2008 R2 Standard/Enterprise/Datacenter/Web +Windows Server 2012 Standard/Datacenter +Windows Server 2012 R2 Standard/Datacenter +Windows Server 2016 Standard/Datacenter +Windows Server 2019 Standard/Datacenter +Windows Server Core Version 1709 + |
+
CentOS + |
+64-bit: CentOS 6.10, 6.9, 6.8, 6.7, 6.6, 6.5, 6.4, and 6.3 +64-bit: CentOS 7.9, 7.8, 7.7, 7.6, 7.5, 7.4, 7.3, 7.2, 7.1, and 7.0 +64-bit: CentOS 8.3, 8.2, 8.1, and 8.0 + |
+
Ubuntu + |
+64-bit: Ubuntu 20.04, 18.04, 16.04, 14.04, and 12.04 Server + |
+
EulerOS + |
+64-bit: EulerOS 2.9, 2.5, 2.3, and 2.2 + |
+
Red Hat + |
+64-bit: Red Hat 6.10, 6.9, 6.8, 6.7, 6.6, 6.5, and 6.4 +64-bit: Red Hat 7.6, 7.5, 7.4, 7.3, 7.2, 7.1, and 7.0 +64-bit: Red Hat 8.0 + |
+
SUSE Linux Enterprise + |
+64-bit: SLES 11 SP4 and 11 SP3 +64-bit: SLES 12 SP4, 12 SP3, 12 SP2, 12 SP1, and 12 +64-bit: SLES 15, 15 SP1, and 15 SP2 + |
+
Debian + |
+64-bit: Debian 8.0.0–8.10.0 +64-bit: Debian 9.13.0, 9.12.0, 9.11.0, 9.9.0, 9.8.0, 9.7.0, 9.6.0, 9.5.0, 9.4.0, 9.3.0, and 9.0.0 +64-bit: Debian 10.0.0–10.5.0, 10.7.0 + |
+
openSUSE + |
+64-bit: openSUSE 13.2 +64-bit: openSUSE Leap 15.1 and 15.0 +64-bit: openSUSE Leap 42.3, 42.2, and 42.1 + |
+
Fedora + |
+64-bit: Fedora 22–32 + |
+
CoreOS + |
+64-bit: CoreOS 2079.4.0 + |
+
FreeBSD + |
+64bit: FreeBSD 11.0,10.3, and 12.1 + |
+
openEuler + |
+64-bit: openEuler 20.03 + |
+
OS + |
+OS Version + |
+Kernel Version + |
+
|---|---|---|
Windows + |
+Windows Server 2008 R2 Enterprise/Datacenter/Web/Standard +Windows Server 2012 R2 Standard/Datacenter +Windows Server 2016 Standard/Datacenter +Windows Server 2019 Datacenter +Windows Server Version 1709 Datacenter + |
+10.0.14393 +6.1.7600 +6.0.6002 +6.1.7600 +6.3.9600 + |
+
CentOS + |
+64-bit: +CentOS 6 +CentOS 7 +CentOS 8 + |
+2.6.32-754.10.1.e16.x86_64 +2.6.32-696.16.1.el6.x86_64 +2.6.32-754.10.1.el6.x86_64 +2.6.32-754.11.1.e16.x86_64 +3.10.0-514.10.2.el7.x86_64 +3.10.0-693.11.1.el7.x86_64 +3.10.0-862.9.1.el7.x86_64 +3.10.0-957.5.1.e17.x86_64 +3.10.0-957.10.1.e17.x86_64 + |
+
Ubuntu + |
+64-bit: +Ubuntu 14.04 Server +Ubuntu 16.04 Server +Ubuntu 18.04 Server +Ubuntu 20.04 Server + |
+4.15.0-52-56 +4.4.0-151-178 +4.4.0-104-generic +4.4.0-141-generic +4.4.0-142-generic +4.4.0-145-generic +4.15.0-34-generic +4.15.0-45-generic +4.15.0-47-generic + |
+
EulerOS + |
+64-bit: +EulerOS 2.2 +EulerOS 2.3 +EulerOS 2.5 + |
+3.10.0-327.62.59.83.h162.x86_64 +3.10.0-514.44.5.10.h198.x86_64 +3.10.0-327.59.59.46.h38.x86_64 +3.10.0-327.62.59.83.h96.x86_64 +3.10.0-327.62.59.83.h128.x86_64 +3.10.0-514.44.5.10.h121.x86_64 +3.10.0-514.44.5.10.h142.x86_64 + |
+
Red Hat + |
+64-bit: +Red Hat 6 +Red Hat 7 + |
+2.6.32-358.6.2.el6.x86_64 +2.6.32-431.20.3.el6 +2.6.32-504.12.2.el6 +2.6.32-573.el6.x86_64 +2.6.32-696.1.1.el6.x86_64 +2.6.32-696.10.2.el6.x86_64 +2.6.32-754.el6.x86_64 +3.10.0-229.1.2.el7.x86_64 +3.10.0-327.36.1.el7.x86_64 +3.10.0-514.36.1.el7 +3.10.0-514.6.1.el7.x86_64 +3.10.0-693.11.6.el7.x86_64 +3.10.0-862.3.2.el7.x86_64 + |
+
SUSE Linux Enterprise + |
+64-bit: +SLES 11 +SLES 12 + |
+3.0.101-108.18-default +3.12.74-60.64.40-default +4.4.103-92.53-default +4.4.120-92.70-default +4.4.121-92.92 + |
+
Debian + |
+64-bit: +Debian 8 +Debian 9 + |
+4.9.168-1+deb9u3 +3.2.0-4-686-pae +3.2.0-4-amd64 +3.16.0-4-amd64 +4.9.0-3-amd64 +4.9.0-4-amd64 +4.9.0-8-amd64 +4.9.0-9-amd64 +4.19.0-5-amd64 + |
+
openSUSE + |
+64-bit: +openSUSE 15.0 +openSUSE 15.1 + |
+4.4.103-18.41-default +3.0.101-108.18-default + |
+
Fedora + |
+64-bit: +Fedora 2x + |
+5.1.11-200.fc29.x86_64 +4.5.5-300.fc24.x86_64 +4.20.8-200.fc29.x86_64 +5.2.8-200.fc30.x86_64 +4.8.6-300.fc25.x86_64 + |
+
openEuler + |
+64-bit: +openEuler 20.03 + |
+4.19.90-2003.4.0.0036.oel.x86_64 + |
+
OS + |
+OS Version + |
+Kernel Version + |
+
|---|---|---|
CentOS + |
+64-bit: +CentOS 6 +CentOS 7 +CentOS 8 + |
+2.6.32-754.15.3.e16.x86_64 +2.6.32-696.16.1.el6.x86_64 +2.6.32-754.10.1.el6.x86_64 +2.6.32-754.11.1.e16.x86_64 +3.10.0-514.10.2.el7.x86_64 +3.10.0-693.11.1.el7.x86_64 +3.10.0-862.9.1.el7.x86_64 +3.10.0-957.21.3.e17.x86_64 +3.10.0-957.5.1.e17.x86_64 +3.10.0-957.10.1.e17.x86_64 + |
+
Ubuntu + |
+64-bit: +Ubuntu 14.04 Server +Ubuntu 16.04 Server +Ubuntu 18.04 Server +Ubuntu 20.04 Server + |
+4.15.0-52-56 +4.4.0-151-178 +4.4.0-104-generic +4.4.0-141-generic +4.4.0-142-generic +4.4.0-145-generic +4.15.0-34-generic +4.15.0-45-generic +4.15.0-47-generic + |
+
EulerOS + |
+64-bit: +EulerOS 2.2 +EulerOS 2.3 +EulerOS 2.5 +EulerOS 2.9 + |
+3.10.0-327.62.59.83.h162.x86_64 +3.10.0-514.44.5.10.h198.x86_64 +3.10.0-327.59.59.46.h38.x86_64 +3.10.0-327.62.59.83.h96.x86_64 +3.10.0-327.62.59.83.h128.x86_64 +3.10.0-514.44.5.10.h121.x86_64 +3.10.0-514.44.5.10.h142.x86_64 + |
+
Red Hat + |
+64-bit: +Red Hat 6 +Red Hat 7 + |
+2.6.32-358.6.2.el6.x86_64 +2.6.32-431.20.3.el6 +2.6.32-504.12.2.el6 +2.6.32-573.el6.x86_64 +2.6.32-696.1.1.el6.x86_64 +2.6.32-696.10.2.el6.x86_64 +2.6.32-754.el6.x86_64 +3.10.0-229.1.2.el7.x86_64 +3.10.0-327.36.1.el7.x86_64 +3.10.0-514.36.1.el7 +3.10.0-514.6.1.el7.x86_64 +3.10.0-693.11.6.el7.x86_64 +3.10.0-862.3.2.el7.x86_64 + |
+
SUSE Linux Enterprise + |
+64-bit: +SLES 11 +SLES 12 +SLES 15 + |
+3.0.101-108.18-default +3.12.74-60.64.40-default +4.4.103-92.53-default +4.4.120-92.70-default +4.4.121-92.92 + |
+
Debian + |
+64-bit: +Debian 8 +Debian 9 +Debian 10 + |
+4.9.168-1+deb9u3 +3.2.0-4-686-pae +3.2.0-4-amd64 +3.16.0-4-amd64 +4.9.0-3-amd64 +4.9.0-4-amd64 +4.9.0-8-amd64 +4.9.0-9-amd64 +4.19.0-5-amd64 + |
+
openSUSE + |
+64-bit: +openSUSE 15.0 +openSUSE 15.1 + |
+4.4.103-18.41-default +3.0.101-108.18-default + |
+
Fedora + |
+64-bit: +Fedora 2x +Fedora 3x + |
+5.1.11-200.fc29.x86_64 +4.5.5-300.fc24.x86_64 +4.20.8-200.fc29.x86_64 +5.2.8-200.fc30.x86_64 +4.8.6-300.fc25.x86_64 + |
+
openEuler + |
+64-bit: +openEuler 20.03 + |
+4.19.90-2003.4.0.0036.oel.x86_64 + |
+
OS + |
+OS Version + |
+Kernel Version + |
+
|---|---|---|
CentOS + |
+64-bit: +CentOS 7 + |
+3.10.0-514.10.2.el7.x86_64 +3.10.0-693.11.1.el7.x86_64 +3.10.0-862.9.1.el7.x86_64 +3.10.0-957.21.3.e17.x86_64 +3.10.0-957.5.1.e17.x86_64 +3.10.0-957.10.1.e17.x86_64 + |
+
Ubuntu + |
+64-bit: +Ubuntu 14.04 Server +Ubuntu 16.04 Server +Ubuntu 18.04 Server + |
+4.4.0-31-generic +4.4.0-131-generic +4.4.0-141-generic +4.4.0-142-generic +4.15.0-29-generic +4.15.0-45-generic + |
+
SUSE Linux Enterprise + |
+64-bit: +SLES 12 + |
+4.4.103-92.53-default +4.4.120-92.70-default + |
+
Debian + |
+64-bit: +Debian 8 +Debian 9 + |
+3.16.0-7-amd64 +3.16.0-4-amd64 +4.9.0-3-amd64 + |
+
Table 5 lists the OSs supported by the following ECSs:
+OS + |
+OS Version + |
+
|---|---|
CentOS + |
+64-bit: CentOS 7.6, 7.5, and 7.4 +64-bit: CentOS 8.0 + |
+
Ubuntu + |
+64-bit: Ubuntu 18.04 Server + |
+
EulerOS + |
+64-bit: EulerOS 2.8 + |
+
Red Hat + |
+64-bit: Red Hat 7.6 and 7.5 + |
+
SUSE Linux Enterprise + |
+64-bit: SLES 12 SP5 and SP4 +64-bit: SLES 15 + |
+
openSUSE + |
+64-bit: openSUSE Leap 15.0 + |
+
Fedora + |
+64-bit: Fedora 29 + |
+
Debian + |
+64-bit: Debian 10.2.0 + |
+
openEuler + |
+64-bit: openEuler 20.03 + |
+
Image files in VMDK, VHD, QCOW2, RAW, VHDX, QED, VDI, QCOW, ZVHD2, or ZVHD format can be used to create private images. Select whichever format best meeting your requirements.
+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 for external image files.
+If the OS cannot be identified or is not supported:
+ +
OS + |
+Version + |
+
|---|---|
Windows + |
+Windows 10 64bit +Windows 7 Enterprise 64bit +Windows Server 2016 Standard 64bit +Windows Server 2016 Datacenter 64bit +Windows Server 2012 R2 Standard 64bit +Windows Server 2012 Essentials R2 64bit +Windows Server 2012 R2 Datacenter 64bit +Windows Server 2012 Datacenter 64bit +Windows Server 2012 Standard 64bit +Windows Server 2008 R2 WEB 64bit +Windows Server 2008 R2 Standard 64bit +Windows Server 2008 R2 Enterprise 64bit +Windows Server 2008 R2 Datacenter 64bit + |
+
SUSE + |
+SUSE Linux Enterprise Server 15 SP1 64bit +SUSE Linux Enterprise Server 15 64bit +SUSE Linux Enterprise Server 12 SP5 64bit +SUSE Linux Enterprise Server 12 SP3 64bit +SUSE Linux Enterprise Server 12 SP2 64bit +SUSE Linux Enterprise Server 12 SP1 64bit +SUSE Linux Enterprise Server 12 64bit +SUSE Linux Enterprise Server 11 SP4 64bit +SUSE Linux Enterprise Server 11 SP3 64bit +SUSE Linux Enterprise Server 11 SP3 32bit +SUSE Linux Enterprise Server 11 SP1 32bit + |
+
Oracle Linux + |
+Oracle Linux Server release 7.6 64bit +Oracle Linux Server release 7.5 64bit +Oracle Linux Server release 7.4 64bit +Oracle Linux Server release 7.3 64bit +Oracle Linux Server release 7.2 64bit +Oracle Linux Server release 7.1 64bit +Oracle Linux Server release 7.0 64bit +Oracle Linux Server release 6.10 64bit +Oracle Linux Server release 6.9 64bit +Oracle Linux Server release 6.8 64bit +Oracle Linux Server release 6.7 64bit +Oracle Linux Server release 6.5 64bit + |
+
Red Hat + |
+Red Hat Linux Enterprise 8.0 64bit +Red Hat Linux Enterprise 7.6 64bit +Red Hat Linux Enterprise 7.5 64bit +Red Hat Linux Enterprise 7.4 64bit +Red Hat Linux Enterprise 7.3 64bit +Red Hat Linux Enterprise 7.2 64bit +Red Hat Linux Enterprise 7.1 64bit +Red Hat Linux Enterprise 7.0 64bit +Red Hat Linux Enterprise 6.10 64bit +Red Hat Linux Enterprise 6.9 64bit +Red Hat Linux Enterprise 6.8 64bit +Red Hat Linux Enterprise 6.7 64bit +Red Hat Linux Enterprise 6.6 64bit +Red Hat Linux Enterprise 6.6 32bit +Red Hat Linux Enterprise 6.5 64bit +Red Hat Linux Enterprise 6.4 64bit +Red Hat Linux Enterprise 6.4 32bit + |
+
Ubuntu + |
+Ubuntu 20.04 Server 64bit +Ubuntu 19.04 Server 64bit +Ubuntu 18.04 Server 64bit +Ubuntu 16.04.3 Server 64bit +Ubuntu 16.04.2 Server 64bit +Ubuntu 16.04 Server 64bit +Ubuntu 14.04.5 Server 64bit +Ubuntu 14.04.4 Server 64bit +Ubuntu 14.04.4 Server 32bit +Ubuntu 14.04.3 Server 64bit +Ubuntu 14.04.3 Server 32bit +Ubuntu 14.04.1 Server 64bit +Ubuntu 14.04.1 Server 32bit +Ubuntu 14.04 Server 64bit +Ubuntu 14.04 Server 32bit + |
+
openSUSE + |
+openSUSE 42.3 64bit +openSUSE 42.2 64bit +openSUSE 42.1 64bit +openSUSE 15.1 64bit +openSUSE 15.0 64bit +openSUSE 13.2 64bit +openSUSE 11.3 64bit + |
+
CentOS + |
+CentOS 8.0 64bit +CentOS 7.9 64bit +CentOS 7.8 64bit +CentOS 7.7 64bit +CentOS 7.6 64bit +CentOS 7.5 64bit +CentOS 7.4 64bit +CentOS 7.3 64bit +CentOS 7.2 64bit +CentOS 7.1 64bit +CentOS 7.0 64bit +CentOS 7.0 32bit +CentOS 6.10 64bit +CentOS 6.10 32bit +CentOS 6.9 64bit +CentOS 6.8 64bit +CentOS 6.7 64bit +CentOS 6.7 32bit +CentOS 6.6 64bit +CentOS 6.6 32bit +CentOS 6.5 64bit +CentOS 6.5 32bit +CentOS 6.4 64bit +CentOS 6.4 32bit +CentOS 6.3 64bit +CentOS 6.3 32bit + |
+
Debian + |
+Debian GNU/Linux 10.0.0 64bit +Debian GNU/Linux 9.3.0 64bit +Debian GNU/Linux 9.0.0 64bit +Debian GNU/Linux 8.8.0 64bit +Debian GNU/Linux 8.7.0 64bit +Debian GNU/Linux 8.6.0 64bit +Debian GNU/Linux 8.5.0 64bit +Debian GNU/Linux 8.4.0 64bit +Debian GNU/Linux 8.2.0 64bit +Debian GNU/Linux 8.1.0 64bit + |
+
Fedora + |
+Fedora 30 64bit +Fedora 29 64bit +Fedora 28 64bit +Fedora 27 64bit +Fedora 26 64bit +Fedora 25 64bit +Fedora 24 64bit +Fedora 23 64bit +Fedora 22 64bit + |
+
EulerOS + |
+EulerOS 2.9 64bit +EulerOS 2.5 64bit +EulerOS 2.3 64bit +EulerOS 2.2 64bit +EulerOS 2.1 64bit + |
+
CoreOS + |
+CoreOS 1068.10.0 +CoreOS 1010.5.0 +CoreOS 1298.6.0 + |
+
openEuler + |
+openEuler 20.03 64bit + |
+
For how to upload an external image file, see Uploading an External Image File and Uploading an External Image File.
+After an external image file is successfully uploaded, you can register this image file as a private image on the cloud platform. For details, see Registering an External Image File as a Private Image and Registering an External Image File as a Private Image.
+Service + |
+Relationship with IMS + |
+Related Operation + |
+
|---|---|---|
Elastic Cloud Server (ECS) + |
+You can use an image to create ECSs or use an ECS to create an image. + |
++ | +
Bare Metal Server (BMS) + |
+You can use an image to create BMSs or use a BMS to create an image. + |
++ | +
Object Storage Service (OBS) + |
+Images are stored in OBS buckets. External image files to be uploaded to the system are stored in OBS buckets, and private images are exported to OBS buckets. + |
++ | +
Key Management Service (KMS) + |
+KMS provides the keys used for encrypting images. + |
++ | +
Elastic Volume Service (EVS) + |
+You can create a data disk image using a data disk of an ECS. The created data disk image can be used to create other EVS disks. + |
++ | +
Cloud Server Backup Service (CSBS) + |
+You can use a CSBS backup to create a full-ECS image. + |
++ | +
Cloud Backup and Recovery (CBR) + |
+You can use a CBR backup to create a full-ECS image. + |
++ | +
Tag Management Service (TMS) + |
+You can add tags to images for convenient classification and search. + |
++ | +
Cloud Trace Service (CTS) + |
+CTS records IMS operations for query, auditing, or backtracking. + |
++ | +
If you have created and configured a Windows ECS based on your service requirements (for example, by installing software and setting up an application environment), you can create a system disk image based on this configured ECS. Then, all new ECSs created from this image will have the same software and environment preinstalled.
+Creating a system disk image does not affect the running of services on the ECS or cause data loss.
+The following figure shows the process of creating a system disk image from an ECS.
+
The ECS must be created from a private image. If it is created from a public image, the system disk image cannot be exported.
+The image creation does not affect service running on the ECS.
+In this process, do not stop, start, or restart the ECS, or the image creation may fail.
+Before creating a private image from an ECS:
+For details, see steps 2 to 5 in Optimization Process.
+
If an ECS is created from a public image, Cloudbase-Init has been installed by default. You can follow the guide in the prerequisites to verify the installation.
+The IMS console is displayed.
+Table 1 and Table 2 list the parameters in the Image Type and Source and Image Information areas, respectively.
+ +Parameter + |
+Description + |
+
|---|---|
Type + |
+Select System disk image. + |
+
Source + |
+Select ECS and select an ECS with required configurations. + |
+
Parameter + |
+Description + |
+
|---|---|
Encryption + |
+This parameter specifies whether the image will be encrypted. The value is provided by the system and cannot be changed. +
|
+
Name + |
+Set a name for the image. + |
+
Tag + |
+(Optional) Set a tag key and a tag value for the image to make identification and management of your images easier. + |
+
Description + |
+(Optional) Enter a description of the image. + |
+
The time required for creating an image depends on the ECS system disk size, network quality, and the number of concurrent tasks. When the image status changes to Normal, the image creation is complete.
+
After a system disk image is created, you can use either of the following methods to migrate data between two servers:
+If a private image is created from an ECS or external image file and the VM where the ECS or external image file is located is configured with a static IP address, you need to change the NIC attribute to DHCP so that the new ECSs created from the private image can dynamically obtain an IP address.
+This section uses Windows Server 2008 R2 as an example to describe how to configure DHCP. For details about how to configure DHCP on ECSs running other OSs, see the relevant OS documentation.
+
When registering an external image file as a private image, configure DHCP on the VM where the external image file is located. You are advised to configure DHCP on the VM and then export the image file.
+You have logged in to the ECS used to create a Windows private image.
+For details about how to log in to an ECS, see Elastic Cloud Server User Guide.
+

You are advised to record the original network information so that you can restore the network if necessary.
+The system will automatically obtain an IP address.
+No. The system disk image of an ECS is a VM file that contains a system running environment and does not have an installation boot program. Therefore, it cannot be used on a physical server.
+If you want to remotely access an ECS, enable remote desktop connection for the source ECS when creating a private image. This function must be enabled for GPU-accelerated ECSs.
+
When registering an external image file as a private image, enable remote desktop connection on the VM where the external image file is located. You are advised to enable this function on the VM and then export the image file.
+You have logged in to the ECS used to create a Windows private image.
+For details about how to log in to an ECS, see Elastic Cloud Server User Guide.
+On the ECS, choose Start > Control Panel. Under Appearance and Personalization, click Adjust screen resolution. Then select a proper value from the Resolution drop-down list box.
+
If a private image is created from an ECS or external image file and the VM where the ECS or external image file is located is configured with a static IP address, you need to change the NIC attribute to DHCP so that the new ECSs created from the private image can dynamically obtain an IP address.
+The configuration method varies depending on OSs.
+
When registering an external image file as a private image, configure DHCP on the VM where the external image file is located. You are advised to configure DHCP on the VM and then export the image file.
+You have logged in to the ECS used to create a Windows private image.
+For details about how to log in to an ECS, see Elastic Cloud Server User Guide.
+This section uses Ubuntu 14.04 as an example to describe how to query and configure NIC attributes of an ECS.
+vi /etc/network/interfaces
+

You can insert a number sign (#) in front of each line of static IP address configuration to comment it out.
+
If the ECS has multiple NICs, you must configure DHCP for all the NICs.
+
The system saves the configuration and exits the vi editor.
+Configure DHCP to enable the ECS to obtain IP addresses continuously.
+If multiple data disks are attached to the ECS used to create a private image, ECSs created from the image may be unavailable. Therefore, you need to detach all data disks from the ECS before using it to create a private image.
+This section describes how to detach all data disks from an ECS.
+You have logged in to the ECS used to create a Linux private image.
+Run the following command to check the number of disks attached to the ECS:
+fdisk -l
+ +/dev/vda1 on / type ext4 (rw,relatime,data=ordered)+
/dev/vda1 on / type ext4 (rw,relatime,data=ordered) +/dev/vdb1 on /mnt/test type ext4 (rw,relatime,data=ordered)+
vi /etc/fstab
+The /etc/fstab file contains information about the file systems and storage devices automatically attached to the ECS when the ECS starts. The configuration about data disks automatically attached to the ECS needs to be deleted, for example, the last line shown in the following figure.
+
Run the following command to detach the disks:
+umount /dev/vdb1
+If the command output contains no information about the data disks, they have been detached from the ECS.
+If you have created and configured a Linux ECS based on your service requirements (for example, by installing software and setting up an application environment), you can create a system disk image based on this configured ECS. Then, all new ECSs created from this image will have the same software and environment preinstalled.
+Creating a system disk image does not affect the running of services on the ECS or cause data loss.
+The following figure shows the process of creating a system disk image from an ECS.
+
The ECS must be created from a private image. If it is created from a public image, the system disk image cannot be exported.
+The image creation does not affect service running on the ECS.
+In this process, do not stop, start, or restart the ECS, or the image creation may fail.
+Before creating a private image from an ECS:
+For details, see steps 2 to 6 in Optimization Process.
+
If an ECS is created from a public image, Cloud-Init has been installed by default. You can follow the guide to verify the installation.
+The IMS console is displayed.
+Table 1 and Table 2 list the parameters in the Image Type and Source and Image Information areas, respectively.
+ +Parameter + |
+Description + |
+
|---|---|
Type + |
+Select System disk image. + |
+
Source + |
+Select ECS and select an ECS with required configurations. + |
+
Parameter + |
+Description + |
+
|---|---|
Encryption + |
+This parameter specifies whether the image will be encrypted. The value is provided by the system and cannot be changed. +
|
+
Name + |
+Set a name for the image. + |
+
Tag + |
+(Optional) Set a tag key and a tag value for the image to make identification and management of your images easier. + |
+
Description + |
+(Optional) Enter a description of the image. + |
+
The time required for creating an image depends on the ECS system disk size, network quality, and the number of concurrent tasks. When the image status changes to Normal, the image creation is complete.
+
After a system disk image is created, you can use either of the following methods to migrate data between two servers:
+You can import a local image or a system disk image from another cloud platform to the current cloud. After an image is imported, you can use it to create ECSs or reinstall the OSs of existing ECSs.
+Figure 1 shows the process of creating a private image.
+ +As shown in the figure, the following steps are required to register an external image file as a private image:
+You are advised to use OBS Browser to upload external image files to OBS buckets. For details, see Object Storage Service User Guide.
+
Register an image file uploaded to the OBS bucket as a private image.
+The IMS console is displayed.
+Table 1 and Table 2 list the parameters in the Image Type and Source and Image Information areas, respectively.
+ +Parameter + |
+Description + |
+
|---|---|
Type + |
+Select System disk image. + |
+
Source + |
+Select Image File for Source. Select the bucket storing the image file from the list and then select the image file. + |
+
Enable Fast Create + |
+This parameter is available only when you select a ZVHD2 or RAW image file. +This function enables fast image creation and supports import of large files (up to 1 TB) as long as the files to be uploaded are converted to ZVHD2 or RAW format and optimized. If you have a file that meets the requirements, select Enable Fast Create and select the confirmation information following Image File Preparation. + NOTE:
+To learn how to convert image file formats and generate bitmap files, see Quickly Importing an Image File. + |
+
Parameter + |
+Description + |
+
|---|---|
Enable automatic configuration + |
+If you select this option, the system will automatically check and optimize the image file. For details, see What Will the System Do to an Image File When I Use the File to Register a Private Image? + |
+
Function + |
+Specifies whether the image is used to create ECSs or BMSs. The value can be ECS system disk image or BMS system disk image. This section uses ECS system disk image as an example. + |
+
Boot Mode + |
+This parameter is optional. The value can be BIOS or UEFI. For details about the differences between the two, 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. + |
+
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. + NOTE:
+
|
+
System Disk (GB) + |
+The system disk capacity. Ensure that this value is at least equal to the system disk size in the image file. + NOTE:
+If the uploaded VHD image is generated using qemu-img or similar tools, check the system disk size based on What Do I Do If the System Disk Size in a VHD Image File Exceeds the One I Have Specified on the Management Console When I Use This File to Register a Private Image? + |
+
Data Disk (GB) + |
+You can also add data disks to the image. You need to obtain an image file containing data disks in advance. This function is used to migrate VMs and data disks from other platforms to the current platform. +To add data disks, click A maximum of three data disks can be added. + |
+
Name + |
+Set a name for the image. + |
+
Encryption + |
+(Optional) If you want to encrypt the image, select KMS encryption and select the key to be used from the key list. After you select KMS encryption, the system will create a default master private key ims/default for you. You can also select a private key from the private key list. +For how to encrypt an image, see Creating Encrypted Images. + |
+
Tag + |
+(Optional) Set a tag key and a tag value for the image to make identification and management of your images easier. + |
+
Description + |
+(Optional) Enter a description of the image. + |
+
If you add data disks during image creation, a system disk image and data disk images will be generated. The number of data disk images depends on the number of data disks you add (a maximum of 3).
+
The time required for image registration is determined by the image file size. You may need to wait a long period of time for the image file to be successfully registered as 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.
+
The proper running of ECSs depends on the XEN Guest OS driver (PV driver) or KVM Guest OS driver (UVP VMTools). If no such a driver is installed, the performance of ECSs will be affected and some functions will be unavailable. Ensure that the PV driver or UVP VMTools has been installed for the image file as needed before it is exported from the original platform. Otherwise, the ECSs created from the image will fail to start.
+Upload the external image file to an OBS bucket. For details, see Uploading an External Image File.
+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.
+The IMS console is displayed.
+For details, see Elastic Cloud Server User Guide.
+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.
+Remotely log in to the ECS created in Step 3: Create an ECS to configure it.
+For details, see Creating a System Disk Image from a Windows ECS.
+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.
+Currently, you cannot directly download a public image. You can use the public image to create an ECS, use the ECS to create a private image, export the private image to your OBS bucket, and download the private image to your local PC.
+Helpful links:
+
Windows and SUSE Linux public images and the private images created from these public images cannot be exported.
+After registering an external image file as a private image on the cloud platform, you can use the image to create ECSs or change the OSs of existing ECSs.
+This section describes how to create an ECS from an image.
+Create an ECS by referring to Creating an ECS from an Image.
+Note the following when setting the parameters:
+You need to prepare an image file that meets the platform requirements.
+
Image File Property + |
+Requirement + |
+
|---|---|
OS + |
+
For details about the supported OS versions, see External Image File Formats and Supported OSs. These OSs support automatic configuration. For details, see What Will the System Do to an Image File When I Use the File to Register a Private Image? For other OSs, check and install the Guest OS driver. On the image registration page, select Other Windows. After the image is imported, whether the system is started depends on the driver integrity. + |
+
Image format + |
+VMDK, VHD, QCOW2, RAW, VHDX, QED, VDI, QCOW, ZVHD2, and ZVHD + |
+
Image size + |
+Maximum file size: 128 GB +If the image size is between 128 GB and 1 TB, convert the image file into the RAW or ZVHD2 format and import the image using fast import.
+
|
+
Network + |
+The NIC must be set to DHCP. Otherwise, the ECS startup or network capability will be abnormal. For details, see: + +The following value-added operations are optional: +
|
+
Tool + |
+You are advised to install Cloudbase-Init. +Cloudbase-Init is an open-source tool for cloud instance initialization. When creating ECSs from an image with Cloudbase-Init, you can use user data injection to inject customized initialization details (for example, an ECS login password) to the ECSs. You can also configure and manage a running ECS by querying and using metadata. If Cloudbase-Init is not installed, you cannot apply custom configurations to the ECSs. You will have to use the original password in the image file to log in to the ECSs. +For details, see Installing and Configuring Cloudbase-Init. + |
+
Driver + |
++ | +
Other requirements + |
+
|
+
You can import a local image or a system disk image from another cloud platform to the current cloud. After an image is imported, you can use it to create ECSs or reinstall the OSs of existing ECSs.
+Figure 1 shows the process of creating a private image.
+ +The procedure is as follows:
+You are advised to use OBS Browser to upload external image files to OBS buckets. For details, see Object Storage Service User Guide.
+
Register an image file uploaded to the OBS bucket as a private image.
+The IMS console is displayed.
+Table 1 and Table 2 list the parameters in the Image Type and Source and Image Information areas, respectively.
+ +Parameter + |
+Description + |
+
|---|---|
Type + |
+Select System disk image. + |
+
Source + |
+Select Image File for Source. Select the bucket storing the image file from the list and then select the image file. + |
+
Enable Fast Create + |
+This parameter is available only when you select a ZVHD2 or RAW image file. +This function enables fast image creation and supports import of large files (up to 1 TB) as long as the files to be uploaded are converted to ZVHD2 or RAW format and optimized. If you have a file that meets the requirements, select Enable Fast Create and select the confirmation information following Image File Preparation. + NOTE:
+To learn how to convert image file formats and generate bitmap files, see Quickly Importing an Image File. + |
+
Parameter + |
+Description + |
+
|---|---|
Enable automatic configuration + |
+If you select this option, the system will automatically check and optimize the image file. For details, see What Will the System Do to an Image File When I Use the File to Register a Private Image? + |
+
Function + |
+Specifies whether the image is used to create ECSs or BMSs. The value can be ECS system disk image or BMS system disk image. This section uses ECS system disk image as an example. + |
+
Boot Mode + |
+This parameter is optional. The value can be BIOS or UEFI. For details about the differences between the two, 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. + |
+
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. + NOTE:
+
|
+
System Disk (GB) + |
+The system disk capacity. Ensure that this value is at least equal to the system disk size in the image file. + NOTE:
+If the uploaded VHD image is generated using qemu-img or similar tools, check the system disk size based on What Do I Do If the System Disk Size in a VHD Image File Exceeds the One I Have Specified on the Management Console When I Use This File to Register a Private Image? + |
+
Data Disk (GB) + |
+You can also add data disks to the image. You need to obtain an image file containing data disks in advance. This function is used to migrate VMs and data disks from other platforms to the current platform. +To add data disks, click A maximum of three data disks can be added. + |
+
Name + |
+Set a name for the image. + |
+
Encryption + |
+(Optional) If you want to encrypt the image, select KMS encryption and select the key to be used from the key list. After you select KMS encryption, the system will create a default master private key ims/default for you. You can also select a private key from the private key list. +For how to encrypt an image, see Creating Encrypted Images. + |
+
Tag + |
+(Optional) Set a tag key and a tag value for the image to make identification and management of your images easier. + |
+
Description + |
+(Optional) Enter a description of the image. + |
+
If you add data disks during image creation, a system disk image and data disk images will be generated. The number of data disk images depends on the number of data disks you add (a maximum of 3).
+
The time required for image registration is determined by the image file size. You may need to wait a long period of time for the image file to be successfully registered as a private image.
+After registering an external image file as a private image on the cloud platform, you can use the image to create ECSs or change the OSs of existing ECSs.
+This section describes how to create an ECS from an image.
+Create an ECS by referring to Creating an ECS from an Image.
+Note the following when setting the parameters:
+You need to prepare an image file that meets the platform requirements.
+
Image File Property + |
+Requirement + |
+
|---|---|
OS + |
+
For details about the supported OS versions, see External Image File Formats and Supported OSs. These OSs support automatic configuration. For details, see What Will the System Do to an Image File When I Use the File to Register a Private Image? For other OSs, check and install the VirtIO driver (see Installing Native KVM Drivers). On the image registration page, select Other Linux. After the image is imported, whether the system is started depends on the driver integrity. + |
+
Image format + |
+VMDK, VHD, QCOW2, RAW, VHDX, QED, VDI, QCOW, ZVHD2, and ZVHD + |
+
Image size + |
+Maximum file size: 128 GB +If the image size is between 128 GB and 1 TB, convert the image file into the RAW or ZVHD2 format and import the image using fast import.
+
|
+
Network + |
+The NIC must be set to DHCP and files must be deleted from the network role directory. Otherwise, the ECS startup or network capability will be abnormal. For details, see: + +The following value-added operations are optional: +
|
+
Tool + |
+You are advised to install Cloud-Init. +Cloud-Init is an open-source tool for cloud instance initialization. When creating ECSs from an image with Cloud-Init, you can use user data injection to inject customized initialization details (for example, an ECS login password) to the ECSs. You can also configure and manage a running ECS by querying and using metadata. If Cloud-Init is not installed, you cannot apply custom configurations to the ECSs. You will have to use the original password in the image file to log in to the ECSs. +For details, see Installing Cloud-Init. + |
+
Driver + |
++ | +
File system + |
++ | +
Other requirements + |
+
|
+
You can modify the following attributes of a private image:
+NIC multi-queue enables multiple CPUs to process NIC interruptions for load balancing. For details, see How Do I Enable NIC Multi-Queue for an Image?
+Use any of the following methods to modify an image:
+The IMS console is displayed.
+The IMS console is displayed.
+You can use a public, private, or shared image to create an ECS.
+The IMS console is displayed.
+When you use a system disk image to create an ECS, you can set the ECS specifications and system disk type without considering those in the image, but the system disk size can only be larger than that in the image.
+You can delete private images that will no longer be used.
+The IMS console is displayed.
+
To delete multiple images:
+This parameter is available only when you have selected full-ECS images from the image list.
+If you select this option, the system will delete CSBS backups of the full-ECS images.
+
If CSBS backups failed to be deleted, the cause may be that these backups are being created and cannot be deleted. In this case, manually delete them as prompted.
+Yes. You can specify the CPU, memory, bandwidth, data disks of the new ECSs if necessary. You can also specify their system disk size. The value must be smaller than 1024 GB but no less than the system disk size in the 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.
+
The proper running of ECSs depends on the Xen or KVM driver. If no such a driver is installed, the performance of ECSs will be affected and some functions will be unavailable. Ensure that the Xen or KVM driver has been installed for the image file as needed before it is exported from the original platform. Otherwise, the ECSs created from the image will fail to start.
+For details, see How Do I Install Native Xen and KVM Drivers?
+Upload the external image file to an OBS bucket. For details, see Uploading an External Image File.
+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.
+Create an ECS from the private image.
+The IMS console is displayed.
+For details, see Elastic Cloud Server User Guide.
+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.
+Remotely log in to the ECS created in Step 3: Create an ECS to configure it.
+Create a private image from the ECS. For details, see Creating a System Disk Image from a Linux ECS.
+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.
+If you selected an incorrect OS, ECSs may fail to be created from the private image. If the configured system disk size is less than the one in the image file, image registration will fail.
+In such cases, delete the incorrect image and create a new one using correct parameter settings.
+Installing Guest OS drivers on an ECS improves your experience in using the ECS. In addition, it also ensures high reliability and stability of ECSs.
+Possible causes:
+Before using an ECS or external image file to create a private image, you need to pre-configure the ECS or the source VM of the image file. If you do not perform the pre-configuration, there will be the following impacts:
+No. Currently, only the VMDK, VHD, RAW, QCOW2, VHDX, QED, VDI, QCOW, ZVHD2, and ZVHD formats are supported.
+Images of the -flat.vmdk format and image file packages containing snapshot volumes or delta volumes are not supported. You can use qemu-img to convert an image to one of the supported formats before uploading it to the cloud platform.
+ +Generally, this is because the xen-blkfront.ko module is not loaded during the startup. You need to modify OS kernel startup parameters. Figure 1 shows the startup screen after the login to the ECS.
+ +Perform the following operations to modify OS kernel boot parameters:
+
These operations must be performed after the OS starts. You are advised to modify kernel boot parameters in the ECS used for creating the image.
+vi /boot/grub2/grub.cfg
+
Search for the line that contains root=UUID= and add xen_emul_unplug=all to the end of the line.
+menuentry 'CentOS Linux (3.10.0-229.el7.x86_64) 7 (Core) with debugging' --class centos --class gnu-linux --class gnu --class os --unrestricted $menuentry_id_option 'gnulinux-3.10.0-229.el7.x86_64-advanced-bf3cc825-7638-48d8-8222-cd2f412dd0de' {
+ load_video
+ set gfxpayload=keep
+ insmod gzio
+ insmod part_msdos
+ insmod ext2
+ set root='hd0,msdos1'
+ if [ x$feature_platform_search_hint = xy ]; then
+ search --no-floppy --fs-uuid --set=root --hint='hd0,msdos1' bf3cc825-7638-48d8-8222-cd2f412dd0de
+ else
+ search --no-floppy --fs-uuid --set=root bf3cc825-7638-48d8-8222-cd2f412dd0de
+ fi
+ linux16 /boot/vmlinuz-3.10.0-229.el7.x86_64 root=UUID=bf3cc825-7638-48d8-8222-cd2f412dd0de xen_emul_unplug=all ro crashkernel=auto rhgb quiet systemd.log_level=debug systemd.log_target=kmsg
+ initrd16 /boot/initramfs-3.10.0-229.el7.x86_64.img
+}
+Yes. However, the value must be smaller than 30,768 GB but no less than the system disk size in the image.
+
Ensure that your ECS OS supports the system disk size you specified.
+To ensure that you can use the user data injection function to inject initial custom information into ECSs created from a private image (such as setting the ECS login password), install Cloudbase-Init on the ECS used to create the image.
+Download the Cloudbase-Init installation package of the appropriate version based on the OS architecture from the Cloudbase-Init official website (http://www.cloudbase.it/cloud-init-for-windows-instances/).
+Cloudbase-Init has two versions: stable and beta.
+To obtain the stable version, visit the following paths:
+To obtain the beta version, visit the following paths:
+ +
The version number shown in the figure is for reference only.
+

The version number shown in the figure is for reference only.
+
NetBIOS contains no more than 15 characters due to Windows system restrictions.
+retry_count=40 +retry_count_interval=5+
[openstack] +add_metadata_private_ip_route=False+
Change the value of user_password_length to customize the password length.
+In the Windows command line, run the following command to release the current DHCP address:
+ipconfig /release
+
This operation will interrupt network connection and adversely affect ECS use. The network will automatically recover after the ECSs are started again.
+Windows has three types of SAN policies: OnlineAll, OfflineShared, and OfflineInternal.
+ +Type + |
+Description + |
+
|---|---|
OnlineAll + |
+All newly detected disks are automatically brought online. + |
+
OfflineShared + |
+All disks on sharable buses, such as iSCSI and FC, are left offline by default, while disks on non-sharable buses are kept online. + |
+
OfflineInternal + |
+All newly detected disks are left offline. + |
+
diskpart
+san policy=onlineall
+To ensure that you can use the user data injection function to inject initial custom information into ECSs created from a private image (such as setting the ECS login password), install Cloud-Init on the ECS used to create the image.
+For details, see Check Whether Cloud-Init Has Been Installed.
+You can install Cloud-Init using either of the following methods: (Recommended) Install Cloud-Init Using the Official Installation Package and Install Cloud-Init Using the Official Source Code Package and pip.
+Perform the operations provided here to check whether Cloud-Init has been installed.
+The methods of checking whether Cloud-Init is installed vary depending on the OSs. Take CentOS 6 as an example. Run the following command to check whether Cloud-Init is installed:
+rpm -qa |grep cloud-init
+If information similar to the following is displayed, Cloud-Init has been installed:
+cloud-init-0.7.5-10.el6.centos.2.x86_64+
cd /root/.ssh
+rm authorized_keys
+cd /home/centos/.ssh
+rm authorized_keys
+sudo rm -rf /var/lib/cloud/*
+
Do not restart the ECS after performing the configuration. Otherwise, you need to configure it again.
+The method of installing Cloud-Init on an ECS varies depending on the OS. Perform the installation operations as user root.
+The following describes how to install Cloud-Init on an ECS running SUSE Linux, CentOS, Fedora, Debian, and Ubuntu. For other OS types, install the required type of Cloud-Init. For example, you need to install coreos-cloudinit on ECSs running CoreOS.
+Paths for obtaining the Cloud-Init installation package for SUSE Linux
+http://ftp5.gwdg.de/pub/opensuse/repositories/Cloud:/Tools/
+http://download.opensuse.org/repositories/Cloud:/Tools/
+
Select the required repo installation package in the provided paths.
+Take SUSE Enterprise Linux Server 12 as an example. Perform the following steps to install Cloud-Init:
+zypper ar http://ftp5.gwdg.de/pub/opensuse/repositories/Cloud:/Tools/SLE_12_SP3/Cloud:Tools.repo
+chkconfig cloud-init-local on; chkconfig cloud-init on; chkconfig cloud-config on; chkconfig cloud-final on
+service cloud-init-local status; service cloud-init status; service cloud-config status; service cloud-final status
+systemctl enable cloud-init-local.service cloud-init.service cloud-config.service cloud-final.service
+systemctl status cloud-init-local.service cloud-init.service cloud-config.service cloud-final.service
+
For SUSE and openSUSE, perform the following steps to disable dynamic change of the ECS name:
+vi etc/sysconfig/network/dhcp
+Table 1 lists the Cloud-Init installation paths for CentOS. Select the required installation package from the following addresses.
+ +OS Type + |
+Version + |
+How to Obtain + |
+
|---|---|---|
CentOS + |
+6 32-bit + |
++ | +
6 64-bit + |
+https://archives.fedoraproject.org/pub/archive/epel/6/x86_64/ + |
+|
7 64-bit + |
++ | +
Run the following commands to install Cloud-Init on an ECS running CentOS 6.5 64-bit (example):
+yum install https://archives.fedoraproject.org/pub/archive/epel/6/x86_64/epel-release-xx-xx.noarch.rpm
+yum install cloud-init
+
xx-xx indicates the version of Extra Packages for Enterprise Linux (EPEL) required by the current OS.
+Before installing Cloud-Init, ensure that the network installation source address has been configured for the OS by checking whether the /etc/yum.repo.d/fedora.repo file contains the installation source address of the software package. If the file does not contain the address, configure the address by following the instructions on the Fedora official website.
+Run the following command to install Cloud-Init:
+yum install cloud-init
+Before installing Cloud-Init, ensure that the network installation source address has been configured for the OS by checking whether the /etc/apt/sources.list file contains the installation source address of the software package. If the file does not contain the address, configure the address by following the instructions on the Debian or Ubuntu official website.
+Run the following commands to install Cloud-Init:
+apt-get update
+apt-get install cloud-init
+The following operations use Cloud-Init 0.7.9 as an example to describe how to install Cloud-Init.
+Download cloud-init-0.7.9.tar.gz from the following path:
+https://launchpad.net/cloud-init/trunk/0.7.9/+download/cloud-init-0.7.9.tar.gz
+
If the ~/.pip/ directory does not exist, run the mkdir ~/.pip command to create it.
+[global] +index-url = https://<$mirror>/simple/ +trusted-host = <$mirror>+
Replace <$mirror> with a public network PyPI source.
+Public network PyPI source: https://pypi.python.org/
+pip install [--upgrade] /home/cloud-init-0.7.9.tar.gz
+cloud-init 0.7.9+
chkconfig --add cloud-init-local; chkconfig --add cloud-init; chkconfig --add cloud-config; chkconfig --add cloud-final
+chkconfig cloud-init-local on; chkconfig cloud-init on; chkconfig cloud-config on; chkconfig cloud-final on
+service cloud-init-local status; service cloud-init status; service cloud-config status; service cloud-final status
+systemctl enable cloud-init-local.service cloud-init.service cloud-config.service cloud-final.service
+systemctl status cloud-init-local.service cloud-init.service cloud-config.service cloud-final.service
+
If you install Cloud-Init using the official source code package and pip, pay attention to the following:
+useradd syslog
+groupadd adm
+usermod -g adm syslog
+For a user that needs to be added to a domain and uses the domain account to log in to Windows, Sysprep is required before a private image is created. Otherwise, the image will contain information about the original ECS, especially the SID. ECSs with the same SID cannot be added to a domain. If Windows does not require any user or ECS to be added to a domain, you do not need to run Sysprep.
+
Sysprep can only be used for configuring a new Windows installation. You can run Sysprep multiple times to install and configure Windows. However, you can reset and activate a Windows OS only three times, and you are not allowed to use Sysprep to re-configure an existing Windows OS.
+
In the Windows command line, enter the following command to check how many times you can run Sysprep in the displayed Windows Script Host dialog box:
+slmgr /dlv
+If the value of Remaining Windows rearm count is 0, you cannot run Sysprep.
+You can share your private images with other tenants. The tenants who accept the shared images can use the images to create ECSs of the same specifications.
+If you want to share a private image with another tenant, the procedure is as follows:
+ +If you have any questions, see Image Sharing FAQs.
+Before a tenant shares an image with you, you need to provide your project ID.
+The IMS console is displayed.
+On the My Credentials page, view the project ID in the project list.
+
After obtaining the project ID from a tenant, you can share specified private images with the tenant. You can share a single image or multiple images as needed.
+The IMS console is displayed.
+To share images with more than one tenant, separate their project IDs with commas (,).
+
You can enter a maximum of 100 project IDs at a time.
+The IMS console is displayed.
+To share an image with more than one tenant, separate their project IDs with commas (,).
+
You can enter a maximum of 100 project IDs at a time.
+After you share images with a tenant, the tenant can accept the shared images on the Images Shared with Me page on the IMS console. For detailed operations, see Accepting or Rejecting Shared Images.
+After another tenant shares images with you, you will receive a message. You can choose to accept or reject all or some of the shared images.
+
If you are not in the same region as the tenant sharing the images with you, you will not receive the message.
+The IMS console is displayed.
+A message is displayed above the image list asking you whether to accept the shared images.
+
If no message is displayed, check whether you have selected a correct region.
+This dialog box is displayed when the shared image is a full-ECS image.
+When accepting a full-ECS image, you must specify a vault for storing the CBR backups associated with the full-ECS image. The vault capacity must be no less than the total capacities of the system disk and data disk backups.
+
For more information about server backup vaults, see Cloud Backup and Recovery User Guide.
+A pending shared image is not displayed in the shared image list.
+You can reject accepted images if you no longer need them.
+After an image is rejected, it will not be displayed on the Images Shared with Me page.
+You have accepted images shared by other users.
+The IMS console is displayed.
+You can stop sharing images. After you stop sharing an image:
+You have shared private images with others.
+The IMS console is displayed.
+In addition to the tenants you have shared images with, you can add more tenants who can use the shared images.
+The IMS console is displayed.
+To add multiple tenants, enter their project IDs and separate them with commas. Click OK.
+This section describes how to delete image recipients who can use shared images.
+The IMS console is displayed.
+You are advised to enable automatic configuration when registering a private image using an image file. Then, the system will perform the following operations:
+
For the following image files, the system does not copy this driver after Enable automatic configuration is selected:
+You can export a private image to a standard OBS bucket and then download it to your local PC.
+
Fast Export is unavailable for encrypted images.
+An OBS bucket is available in the region where the private image is located.
+If no OBS bucket is available, create one by referring to Object Storage Service User Guide. Select Standard for Storage Class.
+The IMS console is displayed.
+
For details about differences between export and fast export, see What Are the Differences Between Import/Export and Fast Import/Export?
+
to expand the bucket list and select an OBS bucket for storing the exported image.You can view the image export progress above the private image list.
+After the image is exported successfully, you can download it from the OBS bucket through the management console or OBS Browser+.
+This may be caused by a disk partition ID change after the cross-platform image import. As a result, no partition can be found based on the original disk partition ID in the image. In this case, you need to change the disk partition in the image (UUID=UUID of the disk partition).
+The following uses openSUSE 13.2 as an example to describe how to change the partition name.
+The example command output is as follows.
+total 0 +lrwxrwxrwx 1 root root 10 Jul 22 01:35 ata-QEMU_HARDDISK_QM00001 -> ../../xvda +lrwxrwxrwx 1 root root 11 Jul 22 01:35 ata-QEMU_HARDDISK_QM00001-part1 -> ../../xvda1 +lrwxrwxrwx 1 root root 12 Jul 22 01:35 ata-QEMU_HARDDISK_QM00001-part10 -> ../../xvda10 +lrwxrwxrwx 1 root root 11 Jul 22 01:35 ata-QEMU_HARDDISK_QM00001-part2 -> ../../xvda2 +lrwxrwxrwx 1 root root 11 Jul 22 01:35 ata-QEMU_HARDDISK_QM00001-part5 -> ../../xvda5 +lrwxrwxrwx 1 root root 11 Jul 22 01:35 ata-QEMU_HARDDISK_QM00001-part6 -> ../../xvda6 +lrwxrwxrwx 1 root root 11 Jul 22 01:35 ata-QEMU_HARDDISK_QM00001-part7 -> ../../xvda7 +lrwxrwxrwx 1 root root 11 Jul 22 01:35 ata-QEMU_HARDDISK_QM00001-part8 -> ../../xvda8 +lrwxrwxrwx 1 root root 11 Jul 22 01:35 ata-QEMU_HARDDISK_QM00001-part9 -> ../../xvda9 +lrwxrwxrwx 1 root root 10 Jul 22 01:35 ata-QEMU_HARDDISK_QM00005 -> ../../xvde +lrwxrwxrwx 1 root root 10 Jul 22 01:35 scsi-SATA_QEMU_HARDDISK_QM00001 -> ../../xvda +lrwxrwxrwx 1 root root 11 Jul 22 01:35 scsi-SATA_QEMU_HARDDISK_QM00001-part1 -> ../../xvda1 +lrwxrwxrwx 1 root root 12 Jul 22 01:35 scsi-SATA_QEMU_HARDDISK_QM00001-part10 -> ../../xvda10 +lrwxrwxrwx 1 root root 11 Jul 22 01:35 scsi-SATA_QEMU_HARDDISK_QM00001-part2 -> ../../xvda2 +lrwxrwxrwx 1 root root 11 Jul 22 01:35 scsi-SATA_QEMU_HARDDISK_QM00001-part5 -> ../../xvda5 +lrwxrwxrwx 1 root root 11 Jul 22 01:35 scsi-SATA_QEMU_HARDDISK_QM00001-part6 -> ../../xvda6 +lrwxrwxrwx 1 root root 11 Jul 22 01:35 scsi-SATA_QEMU_HARDDISK_QM00001-part7 -> ../../xvda7 +lrwxrwxrwx 1 root root 11 Jul 22 01:35 scsi-SATA_QEMU_HARDDISK_QM00001-part8 -> ../../xvda8 +lrwxrwxrwx 1 root root 11 Jul 22 01:35 scsi-SATA_QEMU_HARDDISK_QM00001-part9 -> ../../xvda9 +lrwxrwxrwx 1 root root 10 Jul 22 01:35 scsi-SATA_QEMU_HARDDISK_QM00005 -> ../../xvde+
ata-QEMU_HARDDISK_xxx and scsi-SATA_QEMU_HARDDISK_xxx indicate that the disk of the ECS is simulated using Quick EMUlator (QEMU). The content on the left of -> is the disk partition ID, and that on the right of -> is the partition name.
+The example command output is as follows.
+total 0 +lrwxrwxrwx 1 root root 11 Jul 22 01:35 45ecd7a0-29da-4402-a017-4564a62308b8 -> ../../xvda5 +lrwxrwxrwx 1 root root 11 Jul 22 01:35 55386c6a-9e32-41d4-af7a-e79596221f51 -> ../../xvda9 +lrwxrwxrwx 1 root root 11 Jul 22 01:35 55f36660-9bac-478c-a701-7ecc5347f789 -> ../../xvda8 +lrwxrwxrwx 1 root root 11 Jul 22 01:35 780f36bc-0ada-4c98-9a8d-44570d65333d -> ../../xvda1 +lrwxrwxrwx 1 root root 11 Jul 22 01:35 b3b7c47f-6a91-45ef-80d6-275b1cc16e19 -> ../../xvda6 +lrwxrwxrwx 1 root root 11 Jul 22 01:35 ea63b55d-3b6e-4dcd-8986-956b72bac3e9 -> ../../xvda7 +lrwxrwxrwx 1 root root 12 Jul 22 01:35 eb3cc645-925e-4bc5-bedf-c2a6f3b65809 -> ../../xvda10+
The content on the left of -> is the disk partition UUID, and that on the right of -> is the partition name. Obtain the relationship between the disk partition name, partition ID, and partition UUID.
+vi /etc/fstab
+The example command output is as follows.
+/dev/disk/by-id/scsi-SATA_QEMU_HARDDISK_QM00001-part5 / ext3 defaults,errors=panic 1 1 +/dev/disk/by-id/scsi-SATA_QEMU_HARDDISK_QM00001-part1 /boot ext3 defaults,errors=panic 1 2 +/dev/disk/by-id/scsi-SATA_QEMU_HARDDISK_QM00001-part6 /home ext3 nosuid,errors=panic 1 2 +/dev/disk/by-id/scsi-SATA_QEMU_HARDDISK_QM00001-part10 /opt ext3 defaults,errors=panic 1 2 +/dev/disk/by-id/scsi-SATA_QEMU_HARDDISK_QM00001-part7 /tmp ext3 nodev,nosuid,errors=panic 1 2 +/dev/disk/by-id/scsi-SATA_QEMU_HARDDISK_QM00001-part9 /usr ext3 defaults,errors=panic 1 2 +/dev/disk/by-id/scsi-SATA_QEMU_HARDDISK_QM00001-part8 /var ext3 nodev,nosuid,errors=panic 1 2 +sysfs /sys sysfs noauto 0 0 +proc /proc proc defaults 0 0 +usbfs /proc/bus/usb usbfs noauto 0 0 +devpts /dev/pts devpts mode=0620,gid=5 0 0 +/dev/cdrom /media/ udf,iso9660 noexec,noauto,nouser,nodev,nosuid 1 2 +tmpfs /dev/shm tmpfs noexec,nodev,nosuid 0 0+
The values in the first column are the disk partition IDs.
+UUID=45ecd7a0-29da-4402-a017-4564a62308b8 / ext3 defaults,errors=panic 1 1 +UUID=780f36bc-0ada-4c98-9a8d-44570d65333d /boot ext3 defaults,errors=panic 1 2 +UUID=b3b7c47f-6a91-45ef-80d6-275b1cc16e19 /home ext3 nosuid,errors=panic 1 2 +UUID=eb3cc645-925e-4bc5-bedf-c2a6f3b65809 /opt ext3 defaults,errors=panic 1 2 +UUID=ea63b55d-3b6e-4dcd-8986-956b72bac3e9 /tmp ext3 nodev,nosuid,errors=panic 1 2 +UUID=55386c6a-9e32-41d4-af7a-e79596221f51 /usr ext3 defaults,errors=panic 1 2 +UUID=55f36660-9bac-478c-a701-7ecc5347f789 /var ext3 nodev,nosuid,errors=panic 1 2 +sysfs /sys sysfs noauto 0 0 +proc /proc proc defaults 0 0 +usbfs /proc/bus/usb usbfs noauto 0 0 +devpts /dev/pts devpts mode=0620,gid=5 0 0 +/dev/cdrom /media/ udf,iso9660 noexec,noauto,nouser,nodev,nosuid 1 2 +tmpfs /dev/shm tmpfs noexec,nodev,nosuid 0 0+
Ensure that the UUIDs are correct. Otherwise, the ECS cannot start properly.
+The system boot configuration files vary depending on the OS. Confirm the boot configuration file of the current OS.
+The boot file in this example is /boot/grub/menu.lst. Run the following command to check it:
+vi /boot/grub/menu.lst
+default 0 +timeout 3 +title xxx Server OS - xxxxxx +kernel /boot/vmlinuz-3.0.101-0.47.52-default root=/dev/disk/by-id/scsi-SATA_QEMU_HARDDISK_QM00001-part5 resume= memmap=0x2000000$0x3E000000 nmi_watchdog=2 crashkernel=512M-:256M console=ttyS0,115200 console=tty0 xen_emul_unplug=all +initrd /boot/initrd-3.0.101-0.47.52-default+
Change the disk partition name in the /boot/grub/menu.lst file in 6 to UUID=UUID of the disk partition based on the query results in 1 and 2.
+default 0 +timeout 3 +title xxx Server OS - xxxxxx +kernel /boot/vmlinuz-3.0.101-0.47.52-default root=UUID=45ecd7a0-29da-4402-a017-4564a62308b8 resume= memmap=0x2000000$0x3E000000 nmi_watchdog=2 crashkernel=512M-:256M console=ttyS0,115200 console=tty0 xen_emul_unplug=all +initrd /boot/initrd-3.0.101-0.47.52-default+
Table 1 lists the PV driver software packages required for optimizing Windows private images.
+ +Software Package + |
+OS + |
+How to Obtain + |
+
|---|---|---|
pvdriver-win2008R2-64bit.exe + |
+Windows Server 2008 R2 64bit + |
+https://osdriver.obs.eu-de.otc.t-systems.com/pvdriver/windows/pvdriver-win2008R2-64bit.exe + |
+
pvdriver-win2012R2-64bit.exe + |
+Windows Server 2012 R2 64bit + |
+https://osdriver.obs.eu-de.otc.t-systems.com/pvdriver/windows/pvdriver-win2012R2-64bit.exe + |
+
pvdriver-win2016-64bit.exe + |
+Windows Server 2016 64bit + |
+https://osdriver.obs.eu-de.otc.t-systems.com/pvdriver/windows/pvdriver-win2016-64bit.exe + |
+
pvdriver-win2019-64bit.exe + |
+Windows Server 2019 64bit + |
+https://osdriver.obs.eu-de.otc.t-systems.com/pvdriver/windows/pvdriver-win2019-64bit.exe + |
+
pvdriver-win7-64bit.exe + |
+Windows 7 64bit + |
+https://osdriver.obs.eu-de.otc.t-systems.com/pvdriver/windows/pvdriver-win7-64bit.exe + |
+
pvdriver-win10-64bit.exe + |
+Windows 10 64bit + |
+https://osdriver.obs.eu-de.otc.t-systems.com/pvdriver/windows/pvdriver-win10-64bit.exe + |
+
Table 2 lists the UVP VMTools software packages required for optimizing Windows private images.
+ +Software Package + |
+OS + |
+How to Obtain + |
+
|---|---|---|
vmtools-WIN2008R2-x64.exe + |
+Windows Server 2008 R2 + |
+https://obs.eu-de.otc.t-systems.com/osdriver/vmtools/windows/vmtools-WIN2008R2-x64.exe + |
+
vmtools-WIN2012-x64.exe + |
+Windows Server 2012 R2 + |
+https://obs.eu-de.otc.t-systems.com/osdriver/vmtools/windows/vmtools-WIN2012R2-x64.exe + |
+
vmtools-WIN2016-x64.exe + |
+
|
+https://obs.eu-de.otc.t-systems.com/osdriver/vmtools/windows/vmtools-WIN2016-x64.exe + |
+
Cause 2: Images can only be shared within the same region. If you are attempting to share an image across regions, your attempt will fail.
+Before using an ECS or external image file to create a private image, ensure that UVP VMTools has been installed in the OS to enable subsequently created ECSs to support KVM virtualization and improve network performance.
+
If you do not install UVP VMTools, NICs of the ECS may not be detected and the ECS cannot communicate with other resources.
+UVP VMTools has been installed by default when you use a public image to create ECSs. You can perform the following operations to verify the installation:
+Open the version configuration file to check whether UVP VMTools is the latest:
+C:\Program Files (x86)\virtio\bin\version
+If the version is 2.5.0 or later, the current UVP VMTools can be used. Otherwise, perform operations in Installing UVP VMTools to install UVP VMTools.
+The following operations describe how to install UVP VMTools. vmtools-WIN2008R2-x64.exe extracted from vmtools-WIN2008R2-x64.zip is used as an example.
+For details about how to log in to an ECS, see Elastic Cloud Server User Guide.
+
You must log in to the ECS using VNC. Remote desktop connection is not allowed because the NIC driver needs to be updated during the installation but the NIC is in use for the remote desktop connection. As a result, the installation will fail.
+
Perform the following steps to verify the installation of UVP VMTools:
+When using an ECS or external image file to create a private image, ensure that the PV driver has been installed in the OS to enable Xen virtualization for subsequently created ECSs, improve the I/O processing performance of the ECSs, and implement advanced functions such as monitoring hardware of the ECSs.
+
If you do not install the PV driver, the ECS network performance will be poor, and the security group and firewall configured for the ECS will not take effect.
+The PV driver has been installed by default when you use a public image to create ECSs. You can perform the following operations to verify the installation:
+Open the version configuration file to check whether the PV driver is the latest:
+For details about how to log in to an ECS, see Elastic Cloud Server User Guide.
+
You must log in to the ECS using VNC. Remote desktop connection is not allowed because the NIC driver needs to be updated during the installation but the NIC is in use for the remote desktop connection. As a result, the installation will fail.
+ECSs running Windows Server 2008 must be restarted twice.
+
After the PV driver is installed, the ECS NIC configuration will be lost. If you have configured NICs before, you need to configure them again.
+Perform the following steps to verify the installation of the PV driver:
+If the PV driver exists, the installation is successful, as shown in Figure 1.
+ +You can run the following command to query the virtualization type of an ECS:
+lscpu
+If the value of Hypervisor vendor is Xen, the ECS uses Xen. If KVM is required, perform the operations in this section to optimize the Linux private image.
+
If the ECS uses KVM, you are also advised to optimize the private image to prevent any exceptions with the ECSs created from the image.
+
When optimizing a Linux private image, you need to change the UUID in the fstab and GRUB configuration files, and install native Xen and KVM drivers on the ECS. To ensure that you can successfully install native Xen and KVM drivers, you must uninstall the PV driver from the ECS.
+The PV driver is installed in the OS if the following information is displayed:
+root 4561 1 0 Jun29 ? 00:00:00 /usr/bin/uvp-monitor +root 4567 4561 0 Jun29 ? 00:00:00 /usr/bin/uvp-monitor +root 6185 6085 0 03:04 pts/2 00:00:00 grep uvp-monitor+
The PV driver is uninstalled successfully. Reboot the system for the uninstallation to take effect.+
-bash: /etc/.uvp-monitor/uninstall: No such file or directory+
Information similar to the following is displayed:
+libxenstore_uvp3_0-3.00-36.1.x86_64 +uvp-monitor-2.2.0.315-3.1.x86_64 +kmod-uvpmod-2.2.0.315-3.1.x86_64+
rpm -e uvp-monitor
+rpm -e libxenstore_uvp
+OS + |
+Configuration + |
+Reference + |
+
|---|---|---|
Windows + |
+
|
++ | +
Linux + |
+
|
++ | +
OS + |
+Configuration Item + |
+Reference + |
+
|---|---|---|
Windows + |
+
|
++ | +
Linux + |
+
|
++ | +
OS + |
+Configuration Item + |
+Reference + |
+
|---|---|---|
Windows + |
+
|
+For details, see "Creating a Private Image from a BMS" in Bare Metal Server User Guide. + |
+
Linux + |
+
|
+For details, see "Creating a Private Image from a BMS" in Bare Metal Server User Guide. + |
+
OS + |
+Configuration Item + |
+Reference + |
+
|---|---|---|
Windows + |
+
|
+Bare Metal Server Image Creation Guide + |
+
Linux + |
+
|
+Bare Metal Server Image Creation Guide + |
+
Released On + |
+Description + |
+
|---|---|
2021-08-15 + |
+Added the following content: +
Modified the following content: +
Deleted the following content: +
|
+
2020-08-12 + |
+Added the following content: + +Modified the following content: +
|
+
2020-07-20 + |
+Modified the following content: +
|
+
2020-05-26 + |
+Modified the following content: +Added the link for obtaining the UVP VMTools software package for Windows Server 2019 in Obtaining Required Software Packages. + |
+
2019-03-29 + |
+Added the following content: + +Modified the following content: +
|
+
2019-03-28 + |
+Accepted in OTC-4.0/Agile. + |
+
2019-01-23 + |
+Deleted "Image Storage Fee." + |
+
2018-12-30 + |
+Added the following content: +Added support for external image files using Fedora 29 64bit External Image File Formats and Supported OSs. + |
+
2018-12-21 + |
+Modified the following content: +
|
+
2018-09-30 + |
+Added the following content: +Added Quickly Importing an Image File. +Modified the following content:
+
|
+
2018-08-30 + |
+Modified the following content: +Optimized operations in Accepting or Rejecting Shared Images. + |
+
2018-07-30 + |
+Added the following content: +Added more OS types for external image files, including openSUSE 15 64bit, SUSE 15 64bit, EulerOS 2.1 64bit, and EulerOS 2.3 64bit in External Image File Formats and Supported OSs. + |
+
2018-07-10 + |
+Accepted in Agile-07.2018. + |
+
2018-07-05 + |
+Modified the following content: +Modified the restrictions and limitations in sections "Creating a Full-ECS Image Using an ECS" and "Creating a Full-ECS Image Using a CSBS Backup". + |
+
2018-06-30 + |
+Added the following content: +Converting the Image Format Using qemu-img +Modified the following content:
+
|
+
2018-05-30 + |
+Added the following content:
+
+Modified the following content: +Changed Tools for Windows to Guest OS driver. + |
+
2018-04-30 + |
+Added the following content: +How Do I Delete Redundant Network Connections from a Windows ECS? + |
+
2018-03-30 + |
+Added the following content: + + |
+
2018-02-28 + |
+Modified the following content: +Added support for exporting public images in Exporting Image List. + |
+
2018-01-30 + |
+Added the following content: +What Do I Do If I Cannot Create an Image in ZVHD2 Format Using an API? +Modified the following content: +Added new OSs supported for external image files, including Fedora 27 64bit and Debian 9.3 64bit in External Image File Formats and Supported OSs. + |
+
2017-12-30 + |
+Added the following content: + +Modified the following content: +Added support for the VHDX, QED, VDI, and QCOW formats in External Image File Formats and Supported OSs. + |
+
2017-11-30 + |
+Added the following content: + + |
+
2017-10-30 + |
+Modified the following content:
+
|
+
2017-09-30 + |
+Added the following content:
+
+Modified the following content: +Added the support for the RAW format in External Image File Formats and Supported OSs. + |
+
2017-08-30 + |
+Added the following content: +Creating a BMS System Disk Image +Modified the following content:
+
|
+
2017-07-29 + |
+Added the following content: + +Modified the following content: +Added the method of installing Cloud-Init using pip in Installing Cloud-Init. + |
+
2017-06-30 + |
+Modified the following content: +Updated the operations performed by the system on image files in What Will the System Do to an Image File When I Use the File to Register a Private Image? + |
+
2017-05-30 + |
+Modified the following content:
+
|
+
2017-04-28 + |
+Added the following content:
+
+Modified the following content: +Added support for external image files containing CoreOS 1298.6.0 in External Image File Formats and Supported OSs. + |
+
2017-03-30 + |
+Modified the following content:
+
|
+
2017-02-28 + |
+Added the following content: + +Modified the following content:
+
|
+
2017-02-08 + |
+Modified the following content: +Added support for external image files containing Red Hat 7.3 64bit in External Image File Formats and Supported OSs. + |
+
2017-01-20 + |
+Added the following content: + +Modified the following content:
+
|
+
2016-12-30 + |
+Modified the following content: +Added support for external image files containing openSUSE 11.3 64bit in External Image File Formats and Supported OSs. + |
+
2016-11-24 + |
+Modified the following content: +Added support for external image files containing Debian 8.6.0 64bit in External Image File Formats and Supported OSs. + |
+
2016-10-19 + |
+Added the following content: + +Modified the following content: +Updated the OSs supported for public images. + |
+
2016-07-15 + |
+Added the following content:
+
+Modified the following content: +Updated the OSs supported for public images. + |
+
2016-03-14 + |
+This issue is the first official release. + |
+
IMS allows you to create encrypted images to ensure data security.
+
To use the image encryption function, you must apply for KMS Administrator permissions.
+You can create an encrypted image using an external image file or an encrypted ECS.
+When you register the external image file as a private image, select KMS encryption and select a key. For details, see Creating a Windows System Disk Image from an External Image File and Creating a Linux System Disk Image from an External Image File.
+When you use an ECS to create a private image, if the system disk of the ECS is encrypted, the private image created using the ECS is also encrypted. The key used for encrypting the image must be the same as that used for encrypting the system disk. For details, see Creating a System Disk Image from a Windows ECS and Creating a System Disk Image from a Linux ECS.
+ECSs require Xen Guest OS driver (PV driver) and KVM Guest OS driver (UVP VMTools) for proper running. To ensure that ECSs support both Xen and KVM and to improve network performance, the PV driver and UVP VMTools must be installed for the image.
+For details, see Installing the PV Driver.
+For details, see Installing UVP VMTools.
+For details, see Clearing System Logs.
+A Linux ECS can be switched from Xen to KVM if xen-pv and VirtIO drivers run on the ECS. Before changing a Xen-based ECS to a KVM-based ECS, ensure that the required drivers have been installed and the UUID has been configured for the Linux private image. In addition, optimizing the private image can improve network performance of the ECS.
+For details, see Uninstalling the PV Driver from a Linux ECS.
+For details, see Changing the Disk Identifier in the GRUB Configuration File to UUID.
+For details, see Changing the Disk Identifier in the fstab File to UUID.
+For details, see Installing Native KVM Drivers.
+For details, see Clearing System Logs.
+For details about the terms involved in this document, see Glossary.
+You can convert encrypted and unencrypted images into each other or enable some advanced features (such as fast ECS creation from an image) using the image replication function. You may need to replicate an image in the following scenarios:
+Keys for encrypting the images cannot be changed. If you want to change the key of an encrypted image, you can replicate this image to a new one and encrypt the new image using an encryption key.
+If you want to store an unencrypted image in an encrypted way, you can replicate this image as a new one and encrypt the new image using a key.
+Fast Create greatly reduces the time required for creating ECSs from a system disk image. Currently, this feature is supported by all newly created system disk images by default. Existing system disk images may not support this function. You can optimize the images using the image replication function. For example, if image A does not support fast ECS creation, you can replicate it to generate image copy_A that supports fast ECS creation.
+The images to be replicated are in the Normal state.
+The IMS console is displayed.
+On the Private Images page, view the replication progress. If the status of the new image becomes Normal, the image replication is successful.
+If you want to store an unencrypted image in an encrypted way, you can select an encryption key when you replicate the image. Then, the system will generate an encrypted replica of the unencrypted image.
+If you want to use the ECS console logging function, you need to configure related parameters on the ECS.
+Currently, ECSs running the following OSs are supported: CentOS 6 series, Red Hat 6 series, CentOS 7 series, Red Hat 7 series, Ubuntu 14 series, SUSE 11 series, SUSE 12 series, Debian, Ubuntu 16 series, Fedora, FreeBSD, and CoreOS.
+
To use the Console Log function on the ECS console, perform this operation. Otherwise, skip this section.
+You have logged in to the ECS.
+
To prevent impact on the start of the recovery mode, you are advised to modify only the item used for the default start.
+cat /proc/cmdline | grep ttyS0
+
If the /usr/share/oem/grub.cfg configuration file does not exist, manually create the file.
+Check the system disk size in the VHD image file. Specify a value no less than this size when you use the VHD image file to register an image.
+Run the following command to check the VHD image file information:
+[xxxx@xxxxx test]$ qemu-img info 2g.vhd +image: 2g.vhd +file format: vpc +virtual size: 2.0G (2147991552 bytes) +disk size: 8.0K +cluster_size: 2097152+
The virtual size is converted from the actual size (unit: byte) to an integer in GB. As a result, the actual file size 2147991552 bytes (2.0004 GB) is larger than the virtual size 2 GB. Therefore, you need to specify a value larger than the actual size 2.0004 GB. (The system disk size value on the management can only be an integer, so you only need to enter a value larger than 2.)
+You can use tags to classify images. You can add, modify, or delete image tags, or search for required images by tag in the image list.
+
When adding predefined tags to an image or searching for an image using predefined tags, you must have permission to access the Tag Management Service (TMS).
+An image can have a maximum of 10 tags.
+The IMS console is displayed.
+The IMS console is displayed.
+Neither the tag key nor tag value can be empty. When the tag key and tag value are matched, the system automatically shows your desired private images.
+
to add a tag.You can add multiple tags to search for private images. The system will display private images that match all tags.
+The system searches for private images based on tag keys or tag values.
+To prevent NIC name drift when you use a private image to create ECSs, you need to delete files from the network rule directory of the VM where the ECS or image file is located during the private image creation.
+
When registering an external image file as a private image, delete files from the network rule directory on the VM where the external image file is located. You are advised to delete the files on the VM and then export the image file.
+An OS and VirtIO drivers have been installed on the ECS.
+Example:
+rm /etc/udev/rules.d/30-net_persistent-names.rules
+rm /etc/udev/rules.d/70-persistent-net.rules
+The italic content in the commands varies depending on your environment.
+
For CentOS 6 images, to prevent NIC name drift, you need to create an empty rules configuration file.
+Example:
+touch /etc/udev/rules.d/75-persistent-net-generator.rules //Replace 75 with the actual value in the environment.
+lsinitrd /boot/initrd-2.6.32.12-0.7-default |grep persistent|grep net
+cp /boot/initrd-2.6.32.12-0.7-default /boot/initrd-2.6.32.12-0.7-default_bak
+lsinitramfs /boot/initrd.img-3.19.0-25-generic|grep persistent|grep net
+cp /boot/initrd.img-3.19.0-25-generic /boot/initrd.img-3.19.0-25-generic_bak
+If you want to use the shared images you have rejected, you can accept them from the list of rejected images.
+The IMS console is displayed.
+
After OS partitions of old versions are expanded, the OS must be restarted to update the file system.
+OS + |
+Tool Package + |
+
|---|---|
Debian/Ubuntu + |
+cloud-init, cloud-utils, and cloud-initramfs-growroot + |
+
Fedora/CentOS + |
+cloud-init, cloud-utils, and cloud-utils-growpart + |
+
SUSE/openSUSE + |
+cloud-init and growpart + |
+
For Debian 9, use method 1 to install growpart. If the installation fails, use method 2 to install growpart.
+Method 1:
+Run the following command to install growpart:
+apt-get install -y -f cloud-init cloud-utils cloud-initramfs-growroot
+Method 2:
+You can obtain the dependent packages from the following paths:
+http://ftp.br.debian.org/debian/pool/main/c/cloud-utils/cloud-utils_0.29-1_all.deb
+ +dpkg -i cloud-utils package path cloud-initramfs-growroot package path
+An example command is dpkg -i /root/cloud-utils_0.29-1_all.deb /root/cloud-initramfs-growroot_0.18.debian5_all.deb.
+For other Debian versions, run the following command to install dependent packages:
+apt-get update;apt-get install cloud-utils cloud-initramfs-growroot
+Take the following as two examples of image disk partitioning:
+If the root partition is the last partition, see Root partition at the last.
+If the root partition is not the last partition, see Root partition not at the last.
+
For example, if the system disk size of CentOS 6.5 64bit is 40 GB, perform the following operations to configure a Linux private image so that it can automatically expand its root partition:
+parted -l /dev/xvda
+As shown in the command output, the root partition is the second partition and is 38.7 GB.
+Model: Xen Virtual Block Device (xvd) +Disk /dev/xvda: 42.7GB +Sector size (logical/physical): 512B/512B +Partition Table: msdos + +Number Start End Size Type File system Flags +1 1049kB 4296MB 4295MB primary linux-swap(v1) +2 4296MB 42.9GB 38.7GB primary ext4 boot+
Run the following command to install growpart:
+yum install cloud-*
+
growpart may be contained in the cloud-utils-growpart/cloud-utils/cloud-initramfs-tools/cloud-init package. You can run the preceding command directly and then run the growpart command to check whether growpart has been installed successfully.
+The command output is as follows:
+/dev/xvda1: UUID="25ec3bdb-ba24-4561-bcdc-802edf42b85f" TYPE="swap" +/dev/xvda2: UUID="1a1ce4de-e56a-4e1f-864d-31b7d9dfb547" TYPE="ext4"+
[root@sluo-ecs-e6dc-resizefs ~]# poweroff +Connection closed by foreign host. +Disconnected from remote host at 11:08:54. +Type `help´ to learn how to use Xshell prompt.+
parted -l /dev/xvda
+As shown in the command output, the root partition has been expanded automatically.
+Model: Xen Virtual Block Device (xvd) +Disk /dev/xvda: 53.7GB +Sector size (logical/physical): 512B/512B +Partition Table: msdos + +NumberStartEndSizeTypeFile systemFlags +1 1049kB 4296MB 4295MB primary linux-swap(v1) +2 4296MB 53.7GB 49.4GB primary ext4 boot+
The command output is as follows:
+Filesystem Type Size Used Avail Use% Mounted on +/dev/xvda2 ext4 49.4G 2.6G 46.8G 4% /dev/shm +tmpfs tmpfs 4295M 0 4295M 0% /+
parted -l /dev/xvda
+As shown in the command output, the root partition is the first partition and is 40.9 GB. The swap partition is the second partition.
+Model: Xen Virtual Block Device (xvd) +Disk /dev/xvda: 42.9GB +Sector size (logical/physical): 512B/512B +Partition Table: msdos +Disk Flags: + +Number Start End Size Type File system Flags +1 1049kB 41.0GB 40.9GB primary ext4 boot +2 41.0GB 42.9GB 2000MB primary linux-swap(v1)+
tail -n 3 /etc/fstab
+As shown in the command output, UUIDs of the two partitions are displayed.
+# +UUID=7c4fce5d-f8f7-4ed6-8463-f2bd22d0ddea / ext4 defaults 1 1 +UUID=5de3cf2c-30c6-4fb2-9e63-830439d4e674 swap swap defaults 0 0+
vi /etc/fstab
+wq!
+As shown in the command output, only the UUID of the root partition is displayed.
+UUID=7c4fce5d-f8f7-4ed6-8463-f2bd22d0ddea / ext4 defaults 1 1+
parted /dev/xvda
+The command output is as follows:
+[root@test-0912 bin]# parted /dev/xvda +GNU Parted 3.1 +Using /dev/xvda +Welcome to GNU Parted! Type 'help' to view a list of commands. +(parted)+
(parted) p +Model: Xen Virtual Block Device (xvd) +Disk /dev/xvda: 42.9GB +Sector size (logical/physical): 512B/512B +Partition Table: msdos +Disk Flags: + +Number Start End Size Type File system Flags + 1 1049kB 4296MB 4295MB primary linux-swap(v1) + 2 4296MB 42.9GB 38.7GB primary xfs boot +(parted)+
The command output is as follows:
+(parted) rm 2 +(parted)+
The command output is as follows:
+(parted) p +Model: Xen Virtual Block Device (xvd) +Disk /dev/xvda: 42.9GB +Sector size (logical/physical): 512B/512B +Partition Table: msdos +Disk Flags: + +Number Start End Size Type File system Flags +1 1049kB 41.0GB 40.9GB primary ext4 boot+
parted -l /dev/xvda
+As shown in the command output, the swap partition is deleted.
+Model: Xen Virtual Block Device (xvd) +Disk /dev/xvda: 42.9GB +Sector size (logical/physical): 512B/512B +Partition Table: msdos +Disk Flags: + +Number Start End Size Type File system Flags +1 1049kB 41.0GB 40.9GB primary ext4 boot+
Run the following command to install growpart:
+yum install cloud-*
+
growpart may be contained in the cloud-utils-growpart/cloud-utils/cloud-initramfs-tools/cloud-init package. You can run the preceding command directly and then run the growpart command to check whether growpart has been installed successfully.
+growpart /dev/xvda 1
+The command output is as follows:
+CHANGED: partition=1 start=2048 old: size=79978496 end=79980544 new: size=83873317,end=83875365+
parted -l /dev/xvda
+Model: Xen Virtual Block Device (xvd) +Disk /dev/xvda: 42.9GB +Sector size (logical/physical): 512B/512B +Partition Table: msdos +Disk Flags: + +Number Start End Size Type File system Flags +1 1049kB 42.9GB 42.9GB primary ext4 boot+
The command output is as follows:
+/dev/xvda1: UUID="7c4fce5d-f8f7-4ed6-8463-f2bd22d0ddea" TYPE="ext4"+
[root@sluo-ecs-e6dc-resizefs ~]# poweroff +Connection closed by foreign host. +Disconnected from remote host at 11:08:54. +Type `help´ to learn how to use Xshell prompt.+
parted -l /dev/xvda
+As shown in the command output, the root partition has been expanded to 107 GB.
+Model: Xen Virtual Block Device (xvd) +Disk /dev/xvda: 107GB +Sector size (logical/physical): 512B/512B +Partition Table: msdos +Disk Flags: + +Number Start End Size Type File system Flags + 1 1049kB 107GB 107GB primary ext4 boot ++
The value of Size is the size of the expanded root partition.
+growpart for SUSE and openSUSE is an independent toolkit that does not start with cloud-*. Perform operations in this section to install growpart.
+The command output is as follows:
+cloud-init-0.7.8-39.2+
rpm -qa | grep growpart
+The command output is as follows:
+growpart-0.29-8.1+
rm -fr /var/lib/cloud/*
+zypper install http://download.opensuse.org/repositories/home:/garloff:/OTC:/cloudinit/SLE_11_SP4/noarch/growpart-0.27-1.1.noarch.rpm
+zypper install http://download.opensuse.org/repositories/home:/garloff:/OTC:/cloudinit/SLE_11_SP4/x86_64/python-oauth-1.0.1-35.1.x86_64.rpm
+zypper install http://download.opensuse.org/repositories/home:/garloff:/OTC:/cloudinit/SLE_11_SP4/x86_64/cloud-init-0.7.6-27.23.1.x86_64.rpm
+The command output is as follows:
+growpart-0.27-1.1+
rpm -qa | grep python-oauth
+The command output is as follows:
+python-oauthlib-0.6.0-1.5 +python-oauth-1.0.1-35.1+
rpm -qa | grep cloud-init
+The command output is as follows:
+cloud-init-0.7.6-27.19.1+
chkconfig cloud-init-local on;chkconfig cloud-init on;chkconfig cloud-config on;chkconfig cloud-final on
+Before using some types of ECSs to create private images, you need to install special drivers on the ECSs.
+If you want to use the created private image to create GPU-accelerated ECSs, install a proper GPU driver for the image to enable GPU acceleration. There are two types of NVIDIA Tesla GPU drivers for GPU-accelerated ECSs, Tesla and GRID/vGPU drivers.
+ECS Type + |
+How to Install the Driver + |
+
|---|---|
G1 + |
+For details, see Downloading GRID Driver and Software License Packages in Installing a GRID Driver on a GPU-accelerated ECS. + |
+
G2 + |
+Log in at http://www.nvidia.com/Download/index.aspx?lang=en-us. You are advised to select the latest CUDA Toolkit version. + NOTICE:
+After the GPU driver is installed, run the following command to switch the GPU working mode and restart the ECS (for example, the GPU driver is installed in C:\Program Files\NVIDIA Corporation\NVSMI\nvidia-smi.exe): +"C:\Program Files\NVIDIA Corporation\NVSMI\nvidia-smi.exe" -dm 0 + |
+
If you want to use the created private image to create G2 ECSs, install the SR-IOV NIC driver for the image to improve performance and scalability.
+To download the SR-IOV driver, log in at https://downloadcenter.intel.com/search?keyword=Intel++Ethernet+Connections+CD. You are advised to select version 20.4.1 or later.
+If error "No Intel adapter found" occurs during the driver installation, refer to What Do I Do If a Windows 7 ECS Equipped with an Intel 82599 NIC Reports an Error in SR-IOV Scenarios? for troubleshooting.
+When the 20.4.1 driver package downloaded at Intel website https://downloadcenter.intel.com/search?keyword=Intel++Ethernet+Connections+CD was installed in a Windows 7 64bit ECS with SR-IOV passthrough enabled, the system displayed the message "No Intel adapter found".
+The OS identifies an Intel 82599 passthrough NIC without a driver installed as an Ethernet controller. When the 20.4.1 driver package was installed, the OS did not identify the Intel NIC, leading to the error.
+Run Autorun.exe in the folder where the 20.4.1 driver package is stored. Install a driver on the NIC before installing the driver package so that the NIC can be identified as an Intel 82599 virtual function (VF) device by the OS. Use either of the following methods to install the driver:
+Before using some types of ECSs to create private images, you need to install special drivers on the ECSs.
+If you want to use the private image to create P1 ECSs, install the NVIDIA driver for the image to enable computing acceleration. For details, see How Do I Install the NVIDIA Driver on a P1 ECS?
+A data disk image contains only service data. You can create a data disk image using a local image file or an external image file (image file on another cloud platform). Then, you can use the data disk image to create EVS disks and migrate your service data to the cloud.
+The following figure shows the process of creating a data disk image from an external image file.
+
The IMS console is displayed.
+
After you select Enable Fast Create, select the confirmation information following Image File Preparation if you have prepared the required files.
+When the image status changes to Normal, the image creation is complete.
+If you want to use the created data disk image to create an EVS disk and attach it to an ECS, you can perform either of the following operations:
+
A data disk image can be used to create a data disk for an ECS only once.
+With the increase of network I/O bandwidth, a single vCPU cannot meet the requirement of processing NIC interruptions. NIC multi-queue allows multiple vCPUs to process NIC interruptions, thereby improving network PPS and I/O performance.
+NIC multi-queue can be enabled on an ECS only when the ECS specifications, virtualization type, and image meet the requirements described in this section.
+
If the number of NIC queues is greater than 1, NIC multi-queue is supported.
+
Run the uname -r command to check the kernel version. If the version is earlier than 2.6.35, contact technical support to upgrade it.
+OS + |
+Image + |
+Supported By + |
+
|---|---|---|
Windows + |
+Windows Server 2008 WEB R2 64bit + |
+Private images + |
+
Windows Server 2008 R2 Standard/Datacenter/Enterprise 64bit + |
+Private images + |
+|
Windows Server 2012 R2 Standard/Datacenter 64bit + |
+Private images + |
+|
Windows Server 2016 Standard/Datacenter 64bit + |
+Private images + |
+|
Linux + |
+Ubuntu 14.04/16.04 Server 64bit + |
+Public images + |
+
openSUSE 42.2 64bit + |
+Public images + |
+|
SUSE Enterprise 12 SP1/SP2 64bit + |
+Public images + |
+|
CentOS 6.8/6.9/7.0/7.1/7.2/7.3/7.4/7.5/7.6 64bit + |
+Public images + |
+|
Debian 8.0.0/8.8.0/8.9.0/9.0.0 64bit + |
+Public images + |
+|
Fedora 24/25 64bit + |
+Public images + |
+|
EulerOS 2.2 64bit + |
+Public images + |
+
Assume that an ECS has the required specifications and virtualization type.
+Register the external image file as a private image. For details, see Registering an External Image File as a Private Image.
+Windows OSs have not commercially supported NIC multi-queue. If you enable NIC multi-queue in a Windows image, starting an ECS created using such an image may be slow.
+Use either of the following methods to set NIC multi-queue.
+The IMS console is displayed.
+The IMS console is displayed.
+Method 3: Add hw_vif_multiqueue_enabled to the image using an API.
+The value of X-Auth-Token is the token obtained in step 1.
+The value of Content-Type is application/openstack-images-v2.1-json-patch.
+The request URI is in the following format:
+PATCH /v2/images/{image_id}
+[
+ {
+ "op":"add",
+ "path":"/hw_vif_multiqueue_enabled",
+ "value": "true"
+ }
+ ]
+Figure 1 shows an example request body for setting NIC multi-queue.
+ +KVM ECSs running Windows use private images to support NIC multi-queue.
+For Linux ECSs, which run CentOS 7.4 as an example, perform the following operations to enable NIC multi-queue:
+Example:
+[root@localhost ~]# ethtool -l eth0 #View the number of queues used by NIC eth0. +Channel parameters for eth0: +Pre-set maximums: +RX: 0 +TX: 0 +Other: 0 +Combined: 4 #Indicates that a maximum of four queues can be enabled for the NIC. +Current hardware settings: +RX: 0 +TX: 0 +Other: 0 +Combined: 1 #Indicates that one queue has been enabled. + +[root@localhost ~]# ethtool -L eth0 combined 4 #Enable four queues on NIC eth0.+
Enabling irqbalance allows the system to automatically allocate NIC interruptions, improving network performance. If the improved network performance fails to meet your expectations, manually configure interrupt affinity on the target ECS.
+The detailed operations are as follows:
+Run the following script so that each ECS vCPU responds the interrupt requests initialized by one queue. That is, one queue corresponds to one interrupt, and one interrupt binds to one vCPU.
+#!/bin/bash
+service irqbalance stop
+
+eth_dirs=$(ls -d /sys/class/net/eth*)
+if [ $? -ne 0 ];then
+ echo "Failed to find eth* , sleep 30" >> $ecs_network_log
+ sleep 30
+ eth_dirs=$(ls -d /sys/class/net/eth*)
+fi
+
+for eth in $eth_dirs
+do
+ cur_eth=$(basename $eth)
+ cpu_count=`cat /proc/cpuinfo| grep "processor"| wc -l`
+ virtio_name=$(ls -l /sys/class/net/"$cur_eth"/device/driver/ | grep pci |awk {'print $9'})
+
+ affinity_cpu=0
+ virtio_input="$virtio_name""-input"
+ irqs_in=$(grep "$virtio_input" /proc/interrupts | awk -F ":" '{print $1}')
+ for irq in ${irqs_in[*]}
+ do
+ echo $((affinity_cpu%cpu_count)) > /proc/irq/"$irq"/smp_affinity_list
+ affinity_cpu=$[affinity_cpu+2]
+ done
+
+ affinity_cpu=1
+ virtio_output="$virtio_name""-output"
+ irqs_out=$(grep "$virtio_output" /proc/interrupts | awk -F ":" '{print $1}')
+ for irq in ${irqs_out[*]}
+ do
+ echo $((affinity_cpu%cpu_count)) > /proc/irq/"$irq"/smp_affinity_list
+ affinity_cpu=$[affinity_cpu+2]
+ done
+done
+XPS allows the system with NIC multi-queue enabled to select a queue by vCPU when sending a data packet.
+#!/bin/bash
+# enable XPS feature
+cpu_count=$(grep -c processor /proc/cpuinfo)
+dec2hex(){
+ echo $(printf "%x" $1)
+}
+eth_dirs=$(ls -d /sys/class/net/eth*)
+if [ $? -ne 0 ];then
+ echo "Failed to find eth* , sleep 30" >> $ecs_network_log
+ sleep 30
+ eth_dirs=$(ls -d /sys/class/net/eth*)
+fi
+for eth in $eth_dirs
+do
+ cpu_id=1
+ cur_eth=$(basename $eth)
+ cur_q_num=$(ethtool -l $cur_eth | grep -iA5 current | grep -i combined | awk {'print $2'})
+ for((i=0;i<cur_q_num;i++))
+ do
+ if [ $i -eq $ cpu_count ];then
+ cpu_id=1
+ fi
+ xps_file="/sys/class/net/${cur_eth}/queues/tx-$i/xps_cpus"
+ rps_file="/sys/class/net/${cur_eth}/queues/rx-$i/rps_cpus"
+ cpuset=$(dec2hex "$cpu_id")
+ echo $cpuset > $xps_file
+ echo $cpuset > $rps_file
+ let cpu_id=cpu_id*2
+ done
+done
+When optimizing a Linux private image, you need to install native Xen and KVM drivers for the image.
+
If you do not install Xen drivers for the image, the network performance of the ECSs created from this image will be poor, and the security groups and firewall configured for the ECSs will not take effect.
+If you do not install KVM drivers for the image, the NICs of the ECSs may not be detected and the ECSs will be unable to communicate with other resources.
+This section describes how to install native Xen and KVM drivers.
+Take CentOS 7.0 as an example. Modify the /etc/dracut.conf file. Add the xen-pv and VirtIO drivers to add_drivers. xen-pv drivers include xen-blkfront and xen-netfront. VirtIO drivers include virtio_blk, virtio_scsi, virtio_net, virtio_pci, virtio_ring, and virtio. Separate driver names with spaces. Save and exit the /etc/dracut.conf file. Run the dracut -f command to regenerate initrd.
+For details, see CentOS and EulerOS.
+Modify the /etc/initramfs-tools/modules file. Add the xen-pv and VirtIO drivers. xen-pv drivers include xen-blkfront and xen-netfront. VirtIO drivers include virtio_blk, virtio_scsi, virtio_net, virtio_pci, virtio_ring, and virtio. Separate driver names with spaces. Save and exit the /etc/initramfs-tools/modules file. Run the update-initramfs -u command to regenerate initrd.
+For details, see Ubuntu and Debian.
+
For SUSE, run the following command to check whether xen-kmp (driver package for xen-pv) is installed:
+rpm -qa |grep xen-kmp
+If information similar to the following is displayed, xen-kmp is installed in the OS:
+xen-kmp-default-4.2.2_04_3.0.76_0.11-0.7.5+
If xen-kmp is not installed, obtain it from the ISO file and install it.
+If you add built-in drivers to the initrd or initramfs file by mistake, the ECS will not be affected.
+vi /etc/dracut.conf
+[root@CTU10000xxxxx ~]# vi /etc/dracut.conf +# additional kernel modules to the default +add_drivers+="xen-blkfront xen-netfront virtio_blk virtio_scsi virtio_net virtio_pci virtio_ring virtio" +......+
dracut -f /boot/initramfs-2.6.32-573.8.1.el6.x86_64.img
+If the virtual file system is not the default initramfs, run the dracut -f Name of the initramfs or initrd file actually used command. The actual initramfs or initrd file name can be obtained from the grub.cfg file, which can be /boot/grub/grub.cfg, /boot/grub2/grub.cfg, or /boot/grub/grub.conf depending on the OS.
+lsinitrd /boot/initramfs-`uname -r`.img | grep xen
+lsinitrd /boot/initramfs-`uname -r`.img | grep virtio
+If the virtual file system is initrd, run the following commands to check whether native Xen and KVM drivers have been loaded:
+lsinitrd /boot/initrd-`uname -r` | grep xen
+lsinitrd /boot/initrd-`uname -r` | grep virtio
+Assume that the virtual file system is initramfs. The following command output will be displayed:
+[root@CTU10000xxxxx home]# lsinitrd /boot/initramfs-`uname -r`.img | grep xen +-rwxr--r-- 1 root root 54888 Jul 16 17:53 lib/modules/2.6.32-573.8.1.el6.x86_64/kernel/drivers/block/xen-blkfront.ko +-rwxr--r-- 1 root root 45664 Jul 16 17:53 lib/modules/2.6.32-573.8.1.el6.x86_64/kernel/drivers/net/xen-netfront.ko + +[root@CTU10000xxxxx home]# lsinitrd /boot/initramfs-`uname -r`.img | grep virtio +-rwxr--r-- 1 root root 23448 Jul 16 17:53 lib/modules/2.6.32-573.8.1.el6.x86_64/kernel/drivers/block/virtio_blk.ko +-rwxr--r-- 1 root root 50704 Jul 16 17:53 lib/modules/2.6.32-573.8.1.el6.x86_64/kernel/drivers/net/virtio_net.ko +-rwxr--r-- 1 root root 28424 Jul 16 17:53 lib/modules/2.6.32-573.8.1.el6.x86_64/kernel/drivers/scsi/virtio_scsi.ko +drwxr-xr-x 2 root root 0 Jul 16 17:53 lib/modules/2.6.32-573.8.1.el6.x86_64/kernel/drivers/virtio +-rwxr--r-- 1 root root 14544 Jul 16 17:53 lib/modules/2.6.32-573.8.1.el6.x86_64/kernel/drivers/virtio/virtio.ko +-rwxr--r-- 1 root root 21040 Jul 16 17:53 lib/modules/2.6.32-573.8.1.el6.x86_64/kernel/drivers/virtio/virtio_pci.ko +-rwxr--r-- 1 root root 18016 Jul 16 17:53 lib/modules/2.6.32-573.8.1.el6.x86_64/kernel/drivers/virtio/virtio_ring.ko+
If you add built-in drivers to the initrd or initramfs file, the ECS will not be affected. This makes it easy to modify the drivers. However, you cannot check the drivers by running the lsinitrd command. You can run the following commands to check whether built-in drivers are in the kernel:
+cat /boot/config-`uname -r` | grep CONFIG_VIRTIO | grep y
+cat /boot/config-`uname -r` | grep CONFIG_XEN | grep y
+vi /etc/initramfs-tools/modules
+[root@CTU10000xxxxx ~]#vi /etc/initramfs-tools/modules +...... +# Examples: +# +# raid1 +# sd_mOd +xen-blkfront +xen-netfront +virtio_blk +virtio_scsi +virtio_net +virtio_pci +virtio_ring +virtio+
lsinitramfs /boot/initrd.img-`uname -r` |grep xen
+lsinitramfs /boot/initrd.img-`uname -r` |grep virtio
+[root@ CTU10000xxxxx home]# lsinitramfs /boot/initrd.img-`uname -r` |grep xen +lib/modules/3.5.0-23-generic/kernel/drivers/net/ethernet/qlogic/netxen +lib/modules/3.5.0-23-generic/kernel/drivers/net/ethernet/qlogic/netxen/netxen_nic.ko +lib/modules/3.5.0-23-generic/kernel/drivers/net/xen-netback +lib/modules/3.5.0-23-generic/kernel/drivers/net/xen-netback/xen-netback.ko +lib/modules/3.5.0-23-generic/kernel/drivers/block/xen-blkback +lib/modules/3.5.0-23-generic/kernel/drivers/block/xen-blkback/xen-blkback.ko + +[root@ CTU10000xxxxx home]# lsinitramfs /boot/initrd.img-`uname -r` |grep virtio +lib/modules/3.5.0-23-generic/kernel/drivers/scsi/virtio_scsi.ko+
If you add built-in drivers to the initrd or initramfs file, the ECS will not be affected. This makes it easy to modify the drivers. However, you cannot check the drivers by running the lsinitrd command. You can run the following commands to check whether built-in drivers are in the kernel:
+[root@ CTU10000xxxxx home]# cat /boot/config-`uname -r` | grep CONFIG_VIRTIO | grep y +CONFIG_VIRTIO_BLK=y +CONFIG_VIRTIO_NET=y +CONFIG_VIRTIO=y +CONFIG_VIRTIO_RING=y +CONFIG_VIRTIO_PCI=y +CONFIG_VIRTIO_MMIO_CMDLINE_DEVICES=y +[root@ CTU10000xxxxx home]# cat /boot/config-`uname -r` | grep CONFIG_XEN | grep y +CONFIG_XEN_BLKDEV_FRONTEND=y +CONFIG_XEN_NETDEV_FRONTEND=y+
If the OS version is earlier than SUSE 12 SP1 or openSUSE 13, modify the /etc/sysconfig/kernel file. For details, see scenario 1.
+If the OS version is SUSE 12 SP1, modify the /etc/dracut.conf file and add xen-pv and VirtIO drivers. For details, see scenario 2.
+
For SUSE, run the following command to check whether xen-kmp (driver package for xen-pv) is installed in the OS:
+rpm -qa |grep xen-kmp
+If information similar to the following is displayed, xen-kmp is installed:
+xen-kmp-default-4.2.2_04_3.0.76_0.11-0.7.5+
If xen-kmp is not installed, obtain it from the installation ISO and install it first.
+vi etc/sysconfig/kernel
+SIA10000xxxxx:~ # vi /etc/sysconfig/kernel +# (like drivers for scsi-controllers, for lvm or reiserfs) +# +INITRD_MODULES="ata_piix ata_generic xen_vnif xen_vbd xen_platform_pci virtio_blk virtio_scsi virtio_net virtio_pci virtio_ring virtio"+
If the virtual file system is not the default initramfs or initrd, run the dracut -f Name of the initramfs or initrd file actually used command. The actual initramfs or initrd file name can be obtained from the menu.lst or grub.cfg file (/boot/grub/menu.lst, /boot/grub/grub.cfg, or /boot/grub2/grub.cfg).
+The following is an example initrd file of SUSE 11 SP4:
+default 0 +timeout 10 +gfxmenu (hd0,0)/boot/message +title sles11sp4_001_[_VMX_] +root (hd0,0) +kernel /boot/linux.vmx vga=0x314 splash=silent console=ttyS0,115200n8 console=tty0 net.ifnames=0 NON_PERSISTENT_DEVICE_NAMES=1 showopts +initrd /boot/initrd.vmx +title Failsafe_sles11sp4_001_[_VMX_] +root (hd0,0) +kernel /boot/linux.vmx vga=0x314 splash=silent ide=nodma apm=off noresume edd=off powersaved=off nohz=off highres=off processsor.max+cstate=1 nomodeset x11failsafe console=ttyS0,115200n8 console=tty0 net.ifnames=0 NON_PERSISTENT_DEVICE_NAMES=1 showopts +initrd /boot/initrd.vmx+
/boot/initrd.vmx in the initrd line is the initrd file actually used. Run the dracut -f /boot/initrd.vmx command. If the initrd file does not contain the /boot directory, such as /initramfs-xxx, run the dracut -f /boot/initramfs-xxx command.
+lsinitrd /boot/initrd-`uname -r` | grep xen
+SIA10000xxxxx:~ # lsinitrd /boot/initrd-`uname -r` | grep xen +-rwxr--r-- 1 root root 42400 Jun 22 2012 lib/modules/2.6.32-279.el6.x86_64/kernel/drivers/block/xen-blkfront.ko +-rwxr--r-- 1 root root 44200 Jun 22 2012 lib/modules/2.6.32-279.el6.x86_64/kernel/drivers/net/xen-netfront.ko + +SIA10000xxxxx:~ # lsinitrd /boot/initrd-`uname -r` | grep virtio +-rwxr--r-- 1 root root 19248 Jun 22 2012 lib/modules/2.6.32-279.el6.x86_64/kernel/drivers/scsi/virtio_scsi.ko +-rwxr--r-- 1 root root 23856 Jun 22 2012 lib/modules/2.6.32-279.el6.x86_64/kernel/drivers/block/virtio_blk.ko +drwxr-xr-x 2 root root 0 Jul 12 14:53 lib/modules/2.6.32-279.el6.x86_64/kernel/drivers/virtio +-rwxr--r-- 1 root root 15848 Jun 22 2012 lib/modules/2.6.32-279.el6.x86_64/kernel/drivers/virtio/virtio_ring.ko +-rwxr--r-- 1 root root 20008 Jun 22 2012 lib/modules/2.6.32-279.el6.x86_64/kernel/drivers/virtio/virtio_pci.ko +-rwxr--r-- 1 root root 12272 Jun 22 2012 lib/modules/2.6.32-279.el6.x86_64/kernel/drivers/virtio/virtio.ko +-rwxr--r-- 1 root root 38208 Jun 22 2012 lib/modules/2.6.32-279.el6.x86_64/kernel/drivers/net/virtio_net.ko+
Before the modification:
+###Don't change this comment -YaST2 identifier: Original name: linux### +title SUSE Linux Enterprise Server 11SP4 - 3.0.76-0.11 (default) +root (hd0,0) +kernel /boot/vmlinuz-3.0.76-0.11-default root=UUID=4eb40294-4c6f-4384-bbb6-b8795bbb1130 splash=silentcrashkernel=256M-:128M showopts vga=0x314 +initrd /boot/initrd-3.0.76-0.11-default+
After the modification:
+###Don't change this comment -YaST2 identifier: Original name: linux### +title SUSE Linux Enterprise Server 11SP4 - 3.0.76-0.11 (default) +root (hd0,0) +kernel /boot/vmlinuz-3.0.76-0.11-default root=UUID=4eb40294-4c6f-4384-bbb6-b8795bbb1130 splash=silentcrashkernel=256M-:128M showopts vga=0x314 xen_platform_pci.dev_unplug=all +initrd /boot/initrd-3.0.76-0.11-default+
lsinitrd /boot/initrd-`uname -r` | grep xen
+lsinitrd /boot/initrd-`uname -r` | grep virtio
+SIA10000xxxxx:~ # lsinitrd /boot/initrd-`uname -r` | grep xen +-rwxr--r-- 1 root root 42400 Jun 22 2012 lib/modules/2.6.32-279.el6.x86_64/kernel/drivers/block/xen-blkfront.ko +-rwxr--r-- 1 root root 44200 Jun 22 2012 lib/modules/2.6.32-279.el6.x86_64/kernel/drivers/net/xen-netfront.ko + +SIA10000xxxxx:~ # lsinitrd /boot/initrd-`uname -r` | grep virtio +-rwxr--r-- 1 root root 19248 Jun 22 2012 lib/modules/2.6.32-279.el6.x86_64/kernel/drivers/scsi/virtio_scsi.ko +-rwxr--r-- 1 root root 23856 Jun 22 2012 lib/modules/2.6.32-279.el6.x86_64/kernel/drivers/block/virtio_blk.ko +drwxr-xr-x 2 root root 0 Jul 12 14:53 lib/modules/2.6.32-279.el6.x86_64/kernel/drivers/virtio +-rwxr--r-- 1 root root 15848 Jun 22 2012 lib/modules/2.6.32-279.el6.x86_64/kernel/drivers/virtio/virtio_ring.ko +-rwxr--r-- 1 root root 20008 Jun 22 2012 lib/modules/2.6.32-279.el6.x86_64/kernel/drivers/virtio/virtio_pci.ko +-rwxr--r-- 1 root root 12272 Jun 22 2012 lib/modules/2.6.32-279.el6.x86_64/kernel/drivers/virtio/virtio.ko +-rwxr--r-- 1 root root 38208 Jun 22 2012 lib/modules/2.6.32-279.el6.x86_64/kernel/drivers/net/virtio_net.ko+
If you add built-in drivers to the initrd or initramfs file, the ECS will not be affected. This makes it easy to modify the drivers. However, you cannot check the drivers by running the lsinitrd command. You can run the following commands to check whether built-in drivers are in the kernel:
+cat /boot/config-`uname -r` | grep CONFIG_VIRTIO | grep y
+cat /boot/config-`uname -r` | grep CONFIG_XEN | grep y
+vi /etc/dracut.conf
+[root@CTU10000xxxxx ~]# vi /etc/dracut.conf +# additional kernel modules to the default +add_drivers+="ata_piix ata_generic xen_vnif xen_vbd xen_platform_pci virtio_blk virtio_scsi virtio_net virtio_pci virtio_ring virtio"+
dracut -f /boot/initramfs-File name
+If the virtual file system is not the default initramfs, run the dracut -f Name of the initramfs or initrd file actually used command. The actual initramfs or initrd file name can be obtained from the grub.cfg file, which can be /boot/grub/grub.cfg, /boot/grub2/grub.cfg, or /boot/grub/grub.conf depending on the OS.
+lsinitrd /boot/initramfs-`uname -r`.img | grep xen
+lsinitrd /boot/initramfs-`uname -r`.img | grep virtio
+If the virtual file system is initrd, run the following commands to check whether native Xen and KVM drivers have been loaded:
+lsinitrd /boot/initrd-`uname -r` | grep xen
+lsinitrd /boot/initrd-`uname -r` | grep virtio
+vi /etc/dracut.conf
+[root@CTU10000xxxxx ~]# vi /etc/dracut.conf +# additional kernel modules to the default +add_drivers+="ata_piix ata_generic xen-blkfront xen-netfront virtio_blk virtio_scsi virtio_net virtio_pci virtio_ring virtio"+
dracut -f /boot/initramfs-File name
+If the virtual file system is not the default initramfs, run the dracut -f Name of the initramfs or initrd file actually used command. The actual initramfs or initrd file name can be obtained from the grub.cfg file, which can be /boot/grub/grub.cfg, /boot/grub2/grub.cfg, or /boot/grub/grub.conf depending on the OS.
+lsinitrd /boot/initramfs-`uname -r`.img | grep xen
+lsinitrd /boot/initramfs-`uname -r`.img | grep virtio
+If the virtual file system is initrd, run the following commands to check whether the native Xen and KVM driver modules are successfully loaded:
+lsinitrd /boot/initrd-`uname -r` | grep xen
+lsinitrd /boot/initrd-`uname -r` | grep virtio
+Assume that the virtual file system is initrd. The following command output will be displayed:
+sluo-ecs-30dc:~ # lsinitrd /boot/initrd-`uname -r` | grep xen +-rw-r--r-- 1 root root 69575 Oct 26 2016 lib/modules/4.4.21-69-default/kernel/drivers/block/xen-blkfront.ko +-rw-r--r-- 1 root root 53415 Oct 26 2016 lib/modules/4.4.21-69-default/kernel/drivers/net/xen-netfront.ko +drwxr-xr-x 2 root root 0 Sep 28 10:21 lib/modules/4.4.21-69-default/updates/pvdriver/xen-hcall +-rwxr-xr-x 1 root root 8320 Sep 28 10:21 lib/modules/4.4.21-69-default/updates/pvdriver/xen-hcall/xen-hcall.ko + +sluo-ecs-30dc:~ # lsinitrd /boot/initrd-`uname -r` | grep virtio +-rw-r--r-- 1 root root 29335 Oct 26 2016 lib/modules/4.4.21-69-default/kernel/drivers/block/virtio_blk.ko +-rw-r--r-- 1 root root 57007 Oct 26 2016 lib/modules/4.4.21-69-default/kernel/drivers/net/virtio_net.ko +-rw-r--r-- 1 root root 32415 Oct 26 2016 lib/modules/4.4.21-69-default/kernel/drivers/scsi/virtio_scsi.ko +drwxr-xr-x 2 root root 0 Sep 28 10:21 lib/modules/4.4.21-69-default/kernel/drivers/virtio +-rw-r--r-- 1 root root 19623 Oct 26 2016 lib/modules/4.4.21-69-default/kernel/drivers/virtio/virtio.ko +-rw-r--r-- 1 root root 38943 Oct 26 2016 lib/modules/4.4.21-69-default/kernel/drivers/virtio/virtio_pci.ko +-rw-r--r-- 1 root root 24431 Oct 26 2016 lib/modules/4.4.21-69-default/kernel/drivers/virtio/virtio_ring.ko+
If you add built-in drivers to the initrd or initramfs file, the ECS will not be affected. This makes it easy to modify the drivers. However, you cannot check the drivers by running the lsinitrd command. You can run the following commands to check whether built-in drivers are in the kernel:
+cat /boot/config-`uname -r` | grep CONFIG_VIRTIO | grep y
+cat /boot/config-`uname -r` | grep CONFIG_XEN | grep y
+When optimizing a Linux private image, you need to change the disk identifier to UUID in the GRUB configuration file of the ECS.
+
The root partition identified in the configuration file varies depending on the OS. It may be root=/dev/xvda or root=/dev/disk.
+The following information is displayed:
+/dev/xvda1: UUID="ec51d860-34bf-4374-ad46-a0c3e337fd34" TYPE="ext3" +/dev/xvda5: UUID="7a44a9ce-9281-4740-b95f-c8de33ae5c11" TYPE="swap"+
cat /boot/grub/grub.cfg
+The following information is displayed:
+......menuentry 'Ubuntu Linux, with Linux 3.13.0-24-generic' --class ubuntu --class gnu-linux --class gnu --class os --unrestricted $menuentry_id_option 'gnulinux-3.13.0-24-generic-advanced-ec51d860-34bf-4374-ad46-a0c3e337fd34' {
+recordfail
+load_video
+gfxmode $linux_gfx_mode
+insmod gzio
+insmod part_msdos
+insmod ext2
+if [ x$feature_platform_search_hint = xy ]; then
+search --no-floppy --fs-uuid --set=root ec51d860-34bf-4374-ad46-a0c3e337fd34
+else
+search --no-floppy --fs-uuid --set=root ec51d860-34bf-4374-ad46-a0c3e337fd34
+fi
+echo 'Loading Linux 3.13.0-24-generic ...'
+linux /boot/vmlinuz-3.13.0-24-generic root=/dev/xvda1 ro
+echo 'Loading initial ramdisk ...'
+initrd /boot/initrd.img-3.13.0-24-generic
+}
+vi /boot/grub/grub.cfg
+The change is successful if information similar to the following is displayed:
+......menuentry 'Ubuntu Linux, with Linux 3.13.0-24-generic' --class ubuntu --class gnu-linux --class gnu --class os --unrestricted $menuentry_id_option 'gnulinux-3.13.0-24-generic-advanced-ec51d860-34bf-4374-ad46-a0c3e337fd34' {
+recordfail
+load_video
+gfxmode $linux_gfx_mode
+insmod gzio
+insmod part_msdos
+insmod ext2
+if [ x$feature_platform_search_hint = xy ]; then
+search --no-floppy --fs-uuid --set=root ec51d860-34bf-4374-ad46-a0c3e337fd34
+else
+search --no-floppy --fs-uuid --set=root ec51d860-34bf-4374-ad46-a0c3e337fd34
+fi
+echo 'Loading Linux 3.13.0-24-generic ...'
+linux /boot/vmlinuz-3.13.0-24-generic root=UUID=ec51d860-34bf-4374-ad46-a0c3e337fd34 ro
+echo 'Loading initial ramdisk ...'
+initrd /boot/initrd.img-3.13.0-24-generic
+}
+The following information is displayed:
+/dev/xvda1: UUID="749d6c0c-990a-4661-bed1-46769388365a" TYPE="swap" +/dev/xvda2: UUID="f382872b-eda6-43df-9516-5a687fecdce6" TYPE="ext4"+
cat /boot/grub/grub.conf
+The following information is displayed:
+default=0 +timeout=5 +splashimage=(hd0,1)/boot/grub/splash.xpm.gz +hiddenmenu +title CentOS (2.6.32-573.8.1.el6.x86_64) +root (hd0,1) +kernel /boot/vmlinuz-2.6.32-573.8.1.el6.x86_64 ro root=/dev/xvda2 rd_NO_LUKS rd_NO_LVM LANG=en_US.UTF-8 rd_NO_MD SYSFONT=latarcyrheb-sun16 crashkernel=autoKEYBOARDTYPE=pc KEYTABLE=us rd_NO_DM rhgb quiet +initrd /boot/initramfs-2.6.32-573.8.1.el6.x86_64.img+
vi /boot/grub/grub.conf
+The change is successful if information similar to the following is displayed:
+default=0 +timeout=5 +splashimage=(hd0,1)/boot/grub/splash.xpm.gz +hiddenmenu +title CentOS (2.6.32-573.8.1.el6.x86_64) +root (hd0,1) +kernel /boot/vmlinuz-2.6.32-573.8.1.el6.x86_64 ro root=UUID=f382872b-eda6-43df-9516-5a687fecdce6 rd_NO_LUKS rd_NO_LVM LANG=en_US.UTF-8 rd_NO_MD SYSFONT=latarcyrheb-sun16 crashkernel=autoKEYBOARDTYPE=pc KEYTABLE=us rd_NO_DM rhgb quiet +initrd /boot/initramfs-2.6.32-573.8.1.el6.x86_64.img+
The following information is displayed:
+/dev/xvda2: UUID="4eb40294-4c6f-4384-bbb6-b8795bbb1130" TYPE="xfs" +/dev/xvda1: UUID="2de37c6b-2648-43b4-a4f5-40162154e135" TYPE="swap"+
cat /boot/grub2/grub.cfg
+The following information is displayed:
+......
+menuentry 'CentOS Linux (3.10.0-229.el7.x86_64) 7 (Core)' --class fedora --class gnu-linux --class gnu --class os --unrestricted $menuentry_id_option 'gnulinux-3.10.0-229.el7.x86_64-advanced-4eb40294-4c6f-4384-bbb6-b8795bbb1130' {
+load_video
+set gfxpayload=keep
+insmod gzio
+insmod part_msdos
+insmod xfs
+set root='hd0,msdos2'
+if [ x$feature_platform_search_hint = xy ]; then
+search --no-floppy --fs-uuid --set=root --hint='hd0,msdos2'4eb40294-4c6f-4384-bbb6-b8795bbb1130
+else
+search --no-floppy --fs-uuid --set=root 4eb40294-4c6f-4384-bbb6-b8795bbb1130
+fi
+linux16 /boot/vmlinuz-3.10.0-229.el7.x86_64 root=/dev/xvda2 ro crashkernel=auto rhgb quiet LANG=en_US.UTF-8
+initrd16 /boot/initramfs-3.10.0-229.el7.x86_64.img
+}
+vi /boot/grub2/grub.cfg
+The change is successful if information similar to the following is displayed:
+......
+menuentry 'CentOS Linux (3.10.0-229.el7.x86_64) 7 (Core)' --class fedora --class gnu-linux --class gnu --class os --unrestricted $menuentry_id_option 'gnulinux-3.10.0-229.el7.x86_64-advanced-4eb40294-4c6f-4384-bbb6-b8795bbb1130' {
+load_video
+set gfxpayload=keep
+insmod gzio
+insmod part_msdos
+insmod xfs
+set root='hd0,msdos2'
+if [ x$feature_platform_search_hint = xy ]; then
+search --no-floppy --fs-uuid --set=root --hint='hd0,msdos2'4eb40294-4c6f-4384-bbb6-b8795bbb1130
+else
+search --no-floppy --fs-uuid --set=root 4eb40294-4c6f-4384-bbb6-b8795bbb1130
+fi
+linux16 /boot/vmlinuz-3.10.0-229.el7.x86_64 root=UUID=4eb40294-4c6f-4384-bbb6-b8795bbb1130 ro crashkernel=auto rhgb quiet LANG=en_US.UTF-8
+initrd16 /boot/initramfs-3.10.0-229.el7.x86_64.img
+}
+When optimizing a Linux private image, you need to change the disk identifier to UUID in the fstab configuration file of the ECS.
+The following information is displayed:
+/dev/xvda2: UUID="4eb40294-4c6f-4384-bbb6-b8795bbb1130" TYPE="xfs" +/dev/xvda1: UUID="2de37c6b-2648-43b4-a4f5-40162154e135" TYPE="swap"+
cat /etc/fstab
+The following information is displayed:
+[root@CTU1000028010 ~]# cat /etc/fstab +/dev/xvda2 / xfs defaults 0 0 +/dev/xvda1 swap swap defaults 0 0+
vi /etc/fstab
+/dev/xvda2: UUID="4eb40294-4c6f-4384-bbb6-b8795bbb1130" TYPE="xfs" +/dev/xvda1: UUID="2de37c6b-2648-43b4-a4f5-40162154e135" TYPE="swap"+
Before the change:
+[root@CTU1000028010 ~]# cat /etc/fstab +/dev/xvda2 / xfs defaults 0 0 +/dev/xvda1 swap swap defaults 0 0+
After the change:
+[root@CTU1000028010 ~]# cat /etc/fstab +UUID=4eb40294-4c6f-4384-bbb6-b8795bbb1130 / xfs defaults 0 0 +UUID=2de37c6b-2648-43b4-a4f5-40162154e135 swap swap defaults 0 0+
The change is successful if information similar to the following is displayed:
+[root@CTU1000028010 ~]# cat /etc/fstab +UUID=4eb40294-4c6f-4384-bbb6-b8795bbb1130 / xfs defaults 0 0 +UUID=2de37c6b-2648-43b4-a4f5-40162154e135 swap swap defaults 0 0+
IMS supports multiple image formats, but the system uses ZVHD or ZVHD2 by default.
+Table 1 lists the common image formats.
+ +Image Format + |
+Description + |
+Remarks + |
+
|---|---|---|
ZVHD + |
+This format uses the ZLIB compression algorithm and supports sequential read and write. + |
+A universal format supported by IaaS OpenStack; a format supported for imported and exported images + |
+
ZVHD2 + |
+This format uses the ZSTD algorithm and supports lazy loading. + |
+A format for the lazy loading feature; a format supported for imported images + |
+
QCOW2 + |
+This is a disk image supported by the QEMU simulator. It is a file that indicates a block device disk of a fixed size. Compared with the RAW format, the QCOW2 format has the following features: +
|
+A format supported for imported and exported images + |
+
VMDK + |
+VMDK is a virtual disk format from VMware. A VMDK file represents a physical disk drive of the virtual machine file system (VMFS) on an ECS. + |
+A format supported for imported and exported images + |
+
VHD + |
+VHD is a virtual disk file format from Microsoft. A VHD file is a compressed file stored in the file system of the host machine. It mainly contains a file system required for starting ECSs. + |
+A format supported for imported and exported images + |
+
VHDX + |
+VHDX is a new VHD format introduced into Hyper-V of Windows Server 2012 by Microsoft. Compared with the VHD format, VHDX has a larger storage capacity. It provides protection against data damage during power supply failures, and the disk structure alignment has been optimized to prevent performance degradation of new physical disks in a large sector. + |
+A format supported for imported images + |
+
RAW + |
+A RAW file can be directly read and written by ECSs. This format does not support dynamic space expansion and has the best I/O performance. + |
+A format supported for imported images + |
+
QCOW + |
+QCOW manages the space allocation of an image through the secondary index table. The secondary index uses the memory cache technology and needs the query operation, which results in performance loss. The performance of QCOW is inferior to that of QCOW2, and the read and write performance is inferior to that of RAW. + |
+A format supported for imported images + |
+
VDI + |
+VDI is the disk image file format used by the VirtualBOX virtualization software from Oracle. It supports snapshots. + |
+A format supported for imported images + |
+
QED + |
+The QED format is an evolved version of the QCOW2 format. Its storage location query mode and data block size are the same as those of the QCOW2 format. However, QED implements Copy-On-Write (CoW) in a different way as it uses a dirty flag to replace the reference count table of QCOW2. + |
+A format supported for imported images + |
+
You can export the public or private image list in the current region as a CSV file to your local PC.
+The IMS console is displayed.
+
.The system will automatically export all private images in the current region under your account to a local directory.
+
The file name is in the format of private-images-Region ID-Export time.
+The IMS console is displayed.
+
.The system will automatically export all public images in the current region to a local directory.
+
The file name is in the format of public-images-Region ID-Export time.
+Create a full-ECS image from a CSBS backup. This image can then be used to create ECSs.
+The IMS console is displayed.
+
When the image status changes to Normal, the image creation is complete.
+
If a full-ECS image contains one or more data disks, the system configures data disk parameters automatically when you use the image to create ECSs.
+OS + |
+Driver + |
+How to Obtain + |
+
|---|---|---|
Ubuntu 16.04 + |
+GPU driver installation package NVIDIA-Linux-x86_64-375.66.run + |
+http://www.nvidia.com/download/driverResults.aspx/118955/en-us + |
+
CUDA Toolkit installation package cuda_8.0.61_375.26_linux.run + |
+https://developer.nvidia.com/compute/cuda/8.0/Prod2/local_installers/cuda_8.0.61_375.26_linux-run + |
+|
CentOS 7.4 + |
+GPU driver installation package NVIDIA-Linux-x86_64-375.66.run + |
+http://www.nvidia.com/download/driverResults.aspx/118955/en-us + |
+
CUDA Toolkit installation package cuda_8.0.61_375.26_linux.run + |
+https://developer.nvidia.com/compute/cuda/8.0/Prod2/local_installers/cuda_8.0.61_375.26_linux-run + |
+|
Debian 9.0 + |
+GPU driver installation package NVIDIA-Linux-x86_64-384.81.run + |
+http://www.nvidia.com/download/driverResults.aspx/124722/en-us + |
+
CUDA Toolkit installation package cuda_9.0.176_384.81_linux.run + |
+https://developer.nvidia.com/compute/cuda/9.0/Prod/local_installers/cuda_9.0.176_384.81_linux-run + |
+
The procedure for installing the NVIDIA driver varies according to the OS.
+sudo su
+Perform this step only if the GCC and g++ software has not been installed.
+apt-get install gcc
+apt-get install g++
+apt-get install make
+Perform this step if the Nouveau driver has been installed on the target ECS. This prevents conflict with the NVIDIA driver installation.
+blacklist nouveau
+options nouveau modeset=0
+mv /boot/initramfs-$(uname -r).img /boot/initramfs-$(uname -r).img.bak
+update-initramfs -u
+If the ECS has been logged in using the GUI, disable the X service before installing the NVIDIA driver.
+ +To download the GPU driver, log in at http://www.nvidia.com/Download/index.aspx?lang=en.
+
To download the CUDA Toolkit, log in at https://developer.nvidia.com/cuda-downloads.
+./cuda_a.b.cc_xxx.yy_linux.run -toolkit -samples -silent -override --tmpdir=/tmp/
+cd /usr/local/cuda/samples/1_Utilities/deviceQueryDrv/
+make
+./deviceQueryDrv
+If the terminal display contains "Result = PASS", both CUDA Toolkit and GPU driver have been installed.
+./deviceQueryDrv Starting... + + CUDA Device Query (Driver API) statically linked version + Detected 1 CUDA Capable device(s) + + Device 0: "Tesla P100-PCIE-16GB" + CUDA Driver Version: 8.0 + CUDA Capability Major/Minor version number: 6.0 + Total amount of global memory: 16276 MBytes (17066885120 bytes) + (56) Multiprocessors, ( 64) CUDA Cores/MP: 3584 CUDA Cores + GPU Max Clock rate: 1329 MHz (1.33 GHz) + Memory Clock rate: 715 Mhz + Memory Bus Width: 4096-bit + L2 Cache Size: 4194304 bytes + Max Texture Dimension Sizes 1D=(131072) 2D=(131072, 65536) 3D=(16384, 16384, 16384) + Maximum Layered 1D Texture Size, (num) layers 1D=(32768), 2048 layers + Maximum Layered 2D Texture Size, (num) layers 2D=(32768, 32768), 2048 layers + Total amount of constant memory: 65536 bytes + Total amount of shared memory per block: 49152 bytes + Total number of registers available per block: 65536 + Warp size: 32 + Maximum number of threads per multiprocessor: 2048 + Maximum number of threads per block: 1024 + Max dimension size of a thread block (x,y,z): (1024, 1024, 64) + Max dimension size of a grid size (x,y,z): (2147483647, 65535, 65535) + Texture alignment: 512 bytes + Maximum memory pitch: 2147483647 bytes + Concurrent copy and kernel execution: Yes with 2 copy engine(s) + Run time limit on kernels: No + Integrated GPU sharing Host Memory: No + Support host page-locked memory mapping: Yes + Concurrent kernel execution: Yes + Alignment requirement for Surfaces: Yes + Device has ECC support: Enabled + Device supports Unified Addressing (UVA): Yes + Device PCI Domain ID / Bus ID / location ID: 0 / 0 / 6 + Compute Mode: + < Default (multiple host threads can use ::cudaSetDevice() with device simultaneously) > + Result = PASS+
sudo su
+Perform this step only if GCC, g++, and kernel-devel have not been installed.
+yum install gcc
+yum install gcc-c++
+yum install make
+yum install kernel-devel-`uname -r`
+Perform this step if the Nouveau driver has been installed on the target ECS. This prevents conflict with the NVIDIA driver installation.
+blacklist nouveau
+mv /boot/initramfs-$(uname -r).img /boot/initramfs-$(uname -r).img.bak
+dracut -v /boot/initramfs-$(uname -r).img $(uname -r)
+If the ECS has been logged in using the GUI, disable the X service before installing the NVIDIA driver.
+ +To download the GPU driver, log in at http://www.nvidia.com/Download/index.aspx?lang=en.
+
To download the CUDA Toolkit, log in at https://developer.nvidia.com/cuda-downloads.
+./cuda_a.b.cc_xxx.yy_linux.run -toolkit -samples -silent -override --tmpdir=/tmp/
+cd /usr/local/cuda/samples/1_Utilities/deviceQueryDrv/
+make
+./deviceQueryDrv
+If the terminal display contains "Result = PASS", both CUDA Toolkit and GPU driver have been installed.
+./deviceQueryDrv Starting... + + CUDA Device Query (Driver API) statically linked version + Detected 1 CUDA Capable device(s) + + Device 0: "Tesla P100-PCIE-16GB" + CUDA Driver Version: 8.0 + CUDA Capability Major/Minor version number: 6.0 + Total amount of global memory: 16276 MBytes (17066885120 bytes) + (56) Multiprocessors, ( 64) CUDA Cores/MP: 3584 CUDA Cores + GPU Max Clock rate: 1329 MHz (1.33 GHz) + Memory Clock rate: 715 Mhz + Memory Bus Width: 4096-bit + L2 Cache Size: 4194304 bytes + Max Texture Dimension Sizes 1D=(131072) 2D=(131072, 65536) 3D=(16384, 16384, 16384) + Maximum Layered 1D Texture Size, (num) layers 1D=(32768), 2048 layers + Maximum Layered 2D Texture Size, (num) layers 2D=(32768, 32768), 2048 layers + Total amount of constant memory: 65536 bytes + Total amount of shared memory per block: 49152 bytes + Total number of registers available per block: 65536 + Warp size: 32 + Maximum number of threads per multiprocessor: 2048 + Maximum number of threads per block: 1024 + Max dimension size of a thread block (x,y,z): (1024, 1024, 64) + Max dimension size of a grid size (x,y,z): (2147483647, 65535, 65535) + Texture alignment: 512 bytes + Maximum memory pitch: 2147483647 bytes + Concurrent copy and kernel execution: Yes with 2 copy engine(s) + Run time limit on kernels: No + Integrated GPU sharing Host Memory: No + Support host page-locked memory mapping: Yes + Concurrent kernel execution: Yes + Alignment requirement for Surfaces: Yes + Device has ECC support: Enabled + Device supports Unified Addressing (UVA): Yes + Device PCI Domain ID / Bus ID / location ID: 0 / 0 / 6 + Compute Mode: + < Default (multiple host threads can use ::cudaSetDevice() with device simultaneously) > + Result = PASS+
sudo su
+Perform this step only if the GCC and g++ software has not been installed.
+apt-get install gcc
+apt-get install g++
+apt-get install make
+apt-get install linux-headers-$(uname -r)
+Perform this step if the Nouveau driver has been installed on the target ECS. This prevents conflict with the NVIDIA driver installation.
+blacklist nouveau
+options nouveau modeset=0
+mv /boot/initramfs-$(uname -r).img /boot/initramfs-$(uname -r).img.bak
+update-initramfs -u
+If the ECS has been logged in using the GUI, disable the X service before installing the NVIDIA driver.
+ +To download the GPU driver, log in at http://www.nvidia.com/Download/index.aspx?lang=en.
+
To download the CUDA Toolkit, log in at https://developer.nvidia.com/cuda-downloads.
+./cuda_a.b.cc_xxx.yy_linux.run -toolkit -samples -silent -override --tmpdir=/tmp/
+cd /usr/local/cuda/samples/1_Utilities/deviceQueryDrv/
+make
+./deviceQueryDrv
+If the terminal display contains "Result = PASS", both CUDA Toolkit and GPU driver have been installed.
+./deviceQueryDrv Starting... + +CUDA Device Query (Driver API) statically linked version +Detected 1 CUDA Capable device(s) + +Device 0: "Tesla P100-PCIE-16GB" + CUDA Driver Version: 9.0 + CUDA Capability Major/Minor version number: 6.0 + Total amount of global memory: 16276 MBytes (17066885120 bytes) + (56) Multiprocessors, ( 64) CUDA Cores/MP: 3584 CUDA Cores + GPU Max Clock rate: 1329 MHz (1.33 GHz) + Memory Clock rate: 715 Mhz + Memory Bus Width: 4096-bit + L2 Cache Size: 4194304 bytes + Max Texture Dimension Sizes 1D=(131072) 2D=(131072, 65536) 3D=(16384, 16384, 16384) + Maximum Layered 1D Texture Size, (num) layers 1D=(32768), 2048 layers + Maximum Layered 2D Texture Size, (num) layers 2D=(32768, 32768), 2048 layers + Total amount of constant memory: 65536 bytes + Total amount of shared memory per block: 49152 bytes + Total number of registers available per block: 65536 + Warp size: 32 + Maximum number of threads per multiprocessor: 2048 + Maximum number of threads per block: 1024 + Max dimension size of a thread block (x,y,z): (1024, 1024, 64) + Max dimension size of a grid size (x,y,z): (2147483647, 65535, 65535) + Texture alignment: 512 bytes + Maximum memory pitch: 2147483647 bytes + Concurrent copy and kernel execution: Yes with 2 copy engine(s) + Run time limit on kernels: No + Integrated GPU sharing Host Memory: No + Support host page-locked memory mapping: Yes + Concurrent kernel execution: Yes + Alignment requirement for Surfaces: Yes + Device has ECC support: Enabled + Device supports Unified Addressing (UVA): Yes + Supports Cooperative Kernel Launch: Yes + Supports MultiDevice Co-op Kernel Launch: Yes + Device PCI Domain ID / Bus ID / location ID: 0 / 0 / 6 + Compute Mode: + < Default (multiple host threads can use ::cudaSetDevice() with device simultaneously) > +Result = PASS+
Running Sysprep ensures that an ECS has a unique SID after it is added to a domain.
+After installing Cloudbase-Init on an ECS, you need to decide whether the ECS needs to be added to a domain or whether it must have a unique SID. If yes, run Sysprep as instructed in this section.
+Run the following command in the Windows command line and check how many times you can run Sysprep in the displayed Windows Script Host dialog box:
+slmgr.vbs /dlv
+If the value of Remaining Windows rearm count is 0, you cannot run Sysprep.
+
C:\Program Files\Cloudbase Solutions\ is used as an example of the Cloudbase-Init installation directory. Switch to the root directory of drive C and run the following command to enter the installation directory:
+cd C:\Program Files\Cloudbase Solutions\Cloudbase-Init\conf
+C:\Windows\System32\sysprep\sysprep.exe /generalize /oobe /unattend:Unattend.xml
+

Run the following command to query the ECS SID:
+whoami /user
+

For how to create a BMS private image, see Bare Metal Server User Guide.
+When you create a ZVHD2 image using an API, the image is created in the ZVHD format.
+Check whether your token contains the op_gated_lld role (op_gated_lld is the OBT tag, which can be viewed in the body of the response message of the API used to obtain a user token). The ZVHD2 image has the lazy loading feature. If the current environment does not support this feature or this feature is in the OBT phase, the ZVHD2 image will fail to be created.
+Contact the customer service to ensure that the current environment supports the lazy loading feature, obtain a new token, and use the new token to create an image.
+A data disk image contains only service data. You can create a data disk image from an ECS and then use the image to create new EVS disks. This is a convenient way to migrate data from an ECS to EVS disks.
+For example, you can create a data disk image to clone the data of an ECS whose disk is about to expire.
+The following figure shows the process of creating a data disk image from an ECS.
+
If the capacity is greater than 1 TB, you can only use the ECS to create a full-ECS image.
+The IMS console is displayed.
+
If you want to use the created data disk image to create an EVS disk and attach it to an ECS, you can perform either of the following operations:
+
A data disk image can be used to create a data disk for an ECS only once.
+HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\NetworkList\Profiles
+Click each item under Profiles and query the Data column of ProfileName in the right pane.
+HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\NetworkList\Profiles
+HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\NetworkList\Signatures\Unmanaged
+
An ECS used to create a Windows full-ECS image cannot have a spanned volume. If you attempt to create an image from an ECS with a spanned volume, when the image is used to create new ECSs, data may be lost.
+If an ECS has a spanned volume, back up data in the spanned volume and then delete this volume from the ECS. Use the ECS to create a full-ECS image. Use the full-ECS image to create an ECS. Then, use the backup to create a spanned volume for the new ECS if necessary.
+
If a Linux ECS has a volume group or a logical volume consisting of multiple physical volumes, to ensure you do not lose any data, back up data in the volume group or logical volume and delete the volume group or logical volume before using this ECS to create a full-ECS image.
+Cloud Trace Service (CTS) is a log audit service provided by the public cloud and intended for cloud security. It allows you to collect, store, and query cloud resource operation records and use these records for security analysis, compliance auditing, resource tracking, and fault locating.
+You can use CTS to record IMS operations for later querying, auditing, and backtracking.
+You need to enable CTS before using it. If it is not enabled, IMS operations cannot be recorded. After being enabled, CTS automatically creates a tracker to record all your operations. The tracker stores only the operations of the last seven days. To store the operations for a longer time, store trace files in OBS buckets.
+Operation + |
+Resource Type + |
+Trace Name + |
+
|---|---|---|
Creating an Image + |
+ims + |
+createImage + |
+
Modifying an image + |
+ims + |
+updateImage + |
+
Deleting images in a batch + |
+ims + |
+deleteImage + |
+
Replicating an image + |
+ims + |
+copyImage + |
+
Exporting an image + |
+ims + |
+exportImage + |
+
Adding a tenant that can use a shared image + |
+ims + |
+addMember + |
+
Modifying tenants that can use a shared image + |
+ims + |
+updateMember + |
+
Deleting tenants from the group where the members can use a shared image + |
+ims + |
+deleteMemeber + |
+
Operation + |
+Trace Name + |
+Service Type + |
+Resource Type + |
+OpenStack Component + |
+
|---|---|---|---|---|
Creating an Image + |
+createImage + |
+IMS + |
+image + |
+glance + |
+
Modifying/Uploading an image + |
+updateImage + |
+IMS + |
+image + |
+glance + |
+
Deleting an image + |
+deleteImage + |
+IMS + |
+image + |
+glance + |
+
Tagging an image + |
+addTag + |
+IMS + |
+image + |
+glance + |
+
Deleting an image tag + |
+deleteTag + |
+IMS + |
+image + |
+glance + |
+
Adding a tenant that can use a shared image + |
+addMember + |
+IMS + |
+image + |
+glance + |
+
Modifying information about a tenant that can use a shared image + |
+updateMember + |
+IMS + |
+image + |
+glance + |
+
Deleting a tenant from the group where the members can use a shared image + |
+deleteMember + |
+IMS + |
+image + |
+glance + |
+
Once CTS is enabled, it starts recording IMS operations. You can view operations recorded in the last seven days on the CTS management console.
+This section describes how to view the records.
+Select Management for Trace Type and IMS for Trace Source.
+Note that:
+
to expand the trace details.This issue is probably caused by the failure of offline VirtIO driver injection.
+When you inject the VirtIO driver for a Windows ECS offline, there are some restrictions:
+To update the VirtIO driver, you must install UVP VMTools. For how to install UVP VMTools, see Optimizing a Windows Private Image.
+Boot Mode + |
+Description + |
+Highlight + |
+
|---|---|---|
BIOS + |
+Basic Input Output System (BIOS) stores important basic input/output programs of ECSs, system settings, self-test programs upon system startup, and automatic startup programs. + |
+Provides basic settings and control for ECSs. + |
+
UEFI + |
+Unified Extensible Firmware Interface (UEFI) is a specification that defines a software interface between an OS and platform firmware. UEFI can be used to automatically load an OS from a pre-boot operating environment. + |
+Boots up or recovers from sleep state faster. + |
+
A major cause is that the version of Cloud-Init is incompatible with that of NetworkManager. In Debian 9.0 and later versions, NetworkManager is incompatible with Cloud-Init 0.7.9.
+Uninstall the current Cloud-Init and install Cloud-Init 0.7.6 or an earlier version.
+For details about how to install Cloud-Init, see Installing Cloud-Init.
+You can create an image of an entire ECS, including not just the OS, but also the software and all the service data. You can then use this image to migrate data by quickly provisioning exact clones of the original ECS.
+The following figure shows the process of creating an image from an entire ECS, with both the system and data disks included.
+ +Windows has three types of SAN policies: OnlineAll, OfflineShared, and OfflineInternal.
+ +Type + |
+Description + |
+
|---|---|
OnlineAll + |
+All newly detected disks are automatically brought online. + |
+
OfflineShared + |
+All disks on sharable buses, such as iSCSI and FC, are left offline by default, while disks on non-sharable buses are kept online. + |
+
OfflineInternal + |
+All newly detected disks are left offline. + |
+
diskpart
+san policy=onlineall
+The IMS console is displayed.
+
The created full-ECS image and backup are stored in the server backup vault.
+If no server backup vault is available, click Create Server Backup Vault to create one. Ensure that you select Backup for Protection Type. For more information about CBR backups and vaults, see Cloud Backup and Recovery User Guide.
+In this case, the full-ECS image can be used to provision ECSs only in the specified AZ. If you want to use this image to provision ECSs in other AZs of the region, you need to wait until Available in AZX disappears from under Normal, which indicates that the ECS backup has been successfully created. This process takes about 10 minutes, depending on the data volume of the source ECS.
+
If a full-ECS image contains one or more data disks, the system configures data disk parameters automatically when you use the image to create ECSs.
+If an ECS starts slowly, you can change the default timeout duration to speed up the startup.
+sudo su
+
You can import an image file in VHD, VMDK, QCOW2, RAW, VHDX, QCOW, VDI, QED, ZVHD, or ZVHD2 format to the cloud platform. Image files in other formats need to be converted before being imported. The open-source tool qemu-img is provided for you to convert image file formats.
+For example, to convert a CentOS 6.9 VHD image file into a QCOW2 image file, run the following command:
+qemu-img convert -p -f vpc -O qcow2 centos6.9.vhd centos6.9.qcow2
+
If Path does not exist, add it and set its value to D:\Program Files\qemu.
+Choose Start > Run, enter cmd, and press Enter. In the cmd window, enter qemu-img --help. If the qemu-img version information is contained in the command output, the installation is successful.
+d:
+cd D:\Program Files\qemu
+qemu-img convert -p -f vmdk -O qcow2 centos6.9.vmdk centos6.9.qcow2
+The parameters are described as follows:
+After the conversion is complete, the target image file is displayed in the directory where the source image file is located.
+The following information is displayed:
+# qemu-img convert -p -f vmdk -O qcow2 centos6.9.vmdk centos6.9.qcow2 + (100.00/100%)+
The following information is displayed:
+# qemu-img info centos6.9.qcow2 +image: centos6.9.qcow2 +file format: qcow2 +virtual size: 1.0G (1073741824 bytes) +disk size: 200K +cluster_size: 65536 +Format specific information: + compat: 1.1 + lazy refcounts: false+
If the version information and help manual of the qemu-img tool are contained in the command output, the installation is successful. If CentOS 7 is used, the command output is as follows:
+[root@CentOS7 ~]# qemu-img -v +qemu-img version 1.5.3, Copyright (c) 2004-2008 Fabrice Bellard +usage: qemu-img command [command options] +QEMU disk image utility + +Command syntax: + check [-q] [-f fmt] [--output=ofmt] [-r [leaks | all]] [-T src_cache] filename + create [-q] [-f fmt] [-o options] filename [size] + commit [-q] [-f fmt] [-t cache] filename + compare [-f fmt] [-F fmt] [-T src_cach]+
qemu-img convert -p -f vmdk -O qcow2 centos6.9.vmdk centos6.9.qcow2
+The parameters are described as follows:
+After the conversion is complete, the target image file is displayed in the directory where the source image file is located.
+The following information is displayed:
+[root@CentOS7 home]# qemu-img convert -p -f vmdk -O qcow2 centos6.9.vmdk centos6.9.qcow2 + (100.00/100%)+
The following information is displayed:
+[root@CentOS7 home]# qemu-img info centos6.9.qcow2 +image: centos6.9.qcow2 +file format: qcow2 +virtual size: 1.0G (1073741824 bytes) +disk size: 200K +cluster_size: 65536 +Format specific information: + compat: 1.1 + lazy refcounts: false+
A pre-allocated image depends on two files: xxxx.vmdk (configuration file) and xxxx-flat.vmdk (data file) and cannot be directly imported to the cloud platform. When you export a pre-allocated image file in VMDK monolithic Flat format from the VMware platform, you must convert its format to common VMDK or QCOW2 before it can be imported to the cloud platform.
+The following uses the image files centos6.9-64bit-flat.vmdk and centos6.9-64bit.vmdk as an example to describe how to use qemu-img to convert image formats.
+qemu-img info centos6.9-64bit.vmdk
+qemu-img info centos6.9-64bit-flat.vmdk
+The following information is displayed:
+[root@CentOS7 tmp]# ls -lh centos6.9-64bit* +-rw-r--r--. 1 root root 10G Jun 13 05:30 centos6.9-64bit-flat.vmdk +-rw-r--r--. 1 root root 327 Jun 13 05:30 centos6.9-64bit.vmdk +[root@CentOS7 tmp]# qemu-img info centos6.9-64bit.vmdk +image: centos6.9-64bit.vmdk +file format: vmdk +virtual size: 10G (10737418240 bytes) +disk size: 4.0K +Format specific information: + cid: 3302005459 + parent cid: 4294967295 + create type: monolithicFlat + extents: + [0]: + virtual size: 10737418240 + filename: centos6.9-64bit-flat.vmdk + format: FLAT +[root@CentOS7 tmp]# qemu-img info centos6.9-64bit-flat.vmdk +image: centos6.9-64bit-flat.vmdk +file format: raw +virtual size: 10G (10737418240 bytes) +disk size: 0+
The command output shows that the format of centos6.9-64bit.vmdk is VMDK and that of centos6.9-64bit-flat.vmdk is RAW. You can convert the format of only centos6.9-64bit.vmdk. For details about how to convert it, see 3.
+The following information is displayed:
+[root@CentOS7 tmp]# cat centos6.9-64bit.vmdk +# Disk DescriptorFile +version=1 +CID=c4d09ad3 +parentCID=ffffffff +createType="monolithicFlat" + +# Extent description +RW 20971520 FLAT "centos6.9-64bit-flat.vmdk" 0 + +# The Disk Data Base +#DDB + +ddb.virtualHWVersion = "4" +ddb.geometry.cylinders = "20805" +ddb.geometry.heads = "16" +ddb.geometry.sectors = "63" +ddb.adapterType = "ide"+
[root@CentOS7 tmp]# qemu-img convert -p -f vmdk -O qcow2 centos6.9-64bit.vmdk centos6.9-64bit.qcow2 + (100.00/100%)+
qemu-img info centos6.9-64bit.qcow2
+The following information is displayed:
+[root@CentOS7 tmp]# qemu-img info centos6.9-64bit.qcow2 +image: centos6.9-64bit.qcow2 +file format: qcow2 +virtual size: 10G (10737418240 bytes) +disk size: 200K +cluster_size: 65536 +Format specific information: + compat: 1.1 + lazy refcounts: false+
Open Virtualization Appliance (OVA) is a single file (with the .ova extension) that archives all the files making up an Open Virtualization Format (OVF). OVF is a folder that contains the files required for defining and deploying VMs. An OVF folder always includes .ovf, .mf, and .vmdk files.
+This section describes how to import OVF and OVA files to the cloud platform.
+Manually extract VMDK files from an OVF or OVA template and upload them to an OBS bucket. Then, you can select one from the bucket when you use an external file to create a system or data disk image.
+
The following assumes that the OVF or OVA template contains only one VMDK file. If there are multiple VMDK files (for example, there are three VMDK files, one used as a system disk image file and the others as data disk image files), upload them to an OBS bucket and register them as a system disk image and data disk images, respectively.
+├C +│ ├OvfLib +│ ├MyVm +│ ├MyVm.ovf +│ ├MyVm.mf +│ ├MyVm-disk1.vmdk+
You can import an image file in the VHD, VMDK, QCOW2, RAW, VHDX, QCOW, VDI, QED, ZVHD, or ZVHD2 format to create a private image.
+For details, see Creating a Windows System Disk Image from an External Image File or Creating a Data Disk Image from an External Image File.
+The command output is as follows:
+MyVm.ova: POSIX tar archive (GNU)+
MyVm.ova contains the following two files:
+$tar tf MyVm.ova +MyVm.ovf +MyVm.vmdk+
tar xvf MyVm.ova
+The extracted folder contains the following files:
+MyVm.ovf +MyVm.vmdk+
The image file in the VMDK format can be uploaded to the cloud platform.
+
You can import an image file in the VHD, VMDK, QCOW2, RAW, VHDX, QCOW, VDI, QED, ZVHD, or ZVHD2 format to create a private image.
+For details, see Creating a Linux System Disk Image from an External Image File or Creating a Data Disk Image from an External Image File.
+You need to configure Cloud-Init after it is installed.
+The following operations are required:
+For details, see Configure Cloud-Init.
+For details, see Check the Cloud-Init Configuration.
+Run the following command to open the sshd_config file using the vi editor:
+vi /etc/ssh/sshd_config
+
For SUSE and openSUSE, change the values of the following parameters in the sshd_config file to no:
+vi /etc/cloud/cloud.cfg
+This step is only for Cloud-Init 18.3 or later.
+
For Ubuntu and Debian, set the value of manage_etc_hosts in the /etc/cloud/cloud.cfg file to localhost. Otherwise, switching to user root from a user other than root may time out.
+Take Ubuntu as an example.
+cat /etc/cloud/set_linux_random_password.sh
+#!/bin/bash + +password=$(cat /dev/urandom | tr -dc 'A-Za-z0-9!@#$%&+=' | head -c 9) + +echo "linux:$password" | chpasswd +sed -i -e '/^Login/d' /etc/issue +sed -i -e '/^Initial/d' /etc/issue +sed -i -c -e '/^$/d' /etc/issue +echo -e "\nInitial login with linux:$password\n" >> /etc/issue+
You can run the chmod +x /etc/cloud/set_linux_random_password.sh command to add execute permissions of set_linux_random_password.sh.
+echo -e '\e[1;31m#################################\\e[0m' > /etc/motd
+echo -e '\e[1;31m# Important !!! #\e[0m' >> /etc/motd
+echo -e '\e[1;31m# Please change password for user linux after first login. #\e[0m' >> /etc/motd
+echo -e '\e[1;31m#################################\e[0m' >> /etc/motd
+echo -e '' >> /etc/motd
+
Ensure that the configuration file format (such as alignment and spaces) is consistent with the provided example.
+system_info: + # This will affect which distro class gets used + distro: rhel + # Default user name + that default users groups (if added/used) + default_user: + name: linux //Username for login + lock_passwd: False //Login using a password is enabled. Note that some OSs use value 0 to enable the password login. + gecos: Cloud User + groups: users //Optional. Add users to other groups that have been configured in /etc/group. + passwd: $6$I63DBVKK$Zh4lchiJR7NuZvtJHsYBQJIg5RoQCRLS1X2Hsgj2s5JwXI7KUO1we8WYcwbzeaS2VNpRmNo28vmxxCyU6LwoD0 + sudo: ["ALL=(ALL) NOPASSWD:ALL"] // Assign the root rights to the user. + shell: /bin/bash //Execute shell in bash mode. + # Other config here will be given to the distro class and/or path classes + paths: + cloud_dir: /var/lib/cloud/ + templates_dir: /etc/cloud/templates/ + ssh_svcname: sshd + +bootcmd: +- [cloud-init-per, instance, password, bash, +/etc/cloud/set_linux_random_password.sh]+
The value of passwd is encrypted using SHA512 (which is used as an example). For more details, see https://cloudinit.readthedocs.io/en/latest/topics/examples.html.
+For details about how to encrypt a password and generate ciphertext, see the following (encrypting password cloud.1234 is used as an example):
+[root@** ~]# python -c "import crypt, getpass, pwd; print crypt.mksalt()"
+$6$I63DBVKK
+[root@** ~]# python -c "import crypt, getpass, pwd; print crypt.crypt('cloud.1234', '\$6\$I63DBVKK')"
+$6$I63DBVKK$Zh4lchiJR7NuZvtJHsYBQJIg5RoQCRLS1X2Hsgj2s5JwXI7KUO1we8WYcwbzeaS2VNpRmNo28vmxxCyU6LwoD0
+datasource_list: [ OpenStack ] +datasource: + OpenStack: + metadata_urls: ['http://169.254.169.254'] + max_wait: 120 + timeout: 5+
If the Cloud-Init version is 0.7.9 or later, add the following content to /etc/cloud/cloud.cfg:
+network: + config: disabled+
The added content must be in the YAML format.
+
Move ssh from the bottom to the top to speed up the SSH login.
+
vi /usr/lib/python2.7/site-packages/cloudinit/sources/__init__.py
+Press i to enter editing mode. Search for toks. The following information is displayed:
+if toks:
+ toks = str(toks).split('.')
+else:
+ toks = ["ip-%s" % lhost.replace(".", "-")]
+else:
+ toks = lhost.split(".novalocal")
+
+if len(toks) > 1:
+ hostname = toks[0]
+ #domain = '.'.join(toks[1:])
+else:
+ hostname = toks[0]
+
+if fqdn and domain != defdomain:
+ return "%s.%s" % (hostname, domain)
+else:
+ return hostname
+After the modification is complete, press Esc to exit the editing mode and enter :wq! to save the configuration and exit.
+
cd /usr/lib/python2.7/site-packages/cloudinit/sources/
+rm -rf __init__.pyc
+rm -rf __init__.pyo
+rm -rf /var/log/cloud-init*
+vim /etc/cloud/cloud.cfg.d/05_logging.cfg
+
Run the following command to check whether Cloud-Init has been properly configured:
+cloud-init init --local
+
(Optional) Run the following command to set the password validity period to the maximum:
+chage -M 99999 $user_name
+user_name is a system user, such as user root.
+You are advised to set the password validity period to 99999.
+Open the cmd window and run the following command to query the virtualization type of the ECS:
+systeminfo
+If the values of System Manufacturer and BIOS Version are Xen, the ECS uses Xen. If KVM is required, perform the operations in this section to optimize a Windows private image.
+
If the ECS uses KVM, you are also advised to optimize the private image to prevent any exceptions with the ECSs created from the image.
+
After installing the PV driver and UVP VMTools, perform the following operations to clear system logs:
+Delete log files and historical records, and stop the ECS.
+ +If an image file is larger than 128 GB, you can import it using fast import. Only the RAW and ZVHD2 formats support fast import. The image file to be imported cannot exceed 1 TB.
+
The following describes how to import an external image file. Assume that you need to convert the file format to ZVHD2 or RAW.
+You can use qemu-img-hw or the open-source tool qemu-img to convert the image format. qemu-img-hw can only be used in Linux.
+
The tool package contains qemu-img-hw (for converting image formats) and CreateMF.jar (for generating bitmap files).
+You are advised to use an EulerOS ECS to convert the file format.
+
For details, see Quickly Importing an Image File (Linux).
+You are advised to use a local PC running Windows to convert the file format.
+
qemu-img cannot convert image files to the ZVHD2 format. You need to convert an image file to the RAW format and then use CreateMF.jar to generate a bitmap file.
+
For details, see Quickly Importing an Image File (Windows).
+This section describes how to convert the format of an image file on a Linux server and then quickly import it to the cloud platform. You are advised to use an EulerOS ECS for converting image file formats and generating bitmap files.
+In Linux, you are advised to use qemu-img-hw to convert image formats.
+
Select the reference content based on the OS type in the image file.
+For example, to upload image01.qcow2 to the /usr/ directory of the ECS, run the following command:
+scp /var/image01.qcow2 root@xxx.xxx.xx.xxx:/usr/
+xxx.xxx.xx.xxx indicates the EIP bound to the ECS.
+Tool Package + |
+How to Obtain + |
+
|---|---|
quick-import-tools + |
+https://obs-20181128.ims.obs.eu-de.otc.t-systems.com/DT-image-convert-tools.zip + |
+
cd /usr/quick-import-tools/qemu-img-hw
+chmod +x qemu-img-hw
+Command format:
+./qemu-img-hw convert -p -O Target_image_format Source_image_file Target_image_file
+For example, run the following command to convert an image01.qcow2 file to an image01.zvhd2 file:
+./qemu-img-hw convert -p -O zvhd2 image01.qcow2 image01.zvhd2
+ +Run the following commands to check whether JDK is installed:
+source /etc/profile
+java -version
+If a Java version is displayed, JDK has been installed.
+cd /usr/quick-import-tools/createMF
+java -jar CreateMF.jar /Original RAW file path/Generated .mf file path
+Example:
+java -jar CreateMF.jar image01.raw image01.mf
+
The generated .mf bitmap file must have the same name as the RAW image file. For example, if the image file name is image01.raw, the generated bitmap name is image01.mf.
+If s3cmd has been installed, skip this step.
+wget https://github.com/s3tools/s3cmd/archive/master.zip
+mv master.zip s3cmd-master.zip
+unzip s3cmd-master.zip
+cd s3cmd-master
+python setup.py install
+Run the following command to configure s3cmd:
+s3cmd --configure +Access Key: Enter an AK. +Secret Key: Enter an SK. +Default Region: Enter the region where the bucket is located. +S3 Endpoint: Refer to the OBS endpoint. +DNS-style bucket+hostname:port template for accessing a bucket: Enter a server address with a bucket name, for example, mybucket.obs.myclouds.com. +Encryption password: Press Enter. +Path to GPG program: Press Enter. +Use HTTPS protocol: Specifies whether to use HTTPS. The value can be Yes or No. +HTTP Proxy server name: Specifies the proxy address used to connect the cloud from an external network. (If you do not need it, press Enter.) +HTTP Proxy server port: Specifies the proxy port used to connect to the cloud from an external network (If you do not need it, press Enter.) +Test access with supplied credentials? y +(If "Success. Your access key and secret key worked fine :-)" is displayed, the connection is successful.) +Save settings? y (Specifies whether to save the configurations. If you enter y, the configuration will be saved.)+
The configurations will be stored in /root/.s3cfg. If you want to modify these configurations, run the s3cmd --configure command to configure the parameters or run the vi .s3cfg command to edit the .s3cfg file.
+s3cmd put image01.zvhd2 s3://mybucket/
+
The .mf bitmap file must be in the same OBS bucket as the RAW image file.
+You can register a private image using the converted ZVHD2 or RAW file on the console or using an API.
+Method 1: Register a private image on the console.
+The IMS console is displayed.
+
For details about the parameters, see Registering an External Image File as a Private Image and Registering an External Image File as a Private Image.
+ +Method 2: Register a private image using an API.
+You can use the POST /v2/cloudimages/quickimport/action API to quickly import an image file.
+For details about how to call this API, see "Importing an Image File Quickly" in Image Management Service API Reference.
+The parameters are described as follows:
+-p: indicates the conversion progress.
+The part following -O (which must be in upper case) consists of the target image format, source image file, and target image file.
+For example, run the following command to convert a QCOW2 image file to a ZVHD2 file:
+qemu-img-hw convert -p -O zvhd2 test.qcow2 test.zvhd2
+An example command is qemu-img-hw info test.zvhd2.
+./qemu-img-hw: /lib64/libc.so.6: version `GLIBC_2.14' not found (required by ./qemu-img-hw)+
Solution:
+Run the strings /lib64/libc.so.6 | grep glibc command to check the glibc version. If the version is too early, install the latest version. Run the following commands in sequence:
+wget http://ftp.gnu.org/gnu/glibc/glibc-2.15.tar.gz
+wget http://ftp.gnu.org/gnu/glibc/glibc-ports-2.15.tar.gz
+tar -xvf glibc-2.15.tar.gz
+tar -xvf glibc-ports-2.15.tar.gz
+mv glibc-ports-2.15 glibc-2.15/ports
+mkdir glibc-build-2.15
+cd glibc-build-2.15
+../glibc-2.15/configure --prefix=/usr --disable-profile --enable-add-ons --with-headers=/usr/include --with-binutils=/usr/bin
+
If configure: error: no acceptable C compiler found in $PATH is displayed, run the yum -y install gcc command.
+make
+make install
+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.
+Cloud-Init is an open-source tool for cloud instance initialization. When creating ECSs from an image with Cloud-Init, you can use user data injection to inject customized initialization details (for example, an ECS login password) to the ECSs. You can also configure and manage a running ECS by querying and using metadata. If Cloud-Init is not installed, you cannot apply custom configurations to the ECSs. You will have to use the original password in the image file to log in to the ECSs.
+You are advised to install Cloud-Init or Cloudbase-Init on the ECS to be used to create a private image so that new ECSs created from the private image support custom configurations.
+For how to install Cloudbase-Init, see Installing and Configuring Cloudbase-Init.
+For how to install Cloud-Init, see Installing Cloud-Init.
+For how to configure Cloud-Init, see Configuring Cloud-Init.
+Quotas can limit the number or amount of resources available to users, such as the maximum number of ECSs or EVS disks that can be created.
+If the existing resource quota cannot meet your service requirements, you can apply for a higher quota.
+
in the upper left corner and select the desired region and project.
.The Service Quota page is displayed.
+If a quota cannot meet service requirements, apply for a higher quota.
+The system does not support online quota adjustment. If you need to adjust a quota, call the hotline or send an email to the customer service mailbox. Customer service personnel will timely process your request for quota adjustment and inform you of the real-time progress by making a call or sending an email.
+Before dialing the hotline number or sending an email, make sure that the following information has been obtained:
+Log in to the management console using the cloud account, click the username in the upper right corner, select My Credentials from the drop-down list, and obtain the domain name, project name, and project ID on the My Credentials page.
+An ECS created from a private image using the UEFI boot mode cannot start.
+The image OS uses the UEFI boot mode, but the uefi attribute is not added to the image.
+API URI: PATCH /v2/cloudimages/{image_id}
+For details about how to call the API, see "Updating Image Information" in Image Management Service API Reference.
+The ECS boot mode can be BIOS or UEFI. For details about the differences between the two modes, see How Is BIOS Different from UEFI?
+Table 1 lists the OSs that support the UEFI boot mode.
+ +OS + |
+OS Version + |
+
|---|---|
Windows + |
+Windows Server 2019 Datacenter 64bit + |
+
Windows Server 2019 Standard 64bit + |
+|
Windows Server 2016 Standard 64bit + |
+|
Windows Server 2016 Datacenter 64bit + |
+|
Windows Server 2012 R2 Standard 64bit + |
+|
Windows Server 2012 R2 Datacenter 64bit + |
+|
Windows Server 2012 Essentials R2 64bit + |
+|
Windows Server 2012 Standard 64bit + |
+|
Windows Server 2012 Datacenter 64bit + |
+|
Windows 10 64bit + |
+|
Ubuntu + |
+Ubuntu 19.04 Server 64bit + |
+
Ubuntu 18.04 Server 64bit + |
+|
Ubuntu 16.04 Server 64bit + |
+|
Ubuntu 14.04 Server 64bit + |
+|
Red Hat + |
+Red Hat Linux Enterprise 7.4 64bit + |
+
Red Hat Linux Enterprise 7.3 64bit + |
+|
Red Hat Linux Enterprise 7.1 64bit + |
+|
Red Hat Linux Enterprise 7.0 64bit + |
+|
Red Hat Linux Enterprise 6.9 64bit + |
+|
Red Hat Linux Enterprise 6.6 32bit + |
+|
Red Hat Linux Enterprise 6.5 64bit + |
+|
Oracle Linux + |
+Oracle Linux Server release 7.4 64bit + |
+
Oracle Linux Server release 6.9 64bit + |
+|
openSUSE + |
+openSUSE 42.1 64bit + |
+
SUSE + |
+SUSE Linux Enterprise Server 12 SP5 64bit + |
+
SUSE Linux Enterprise Server 12 SP1 64bit + |
+|
SUSE Linux Enterprise Server 11 SP3 64bit + |
+|
Fedora + |
+Fedora 29 64bit + |
+
Fedora 24 64bit + |
+|
Debian + |
+Debian GNU/Linux 8.8.0 64bit + |
+
CentOS + |
+CentOS 7.6 64bit + |
+
CentOS 7.5 64bit + |
+|
CentOS 7.4 64bit + |
+|
CentOS 7.0 64bit + |
+|
CentOS 6.9 64bit + |
+|
CentOS 6.6 64bit + |
+|
EulerOS + |
+EulerOS 2.8 64bit + |
+
EulerOS 2.5 64bit + |
+|
EulerOS 2.3 64bit + |
+|
EulerOS 2.2 64bit + |
+|
openEuler + |
+openEuler 20.03 64bit + |
+
You can import an image file in VHD, VMDK, QCOW2, RAW, VHDX, QCOW, VDI, QED, ZVHD, or ZVHD2 format to the cloud platform. Image files in other formats need to be converted into any of these formats using the open-source tool qemu-img before being imported. However, the qemu-img tool cannot convert image files to the ZVHD or ZVHD2 format. To convert image files to any of the two formats, use the self-developed tool qemu-img-hw. This section describes how to use qemu-img-hw to convert an image file to ZVHD2.
+qemu-img-hw can be used only in Linux. You can run it on a local Linux server or a Linux ECS on the cloud platform. The following procedure uses an EulerOS ECS as an example.
+For example, to upload image01.qcow2 to the /usr/ directory on the ECS, run the following command:
+scp /var/image01.qcow2 root@xxx.xxx.xx.xxx:/usr/
+xxx.xxx.xx.xxx indicates the EIP bound to the ECS.
+Tool Package + |
+How to Obtain + |
+
|---|---|
quick-import-tools + |
+https://obs-20181128.ims.obs.eu-de.otc.t-systems.com/DT-image-convert-tools.zip + |
+
This tool can be used only on x86 servers.
+cd /usr/quick-import-tools/qemu-img-hw
+The command format of qemu-img-hw is as follows:
+./qemu-img-hw convert -p -O Target_image_format Source_image_file Target_image_file
+For example, run the following command to convert an image01.qcow2 file to an image01.zvhd2 file:
+./qemu-img-hw convert -p -O zvhd2 image01.qcow2 image01.zvhd2
+The parameters are described as follows:
+-p: indicates the conversion progress.
+The part following -O (which must be in upper case) consists of the target image format, source image file, and target image file.
+For example, run the following command to convert a QCOW2 image file to a ZVHD2 file:
+qemu-img-hw convert -p -O zvhd2 test.qcow2 test.zvhd2
+An example command is qemu-img-hw info test.zvhd2.
+./qemu-img-hw: /lib64/libc.so.6: version `GLIBC_2.14' not found (required by ./qemu-img-hw)+
Solution:
+Run the strings /lib64/libc.so.6 | grep glibc command to check the glibc version. If the version is too early, install the latest version. Run the following commands in sequence:
+wget http://ftp.gnu.org/gnu/glibc/glibc-2.15.tar.gz
+wget http://ftp.gnu.org/gnu/glibc/glibc-ports-2.15.tar.gz
+tar -xvf glibc-2.15.tar.gz
+tar -xvf glibc-ports-2.15.tar.gz
+mv glibc-ports-2.15 glibc-2.15/ports
+mkdir glibc-build-2.15
+cd glibc-build-2.15
+../glibc-2.15/configure --prefix=/usr --disable-profile --enable-add-ons --with-headers=/usr/include --with-binutils=/usr/bin
+
If configure: error: no acceptable C compiler found in $PATH is displayed, run the yum -y install gcc command.
+make
+make install
+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.
+A region and availability zone (AZ) identify the location of a data center. You can create resources in a specific region and AZ.
+Figure 1 shows the relationship between regions and AZs.
+ +Select a region closest to your target users for lower network latency and quick access.
+When deploying resources, consider your applications' requirements on disaster recovery (DR) and network latency.
+Before you use an API to call resources, specify its region and endpoint. For more details, see Regions and Endpoints.
+Yes.
+Other tenants can share a private image with you. You can use it after accepting it. For details about image sharing, see Sharing Specified Images.
+This section describes how to convert the format of an image file on a Windows server and then quickly import it to the cloud platform. You are advised to use a local Windows PC for converting image formats and generating bitmap files.
+In Windows, use the open-source tool qemu-img to convert image formats. qemu-img supports conversion between image files of the VHD, VMDK, QCOW2, RAW, VHDX, QCOW, VDI, and QED formats. Convert an image to the RAW format and then use the CreateMF.jar tool to generate a bitmap file.
+
Select the reference content based on the OS type in the image file.
+For example, run the following command to convert an image.qcow2 file to an image.raw file:
+qemu-img convert -p -O raw image.qcow2 image.raw
+Tool Package + |
+How to Obtain + |
+
|---|---|
quick-import-tools + |
+https://obs-20181128.ims.obs.eu-de.otc.t-systems.com/DT-image-convert-tools.zip + |
+
You can verify the installation by running cmd.exe and then java -version. If Java version information is displayed, JDK has been installed.
+For example, if you have downloaded CreateMF.jar to D:/test, run the following commands to access the directory:
+D:
+cd test
+You must upload the RAW image file and its bitmap file to the same OBS bucket.
+You can register a private image using the converted ZVHD2 or RAW file on the console or using an API.
+Method 1: Register a private image on the console.
+The IMS console is displayed.
+
For details about the parameters, see Registering an External Image File as a Private Image and Registering an External Image File as a Private Image.
+ +Method 2: Register a private image using an API.
+You can use the POST /v2/cloudimages/quickimport/action API to quickly import an image file.
+For details about how to call this API, see "Importing an Image File Quickly" in Image Management Service API Reference.
+You can use a Cloud Backup and Recovery (CBR) backup to create a full-ECS image, which can be used to create ECSs.
+The IMS console is displayed.
+When the image status changes to Normal, the image creation is complete.
+After the full-ECS image creation is complete, you can perform the following operations:
+
If a full-ECS image contains one or more data disks, the system configures data disk parameters automatically when you use the image to create ECSs.
+128
+There is no limit.
+No.
+No.
+Yes. After sharing an image with other tenants, you can still use the image to create an ECS and use the created ECS to create a private image.
+If you have rejected an image shared by another tenant, but now want to use it, two methods are available:
+Ask the image owner to add you to the tenants the image is shared with. For details, see Adding Tenants Who Can Use Shared Images.
+Accept the rejected image again. For details, see Accepting Rejected Images.
+Fast Create greatly reduces the time required for creating ECSs from a system disk image. Currently, this feature is supported by all newly created system disk images by default. Some existing system disk images may not support this feature, you can make them support it through image replication.
+For example, if image A does not support fast ECS creation, you can replicate it to generate image copy_A that supports fast ECS creation.
+Full-ECS images cannot be configured using this method.
+The IMS console is displayed.
+The Replicate Image dialog box is displayed.
+Currently, you can create a maximum of 100 private images under an account in a region.
+No. You can create an image from a running ECS. However, if data is written to the ECS during image creation, that new data will not be included in the created image.
+Log in to the management console. Choose Compute > Image Management Service and click the Private Images tab. Monitor the image creation progress in the Status column.
+The image creation involves the installation of Xen and KVM drivers, OS kernel loading, and GRUB boot configuration, which may take a long time. In addition, the network speed, image file type, and disk size have an impact on how long image creation takes.
+When creating an ECS or BMS, you can select an image based on the following factors:
+ +An image is a regional resource. You cannot use an image to create an instance in a different region. For example, when creating an instance in region A, you can only select an image that is already in region A. For more regions, see Region and AZ.
+Images are classified into public images, private images, and shared images. A private image can be a system disk image, data disk image, or full-ECS image. For details, see What Is Image Management Service?
+When selecting an OS, consider the following factors:
+System Architecture + |
+Applicable Memory + |
+Constraints + |
+
|---|---|---|
32-bit + |
+Smaller than 4 GB + |
+
|
+
64-bit + |
+4 GB or larger + |
+If your application requires more than 4 GB of memory or the memory may need to be expanded to more than 4 GB, use a 64-bit OS. + |
+
OS Type + |
+Applicable Scenario + |
+Constraints + |
+
|---|---|---|
Windows + |
+
|
+The system disk must be at least 1 GB, and there must be at least 1 GB of memory. + |
+
Linux + |
+
|
+The system disk must be at least 1 GB, and there must be at least 512 MB of memory. + |
+
Some images cannot be exported. Therefore, the Export option is not provided for them in the Operation column. The following images cannot be exported:
+Item + |
+Description + |
+Helpful Link + |
+
|---|---|---|
Import + |
+Import an external image file to the management console for creating a private image. +External image files in the following formats can be imported: VMDK, VHD, QCOW2, RAW, VHDX, QED, VDI, QCOW, ZVHD2, and ZVHD. +Maximum file size: 128 GB +During the import, operations such as driver injection will be performed in the background. Therefore, the import takes a longer time than fast import. + |
++ | +
Fast import + |
+When importing an external image file in the RAW or ZVHD2 format to the management console, you can select Enable Fast Create. The system does not perform any operations such as driver injection. Verify that: +
Maximum file size: 1 TB + |
++ | +
Export + |
+You can export private images to OBS buckets and download them to your local PC for further use on other cloud platforms. +Maximum file size: 128 GB (If an image file is larger than 128 GB, use fast export to export it.) +You can specify the format of the exported image file. Currently, only QCOW2, VMDK, VHD, and ZVHD are supported. + |
++ | +
Fast export + |
+On the Export Image page, select Enable following Fast Export. You cannot specify the format of the exported image file. After the export is complete, you can use a tool to convert the exported image to your desired format. +The file size is not limited. +Encrypted images do not support fast export. + |
++ | +
Yes. You can download private images in VMDK, VHD, QCOW2, or ZVHD format as instructed in Exporting an Image.
+After a private image is exported to an OBS bucket, the image size in the bucket is different from that displayed in IMS. For example, the size of a private image is 1.04 GB on the IMS console. After it is exported to an OBS bucket, the size is displayed as 2.91 GB.
+The size of an image in an OBS bucket varies depending on the file's storage format in the bucket.
+You can check the disk capacity of a private image.
+Check the disk capacity in the Disk Capacity column of the private image list.
+The IMS console is displayed.
+The disk capacity of a full-ECS image is the sum of the system disk capacity and data disk capacity in the backup from which the full-ECS image is created.
+The IMS console is displayed.
+The value in the Disk Capacity column is --.
+Disk capacity of a full-ECS image = Capacity of the system disk in the backup + Capacity of data disks in the backup
+For example:
+