From: Kaiyang Wu <wukaiyang2003@gmail.com>
To: pve-devel@lists.proxmox.com
Cc: Kaiyang Wu <wukaiyang@loongfans.cn>
Subject: Re: [PATCH qemu-server v4 0/3] add pvpanic device support
Date: Thu, 12 Nov 2026 17:41:14 +0800 [thread overview]
Message-ID: <5d8ab380-0a09-434d-a7e8-1447c8835468@gmail.com> (raw)
In-Reply-To: <20261102095525.1635251-1-wukaiyang@loongfans.cn>
Gentle ping, can anyone please take a look? Sorry for the wrong patchset
prefix, the patchset actually covers qemu-server, pve-manager, and pve-docs.
On 2026-11-02 17:55, Kaiyang Wu wrote:
> This patchset adds pvpanic device support to QEMU virtual machines to
> provide extra virtual machine status (guest-panicked) when virtual
> machines panic [0] and perform panic actions.
>
> [0]: https://www.qemu.org/docs/master/specs/pvpanic.html
>
> v1: https://lore.proxmox.com/pve-devel/20260827103529.393388-1-wukaiyang@loongfans.cn/
> v2: https://lore.proxmox.com/pve-devel/20260914092015.125780-1-wukaiyang@loongfans.cn/
> v3: https://lore.proxmox.com/pve-devel/20261009065813.109006-1-wukaiyang@loongfans.cn/
>
> Changes v1 -> v2:
> - Remove the pvpanic ISA device support to simplify the code
> - Move the pvpanic setting from Hardware to Options
> - Restart a HA-managed VM when it panics to restore the "started" state
>
> Changes v2 -> v3:
> - Allow to set panic action. The HA stack automatically restarts a panicked VM
> when the VM exits using the 'exit-failure' panic action
>
> Changes v3 -> v4:
> - Specify the default panic action (shutdown) in the 'pvpanic_fmt' schema
> - Mention only the default panic action in the documentation
> - Mention only since when the pvpanic-pci device is supported in the Linux kernel in the documentation
> - Briefly mention Windows VirtIO Drivers in the pvpanic section
> - Make panic actions translatable in the manager
>
>
> qemu-server:
>
> Kaiyang Wu (1):
> qemuserver: add pvpanic device
>
> src/PVE/API2/Qemu.pm | 1 +
> src/PVE/QemuServer.pm | 43 +++++++++++++++++++++++++++++++++++++++
> src/PVE/QemuServer/PCI.pm | 1 +
> 3 files changed, 45 insertions(+)
>
>
> docs:
>
> Kaiyang Wu (1):
> qm: add document section for the pvpanic device
>
> qm.adoc | 34 ++++++++++++++++++++++++++++++++++
> 1 file changed, 34 insertions(+)
>
>
> manager:
>
> Kaiyang Wu (1):
> ui: qemu: add pvpanic device support
>
> www/manager6/Makefile | 1 +
> www/manager6/Utils.js | 18 +++++++++
> www/manager6/form/PvpanicSelector.js | 56 ++++++++++++++++++++++++++++
> www/manager6/qemu/Options.js | 16 ++++++++
> 4 files changed, 91 insertions(+)
> create mode 100644 www/manager6/form/PvpanicSelector.js
>
prev parent reply other threads:[~2026-11-12 9:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-02 9:55 [PATCH qemu-server v4 0/3] add pvpanic device support Kaiyang Wu
2026-11-02 9:55 ` [PATCH qemu-server v4 1/3] qemuserver: add pvpanic device Kaiyang Wu
2026-11-16 16:10 ` Dominik Csapak
2026-11-02 9:55 ` [PATCH docs v4 2/3] qm: add document section for the " Kaiyang Wu
2026-11-16 16:10 ` Dominik Csapak
2026-11-02 9:55 ` [PATCH manager v4 3/3] ui: qemu: add pvpanic device support Kaiyang Wu
2026-11-16 16:10 ` Dominik Csapak
2026-11-12 9:41 ` Kaiyang Wu [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=5d8ab380-0a09-434d-a7e8-1447c8835468@gmail.com \
--to=wukaiyang2003@gmail.com \
--cc=pve-devel@lists.proxmox.com \
--cc=wukaiyang@loongfans.cn \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox