From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([2001:4830:134:3::10]:49877)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <chris@onthe.net.au>) id 1WTKCn-0007vW-Fx
	for qemu-devel@nongnu.org; Thu, 27 Mar 2014 19:59:35 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <chris@onthe.net.au>) id 1WTKCh-0006Se-HA
	for qemu-devel@nongnu.org; Thu, 27 Mar 2014 19:59:29 -0400
Received: from smtp1.onthe.net.au ([203.22.196.249]:46471)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <chris@onthe.net.au>) id 1WTKCh-0006S9-7K
	for qemu-devel@nongnu.org; Thu, 27 Mar 2014 19:59:23 -0400
Date: Fri, 28 Mar 2014 10:59:18 +1100
From: Chris Dunlop <chris@onthe.net.au>
Message-ID: <20140327235918.GA7689@onthe.net.au>
References: <20140327225242.GA5005@onthe.net.au> <5334B44E.4080300@beyond.pl>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
In-Reply-To: <5334B44E.4080300@beyond.pl>
Content-Transfer-Encoding: quoted-printable
Subject: Re: [Qemu-devel] Unresponsive linux guest once migrated
List-Id: <qemu-devel.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Marcin =?utf-8?Q?Gibu=C5=82a?= <m.gibula@beyond.pl>
Cc: qemu-devel@nongnu.org

On Fri, Mar 28, 2014 at 12:29:18AM +0100, Marcin Gibu=C5=82a wrote:
> 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).
>=20
> Hi,
>=20
> 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?

Thanks,

Chris