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-users] Problem with VT-d on Mainboard Intel DQ45CB

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-users] Problem with VT-d on Mainboard Intel DQ45CB
From: Franz Regensburger <Franz.Regensburger@xxxxxxxx>
Date: Thu, 20 Nov 2008 21:27:57 +0100
Delivery-date: Thu, 20 Nov 2008 12:28:28 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <20574334.post@xxxxxxxxxxxxxxx>
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <200810230925.04813.Franz.Regensburger@xxxxxxxx> <200811171412.58630.Franz.Regensburger@xxxxxxxx> <20574334.post@xxxxxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: KMail/1.9.1
Hello James,

did you do the following (it's metioned in my howto file)?

>make linux-2.6-xen-config CONFIGMODE=menuconfig
>      change XEN->"PCI-device backend driver" from "M" to "*".

This compiles the PCI-device backend driver fixed into the kernel.
I tried to use the module but did not succeed in loading the module and 
activating the PCI backend hiding that way. However, compiling it fixed into 
the kernel works for me.



Am Mittwoch, 19. November 2008 07:19 schrieb James550:
> Still using Centos5.2, followed the steps mentioned here and elsewhere to
> see if it made a difference when compared to my original steps. 
> Unfortunately I am still running into a boot freeze at the "MTRR" line that
> I mentioned earlier.  If I change "iommu" to 0, then I can boot into the
> 2.6.18-xen kernel w/out the freeze.  Is there a bios setting that I am
> missing?  Is there a setting during the "make linux-2.6-xen-config
> CONFIGMODE=menuconfig" step that I missed or need to change?
> It looks like this is what is expected to follow this "(XEN) mtrr: your
> CPUs had inconsistent fixed MTRR settings":
> (XEN) *** LOADING DOMAIN 0 ***
> (XEN)  Xen  kernel: 64-bit, lsb, compat32
> (XEN)  Dom0 kernel: 64-bit, lsb, paddr 0xffffffff80200000 ->
> 0xffffffff805c048c
> I'm stumped and would love to benefit from any of your knowledge and
> experience. :)

Xen-users mailing list