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] Re: [Fedora-xen] 2.6.31-1.2.65.xendom0.fc12.x86_64 crash

To: "Jeremy Fitzhardinge" <jeremy@xxxxxxxx>
Subject: Re: [Xen-devel] Re: [Fedora-xen] 2.6.31-1.2.65.xendom0.fc12.x86_64 crash on boot
From: "Charles J Gruener" <cjg9411@xxxxxxx>
Date: Mon, 21 Sep 2009 15:24:41 -0400
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx, M A Young <m.a.young@xxxxxxxxxxxx>, fedora-xen@xxxxxxxxxx
Delivery-date: Mon, 21 Sep 2009 12:25:10 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4AB7CEFE.3020109@xxxxxxxx>
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/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <976E8557-F11D-416E-84C2-CD12B180CA1B@xxxxxxx> <20090915071730.GP31123@xxxxxxxxxxx> <20090915075613.GQ31123@xxxxxxxxxxx> <82B3AFF8-B4F1-4347-82F3-04F100002684@xxxxxxx> <20090915113914.GT31123@xxxxxxxxxxx> <4AB013D2.908@xxxxxxxx> <alpine.GSO.2.00.0909160942300.28938@xxxxxxxxxxxxxxxx> <20090916114713.GC31123@xxxxxxxxxxx> <20FE5C88-00D8-47FC-AACE-99DD211EC99E@xxxxxxx> <4AB7CEFE.3020109@xxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: Aco68S16edGBtKH6RseXpWRoErstuQ==
Thread-topic: [Xen-devel] Re: [Fedora-xen] 2.6.31-1.2.65.xendom0.fc12.x86_64 crash on boot
This is coming from memory as I won't be in front of the machine experiencing the issue for another three weeks. Gotta love paternity leave. :)

From what I recall, if I leave VT-d enabled in the BIOS, I experience the dom0 crash I had sent earlier as a .gz file. I can verify this at a later date.

Ideally, I am looking to have the ability to assign the NVidia cards to the individual domU machines for CUDA development. We want to see how virtualization affects CUDA performance among other things.

The patch that you provided earlier now allows the machine to boot no matter what the NX setting is in the BIOS.

Does that help clarify the situation?

Charles

On Sep 21, 2009, at 3:07 PM, "Jeremy Fitzhardinge" <jeremy@xxxxxxxx> wrote:


Just a final note, I do need to make sure VT-d is disabled in the
BIOS, and then I can boot.  This was obviously not addressed in this
patch nor was it requested to be. It would be nice to have it working
at some point as this machine will hopefully have a bunch of NVidia
cards in it that will need to be dedicated to each of the domU's for
CUDA research.

Just to clarify this a bit:

   Are you saying that if you leave VT-d enabled in BIOS something bad
   happens?  Does it crash?

   But ideally you'd like to enable it and have it working to allow
   NVidia cards work, which require it?

Thanks,
   J

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