From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from gate001.proxmox.com (gate001.proxmox.com [45.144.208.40]) by lore.proxmox.com (Postfix) with ESMTPS id 461A51FF12C for ; Wed, 05 Aug 2026 10:21:33 +0200 (CEST) Received: from gate001.proxmox.com (localhost.localdomain [127.0.0.1]) by gate001.proxmox.com (Proxmox) with ESMTP id 140D22173B; Wed, 05 Aug 2026 10:21:33 +0200 (CEST) From: Maximiliano Sandoval To: Thomas Lamprecht Subject: Re: [PATCH manager] report: list recent reboot events and their kernel version In-Reply-To: (Thomas Lamprecht's message of "Mon, 20 Jul 2026 17:41:00 +0200") References: <20260720123649.226360-1-a.zeidler@proxmox.com> <55625334-51ae-45d8-b365-91d85d1cc541@proxmox.com> User-Agent: mu4e 1.12.9; emacs 30.1 Date: Wed, 05 Aug 2026 10:21:29 +0200 Message-ID: MIME-Version: 1.0 Content-Type: text/plain X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1785918076157 X-SPAM-LEVEL: Spam detection results: 0 AWL 0.209 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_LOW -0.7 Sender listed at https://www.dnswl.org/, low 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: PGAQM6ASL6BN7XF2NIG4QPG45SRWQ72W X-Message-ID-Hash: PGAQM6ASL6BN7XF2NIG4QPG45SRWQ72W X-MailFrom: m.sandoval@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: pve-devel@lists.proxmox.com X-Mailman-Version: 3.3.10 Precedence: list List-Id: Proxmox VE development discussion List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: Thomas Lamprecht writes: > Am 20.07.26 um 16:58 schrieb Alexander Zeidler: > [..] > FWIW, we already got proxmox-mini-journalreader and it can already produce > json that we could extend to produce the relevant info, i.e. iterating through > boots (IIRC that is a indexed table) and parser first Line to extract the > kernel. That could then be outputted as structured JSON there which can be > parsed by the report here. In the midterm we could even think about integrating > that as fully fledged API to our products API, if it can provide value as first > class boot + kernel list there. For now just parsing the json in the report > would be more than enough (or CLI only integration as middleground). > > You can try "poaching" one of our Devs that isn't to afraid from a bit of > C to implement this, would be probably the safest course be here, especially > as we maintain the journald handling already anyway. I tried my hand at this, see https://lore.proxmox.com/all/20260805081911.131557-1-m.sandoval@proxmox.com/T/#u. The json output part is not implemented, but for our interests this is perfectly OK. -- Maximiliano