From mboxrd@z Thu Jan 1 00:00:00 1970 From: Goncalo Gomes Subject: Re: Xen 4.2 unstable + Jeremy's stable/2.6.32.x Date: Sun, 27 Mar 2011 02:57:22 +0100 Message-ID: <1301191042.15612.13.camel@eire> References: <1300988390.2215.9.camel@eire> <20110325144943.GC27651@dumpdata.com> <1301067276.10386.6.camel@eire> <20110325164202.GA5250@dumpdata.com> Reply-To: Goncalo.Gomes@Eu.Citrix.Com Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20110325164202.GA5250@dumpdata.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Konrad Rzeszutek Wilk Cc: "xen-devel@lists.xensource.com" List-Id: xen-devel@lists.xenproject.org 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! Goncalo