Hey,
Greg KH schrieb am Donnerstag, dem 01. Juli 2010:
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.
Cheers,
Peter
0.
http://asteria.noreply.org/~weasel/volatile/2010-07-07-x9KxN34l17c/fileztnjyZ
1.
http://asteria.noreply.org/~weasel/volatile/2010-07-07-VTRuAQGOKlY/zoe-2.6.32.16.png
2.
http://asteria.noreply.org/~weasel/volatile/2010-07-07-Fq0PVc1ecsc/config-2.6.32.16-ds...
--
| .''`. ** Debian GNU/Linux **
Peter Palfrader | : :' : The universal
http://www.palfrader.org/ | `. `' Operating System
| `-
http://www.debian.org/
--