VRM VMs Cannot Be Started After Shutdown

Hello, Lisa!

Have a nice day!

What's the version of your FusionCompute?

Wait for your feedback!

Lisa,

Users cannot log in to FusionCompute after all Virtualization Resource Management (VRM) VMs are stopped even though the hosts on which the VMs are created are still running.

And the possible causes:

• The VRM VM is stopped by a command executed on the VM.

• The VRM VM automatically stops because an OS exception occurs.

You can refer to the following steps to solve the issue:

1. Use PuTTY to log in to the host on which the VRM VM is deployed.

Log in to the host using the management IP address as the gandalf user.

2. Run the following command and enter the password of the root user as prompted to switch to the root user:

su - root

3. Run the following command to disable user logout upon system timeout:

TMOUT=0

4. Run the following command to obtain the VRM VM ID:

cat /etc/vna-api/vrminfo

The command output contains the VRM VM ID, for example,

i-00000002

5. Run the following command to start the VRM VM:

python /usr/lib/python2.7/site-packages/vna/compute/scripts/vna_tool.py start ID of the VRM VM

Example:

python /usr/lib/python2.7/site-packages/vna/compute/scripts/vna_tool.py start i-00000002

Note:

This command is used to start one of the VRM VMs when both the active and standby VRM VMs are stopped. You need to start the other VRM VM on FusionCompute.

Hope this helps!