From: John Snow <jsnow@redhat.com>
To: "quint >> juan quin >> Juan Jose Quintela Carreira"
<quintela@redhat.com>
Cc: "Dr. David Alan Gilbert" <dgilbert@redhat.com>,
qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] QMP events and the migration of halted machines
Date: Tue, 24 Feb 2015 11:39:28 -0500 [thread overview]
Message-ID: <54ECA940.9050405@redhat.com> (raw)
In-Reply-To: <54ECA75E.30105@redhat.com>
On 02/24/2015 11:31 AM, John Snow wrote:
> In writing migration tests for qtest and ahci-test, I ran into an
> interesting pattern and wanted to know if this was expected:
>
> 1) Using blkdebug, I inject an error to execute once for the first flush
> request.
> 2) Executing the command, I get a STOP event.
> 3) I migrate the VM, and poll the source until it reports that it is
> completed.
>
> So far, so good.
>
> 4) I receive a RESUME event from the destination, even though the
> machine wasn't started.
Small correction: BLOCK_IO_ERROR and STOP occur here.
> 5) Naively, my script assumes the machine is stopped and sends
> {"execute": "cont"} to resume execution from the failed flush command.
> 6) I then see BLOCK_IO_ERROR, STOP, and then RESUME events in order.
...and not here.
> 7) The command appears to then execute and finish successfully.
>
> Is this the expected flow? I perhaps naively assumed that the machine
> would stay stopped during migration and wait for me to resume it, and
> not what appears to happen, which is resume automatically and then stop.
>
> This flow seems *very* odd to me.
>
prev parent reply other threads:[~2015-02-24 16:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-24 16:31 [Qemu-devel] QMP events and the migration of halted machines John Snow
2015-02-24 16:39 ` John Snow [this message]
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=54ECA940.9050405@redhat.com \
--to=jsnow@redhat.com \
--cc=dgilbert@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).