Re: [patch 134/149] x86, paravirt: Add a global synchronizationpoint for pvclock

[Glauber Costa]

On Wed, Jul 07, 2010 at 02:47:31PM +0200, 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.
if you boot with another clocksource, and then switch to kvmclock with the machine already
running, do you see anything strange or suspicious?
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/