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-devel] Xen 4.2 unstable + Jeremy's stable/2.6.32.x

To: Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>
Subject: Re: [Xen-devel] Xen 4.2 unstable + Jeremy's stable/2.6.32.x
From: Goncalo Gomes <Goncalo.Gomes@xxxxxxxxxxxxx>
Date: Sun, 27 Mar 2011 02:57:22 +0100
Cc: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Sat, 26 Mar 2011 18:54:30 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <20110325164202.GA5250@xxxxxxxxxxxx>
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>
Organization: Citrix Systems, Inc
References: <1300988390.2215.9.camel@eire> <20110325144943.GC27651@xxxxxxxxxxxx> <1301067276.10386.6.camel@eire> <20110325164202.GA5250@xxxxxxxxxxxx>
Reply-to: Goncalo.Gomes@xxxxxxxxxxxxx
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
On Fri, 2011-03-25 at 16:42 +0000, Konrad Rzeszutek Wilk wrote:
> On Fri, Mar 25, 2011 at 03:34:36PM +0000, Goncalo Gomes wrote:
> > On Fri, 2011-03-25 at 14:49 +0000, Konrad Rzeszutek Wilk wrote:
> > > > Any alternate hints and/or suggestions would be fairly welcome. I'm
> > > > attaching some relevant information about the HW in question.
> > > 
> > > Try adding 'debug loglevel=10 earlyprintk=xenboot' on the Linux command 
> > > line.
> > 
> > Thanks for the suggestions, but with these changes nothing substantially
> > different comes up on the serial. It stops just after adding PCI 01:03.0
> > as before. Starting to suspect CONFIG_XEN_DOM0_PCI, as I've never
> Yeah, that is quite important.

That didn't help still. I ended up solving my problem using a hackedup
version of Gianni's config file. 

Thanks though!


Xen-devel mailing list

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