From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jeremy Fitzhardinge Subject: Re: pv_ops: 2.6.24.3 - no vm86_info: BAD Date: Tue, 25 Mar 2008 08:04:35 -0700 Message-ID: <47E91483.1080608@goop.org> References: <47E856ED.60800@theshore.net> <1206445486.21465.17.camel@zakaz.uk.xensource.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <1206445486.21465.17.camel@zakaz.uk.xensource.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: Ian Campbell Cc: xen devel List-Id: xen-devel@lists.xenproject.org Ian Campbell wrote: > If I remember correctly this was due to the generic parts of the kernel > trying to use sysenter because the hypervisor claimed to support it in > 32on64 mode (by setting SEP in cpuid). However the Xen kernel side code > wasn't present to support it. > Yep, that's right. > You can try booting with "nosep" on your command line or grabbing the > git changeset d40e705903397445c6861a0a56c23e5b2e8f9b9a (which I thought > had been put forward for the stable kernel but I don't see it there > now). > Yes, I should make sure that gets pushed out, along with the other bugfix. Booting with "nosep" is a good workaround for the meantime. > Lastly you could also try b8228d191b5ff7e37525846d187807d162e30464 from > the x86.git#testing branch which actually implements sysenter support, I > don't know which other changesets that one depends on though. > I think its fairly independent of everything else. J