Failed to Migrate a VM Because No Space Is Left in the Host or Partition

197 0 1 0

Symptom

A VM fails to be upgraded. The fault description indicates that an internal system exception occurs and asks you to contact technical support engineers.

Analysis

1.         Log in to the active VRM node and run the psql -U galax vrm command to log in to the database. In tbl_history_task, find the ID of the VM migration task based on the VM ID.

 143044qpbrmmmctvhr1v6m.png?图片.png

2.         Query VRM logs generated at the fault time and locate the host where the migration task is performed based on taskId. 

143053kyynlx9vdfr9mn99.png?图片.png

3.         Log in to the host, query the NC logs generated at the fault time, and find the cause of the fault based on the task. In this example, the cause is that the destination host domID is empty.

143103w0njxhx4i0txxxke.png?图片.png

4.         Query the libvirt logs generated at the fault time, or re-execute the migration task and run tailf libvirt.log to view the logs. The following figure shows the root cause of the fault.

143123z9w2l507fl7575ff.png?图片.png

5.         In conclusion, the migration fails because no space is left in the root directory of the host or the /var/log partition.

Solution

Run the du -sh * command in each directory, delete unnecessary files, and execute the migration task again. You can compare files on the faulty host with those on a normal host to determine which files can be deleted.


  • x
  • convention:

Login and enjoy all the member benefits

Login and enjoy all the member benefits

Login