From mboxrd@z Thu Jan 1 00:00:00 1970 From: Antoine Martin Subject: Re: guest patched with pax causes "set_cr0: 0xffff88000[...] #GP, reserved bits 0x8004003?" flood on host Date: Thu, 11 Mar 2010 18:05:24 +0700 Message-ID: <4B98CE74.8080201@nagafix.co.uk> References: <4B97C614.3030802@nagafix.co.uk>, <4B989162.4080008@redhat.com> <4B98C675.22780.5AAA17C0@pageexec.freemail.hu> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Avi Kivity , kvm@vger.kernel.org To: pageexec@freemail.hu Return-path: Received: from mamba.nagafix.co.uk ([194.145.196.68]:46170 "EHLO mail.nagafix.co.uk" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1757087Ab0CKLFb (ORCPT ); Thu, 11 Mar 2010 06:05:31 -0500 In-Reply-To: <4B98C675.22780.5AAA17C0@pageexec.freemail.hu> Sender: kvm-owner@vger.kernel.org List-ID: On 03/11/2010 04:31 PM, pageexec@freemail.hu wrote: > On 11 Mar 2010 at 8:44, Avi Kivity wrote: > > >> On 03/10/2010 06:17 PM, Antoine Martin wrote: >> >>> Hi, >>> >>> I've updated my host kernel headers to 2.6.33, rebuilt glibc (and the >>> base system), rebuilt kvm. >>> ... and now I get hundreds of those in dmesg on the host when I start >>> a guest kernel that worked fine before. (2.6.33 + pax patch v5) >>> set_cr0: 0xffff88000ec29d58 #GP, reserved bits 0x80040033 >>> set_cr0: 0xffff88000f3cdb38 #GP, reserved bits 0x8004003b >>> set_cr0: 0xffff88000f3dbc88 #GP, reserved bits 0x80040033 >>> set_cr0: 0xffff88000f83b958 #GP, reserved bits 0x8004003b >>> >> The guest is clearly confused. Can you bisect kvm to find out what >> introduced this problem? >> OK, will try to find the time. > the guest is calling pax_{open,close}_kernel that flip cr0.wp off/on, > respectively. Antoine, can you decode some of those rip values please > (or better, send me the corresponding vmlinux and all logs) I've dumped everything here (.config, vmlinuz and log): http://users.nagafix.co.uk/~antoine/KVM/ Antoine