From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:45438) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WTJjx-0002Wo-Qm for qemu-devel@nongnu.org; Thu, 27 Mar 2014 19:29:49 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1WTJjq-00066S-HL for qemu-devel@nongnu.org; Thu, 27 Mar 2014 19:29:41 -0400 Received: from mx.beyond.pl ([92.43.117.49]:57207) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WTJjq-000669-AZ for qemu-devel@nongnu.org; Thu, 27 Mar 2014 19:29:34 -0400 Message-ID: <5334B44E.4080300@beyond.pl> Date: Fri, 28 Mar 2014 00:29:18 +0100 From: =?UTF-8?B?TWFyY2luIEdpYnXFgmE=?= MIME-Version: 1.0 References: <20140327225242.GA5005@onthe.net.au> In-Reply-To: <20140327225242.GA5005@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, chris@onthe.net.au W dniu 2014-03-27 23:52, Chris Dunlop pisze: > Hi, > > I have a problem where I migrate a linux guest VM, and on the > receiving side the guest goes to 100% cpu as seen by the host, and > the guest itself is unresponsive, e.g. not responding to ping etc. > The only way out I've found is to destroy the guest. > > This seems to only happen if the guest has been idle for an extended > period (e.g. overnight). I've migrated the guest 100 times in a row > without any problems when the guest has been used "a little" (e.g. > logging in and looking around, it's not doing anything normally). Hi, 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) ? -- mg