All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marcelo Tosatti <mtosatti@redhat.com>
To: Jun Koi <junkoi2004@gmail.com>
Cc: pbonzini@redhat.com, qemu-devel@nongnu.org,
	Luiz Capitulino <lcapitulino@redhat.com>
Subject: Re: [Qemu-devel] Weird thing happen when the VM is stop! (0.12.3)
Date: Fri, 9 Apr 2010 15:09:09 -0300	[thread overview]
Message-ID: <20100409180909.GA16476@amt.cnet> (raw)
In-Reply-To: <r2sfdaac4d51004090912r53449ccj569223bdbee22556@mail.gmail.com>

On Sat, Apr 10, 2010 at 01:12:27AM +0900, Jun Koi wrote:
> On Fri, Apr 9, 2010 at 10:20 PM, Luiz Capitulino <lcapitulino@redhat.com> wrote:
> > On Fri, 9 Apr 2010 18:32:21 +0900
> > Jun Koi <junkoi2004@gmail.com> 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. Use
> >> "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???
> >
> >  Can 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 bisect.
> >
> 
> 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.
> 
> After bisecting, I can say that the culprit is the below patch, from Marcelo.
> 
> 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?

  reply	other threads:[~2010-04-09 18:09 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-09  9:32 [Qemu-devel] Weird thing happen when the VM is stop! (0.12.3) Jun Koi
2010-04-09 13:20 ` Luiz Capitulino
2010-04-09 16:12   ` Jun Koi
2010-04-09 18:09     ` Marcelo Tosatti [this message]
2010-04-12  6:22       ` Jun Koi

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20100409180909.GA16476@amt.cnet \
    --to=mtosatti@redhat.com \
    --cc=junkoi2004@gmail.com \
    --cc=lcapitulino@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.