Messages in this thread | | | Date | Thu, 08 Jul 2010 12:41:46 +0300 | From | Avi Kivity <> | Subject | Re: [patch 134/149] x86, paravirt: Add a global synchronization point for pvclock |
| |
On 07/07/2010 03:47 PM, Peter Palfrader wrote: > Hey, > > Greg KH schrieb am Donnerstag, dem 01. Juli 2010: > > >> 2.6.32-stable review patch. If anyone has any objections, please let us know. >> > 2.6.32.16 fails to boot on my KVM domains using qemu-kvm 0.11.1. > > Bisecting between 2.6.32.14 which worked and .16 turned up this commit > as the first culprit[0]. > > The host is still running 2.6.32.14 and has 8 cores on 2 CPUs. The > single-cpu KVM domain hangs just after printing 'Write protecting the > kernel read-only data: 9492k'[1]. On a successful boot this line would > usually be followed by 'INIT: version 2.86 booting'. > > A 2.6.32.16 with this patch reverted boots fine. > > If there's any info you need please just ask. >
I'm unable to reproduce.
Can you provide the stack trace where this hangs? Add CONFIG_DEBUG_INFO, and then
- copy vmlinux somewhere on the host filesystem - start the guest - when it hangs, type 'gdbserver' in the qemu monitor - on the host, the 'gdb /path/to/vmlinux' - 'target remote :1234' - 'backtrace'
-- error compiling committee.c: too many arguments to function
| |