If on cluster + HA, either set all resources to ignore or move/rename /etc/pve/ha/resources.cfg (and move/rename back once maintenance is done), then:

- |systemctl disable pve-guests.service|.
- Reboot and no VM will be started. Do the update or whatever maintenance is needed.
- Reboot if needed (i.e. kernel update).
- |systemctl enable pve-guests.service && /usr/bin/pvesh --nooutput create /nodes/localhost/startall|.

Disclaimer: I've used this procedure a few times now on single node setups. Haven't tested this procedure much con clusters as usually can live migrate and the node is empty for maintenance, so no need to disable VM start.


On 9/28/25 02:04, Randy Bush wrote:
debian bookworm
proxmox 8.4.14

we are going perform some complex surgery on a cluster.  so we want to
shut proxmox down and have it stay down across a few power up and down
cycles aided by the usual `shutdown -[hr] now` etc.

what is the best way to tell proxmox not to come back up and start vms
on reboot / power-up?  there seems to be no

     sudo systemctl disable proxmox.service

ddg gives me a million hits for disabling the no subscription notice :)

thanks for clues

randy

_______________________________________________
pve-user mailing list
[email protected]
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user

--
_______________________________________________
_______________________________________________
pve-user mailing list
[email protected]
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user

Reply via email to