From mboxrd@z Thu Jan 1 00:00:00 1970 From: Zachary Amsden Subject: Re: regression - 2.6.36 -> 2.6.37 - kvm - 32bit SMP guests don't boot Date: Thu, 03 Mar 2011 16:58:33 -0500 Message-ID: <4D700F09.9000002@redhat.com> References: <20110227172052.GB2474@nik-comp.lan> <4D6BA85B.7080908@redhat.com> <20110228143247.GE29840@pcnci.linuxbox.cz> <4D6BBC84.6020408@redhat.com> <20110228152823.GF29840@pcnci.linuxbox.cz> <4D6BC5CA.8060004@redhat.com> <20110228171550.GA2173@nik-comp.lan> <4D6EF536.305@redhat.com> <20110303070652.GG29840@pcnci.linuxbox.cz> <4D6FFE5D.1030401@redhat.com> <20110303210647.GA27691@nik-comp.lan> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Avi Kivity , Nikola Ciprich , KVM list , Linux kernel list , Glauber Costa To: Nikola Ciprich Return-path: In-Reply-To: <20110303210647.GA27691@nik-comp.lan> Sender: linux-kernel-owner@vger.kernel.org List-Id: kvm.vger.kernel.org On 03/03/2011 04:06 PM, Nikola Ciprich wrote: >> What is the exact kernel version you are using in the guest. >> > It's latest centos (2.6.18-194.32.1.el5), so I guess there are a lot > of fixes, but it's possible the kvm-clock is broken in it. > I can't influence what kernel is used there (at least not on customer's > guests), but I guess asking for adding clocksource kernel parameter is > not problem. > > That sounds like a kernel which will be vulnerable to broken KVM clock on 32-bit. There's a kernel side fix that is needed, but why the server side change triggers the problem needs more investigation. Zach