From: "Andrew D. Ball" <aball@us.ibm.com>
To: "Daniel P. Berrange" <berrange@redhat.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: Invalid length provided for SMBIOS data
Date: Mon, 02 Oct 2006 10:10:40 -0400 [thread overview]
Message-ID: <1159798240.27206.13.camel@localhost> (raw)
In-Reply-To: <20060927180359.GL20056@redhat.com>
This is seriously broken -- I'll write a patch as soon as I can, unless
somebody beats me to it :-)
Peace.
Andrew
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
>
> Regards,
> Dan.
next prev parent reply other threads:[~2006-10-02 14:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-27 18:03 Invalid length provided for SMBIOS data Daniel P. Berrange
2006-10-02 14:10 ` Andrew D. Ball [this message]
2006-10-02 17:13 ` Keir Fraser
2006-10-02 17:52 ` Andrew D. Ball
2006-10-03 6:47 ` Keir Fraser
2006-10-03 20:08 ` Daniel P. Berrange
[not found] ` <1159802159.27206.15.camel@localhost>
[not found] ` <20061002154857.GA1730@redhat.com>
2006-10-02 17:49 ` Andrew D. Ball
2006-10-03 14:53 ` Andrew D. Ball
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=1159798240.27206.13.camel@localhost \
--to=aball@us.ibm.com \
--cc=berrange@redhat.com \
--cc=xen-devel@lists.xensource.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.