All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kevin Wolf <kwolf@redhat.com>
To: Luiz Capitulino <lcapitulino@redhat.com>
Cc: zwu.kernel@gmail.com, armbru@redhat.com, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v3 0/6]: block: Add I/O status support
Date: Mon, 10 Oct 2011 19:30:32 +0200	[thread overview]
Message-ID: <4E932BB8.30305@redhat.com> (raw)
In-Reply-To: <1317069835-28815-1-git-send-email-lcapitulino@redhat.com>

Am 26.09.2011 22:43, schrieb Luiz Capitulino:
> This series adds support to the block layer to keep track of devices'
> I/O status. That information is also made available in QMP and HMP.
> 
> The goal here is to allow management applications that miss the
> BLOCK_IO_ERROR event to able to query the VM to determine if any device has
> caused the VM to stop and which device caused it.
> 
> Here's an HMP example:
> 
>   (qemu) info status 
>   VM status: paused (io-error)
>   (qemu) info block
>   ide0-hd0: removable=0 io-status=ok file=disks/test2.img ro=0 drv=qcow2 encrypted=0
>   ide0-hd1: removable=0 io-status=nospace file=/dev/vg_doriath/kvmtest ro=0 drv=qcow2 encrypted=0
>   ide1-cd0: removable=1 locked=0 io-status=ok [not inserted]
>   floppy0: removable=1 locked=0 [not inserted]
>   sd0: removable=1 locked=0 [not inserted]
> 
> The session above shows that the VM is stopped due to an I/O error. By using
> the info block command it's possible to determine that the 'ide0-hd1' device
> caused the error, which turns out to be due to no space.

Thanks, applied all to the block branch.

Kevin

  parent reply	other threads:[~2011-10-10 17:27 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-26 20:43 [Qemu-devel] [PATCH v3 0/6]: block: Add I/O status support Luiz Capitulino
2011-09-26 20:43 ` [Qemu-devel] [PATCH 1/6] block: Keep track of devices' I/O status Luiz Capitulino
2011-09-26 20:43 ` [Qemu-devel] [PATCH 2/6] virtio: Support " Luiz Capitulino
2011-09-26 20:43 ` [Qemu-devel] [PATCH 3/6] ide: " Luiz Capitulino
2011-09-26 20:43 ` [Qemu-devel] [PATCH 4/6] scsi: " Luiz Capitulino
2011-09-26 20:43 ` [Qemu-devel] [PATCH 5/6] QMP: query-status: Add 'io-status' key Luiz Capitulino
2011-09-26 20:43 ` [Qemu-devel] [PATCH 6/6] HMP: Print 'io-status' information Luiz Capitulino
2011-09-27 18:40 ` [Qemu-devel] [PATCH v3 0/6]: block: Add I/O status support Markus Armbruster
2011-09-28  9:45 ` hkran
2011-09-28 20:00   ` Luiz Capitulino
2011-09-29  7:20 ` Mark Wu
2011-10-10 17:30 ` Kevin Wolf [this message]
2011-10-10 20:25   ` Luiz Capitulino
2011-10-11  7:49     ` Kevin Wolf

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=4E932BB8.30305@redhat.com \
    --to=kwolf@redhat.com \
    --cc=armbru@redhat.com \
    --cc=lcapitulino@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=zwu.kernel@gmail.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 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.