From: Paolo Bonzini <pbonzini@redhat.com>
To: Kevin Wolf <kwolf@redhat.com>
Cc: famz@redhat.com, qemu-devel@nongnu.org, stefanha@redhat.com
Subject: Re: [Qemu-devel] [PATCH] block: asynchronously stop the VM on I/O errors
Date: Wed, 04 Jun 2014 11:04:24 +0200 [thread overview]
Message-ID: <538EE118.7060407@redhat.com> (raw)
In-Reply-To: <20140604082831.GB3851@noname.str.redhat.com>
Il 04/06/2014 10:28, Kevin Wolf ha scritto:
>> Breaking this invariant means that you have a very small window where
>> {'execute':'cont'} would actually not restart the VM. I think this
>> should be fixed by dropping the request in vm_start, like this:
>> [...]
>
> Sounds like an option. Do we need to send a QEVENT_STOP/QEVENT_RESUME
> pair? If we don't, the client will still notice a difference to a real
> stop and resume.
Yes, better do that.
>> Also, I think that bdrv_emit_qmp_error_event is placed wrong.
>> It should be called only after setting the iostatus, otherwise
>> there is a small window where the iostatus is "no error" but
>> the event has been generated already.
>
> Yes, I agree.
>
> The documentation for this event actually answers my above question:
>
> Note: If action is "stop", a STOP event will eventually follow the
> BLOCK_IO_ERROR event.
>
> Perhaps we should also change the documentation of the "stop" value to
> clarify that the VM may not actually be stopped yet. It currently reads
> like this:
>
> "stop": error caused VM to be stopped
Yes.
Paolo
prev parent reply other threads:[~2014-06-04 9:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-03 14:16 [Qemu-devel] [PATCH] block: asynchronously stop the VM on I/O errors Paolo Bonzini
2014-06-03 14:37 ` Kevin Wolf
2014-06-03 15:51 ` Paolo Bonzini
2014-06-04 8:28 ` Kevin Wolf
2014-06-04 9:04 ` Paolo Bonzini [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=538EE118.7060407@redhat.com \
--to=pbonzini@redhat.com \
--cc=famz@redhat.com \
--cc=kwolf@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@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).