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
--
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
