From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:57459) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WVIFc-0006tZ-4e for qemu-devel@nongnu.org; Wed, 02 Apr 2014 06:18:38 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1WVIFW-0003zg-5y for qemu-devel@nongnu.org; Wed, 02 Apr 2014 06:18:32 -0400 Received: from mx.beyond.pl ([92.43.117.49]:33300) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WVIFV-0003zO-TL for qemu-devel@nongnu.org; Wed, 02 Apr 2014 06:18:26 -0400 Received: from localhost (localhost [127.0.0.1]) by mx.beyond.pl (Postfix) with ESMTP id 5F85E262D for ; Wed, 2 Apr 2014 12:18:24 +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 dEv0pZFf5wG0 for ; Wed, 2 Apr 2014 12:18:23 +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 D342DFB9 for ; Wed, 2 Apr 2014 12:18:23 +0200 (CEST) Message-ID: <533BE3ED.8070305@beyond.pl> Date: Wed, 02 Apr 2014 12:18:21 +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> <533BCE40.8060908@beyond.pl> <20140402090450.GA2586@work-vm> <533BD8CE.9060002@beyond.pl> <20140402093938.GB2586@work-vm> In-Reply-To: <20140402093938.GB2586@work-vm> 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 On 02.04.2014 11:39, Dr. David Alan Gilbert wrote: > * Marcin Gibu??a (m.gibula@beyond.pl) wrote: >>> Can you give: >>> 1) A backtrace from the guest >>> thread apply all bt full >>> in gdb >> >> You mean from gdb attached to hanged guest? I'll try to get it. From >> what I remember it looks rather "normal" - busy executing guest >> code. > > yes; if you can send it a sysrq to trigger a backtrace it might also > be worth a try - I'm just trying to find what the guest is really doing > when it's apparentyly 'hung'. IIRC VM doesn't respond to sysrq key sequence. It doesn't respond to anything actually but NMI. I tried to do inject-nmi. VMs kernel responded with timestamped message "Uhhuh. NMI received. Dazed and confused, but trying to continue". That timestamp never changes - its like time is frozen on VM. I'll try to find my notes from this gdb session. -- mg