From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:38205) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WUXlA-00037j-PQ for qemu-devel@nongnu.org; Mon, 31 Mar 2014 04:40:08 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1WUXl3-0005oD-A3 for qemu-devel@nongnu.org; Mon, 31 Mar 2014 04:40:00 -0400 Received: from mx.beyond.pl ([92.43.117.49]:45665) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WUXl3-0005ny-2h for qemu-devel@nongnu.org; Mon, 31 Mar 2014 04:39:53 -0400 Message-ID: <533929D3.30109@beyond.pl> Date: Mon, 31 Mar 2014 10:39:47 +0200 From: =?UTF-8?B?TWFyY2luIEdpYnXFgmE=?= MIME-Version: 1.0 References: <20140327225242.GA5005@onthe.net.au> <5334B44E.4080300@beyond.pl> <20140327235918.GA7689@onthe.net.au> In-Reply-To: <20140327235918.GA7689@onthe.net.au> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] Unresponsive linux guest once migrated List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Chris Dunlop Cc: qemu-devel@nongnu.org >> I've seen very similar problem on our installation. Have you tried to >> run with kvm-clock explicitly disabled (either via no-kvmclock in >> guest kernel or with -kvm-clock in qemu) ? > > No, I haven't tried it yet (I've confirmed kvm-clock is currently > being used). I'll have a look at it. > > Did it help your issue? My results were inconclusive, but there way a guy two months ago who had the same problem and disabling kvm-clock resolved this for him. I wonder if it'll help you as well. -- mg