WARNING - OLD ARCHIVES

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/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: FW: [Xen-devel] qemu-dm exit(1) for invalid option '-vncviewer' -- X

To: "Daniel P. Berrange" <berrange@xxxxxxxxxx>
Subject: Re: FW: [Xen-devel] qemu-dm exit(1) for invalid option '-vncviewer' -- Xen #18023
From: John Levon <levon@xxxxxxxxxxxxxxxxx>
Date: Fri, 11 Jul 2008 16:27:36 +0100
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx, Ian Jackson <Ian.Jackson@xxxxxxxxxxxxx>, Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
Delivery-date: Fri, 11 Jul 2008 08:28:55 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <20080711104642.GB15083@xxxxxxxxxx>
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/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <0E6B8CEB89DCFE40A52F80EB8F97D99D02B388E3@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> <C49CD85B.1AD86%keir.fraser@xxxxxxxxxxxxx> <18551.14417.318546.860543@xxxxxxxxxxxxxxxxxxxxxxxx> <20080711104642.GB15083@xxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.9i
On Fri, Jul 11, 2008 at 11:46:42AM +0100, Daniel P. Berrange wrote:

> > This option works (worked) by passing the caller's display and
> > xauthority through xm and xend to qemu.  qemu then connects to it
> > later.  This is a very remarkable way of going about things.  Its
> > security properties are problematic from several points of view.
> > 
> > I had assumed that because it was so strange no-one would be using it,
> > so I deliberately dropped that change.  Evidently I was wrong.  If
> > this is a feature that is seriously used then I could reinstate it but
> > I think it should come with a health warning.

What might be useful is allowing "wait" mode for VNC like you can with
telnet serial console. I'm suspecting that's the only reason you would
ever want -vncviewer (to catch the BIOS screen).

> I think it should be killed - its easy todo it in the 'xm' client code,
> after all xm already knows how to spawn 'xm console' for text mode 
> display - this is just same use case in graphical mode.

Heck, then can we kill SDL, which does exactly the same thing, but in
xend?

I must admit when I discovered this, I blanched.

john

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel