From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: guest patched with pax causes "set_cr0: 0xffff88000[...] #GP, reserved bits 0x8004003?" flood on host Date: Thu, 11 Mar 2010 08:44:50 +0200 Message-ID: <4B989162.4080008@redhat.com> References: <4B97C614.3030802@nagafix.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: kvm@vger.kernel.org, pageexec@freemail.hu To: Antoine Martin Return-path: Received: from mx1.redhat.com ([209.132.183.28]:49566 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751900Ab0CKGpB (ORCPT ); Thu, 11 Mar 2010 01:45:01 -0500 In-Reply-To: <4B97C614.3030802@nagafix.co.uk> Sender: kvm-owner@vger.kernel.org List-ID: 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? > (hundreds of all 4) > And the VM just reboots shortly after starting init. > Funnily enough, I've got some VMs still running that kernel just fine! > (as I started them before the headers+glibc+qemu-kvm rebuild) > > Now, you might just say that I shouldn't use out of tree patches like > pax, You can run anything you like in a guest. > but I just want to know one thing: should the guest kernel still be > able to flood dmesg on the host like this? No, these are debug messages. > > Thanks > Antoine > > PS: Avi, are you still interested in seeing if this rebuild fixes the > pread/glibc bug? I think we figured it out, but a confirmation would be nice. -- error compiling committee.c: too many arguments to function