This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


Re: [Xen-devel] interest SMBIOS on domU's

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-devel] interest SMBIOS on domU's
From: "B Thomas" <bjthomas3@xxxxxxxxx>
Date: Tue, 16 May 2006 11:15:16 -0400
Delivery-date: Tue, 16 May 2006 08:15:39 -0700
Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; b=qsCIfFH8ER9l7T3XTbkwhq4IATLhapKrsUUTrVZ0RR9nYS9xvAyso6pmsCNiPhaoPArEw/tdDBCOlpju6ELOcQLGsaHeXGg4wA2qU1BdhH8PPum1mK5wmTsTeoEAqRcDbWv/c0pdt30DZO8qyvm/08BkAmXN8wP31A8NN/DFLd4=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <b3bd3a9d0605151822w5f8fb03av58a968064fc7ae19@xxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <b3bd3a9d0605151822w5f8fb03av58a968064fc7ae19@xxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
I have been using the entire table for some time, with specific highlights for BIOS, System, Module and Chassis.  These contain relatively interesting information about system IDs, manufacturer, version numbers, product name and so forth. This has been of use to both management software, as well as to your own eyeballs when you're trying to track something down to a particular machine. I've included a sample of these items below (taken from an HVM domain0 on a Dell 380).

Clearly, much of this information is of use as applied to real hardware and domain0, but there is probably an interesting subset for virtual machines in domU.  There's probably an interesting subset and analog for domainU information. It will be interesting to see what you propose doing for the domU visible DMI data. Do you intend to go as far as to include slots, devices and ports ?  Will you match what the ACPI tables report ?


    <BIOS Type="0" Item="2" Handle="0x0">
      <Vendor>Dell Inc.                </Vendor>
    <System Type="1" Item="3" Handle="0x100">
      <Manufacturer>Dell Inc.                </Manufacturer>
      <ProductName>Precision WorkStation 380    </ProductName>
    <Module Type="2" Item="4" Handle="0x200">
      <Manufacturer>Dell Inc.          </Manufacturer>
      <Version>   </Version>
    <Chassis Type="3" Item="5" Handle="0x300">
      <Manufacturer>Dell Inc.                </Manufacturer>
      <AssetTag>          </AssetTag>

On 5/15/06, Andrew Ball <anball@xxxxxxxxx> wrote:
Is anyone else interested in SMBIOS tables for domU's?  (These are the
things that dmidecode reads -- they're often used by systems
management software and occasionally used by drivers.)

I've been working on a patch for fully virtualized domU's for some
time now and am curious about who else might care about it and what
types they think make sense.

A lot of the types make very little sense, like system chassis, but
the system information one that contains the system UUID (universally
unique identifier) is crucial for supporting arbitrary OSes in HVM
domU's for some systems management software.  The idea is to correlate
domU's with dom0's by UUID's of the domU's.

I'll try to send out the patches soon.  I hope they're not too ugly to
stomach -- it's been difficult for me to make something like this

Thanks for your help!
Andrew D. Ball
"Festina lente" $\approx$ "Make haste slowly"
    -- Caesar Augustus

Xen-devel mailing list

Xen-devel mailing list
<Prev in Thread] Current Thread [Next in Thread>