From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1O0IeB-0007WA-QA for qemu-devel@nongnu.org; Fri, 09 Apr 2010 14:09:39 -0400 Received: from [140.186.70.92] (port=35578 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1O0IeA-0007Uo-05 for qemu-devel@nongnu.org; Fri, 09 Apr 2010 14:09:39 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69) (envelope-from ) id 1O0Ie8-0007ki-4p for qemu-devel@nongnu.org; Fri, 09 Apr 2010 14:09:37 -0400 Received: from mx1.redhat.com ([209.132.183.28]:48652) by eggs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1O0Ie7-0007k8-TV for qemu-devel@nongnu.org; Fri, 09 Apr 2010 14:09:36 -0400 Date: Fri, 9 Apr 2010 15:09:09 -0300 From: Marcelo Tosatti Subject: Re: [Qemu-devel] Weird thing happen when the VM is stop! (0.12.3) Message-ID: <20100409180909.GA16476@amt.cnet> References: <20100409102051.532ce0e8@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline In-Reply-To: Content-Transfer-Encoding: quoted-printable List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Jun Koi Cc: pbonzini@redhat.com, qemu-devel@nongnu.org, Luiz Capitulino On Sat, Apr 10, 2010 at 01:12:27AM +0900, Jun Koi wrote: > On Fri, Apr 9, 2010 at 10:20 PM, Luiz Capitulino wrote: > > On Fri, 9 Apr 2010 18:32:21 +0900 > > Jun Koi wrote: > > > >> Hi, > >> > >> I found something very funny happening with 0.12.3: it seems the VM = is > >> still running even I already stopped it. > >> > >> Here is how I verified that: Boot any OS (I checked with Windows XP > >> and Ubuntu) with 0.12.3, and stop it any time after it booted up. Us= e > >> "stop" command on monitor interface. > >> > >> Now the VM stops. Then in the same monitor interface, run "info > >> registers" again and again. You can see that the value of EIP and > >> EFLAGS still change once in a while. This should not happen, becaues > >> the VM already stopped. > >> > >> I checked, and dont see this problem with 0.11.1. And this doesnt > >> happen with the latest code in the git tree, either. > >> > >> Any idea on why this happens??? > > > > =A0Can you try commit 55274a305 ? If it fixes the problem we need it > > in stable, if it doesn't you can try to find the fix by using git bis= ect. > > >=20 > This hint makes sense, but the point is that I tried with some commits > before that 55274a305, and didnt see the problem. Still I am not sure > the problem is already fixed before 55274a305, or I am just unlucky > enough not see the problem when testing. >=20 > After bisecting, I can say that the culprit is the below patch, from Ma= rcelo. >=20 > Now I am wondering if the above commit 55274a305 of Paolo Bonzini > fixed the bug, or other commit before that?? We should find the > correct fix, and port it to 0.12.4. Guess its c5f32c99. Can you confirm please?