> ## Documentation Index
> Fetch the complete documentation index at: https://docs.cloud.vessl.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Reboot a node

> When and how to reboot a node, and what happens when you reboot.

You can reboot a node yourself from the cluster detail page — useful for clearing transient GPU faults or applying driver changes.

<div>
  <Frame>
    <img src="https://mintcdn.com/dora/5t6p_q3y3A1ut21q/images/vm-clusters-node-reboot.png?fit=max&auto=format&n=5t6p_q3y3A1ut21q&q=85&s=d4a5cabf1b84ad95e860568d90a8605a" alt="Node detail page header showing the node status, public and internal IP, and a Reboot button" width="1800" height="190" data-path="images/vm-clusters-node-reboot.png" />
  </Frame>

  <small>Example: the Reboot button on a node's detail page</small>
</div>

## What happens when you reboot

* **Cold restart only.** Because GPUs are passed through to the VM, live migration isn't possible — the VM is fully restarted.
* The VM may come back on the **same or a different physical node**.
* Reconnecting over SSH typically takes **tens of minutes**, and can run past an hour in some cases.

<Note>
  Billing continues during a reboot, because a VM cluster is a reserved contract.
</Note>

<Note>
  Keep important data on [NFS shared storage](/vm-clusters/nfs-storage). A node's boot disk can be lost if the node is relocated due to a hardware fault.
</Note>