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] Xen 4.0 + PVOPS + Intel VTD + USB EHCI = BUG()

To: "David P. Quigley" <dpquigl@xxxxxxxxxxxxx>
Subject: Re: [Xen-devel] Xen 4.0 + PVOPS + Intel VTD + USB EHCI = BUG()
From: Pasi Kärkkäinen <pasik@xxxxxx>
Date: Thu, 28 Jan 2010 11:24:45 +0200
Cc: Daniel Stodden <daniel.stodden@xxxxxxxxxx>, "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>, Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>
Delivery-date: Thu, 28 Jan 2010 01:25:05 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <1264623777.20881.12.camel@xxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
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: <1264198967.20158.23.camel@xxxxxxxxxxxxxxxxxxxxxxxxxxxxx> <20100122224307.GA9943@xxxxxxxxxxxxxxxxxxx> <1264461835.20158.67.camel@xxxxxxxxxxxxxxxxxxxxxxxxxxxxx> <20100126144212.GA10928@xxxxxxxxxxxxxxxxxxx> <1264524172.20158.82.camel@xxxxxxxxxxxxxxxxxxxxxxxxxxxxx> <20100126165724.GA13847@xxxxxxxxxxxxxxxxxxx> <1264527964.20158.87.camel@xxxxxxxxxxxxxxxxxxxxxxxxxxxxx> <20100126181949.GA14346@xxxxxxxxxxxxxxxxxxx> <1264534209.20881.5.camel@xxxxxxxxxxxxxxxxxxxxxxxxxxxxx> <1264623777.20881.12.camel@xxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.18 (2008-05-17)
On Wed, Jan 27, 2010 at 03:22:57PM -0500, David P. Quigley wrote:
> On Tue, 2010-01-26 at 14:30 -0500, David P. Quigley wrote:
> > I have a small update on the problem. It does seem like it is tied to
> > VT-D because I just turned it off in the bios and the dom0 manages to
> > boot on top of xen and I can log in. Are there any options for VT-D that
> > you would like me to try to help pin point the problem?
> > 
> > Dave
> > 
> > 
> > _______________________________________________
> > Xen-devel mailing list
> > Xen-devel@xxxxxxxxxxxxxxxxxxx
> > http://lists.xensource.com/xen-devel
> 
> 
> So I've managed to get my dom0 booting on top of xen however now I'm
> running into a problem where my domU is kernel oopsing on startup. The
> traces I've gotten seem to be in the memory allocation functions.
> Normally this is a sign of memory corruption. Considering this VM was
> working perfectly with the 2.6.31.10 dom0 based on the Novell patches
> and xen 4.0 I don't think it is the VM that is the problem (however I
> can try starting it under kvm to be certain. Any suggestions on what I
> can do to try to hunt down the memory corruption?
> 

Hmm.. interesting.

You could try this: Set on_crash="preserve" in /etc/xen/<guest> cfgfile,
and when the guest crashes, run in dom0:

/usr/lib/xen/bin/xenctx -s System.map-domUkernelversion <domUid>

If your system is 64bit then xenctx might be under /usr/lib64/
That should give you a stack trace of the crashed guest..

-- Pasi


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