Help Center> Bare Metal Server> Service Overview> Features and Constraints
Updated on 2022-09-23 GMT+08:00

Features and Constraints



  • Automatic BMS provisioning and remote login to BMSs through the management console
  • Managing the lifecycle of a BMS, including querying, starting, stopping, restarting, and deleting a BMS
  • One-click password reset
  • Reinstalling the OS
  • Rebuilding a BMS if the BMS hardware or SDI iNIC is damaged
  • Using Cloud Server Backup Service (CSBS) to back up BMS configurations and EVS disk data into Object Storage Service (OBS) buckets for data security
  • Injecting scripts to simplify BMS configuration and initialization
  • Installation of Cloudera's Distribution Including Apache Hadoop (CDH) on BMSs, which enables communication with other services you have purchased
  • Using APIs to manage BMSs
  • Server monitoring, with which you can obtain the CPU, memory, and disk I/O metrics of your BMSs
  • Tagging BMSs to make them easier to identify and search


  • Attaching EVS disks to or detaching EVS disks from Linux or Windows BMSs
  • Shared EVS disks
  • Dynamic capacity expansion of EVS disks


  • Using a public, private, or shared image to create BMSs
  • Creating a private image from a BMS
  • Creating a private image from an external image file
  • Sharing images, replicating images across regions, and exporting images to an OBS bucket


  • VPC and IB network
  • Creating a security group and defining rules to protect BMS security
  • Binding an EIP to a BMS to enable the BMS to access the Internet
  • Attaching multiple NICs to a BMS


  • External hardware devices (such as USB devices, bank U keys, external hard disks, and dongles) cannot be loaded.
  • Out-of-band management is not supported. Your BMSs are managed and maintained by HUAWEI CLOUD.
  • Live migration is not supported. If a BMS is faulty, your services running on it may be affected. It is good practice to deploy your services in a cluster or in primary/standby mode to ensure high availability.
  • You cannot create a server without an OS, that is, a BMS must have an OS.
  • The OS of a BMS cannot be changed after it is created or during OS reinstallation.
  • After a BMS is created, you cannot change its VPC.
  • When you create a BMS, you can only select a flavor with specified CPU, memory, and local disks but cannot configure them separately. After a BMS is created, you can expand the capacity of attached EVS disks but cannot modify the BMS CPU, memory, or local disks.
  • You can only attach EVS disks whose device type is SCSI to a BMS.
  • You cannot attach EVS disks to BMSs of certain flavors or BMSs created from certain images because these BMSs do not have SDI iNICs or lack compatibility.
  • Do not delete or modify built-in plug-ins of an image, such as Cloud-Init and bms-network-config. Otherwise, basic BMS functions will be affected.
  • If you choose to assign an IP address automatically when you create a BMS, do not change the private IP address of the BMS after the BMS is provisioned. Otherwise, the IP address may conflict with that of another BMS.
  • BMSs do not support bridge NICs because they will cause network interruptions.
  • Do not upgrade the OS kernel. Otherwise, the hardware driver may become incompatible with the BMS and adversely affect the BMS reliability.