Overview
While extremely rare, sometimes Virtual Machines (VM’s) can stop responding completely and need a hard reset (or hard stop) before they become operational again.
Instructions
- Login to the Conetix Control Panel.
- Find the affected service (it should have Proxmox Cloud VM or similar in the product name) and open up the detail page:

- Ping the IP address to confirm the VM is unresponsive. If you get results, do not continue with the hard stop below as it may result in data loss.
- Open up the noVNC Console:

- This should open a new window. For a functional VM, you should be able to hit <Enter> and see a login prompt appear for a working system:

(kpatch messages may also appear in the console and this is expected behaviour) - If pressing <Enter> within the console does NOT result in a login prompt AND pings aren’t returning, then it’s very likely the VM has become completely unresponsive and therefore won’t shutdown nor reboot.
- Select Stop as the action:

(This is equivalent to pulling the power plug so it’s only for completely unresponsive systems) - This will ask you to confirm the Stop command:

- Click Confirm and it will issue the stop command to our clustered system.
- Confirm via the status of the VM that it has completely stopped:

(You may need to refresh the page for the status to update) - With the VM stopped, we can now issue the Start command:

- This will again confirm you wish to start the VM:

- Click Confirm. Wait 60 seconds for the command to fully go through.
- Monitor the boot process via the noVNC console to ensure it starts correctly and you should also test pinging the server.
