From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: pve-devel@lists.proxmox.com, Fiona Ebner <f.ebner@proxmox.com>
Subject: [pve-devel] applied: [PATCH qemu-server] qmeventd: go back to extracting vmid from commandline instead of cgroup file
Date: Tue, 8 Apr 2025 00:53:31 +0200 [thread overview]
Message-ID: <174406640161.3303433.12506884592924242514.b4-ty@proxmox.com> (raw)
In-Reply-To: <20240614092134.18729-1-f.ebner@proxmox.com>
On Fri, 14 Jun 2024 11:21:34 +0200, Fiona Ebner wrote:
> In spirit, this is a revert of 502870a0 ("qmeventd: extract vmid from
> cgroup file instead of cmdline"), but instead of relying on the custom
> 'id' commandline option that's added by a Proxmox VE patch to QEMU,
> rely on the standard 'pidfile' option to extract the VM ID.
>
> As reported in the community forum [0], at least during stop mode
> backup, it seems to be possible to end up with the VM process having
> > 0::/system.slice/pvescheduler.service
> as its single cgroup entry. It's not clear what exactly happens and
> there was no success to reproduce the issue. Might be a rare bug in
> systemd or in pve-common's enter_systemd_scope() code.
>
> [...]
Applied, thanks!
[1/1] qmeventd: go back to extracting vmid from commandline instead of cgroup file
commit: 556cc662abe3f8303b01a0b0bf85dbb41db229c1
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
prev parent reply other threads:[~2025-04-07 22:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-14 9:21 [pve-devel] " Fiona Ebner
2025-04-07 8:32 ` Fiona Ebner
2025-04-07 22:53 ` Thomas Lamprecht [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=174406640161.3303433.12506884592924242514.b4-ty@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=f.ebner@proxmox.com \
--cc=pve-devel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal