From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([140.186.70.92]:45745) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1R8qie-00010N-0C for qemu-devel@nongnu.org; Wed, 28 Sep 2011 05:46:24 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1R8qid-0005sp-3J for qemu-devel@nongnu.org; Wed, 28 Sep 2011 05:46:23 -0400 Received: from e23smtp04.au.ibm.com ([202.81.31.146]:45067) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1R8qic-0005sc-Da for qemu-devel@nongnu.org; Wed, 28 Sep 2011 05:46:23 -0400 Received: from d23relay05.au.ibm.com (d23relay05.au.ibm.com [202.81.31.247]) by e23smtp04.au.ibm.com (8.14.4/8.13.1) with ESMTP id p8S9dQJQ032192 for ; Wed, 28 Sep 2011 19:39:26 +1000 Received: from d23av01.au.ibm.com (d23av01.au.ibm.com [9.190.234.96]) by d23relay05.au.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id p8S9i07u2375818 for ; Wed, 28 Sep 2011 19:44:02 +1000 Received: from d23av01.au.ibm.com (loopback [127.0.0.1]) by d23av01.au.ibm.com (8.14.4/8.13.1/NCO v10.0 AVout) with ESMTP id p8S9k4w3016902 for ; Wed, 28 Sep 2011 19:46:05 +1000 Message-ID: <4E82ECB7.6080701@vnet.linux.ibm.com> Date: Wed, 28 Sep 2011 17:45:27 +0800 From: hkran MIME-Version: 1.0 References: <1317069835-28815-1-git-send-email-lcapitulino@redhat.com> In-Reply-To: <1317069835-28815-1-git-send-email-lcapitulino@redhat.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [PATCH v3 0/6]: block: Add I/O status support List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Luiz Capitulino Cc: kwolf@redhat.com, zwu.kernel@gmail.com, armbru@redhat.com, qemu-devel@nongnu.org On 09/27/2011 04:43 AM, Luiz Capitulino wrote: > 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. > > changelog > --------- > > v3 > > o Introduce bdrv_iostatus_disable() > o Also reset the I/O status on bdrv_attach_dev() > o Fix bad assert() in bdrv_iostatus_enable() > o Improve documentation > > v2 > > o Rebase against latest master > o Renamed bdrv_iostatus_update() to bdrv_iostatus_set_err() > o Minor changelog clarifications > > block.c | 57 +++++++++++++++++++++++++++++++++++++++++++++++++++++++ > block.h | 10 +++++++++ > block_int.h | 1 + > hw/ide/core.c | 2 + > hw/scsi-disk.c | 2 + > hw/virtio-blk.c | 2 + > monitor.c | 6 +++++ > qmp-commands.hx | 6 +++++ > 8 files changed, 86 insertions(+), 0 deletions(-) > Hi, How to reproduce a scenario in which the VM is stopped due to the I/O error? I tried several times by copying data from one place to another place in guest OS and finally the system prompted me that there is no space is available, however it did not cause any I/O error and not stop the VM either.