From mboxrd@z Thu Jan 1 00:00:00 1970 From: Pasi =?iso-8859-1?Q?K=E4rkk=E4inen?= Subject: Re: Xen 4.0 crashes with pvops kernel Date: Tue, 15 Jun 2010 17:17:15 +0300 Message-ID: <20100615141715.GF17817@reaktio.net> References: <4C17932F0200007800006821@vpn.id2.novell.com> <4C179A47020000780000683A@vpn.id2.novell.com> <4C179FBC020000780000685D@vpn.id2.novell.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <4C179FBC020000780000685D@vpn.id2.novell.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: Jan Beulich Cc: Cris Daniluk , "xen-devel@lists.xensource.com" , Keir Fraser List-Id: xen-devel@lists.xenproject.org On Tue, Jun 15, 2010 at 02:43:56PM +0100, Jan Beulich wrote: > >>> On 15.06.10 at 15:24, Cris Daniluk wrote: > > For what its worth, it happened in 2.6.32.11 in addition to 2.6.32.13. > > I also had earlier tried a 2.6.31 pvops distro kernel with the same > > results last week. Interestingly, I also tried a 2.6.31 kernel with > > Xen 3.4 on the same hardware with no issues. It seems like XenLinux > > kernel with Xen 4.0 is fine, and pvops with Xen 3.x is fine. > > That's odd, but perhaps the kernel behaves differently on older Xen. > Attempts to map IO-APIC space should be disallowed by 3.4 just as > with 4.0. > At least Xen 4.0 has the new IOAPIC hypercall that pvops 2.6.32 is using.. -- Pasi