On 03/11/2010 04:31 PM, pageexec@xxxxxxxxxxx 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
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
