If the VMs status is "Suspended"

Problem

The VM has the "Suspended" status and does not resume.

Cause

A VM may enter the "Suspended" status due to a hypervisor error. For example, if the node runs out of disk space, QEMU cannot write data to the VM image and suspends the VM.

Diagnostics

To determine the cause of the suspension:

1. Connect to the cluster node via SSH. For more information about connecting via SSH, see Workstation setup.
2. Get the list of suspended VMs:
   

   virsh list --state-paused

   Example output

   Id    Name                       State
   ------------------------------------------
    335   3101_blue-gray_succinite   paused
    402   3309_violet_topaz          paused
    448   2145_warm_essonite         paused
    490   3546_violet-blue_kunzite   paused

3. Check the VM status and the reason for the suspension:
   

   virsh domstate <vm_name> --reason

   Command explanation

   <vm_name> — the value from the Name column in the list of suspended VMs
   Example output

   paused (io-error)

   In this example, the VM is suspended due to an I/O error. For example, this error may occur if the node runs out of disk space and QEMU cannot write data to the VM image.

4. If the cause is not specified or cannot be determined from the command output, check the QEMU log:
   

   cat /var/log/libvirt/qemu/<vm_name>.log

   Command explanation

   <vm_name> — the value from the Name column in the list of suspended VMs

5. Find error messages in the log that appeared immediately before the VM was suspended. For example, if the node runs out of disk space, the following message may appear:
   

   No space left on device

6. Check the node resources, such as available disk space.
   

   df -h

Solution

To resolve the issue:

1. Resolve the cause of the error. For example, if the node has run out of disk space, free up space or increase the available capacity.
2. Resume the VM. Choose the method depending on the VMmanager version:
   • VMmanager 2025.09.1 and later — In the web interface, go to Virtual Machines → menu → Resume.
   • VMmanager versions earlier than 2025.09.1 — For these versions, you can resume the VM only via SSH:
     1. Connect to the cluster node via SSH. For more information about connecting via SSH, see Workstation setup.
     2. Run:

        virsh resume <vm_name>

        Command explanation

        <vm_name> — the value from the Name column in the list of suspended VMs. Obtained in step 2 of the Diagnostics

     3. Check the VM status:
        

        virsh domstate <vm_name>

        Command explanation

        <vm_name> — the value from the Name column in the list of suspended VMs. Obtained in step 2 of the Diagnostics

        Expected result: The VM has the running.