public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Antoine Martin <antoine@nagafix.co.uk>
To: kvm@vger.kernel.org, Avi Kivity <avi@redhat.com>, pageexec@freemail.hu
Subject: guest patched with pax causes "set_cr0: 0xffff88000[...] #GP, reserved bits 0x8004003?" flood on host
Date: Wed, 10 Mar 2010 23:17:24 +0700	[thread overview]
Message-ID: <4B97C614.3030802@nagafix.co.uk> (raw)

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
(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, but I just want to know one thing: should the guest kernel still be 
able to flood dmesg on the host like this?

Thanks
Antoine

PS: Avi, are you still interested in seeing if this rebuild fixes the 
pread/glibc bug?

             reply	other threads:[~2010-03-10 16:17 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-10 16:17 Antoine Martin [this message]
2010-03-11  6:44 ` guest patched with pax causes "set_cr0: 0xffff88000[...] #GP, reserved bits 0x8004003?" flood on host Avi Kivity
2010-03-11  9:31   ` pageexec
2010-03-11 11:05     ` Antoine Martin
2010-03-11 11:10   ` pageexec

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4B97C614.3030802@nagafix.co.uk \
    --to=antoine@nagafix.co.uk \
    --cc=avi@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=pageexec@freemail.hu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox