From: Krasimir Rangelov <krasimir.rangelov12@icloud.com>
To: pve-devel@lists.proxmox.com
Subject: [RFC] Add read-only DMI hardware endpoint to Proxmox VE
Date: Tue, 16 Jun 2026 16:43:06 +0300 [thread overview]
Message-ID: <0FC20308-4392-4A01-AD93-9FF741A4C9C3@icloud.com> (raw)
Hello Proxmox developers,
>
> I would like to propose a small, read-only API extension for Proxmox VE: a new endpoint at GET /nodes/{node}/hardware/dmi.
>
> The endpoint would expose basic DMI hardware identification data from /sys/devices/virtual/dmi/id/ (for example BIOS vendor/version/date, board vendor/name/serial, chassis details, product name/UUID/serial, and system vendor). The implementation would be protected => 1 so it runs via pvedaemon with sufficient privileges to read sysfs directly, while still requiring Sys.Audit on /nodes/{node}.
>
> My goal is to provide a standard, documented way to retrieve hardware metadata for asset management, inventory tracking, provisioning, CMDB integration, and reporting. I am reading the data directly from sysfs rather than using dmidecode, since sysfs is faster, avoids parsing, and is available on Linux systems exposing DMI.
>
> I have prepared a sample implementation as a new module PVE/API2/Hardware/DMI.pm, plus registration in PVE/API2/Hardware.pm. I would appreciate feedback on the API shape, permission model, and whether the endpoint belongs in pve-manager or another repository.
>
> If this sounds acceptable, I can split it into a small patch series and send it to the list.
>
> Best regards,
> Krasimir Rangelov
reply other threads:[~2026-06-16 14:06 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=0FC20308-4392-4A01-AD93-9FF741A4C9C3@icloud.com \
--to=krasimir.rangelov12@icloud.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