From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from gate001.proxmox.com (gate001.proxmox.com [IPv6:2a0f:8001:1:32::40]) by lore.proxmox.com (Postfix) with ESMTPS id A77101FF0C2 for ; Thu, 22 Oct 2026 14:51:46 +0200 (CEST) Received: from gate001.proxmox.com (localhost.localdomain [127.0.0.1]) by gate001.proxmox.com (Proxmox) with ESMTP id 99C7D2185B; Thu, 22 Oct 2026 14:51:33 +0200 (CEST) From: Jakob Klocker To: pve-devel@lists.proxmox.com Subject: [PATCH pve-docs v2 2/8] qm: add reboot behavior information Date: Thu, 22 Oct 2026 14:51:05 +0200 Message-ID: <20261022125111.236538-3-j.klocker@proxmox.com> X-Mailer: git-send-email 2.47.3 In-Reply-To: <20261022125111.236538-1-j.klocker@proxmox.com> References: <20261022125111.236538-1-j.klocker@proxmox.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1792673489017 X-SPAM-LEVEL: Spam detection results: 0 AWL 1.577 Adjusted score from AWL reputation of From: address DMARC_MISSING 0.1 Missing DMARC policy KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment (newer systems) RCVD_IN_DNSWL_MED -2.3 Sender listed at https://www.dnswl.org/, medium trust SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record Message-ID-Hash: 7QSZZNBGGQ5ARNT7F4U3656YRYJQDDKB X-Message-ID-Hash: 7QSZZNBGGQ5ARNT7F4U3656YRYJQDDKB X-MailFrom: j.klocker@proxmox.com X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; loop; banned-address; emergency; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header X-Mailman-Version: 3.3.10 Precedence: list List-Id: Proxmox VE development discussion List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: Add information about the newly created `Reboot behavior` option in PVE. Signed-off-by: Jakob Klocker --- qm.adoc | 40 ++++++++++++++++++++++++++++++++++++++++ 1 file changed, 40 insertions(+) diff --git a/qm.adoc b/qm.adoc index 18a4fbe..04193e8 100644 --- a/qm.adoc +++ b/qm.adoc @@ -1558,6 +1558,46 @@ cluster-wide. If you require a delay between the host boot and the booting of the first VM, see the section on xref:first_guest_boot_delay[Proxmox VE Node Management]. +[[qm_reboot_behavior]] +Reboot Behavior +~~~~~~~~~~~~~~~ + +When a guest reboots itself from inside the operating system, {pve} does not +need to restart the virtual machine to service the request. By default the +machine is reset in place: the QEMU process keeps running and only the guest +operating system boots again. + +This is fast and transparent to the guest, but it means the VM keeps running +with everything it was started with - its configuration, its machine version +and the host resources assigned to it. Configuration changes that are marked as +*pending* in the *Options* and hardware panels therefore stay pending, and a +newer `pve-qemu-kvm` package installed in the meantime is not picked up. A +reboot triggered through the web interface, `qm` or the API is not affected by +this, as it always stops and starts the virtual machine, unless rebooting is +disabled entirely. + +The `reboot` option has two properties: + +`enabled` (default: `1`):: +Whether the virtual machine may reboot at all. If disabled, a reboot requested +from inside the guest or through `qm reboot` or the API shuts the VM down +instead, and it stays off. The exception is an explicit reset (`qm reset`, the +API or the web interface), which still restarts the VM. Note that guests managed +by the xref:chapter_ha_manager[HA stack] with the requested state `started` are +started again by the HA manager. + +`powercycle` (default: `0`):: +Stop and start the virtual machine on a reset instead of resetting it in place. +A reset is what a reboot from inside the guest looks like to QEMU, and it is +also what `qm reset` and the corresponding API call and web interface action +trigger. Because this is a full start, pending configuration changes take +effect and the VM is launched with the currently installed QEMU version, and +the `post-stop` and `pre-start` hookscript phases run again. This property is +ignored when `enabled` is `0`. + +---- +# qm set --reboot 1,powercycle=1 +---- [[qm_qemu_agent]] QEMU Guest Agent -- 2.47.3