This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


Re: [Xen-devel] [PATCH] Update new qemu-dm to spawn vncviewer

To: "Donald D. Dugger" <donald.d.dugger@xxxxxxxxx>
Subject: Re: [Xen-devel] [PATCH] Update new qemu-dm to spawn vncviewer
From: "Christian Limpach" <christian.limpach@xxxxxxxxx>
Date: Fri, 14 Jul 2006 19:03:46 +0100
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Fri, 14 Jul 2006 11:04:09 -0700
Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=oUfC7wtTGaqiz+96Or29if0KX1WfVemAwNp/oSXm4f5BizS4YrM11kABMzqCCts+tHWsChgLaTGFmxfMpkcwgUSf/3FAjBCAWClOWC5WJozhssr3XuvxcXtPqYSGirkMRjAFnpbmNpxlzVyxyO2W2Jn3UC2EMbiR5e86x7mPpSc=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <20060713040439.GA4099@xxxxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <20060713040439.GA4099@xxxxxxxxxxxxxxxxxxxx>
Reply-to: Christian.Limpach@xxxxxxxxxxxx
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
On 7/13/06, Donald D. Dugger <donald.d.dugger@xxxxxxxxx> wrote:
This patch does 3 things to the new device model, qemu-dm:

1)  Add `vncviewer' as an option to `qemu-dm' to spawn a `vncviewer' process.

2)  Have the `vncviewer' config parameter translate to the `vncviewer' flag to

3)  Add a new config parameter, `vncconnect', that spawns a `vncviewer'
process that looks for a reverse connection (the way the `vncviewer'
config option currently works)

Signed-off-by: Don Dugger <donald.d.dugger@xxxxxxxxx>

Thanks, I've checked this in with the following changes:
- support xvncviewer, xvnc4viewer and xtightvncviewer (all support
:DISPLAY, only two support :PORTNO, only one supports -log)
- use vncconsole config option instead of vncviewer option, leaving
the existing vncviewer option as is
- don't abuse the command line to pass the option to xend but pass it
along all other options
- don't add vnc specific code to qemu's vl.c but put it in vnc.c instead
- don't handle/pass vncviewer config option for hvm guests any longer
in/to xend -- it should be handled inside the guest

We'll want to make the vncconsole option also work with the
framebuffer for PV guests.  It then makes sense to have both in that
case -- vncviewer gets you a vncviewer to a vnc server running in the
guest, vncconsole gets you a vncviewer to the vnc server rendering the
guest's framebuffer.


Xen-devel mailing list

<Prev in Thread] Current Thread [Next in Thread>