From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jeremy Fitzhardinge Subject: Re: Crashing DomU Date: Wed, 11 Nov 2009 13:49:49 -0800 Message-ID: <4AFB317D.4060505@goop.org> References: <4AF9E19C.2060900@scarlet.be> <4AFA7119.4090108@scarlet.be> <20091111092932.GN16033@reaktio.net> <4AFAD293.6040806@scarlet.be> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <4AFAD293.6040806@scarlet.be> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Killian De Volder Cc: "xen-devel@lists.xensource.com" , Konrad Rzeszutek Wilk List-Id: xen-devel@lists.xenproject.org On 11/11/09 07:04, Killian De Volder wrote: > I'm not entirely certain, if you wish i could seek out the option. It would be helpful to isolate it. Mainline kernels should work as domU without any other patches. Its possible there's a bugfix in xen.git should should be in mainline. J >> On Wed, Nov 11, 2009 at 09:08:57AM +0100, Killian De Volder wrote: >> >>> After removing some things from my .config (of witch PCI support) xen now >>> seems to boot. >>> >>> >> >> What was the option causing the crash? >> >> -- Pasi >> >> >> > > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xensource.com > http://lists.xensource.com/xen-devel >