From: Victor Rodriguez <vrodriguez@soltecsis.com>
To: pve-user@lists.proxmox.com
Subject: Re: [PVE-User] shutdown and stay shut
Date: Sun, 28 Sep 2025 09:13:37 +0200 [thread overview]
Message-ID: <895ddd8c-ba54-4a01-95f3-1217616df57a@soltecsis.com> (raw)
In-Reply-To: <m24isn8msy.wl-randy@psg.com>
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
> pve-user@lists.proxmox.com
> https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user
>
--
_______________________________________________
_______________________________________________
pve-user mailing list
pve-user@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user
prev parent reply other threads:[~2025-09-28 7:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-28 0:04 Randy Bush
2025-09-28 7:13 ` Victor Rodriguez [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=895ddd8c-ba54-4a01-95f3-1217616df57a@soltecsis.com \
--to=vrodriguez@soltecsis.com \
--cc=pve-user@lists.proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.