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] SMBIOS problem with PXE booting

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-devel] SMBIOS problem with PXE booting
From: Evan Bigall <evan.bigall@xxxxxxxxxxx>
Date: Fri, 05 Jan 2007 11:25:40 +0700
Delivery-date: Thu, 04 Jan 2007 20:26:23 -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>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Thunderbird 1.5.0.9 (X11/20061206)
I am using Xen 3.03 on IBM T60s running FC5 and RHEL4 with VT enabled.

We have a standard linux bootable iso that we use to run diagnostics (2.6.11 kernel). When I boot that image in an HVM guest, the diagnostics run fine, and SMBIOS looks normal.

When I change nothing in the config but the image to boot, and then boot eb-5.4.2-rtl8139.iso (downloaded from *rom*-*o*-*matic*.net), the iso boots, correctly, PXEs, tftps our kernel and ramdisk, but then if I run dmidecode on the ramdisk, it looks like SMBIOS has been corrupted somehow.

A correct dmidecode starts out like this:

SMBIOS 2.4 present.
10 structures occupying 283 bytes
Table at 0x0009f01
Handle 0x0000
   DMI type 0, 24 bytes
   BIOS information
      Vendor: Xen
      Version 3.0.3-0
[etc...]
The corrupted one looks like this:

SMBIOS 2.4 present.
10 structures occupying 283 bytes
Table at 0x0009f01f
Handle 0x009e
   DMI type 0, 0 bytes.
   BIOS Information
Handle 0x09e0
   DMI type 158, 0 bytes.

I've tried integrating the rom image directly into /usr/lib/xen/boot/hvmloader, but get the same results.

Any ideas?

I've also noted that in the HVM guest, if I try to boot an SMP kernel, it hangs, only the non-SMP kernel successfully boots.

Evan

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

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