From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <a.zeidler@proxmox.com>
Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68])
 (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)
 key-exchange X25519 server-signature RSA-PSS (2048 bits))
 (No client certificate requested)
 by lists.proxmox.com (Postfix) with ESMTPS id 1033F950DD
 for <pve-devel@lists.proxmox.com>; Thu, 11 Apr 2024 19:14:27 +0200 (CEST)
Received: from firstgate.proxmox.com (localhost [127.0.0.1])
 by firstgate.proxmox.com (Proxmox) with ESMTP id ECD20357BA
 for <pve-devel@lists.proxmox.com>; Thu, 11 Apr 2024 19:14:26 +0200 (CEST)
Received: from proxmox-new.maurer-it.com (proxmox-new.maurer-it.com
 [94.136.29.106])
 (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)
 key-exchange X25519 server-signature RSA-PSS (2048 bits))
 (No client certificate requested)
 by firstgate.proxmox.com (Proxmox) with ESMTPS
 for <pve-devel@lists.proxmox.com>; Thu, 11 Apr 2024 19:14:26 +0200 (CEST)
Received: from proxmox-new.maurer-it.com (localhost.localdomain [127.0.0.1])
 by proxmox-new.maurer-it.com (Proxmox) with ESMTP id 0453B44C59
 for <pve-devel@lists.proxmox.com>; Thu, 11 Apr 2024 19:14:26 +0200 (CEST)
Message-ID: <a82b50b58e795e5555623c720d9d9448e8239bf5.camel@proxmox.com>
From: Alexander Zeidler <a.zeidler@proxmox.com>
To: Aaron Lauterer <a.lauterer@proxmox.com>, Proxmox VE development
 discussion <pve-devel@lists.proxmox.com>
Date: Thu, 11 Apr 2024 19:14:24 +0200
In-Reply-To: <1858f426-47cc-41cf-bbc4-523ab2bff4e9@proxmox.com>
References: <20240322135933.164404-1-a.zeidler@proxmox.com>
 <20240322135933.164404-7-a.zeidler@proxmox.com>
 <1858f426-47cc-41cf-bbc4-523ab2bff4e9@proxmox.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
User-Agent: Evolution 3.46.4-2 
MIME-Version: 1.0
X-SPAM-LEVEL: Spam detection results:  0
 AWL 0.099 Adjusted score from AWL reputation of From: address
 BAYES_00                 -1.9 Bayes spam probability is 0 to 1%
 DMARC_MISSING             0.1 Missing DMARC policy
 KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment
 SPF_HELO_NONE           0.001 SPF: HELO does not publish an SPF Record
 SPF_PASS               -0.001 SPF: sender matches SPF record
Subject: Re: [pve-devel] [PATCH manager 7/9] report: add info of the
 mainboard in use
X-BeenThere: pve-devel@lists.proxmox.com
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Proxmox VE development discussion <pve-devel.lists.proxmox.com>
List-Unsubscribe: <https://lists.proxmox.com/cgi-bin/mailman/options/pve-devel>, 
 <mailto:pve-devel-request@lists.proxmox.com?subject=unsubscribe>
List-Archive: <http://lists.proxmox.com/pipermail/pve-devel/>
List-Post: <mailto:pve-devel@lists.proxmox.com>
List-Help: <mailto:pve-devel-request@lists.proxmox.com?subject=help>
List-Subscribe: <https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel>, 
 <mailto:pve-devel-request@lists.proxmox.com?subject=subscribe>
X-List-Received-Date: Thu, 11 Apr 2024 17:14:27 -0000

On Fri, 2024-03-22 at 15:26 +0100, Aaron Lauterer wrote:
> If we add more info, then dmidecode -t {1,2,3} might be interesting as=
=20
> well as those deliver motherboard, system and chassis infos.
>=20
> If you want to see what you get there, run them on some decent servers=
=20
> as most consumer boards and systems will not show useful information here

Thanks! I've now looked at the output from different servers/motherboards
from the past years (ASUS, Dell, GIGABYTE, HP, 2x Supermicro).


In the system and base board output there was (only) the following
relevant information:

System Information
	Manufacturer: Thomas-Krenn.AG
	Product Name: RS700-E11-RS12U 1HE Intel Dual-CPU RI2112-ASXSN Server CHECK=
LISTE
	Version: 00
Base Board Information
	Manufacturer: ASUSTeK COMPUTER INC.
	Product Name: Z13PP-D32 Series
	Version: 60SB09M0-SB0G11

But to avoid blindness, and since the unfiltered output is not that long,
we could include it as a whole.


The chassis output contains several potentially interesting lines. So we
could include that as a whole too:

Handle 0x0300, DMI type 3, 21 bytes
Chassis Information
->	Manufacturer: HP
->	Type: Rack Mount Chassis
	Lock: Not Present
	Version: Not Specified
	Serial Number: (...)
	Asset Tag:
->	Boot-up State: Critical
->	Power Supply State: Critical
->	Thermal State: Safe
	Security Status: Unknown
	OEM Information: 0x00000000
	Height: 2 U
->	Number Of Power Cords: 2
	Contained Elements: 0

>=20
> On  2024-03-22  14:59, Alexander Zeidler wrote:
> > Signed-off-by: Alexander Zeidler <a.zeidler@proxmox.com>
> > ---
> >   PVE/Report.pm | 1 +
> >   1 file changed, 1 insertion(+)
> >=20
> > diff --git a/PVE/Report.pm b/PVE/Report.pm
> > index 3a81bdb2..f28d7b38 100644
> > --- a/PVE/Report.pm
> > +++ b/PVE/Report.pm
> > @@ -104,6 +104,7 @@ my $init_report_cmds =3D sub {
> >   	hardware =3D> {
> >   	    order =3D> 70,
> >   	    cmds =3D> [
> > +		'cd /sys/devices/virtual/dmi/id; cat board_vendor board_name',
> >   		'dmidecode -t bios -q',
> >   		'lscpu',
> >   		'lspci -nnk',