From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1MNtL7-0008Ki-N6
	for qemu-devel@nongnu.org; Mon, 06 Jul 2009 14:54:57 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1MNtL2-0008Ip-J3
	for qemu-devel@nongnu.org; Mon, 06 Jul 2009 14:54:56 -0400
Received: from [199.232.76.173] (port=41917 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1MNtL2-0008Ig-CX
	for qemu-devel@nongnu.org; Mon, 06 Jul 2009 14:54:52 -0400
Received: from verein.lst.de ([213.95.11.210]:56031)
	by monty-python.gnu.org with esmtps
	(TLS-1.0:DHE_RSA_3DES_EDE_CBC_SHA1:24) (Exim 4.60)
	(envelope-from <hch@lst.de>) id 1MNtL0-0007dJ-Sp
	for qemu-devel@nongnu.org; Mon, 06 Jul 2009 14:54:52 -0400
Date: Mon, 6 Jul 2009 20:54:48 +0200
From: Christoph Hellwig <hch@lst.de>
Subject: Re: [Qemu-devel] [PATCH] qemu-iotests: Test L1 table growth
Message-ID: <20090706185448.GA6800@lst.de>
References: <1246888767-29072-1-git-send-email-kwolf@redhat.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <1246888767-29072-1-git-send-email-kwolf@redhat.com>
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Kevin Wolf <kwolf@redhat.com>
Cc: hch@lst.de, qemu-devel@nongnu.org

On Mon, Jul 06, 2009 at 03:59:27PM +0200, Kevin Wolf wrote:
> Signed-off-by: Kevin Wolf <kwolf@redhat.com>
> ---
> I don't really like about this one that it contains the monitor echo of our
> commands from stdin. It contains lots of control characters and who knows if
> the monitor won't change to do a more reasonable echo some time... However, we
> need the monitor output to see if an error occured during savevm or loadvm. So,
> I'm open for suggestions, but in case nobody has a better option, let's do it
> this way.

It does fail for me because I get different escape sequences..

I suspect we'll just have to wait until Luiz' gets a proper
machine-readable protocol for the monitor in and then use that one.  And
pray that we'll stick with the text protocol instead of some rpc
crap..