From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:40507) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WVGoE-0002RE-5h for qemu-devel@nongnu.org; Wed, 02 Apr 2014 04:46:17 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1WVGo3-0007kM-Kx for qemu-devel@nongnu.org; Wed, 02 Apr 2014 04:46:09 -0400 Received: from mx.beyond.pl ([92.43.117.49]:58998) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WVGo3-0007k4-Dy for qemu-devel@nongnu.org; Wed, 02 Apr 2014 04:45:59 -0400 Received: from localhost (localhost [127.0.0.1]) by mx.beyond.pl (Postfix) with ESMTP id 9FC782615 for ; Wed, 2 Apr 2014 10:45:55 +0200 (CEST) Received: from mx.beyond.pl ([127.0.0.1]) by localhost (mw.beyond.pl [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Euvj3-bqQoQO for ; Wed, 2 Apr 2014 10:45:53 +0200 (CEST) Received: from [10.113.190.133] (ip-91-102-114-166.beyond.pl [91.102.114.166]) (Authenticated sender: m.gibula@beyond.pl) by mx.beyond.pl (Postfix) with ESMTPSA id DCA371017 for ; Wed, 2 Apr 2014 10:45:53 +0200 (CEST) Message-ID: <533BCE40.8060908@beyond.pl> Date: Wed, 02 Apr 2014 10:45:52 +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> <533929D3.30109@beyond.pl> <20140402054144.GA31323@onthe.net.au> In-Reply-To: <20140402054144.GA31323@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: qemu-devel@nongnu.org > It's looking good so far, after a few migrations (it takes a while to test > because I'm waiting at least 5 hours between migrations). I'll be happier > once I've done a couple of weeks of this without any failures! Does anyone have any hints how to debug this thing? :( I've tried to put hanged guest under gdb and found it's looped deep inside kernel time management functions. Disabling kvmclock suggests it is somehow related to its corruption during migration. It happens on both old and new versions of guest kernels. Any hints from developers are welcome:) -- mg