From mboxrd@z Thu Jan 1 00:00:00 1970 From: William Pitcock Subject: Re: Crash with paravirt-ops 2.6.31.6 kernel Date: Thu, 19 Nov 2009 11:21:44 +0300 (MSK) Message-ID: <9082131.751258618904958.JavaMail.root@ifrit.dereferenced.org> References: <20091118144518.GD15585@phenom.dumpdata.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20091118144518.GD15585@phenom.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 Hi Konrad, ----- "Konrad Rzeszutek Wilk" wrote: > > [ 1.254927] init[1] general protection ip:f779042f sp:ff9b0340 > error:0 > This is a domU kernel only. And I am aware that init crashing is the reason why. My paravirt-ops dom0 kernels boot fine, but they are 64bit userland. The reason why I ask is because this only happens with the paravirt-ops tree, e.g. not with the XenLinux 2.6.18 tree or the forward ports. I think it might be related to the stackprotector option? William