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 9E4181FF0BC for ; Mon, 16 Nov 2026 17:10:36 +0100 (CET) Received: from gate001.proxmox.com (localhost.localdomain [127.0.0.1]) by gate001.proxmox.com (Proxmox) with ESMTP id 3864121661; Mon, 16 Nov 2026 17:10:26 +0100 (CET) Message-ID: <782e35ac-6e60-444e-a101-db0dcd5fb17c@proxmox.com> Date: Mon, 16 Nov 2026 17:10:21 +0100 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Beta Subject: Re: [PATCH docs v4 2/3] qm: add document section for the pvpanic device To: Kaiyang Wu , pve-devel@lists.proxmox.com References: <20261102095525.1635251-1-wukaiyang@loongfans.cn> <20261102095525.1635251-3-wukaiyang@loongfans.cn> Content-Language: en-US From: Dominik Csapak In-Reply-To: <20261102095525.1635251-3-wukaiyang@loongfans.cn> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1794845421435 X-SPAM-LEVEL: Spam detection results: 0 AWL 0.305 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: SP6DIAYHNY3YJQFEJ4UU6O6OJGWEB25C X-Message-ID-Hash: SP6DIAYHNY3YJQFEJ4UU6O6OJGWEB25C X-MailFrom: d.csapak@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 CC: Kaiyang Wu X-Mailman-Version: 3.3.10 Precedence: list List-Id: Proxmox VE development discussion List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: LGTM Reviewed-by: Dominik Csapak On 11/2/26 10:55 AM, Kaiyang Wu wrote: > Document the pvpanic device and corresponding driver requirements on > different VMs. > > Suggested-by: Dominik Csapak > Signed-off-by: Kaiyang Wu > --- > qm.adoc | 34 ++++++++++++++++++++++++++++++++++ > 1 file changed, 34 insertions(+) > > diff --git a/qm.adoc b/qm.adoc > index 18a4fbe..a994372 100644 > --- a/qm.adoc > +++ b/qm.adoc > @@ -1476,6 +1476,40 @@ tag (name used to mount the device on the guest). > For more information on available virtiofsd parameters, see the > https://gitlab.com/virtio-fs/virtiofsd[GitLab virtiofsd project page]. > > +[[qm_pvpanic]] > +Pvpanic > +~~~~~~~ > + > +Pvpanic is a device to send system panic events to QEMU. It allows to > +provide extra VM status and perform the specified panic action when the VM > +system crashes. > + > +To add a pvpanic device run the following command: > + > +---- > +qm set -pvpanic enabled=1[,action=] > +---- > + > +A panic action can be specified to perform when the VM system crashes. Available > +panic actions are: > + > +* `none`: Continue VM execution > +* `pause`: Pause the VM > +* `shutdown`: Shutdown the VM and exit, according to the shutdown action > +* `exit-failure`: Shutdown the VM and exit with non-zero status > + > +NOTE: The default panic action is `shutdown`. > + > +NOTE: VMs managed by the HA stack can set `exit-failure` to exit the QEMU > +process completely and let the HA stack start it again. > + > +Linux VMs with kernel >=5.2 support pvpanic PCI device by default. > + > +Windows VMs require https://pve.proxmox.com/wiki/Windows_VirtIO_Drivers[Windows > +VirtIO Drivers] to use pvpanic. > + > +FreeBSD VMs do not support pvpanic. > + > [[qm_bootorder]] > Device Boot Order > ~~~~~~~~~~~~~~~~~