No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

CloudEC V600R019C00 Troubleshooting (Enterprise On-premises, Convergent Conference)

Rate and give feedback:
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document. Note: Even the most advanced machine translation cannot match the quality of professional translators. Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
VM Is Relocated and Fails to Automatically Start After the Host Restarts

VM Is Relocated and Fails to Automatically Start After the Host Restarts

Symptom

A user logs in to the ESXi remotely and presses F12+F11 to restart the host. After the host starts up, the virtual machine (VM) running on the host is relocated and fails to automatically start, as shown in Figure 3-11.

Figure 3-11 VM relocation

NOTE:
VM relocation refers to the VM migration to another host triggered by the vCenter.

Possible Causes

After the user presses F12+F11 on the ESXi window, the system performs the following operations:

  1. Stops all the VMs running on the host.
  2. Stops the host.
  3. Starts the host.
  4. Starts all the VMs running on the host.

During this process, the high availability (HA) mechanism does not work for the VMs running on the host. As a result, after a VM is migrated to another host, the VM does not automatically start.

After the host stops, the vCenter triggers VM relocation in shared storage scenarios.

To prevent service failures when the HA mechanism does not work for VMs, do not restart the host running these VMs after you log in to the ESXi.

It is recommended that you restart the host from the hardware layer so that the HA mechanism always work for the VMs running on the host. For example, click Cold boot or Reset on the iLO interface of the HP server.

Fault Diagnosis

None.

Procedure

  1. Contact infrastructure maintenance engineers to manually start the VM.

Related Information

None.

Translation
Download
Updated: 2019-08-07

Document ID: EDOC1100059098

Views: 19981

Downloads: 12

Average rating:
This Document Applies to these Products
Related Version
Related Documents
Share
Previous Next