From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([140.186.70.92]:38587) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RDJdU-0003mR-C3 for qemu-devel@nongnu.org; Mon, 10 Oct 2011 13:27:33 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1RDJdT-00007R-C1 for qemu-devel@nongnu.org; Mon, 10 Oct 2011 13:27:32 -0400 Received: from mx1.redhat.com ([209.132.183.28]:24962) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RDJdT-00007N-3H for qemu-devel@nongnu.org; Mon, 10 Oct 2011 13:27:31 -0400 Message-ID: <4E932BB8.30305@redhat.com> Date: Mon, 10 Oct 2011 19:30:32 +0200 From: Kevin Wolf 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-15 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: zwu.kernel@gmail.com, armbru@redhat.com, qemu-devel@nongnu.org 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