From: Kevin Wolf <kwolf@redhat.com>
To: Jack Schwartz <jack.schwartz@oracle.com>
Cc: lcapitulino@redhat.com, armbru@redhat.com, qemu-devel@nongnu.org,
qemu-block@nongnu.org
Subject: Re: [Qemu-devel] query-block io-status display
Date: Wed, 6 Sep 2017 11:08:01 +0200 [thread overview]
Message-ID: <20170906090801.GC3753@dhcp-200-186.str.redhat.com> (raw)
In-Reply-To: <c749629a-3352-e2fc-812a-0a2489593c25@oracle.com>
[ Cc: qemu-block ]
Am 05.09.2017 um 06:59 hat Jack Schwartz geschrieben:
> Hi Luiz, Markus and everyone.
>
> I am working on a qemu enhancement to display io-status in each query-block
> command, not just those for devices which have werror and/or rerror set to
> stop on error.
>
> I'd like to verify the reasons behind the query-block command not reporting
> io-status if errors were reported to the guest or ignored. A clue may come
> from the original code review email[1] for when this code was implemented:
>
> "In case of multiple errors being triggered in sequence only the first
> one is stored. The I/O status is always reset to BDRV_IOS_OK when the
> 'cont' command is issued."
>
> From this I infer:
> - io-status is shown when qemu is stopped onerror so errors can be seen in
> cases where a guest does not handle them.
> - io-status is not shown when errors are already being handled by a guest
> - io-status is not shown when errors are ignored
>
> Is this correct? Are there other subtleties/reasons as well?
I think that covers it more or less, except maybe for one missing piece
of information: io-status reports the error while the guest is stopped
for an I/O error. It is reset (i.e. returns 'ok' again) as soon as the
VM is continued, so that you don't see an old error later while the VM
is running just fine at that moment.
This is also why there is no io-status when errors are ignored or
reported to the guest: The VM is immediately resumed (or actually not
even stopped), so it would either always return 'ok' or you wouldn't
know whether the error is old or new.
Kevin
prev parent reply other threads:[~2017-09-06 9:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-05 4:59 [Qemu-devel] query-block io-status display Jack Schwartz
2017-09-06 9:08 ` Kevin Wolf [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=20170906090801.GC3753@dhcp-200-186.str.redhat.com \
--to=kwolf@redhat.com \
--cc=armbru@redhat.com \
--cc=jack.schwartz@oracle.com \
--cc=lcapitulino@redhat.com \
--cc=qemu-block@nongnu.org \
--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 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).