WARNING - OLD ARCHIVES

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/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

[Xen-devel] approach for heavily hw-oriented values in smbios for guests

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-devel] approach for heavily hw-oriented values in smbios for guests
From: "Andrew D. Ball" <aball@xxxxxxxxxxxxxxxxxx>
Date: Thu, 16 Nov 2006 10:54:36 -0500
Delivery-date: Thu, 16 Nov 2006 07:54:55 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
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>
Organization: IBM
Reply-to: aball@xxxxxxxxxxxxxxxxxx
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
When I was implementing smbios, I occasionally put in mock values for
things like the data width of dimms, much to my chagrin.

What do y'all think the best approach to such situations would be?  If
specific migration groups were enforced, such that a guest will not be
migrated to a different type of cpu/memory/etc., putting accuracte data
there makes sense to me.  Otherwise, I'd prefer to put no values.
However, even though the SMBIOS 2.4 standard specifies lots of places
where a value of 'unknown' is syntactically valid, the comformance
guidelines require a ton of very hardware oriented things to be fully
specified.

Thanks for your help!
Andrew


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

<Prev in Thread] Current Thread [Next in Thread>