From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from [140.186.70.92] (port=41853 helo=eggs.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1PITWz-0008MB-SG
	for qemu-devel@nongnu.org; Tue, 16 Nov 2010 16:57:38 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <stefanha@gmail.com>) id 1PITWy-0004HD-Qh
	for qemu-devel@nongnu.org; Tue, 16 Nov 2010 16:57:37 -0500
Received: from mail-wy0-f173.google.com ([74.125.82.173]:48521)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <stefanha@gmail.com>) id 1PITWy-0004H0-Jm
	for qemu-devel@nongnu.org; Tue, 16 Nov 2010 16:57:36 -0500
Received: by wyj26 with SMTP id 26so1268911wyj.4
	for <qemu-devel@nongnu.org>; Tue, 16 Nov 2010 13:57:35 -0800 (PST)
MIME-Version: 1.0
In-Reply-To: <1289870175-14880-1-git-send-email-mdroth@linux.vnet.ibm.com>
References: <1289870175-14880-1-git-send-email-mdroth@linux.vnet.ibm.com>
Date: Tue, 16 Nov 2010 21:57:35 +0000
Message-ID: <AANLkTims5Laer_rrWO5Purm=kvYHRJCRKnEGpEah9FKE@mail.gmail.com>
Subject: Re: [Qemu-devel] [RFC][PATCH v3 00/21] virtproxy: host/guest
	communication layer
From: Stefan Hajnoczi <stefanha@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
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.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: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Michael Roth <mdroth@linux.vnet.ibm.com>
Cc: agl@linux.vnet.ibm.com, abeekhof@redhat.com, qemu-devel@nongnu.org, aliguori@linux.vnet.ibm.com, ryanh@us.ibm.com, amit.shah@redhat.com

On Tue, Nov 16, 2010 at 1:15 AM, Michael Roth <mdroth@linux.vnet.ibm.com> w=
rote:
Some basic questions from someone who has never used virtio-serial:

> EXAMPLE USAGE:
>
> note: oforward/iforward chardev options have not yet been converted over =
from original standalone host daemon implementation so this won't work till=
 then. The examples however have been updated for reference.
>
> =A0- Proxy http and ssh connections from a host to a guest over a virtio-=
serial connection:
> =A0 =A0# start guest with virtio-serial. for example (RHEL6s13):
> =A0 =A0qemu \
> =A0 =A0-device virtio-serial \
> =A0 =A0-chardev virtproxy,id=3Dtest0, \
> =A0 =A0 =A0 =A0 =A0 =A0 oforward=3Dhttp:127.0.0.1:9080,oforward=3Dssh:127=
.0.0.1:22 \
> =A0 =A0-device virtconsole,chardev=3Dtest0,name=3Dtest0 \
> =A0 =A0...

Is virtconsole just a way of throwing something on the virtio-serial
bus?  A quick peek at hw/virtio-console.c suggests "virtserialport"
could also be used (and would be more intuitive because we don't want
a console, just a serial port)?

> =A0 =A0# in the guest:
> =A0 =A0./qemu-vp -c virtserial-open:/dev/virtio-ports/test2:- -i http:127=
.0.0.1:80 \
> =A0 =A0 =A0 =A0 =A0 =A0 =A0-i ssh:127.0.0.1:22

name=3Dtest0 above.  Is this a typo or where does test2 come from?

What does "virtserial-open" mean?  Why not
virtio-serial:/dev/virtio-ports/test2 to match the "-device
virtio-serial" above?  Virtio has a naming issue, every implementation
names things slightly differently :).

> =A0 =A0# from host, access guest http server
> =A0 =A0wget http://locahost:9080
> =A0 =A0# from host, access guest ssh server
> =A0 =A0ssh localhost -p 9022

I don't see 9022 above, should it have been "oforward=3Dssh:127.0.0.1:9022"=
?

Stefan