From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1Kuw7S-0006e2-O8
	for qemu-devel@nongnu.org; Tue, 28 Oct 2008 17:28:54 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1Kuw7R-0006by-6O
	for qemu-devel@nongnu.org; Tue, 28 Oct 2008 17:28:54 -0400
Received: from [199.232.76.173] (port=55627 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1Kuw7Q-0006bi-L2
	for qemu-devel@nongnu.org; Tue, 28 Oct 2008 17:28:52 -0400
Received: from mx2.redhat.com ([66.187.237.31]:41806)
	by monty-python.gnu.org with esmtp (Exim 4.60)
	(envelope-from <kraxel@redhat.com>) id 1Kuw7Q-0000MM-J1
	for qemu-devel@nongnu.org; Tue, 28 Oct 2008 17:28:52 -0400
Received: from int-mx2.corp.redhat.com (int-mx2.corp.redhat.com [172.16.27.26])
	by mx2.redhat.com (8.13.8/8.13.8) with ESMTP id m9SLSpDV007434
	for <qemu-devel@nongnu.org>; Tue, 28 Oct 2008 17:28:51 -0400
Message-ID: <49078410.4080600@redhat.com>
Date: Tue, 28 Oct 2008 22:28:48 +0100
From: Gerd Hoffmann <kraxel@redhat.com>
MIME-Version: 1.0
Subject: Re: [Qemu-devel] [PATCH 1/4] Implement "info chardev" command.
References: <1225198518-16529-1-git-send-email-kraxel@redhat.com>
	<1225198518-16529-2-git-send-email-kraxel@redhat.com>
	<20081028201952.GA30966@redhat.com>
In-Reply-To: <20081028201952.GA30966@redhat.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Reply-To: qemu-devel@nongnu.org
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: "Daniel P. Berrange" <berrange@redhat.com>
Cc: qemu-devel@nongnu.org

Daniel P. Berrange wrote:
> I don't know if the info is easily available, but for the 'vc' use case,
> it might be worth exposing the VC number, so a intelligent client app can
> read it, and be able to send 'ctl-alt-NN' in the VNC/SDL console to switch
> directly to the char device's VC.

The numbering can change after initialization due to graphic displays
being inserted at screen 0 and moveing any text screens away for that.
Which makes this non-trivial ...

IMHO a management app is better of *not* using vc, but something else
(pty/unix) which then can be linked to and displayed in a vte (gtk
terminal) widget.  One major advantage is that cut&paste works then,
also the qemu terminal emulation on the vc's isn't that great.

cheers,
  Gerd