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: [Xen-devel] [PATCH] tools/libxl: prepare vnc options for dm_args in

To: Ian Jackson <Ian.Jackson@xxxxxxxxxxxxx>
Subject: Re: [Xen-devel] [PATCH] tools/libxl: prepare vnc options for dm_args in libxl__build_device_model_args_new
From: ZhouPeng <zpengxen@xxxxxxxxx>
Date: Tue, 10 May 2011 19:32:44 +0800
Cc: "Xen-Devel \(E-mail\)" <xen-devel@xxxxxxxxxxxxxxxxxxx>, Stefano Stabellini <stefano.stabellini@xxxxxxxxxxxxx>
Delivery-date: Tue, 10 May 2011 04:33:34 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=JTYcJy22/k5d7XGouBV/++GGdK0eJR+YIrem4e6Y8oA=; b=NUtLfcT9Ehs6lUIbpkRQ6EsoaQi4zUq0Oql8GBbtao8JwxIzFM7M9qQT7VroUEy/fe fTYLH+6R04B/ggnCIP/Lr2mnEA6isWMpYtndJNdkTY33bVtctjPq5dRn61I62Ueth7Uy YLdlcjq2qN0sie+3iuT5RoWiAV9QU/ZiBQ2zU=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=C9VKPD8e+iGfXMPBdnWXNanw0ZLmd/7W7HvTOO+0f8SM/AxIrb2lcvttDrvG+JHxKm qVKuigUGWi/UNX1QH1J/iNZsLWhAa/oRGRcYMJwdTBEX0hP3O+jO0Ya87bRGhKA4L1Bn YlFzXgVigfAmpc65Bqnjd/BmISRebkRiZcpG4=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <19911.56954.391942.786415@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: <BANLkTimAoF-wuMrL4Zunjzy7QRV_xv_3ZA@xxxxxxxxxxxxxx> <19911.56954.391942.786415@xxxxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
2011/5/9 Ian Jackson <Ian.Jackson@xxxxxxxxxxxxx>:
> ZhouPeng writes ("[Xen-devel] [PATCH] tools/libxl: prepare vnc options for 
> dm_args in libxl__build_device_model_args_new"):
>> This pacth clean up vnc options preparing code for xen-upstream-qemu.
>> Add password option which allows you to use vncpasswd auth by xl.
>
> How does the new qemu actually find out what the password is ?  AFAICT
> from the current code, it is only written to xenstore.
Yes, it is only writen to xenstore for new qemu
> Does the new qemu read it from there like the old one ?
New qemu hasn't implemented it yet, but I have send a patch named
[xen-upstream-qemu: get vncpassword through xenstore, enable
VNC_AUTH_VNC] [http://patchwork.ozlabs.org/patch/92372/] to this
mail-list before which was cced to you.
That patch allows to read vncpasswd through xenstore in new qemu.

In the discussion, Stefano Stabellini suggest to use QMP to
communicate vncpasswd.

Thanks,
> Ian.
>



-- 
Zhou Peng
Operating System Technology Group
Institute of Software, the Chinese Academy of Sciences (ISCAS)

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

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