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

Re: [Xen-devel] Invalid length provided for SMBIOS data

To: "Daniel P. Berrange" <berrange@xxxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-devel] Invalid length provided for SMBIOS data
From: "Andrew D. Ball" <aball@xxxxxxxxxx>
Date: Mon, 02 Oct 2006 13:49:43 -0400
Delivery-date: Mon, 02 Oct 2006 10:48:02 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <20061002154857.GA1730@xxxxxxxxxx>
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
References: <20060927180359.GL20056@xxxxxxxxxx> <1159802159.27206.15.camel@localhost> <20061002154857.GA1730@xxxxxxxxxx>
Reply-to: aball@xxxxxxxxxx
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
I wonder if some of the smbios tables are squashed...  I have [much
to my chagrin] a hard-coded the starting address and size of the 
tables:

/* These constants must agree with the ACPI e820 memory map as defined
   in tools/libxc/xc_hvm_build.c and the address the ROMBIOS pulls the
   SMBIOS entry point from in the smbios_init subroutine.
 */
#define SMBIOS_PHYSICAL_ADDRESS 0x9f000
#define SMBIOS_SIZE_LIMIT 0x800

I'll look at what data I get from a 64-bit domU as soon as I can get to
my VT machine.  You're welcome to futz around as well.  The dmidecode
isn't terribly difficult to read.  I've also written a tool to examine
memory by physical (will be pseudo-physical in this case) address that
I'd be happy to share.

Peace.
Andrew

On Mon, 2006-10-02 at 16:48 +0100, Daniel P. Berrange wrote:
> On Mon, Oct 02, 2006 at 11:15:58AM -0400, Andrew D. Ball wrote:
> > Please post the domU's configuration.  Looks like the type 4 (cpu
> > information) generation is broken.
> 
> Here's the config from my RHEL-3, x86_64  guest
> 
> # Automatically generated xen config file
> name = "rhel3x86_64"
> builder = "hvm"
> memory = "500"
> disk = [ 'file:/xen/rhel3x86_64.img,hda,w', ]
> vif = [ 'mac=00:16:3e:05:eb:04, bridge=xenbr0', ]
> uuid = "dbc4c892-4b67-bc7a-895a-a6b5f56ff061"
> device_model = "/usr/lib64/xen/bin/qemu-dm"
> kernel = "/usr/lib/xen/boot/hvmloader"
> vnc=1
> vncunused=1
> apic=1
> acpi=0
> pae=1
> vcpus=4
> serial = "pty" 
> on_reboot   = 'restart'
> on_crash    = 'restart'
> 
> > On Wed, 2006-09-27 at 19:03 +0100, Daniel P. Berrange wrote:
> > > I was running some tests of HVM guests on Fedora Core 6, test3 and came
> > > across a potential issue with SMBIOS data. When running dmidecode in the
> > > guest VMs it reports that the actual SMBIOS data size, does not match
> > > the advertised size. eg
> > > 
> > > "Wrong DMI structures length: 439 bytes announced, structures occupy 363 
> > > bytes."
> > > 
> > > I've tried this in a variety of guest OS (RHEL-3 32-bit, RHEL-3 64-bit,
> > > RHEL-4 64-bit) all the same results. The host is running FC6 test3, but
> > > the bit of code responsible for constructing the SMBIOS tables is 
> > > identical
> > > to that on the vanilla xen-unstable.hg  repository. I'm not familiar 
> > > enough with SMBIOS specs / code to determine where the mistake in the
> > > length calculation is though...
> > > 
> > > Is anyone else seeing this length mismatch in HVM guests ?
> > > 
> > > FYI, we're tracking this as 
> > > https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=207501
> > > 
> 
> 
> Dan.


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