From: Michael Tokarev Subject: Re: 2.6.32 guest with paravirt clock enabled hangs on 2.6.37.6 host (w qemu-kvm-0.13.0) Date: Sun, 08 May 2011 22:53:56 +0400 Message-ID: <4DC6E6C4.4030103@msgid.tls.msk.ru> References: <20110508183303.GA7918@nik-comp.lan> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: kvm@vger.kernel.org To: Nikola Ciprich Return-path: Received: from isrv.corpit.ru ([86.62.121.231]:40912 "EHLO isrv.corpit.ru" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932201Ab1EHSx6 (ORCPT ); Sun, 8 May 2011 14:53:58 -0400 In-Reply-To: <20110508183303.GA7918@nik-comp.lan> Sender: kvm-owner@vger.kernel.org List-ID: 08.05.2011 22:33, Nikola Ciprich wrote: > Hello everyboy, > while installing new virt machine today, I noticed that 2.6.32 x86_64 SMP guests are hanging if they have paravirt-clock enabled... There were about 10 bugfixes pushed to 2.6.32.y stable series, some of them were for kvm-clock, and some were for problems which manifested itself like you described. You may actually take a look which guests you're booting. FWIW. /mjt