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: Ian Jackson <Ian.Jackson@xxxxxxxxxxxxx>
Subject: Re: FW: [Xen-devel] qemu-dm exit(1) for invalid option '-vncviewer' -- Xen #18023
From: "Daniel P. Berrange" <berrange@xxxxxxxxxx>
Date: Fri, 11 Jul 2008 11:46:42 +0100
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx, Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
Delivery-date: Fri, 11 Jul 2008 03:47:05 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <18551.14417.318546.860543@xxxxxxxxxxxxxxxxxxxxxxxx>
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>
Reply-to: "Daniel P. Berrange" <berrange@xxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.4.1i
On Fri, Jul 11, 2008 at 11:39:13AM +0100, Ian Jackson wrote:
> Keir Fraser writes ("FW: [Xen-devel] qemu-dm exit(1) for invalid option 
> '-vncviewer' -- Xen #18023"):
> > Conversation: qemu-dm exit(1) for invalid option '-vncviewer' -- Xen #18023
> > Subject: [Xen-devel] qemu-dm exit(1) for invalid option '-vncviewer' -- Xen
> > #18023
> 
> 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.

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.

> A better place to implement this would be xm or some higher level
> tool, I think, but that wouldn't be sensible at this stage of the
> release cycle.

xm already seems to have some kind of vncviewer support, though its
running it in listen mode, rather than connect mode. 

Daniel
-- 
|: Red Hat, Engineering, London   -o-   http://people.redhat.com/berrange/ :|
|: http://libvirt.org  -o-  http://virt-manager.org  -o-  http://ovirt.org :|
|: http://autobuild.org       -o-         http://search.cpan.org/~danberr/ :|
|: GnuPG: 7D3B9505  -o-  F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 :|

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