From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([2001:4830:134:3::10]:32799)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <famz@redhat.com>) id 1atPhe-0001An-FQ
	for qemu-devel@nongnu.org; Thu, 21 Apr 2016 21:16:15 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <famz@redhat.com>) id 1atPhd-0006ao-OF
	for qemu-devel@nongnu.org; Thu, 21 Apr 2016 21:16:14 -0400
Date: Fri, 22 Apr 2016 09:16:12 +0800
From: Fam Zheng <famz@redhat.com>
Message-ID: <20160422011612.GA12648@ad.usersys.redhat.com>
References: <nf5r01$klb$1@ger.gmane.org>
	<20160420021101.GC8684@ad-mail.usersys.redhat.com>
	<20160420115036.GG6517@noname.str.redhat.com>
	<nf848r$jfe$1@ger.gmane.org> <nfat48$9u1$1@ger.gmane.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <nfat48$9u1$1@ger.gmane.org>
Subject: Re: [Qemu-devel] I/O errors reported to guest for raw-image-file
 backed /dev/vda - but host sees no I/O errors
List-Id: <qemu-devel.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel/>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Lutz Vieweg <lvml@5t9.de>
Cc: qemu-devel@nongnu.org, qemu-block@nongnu.org

On Thu, 04/21 17:54, Lutz Vieweg wrote:
> Nevertheless, I think qemu could be somewhat more verbose, reporting
> when and why it stops emulation. Something like a message to the monitor
> or to standard out would be helpful to start with...

QEMU does report an error message to connected monitor if configured to. See
the werror= and rerror= options.

Fam