xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: ZhouPeng <zpengxen@gmail.com>
To: Ian Jackson <Ian.Jackson@eu.citrix.com>
Cc: "Xen-Devel (E-mail)" <xen-devel@lists.xensource.com>,
	Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Subject: Re: [PATCH] tools/libxl: prepare vnc options for dm_args in libxl__build_device_model_args_new
Date: Tue, 10 May 2011 19:32:44 +0800	[thread overview]
Message-ID: <BANLkTimk0JCKuviPyThUBXOeLS=1BQJn3A@mail.gmail.com> (raw)
In-Reply-To: <19911.56954.391942.786415@mariner.uk.xensource.com>

2011/5/9 Ian Jackson <Ian.Jackson@eu.citrix.com>:
> 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)

      reply	other threads:[~2011-05-10 11:32 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-20  6:30 [PATCH] tools/libxl: prepare vnc options for dm_args in libxl__build_device_model_args_new ZhouPeng
2011-04-20 12:10 ` Stefano Stabellini
2011-04-21  1:35   ` ZhouPeng
2011-05-09 12:30 ` Ian Jackson
2011-05-10 11:32   ` ZhouPeng [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='BANLkTimk0JCKuviPyThUBXOeLS=1BQJn3A@mail.gmail.com' \
    --to=zpengxen@gmail.com \
    --cc=Ian.Jackson@eu.citrix.com \
    --cc=stefano.stabellini@eu.citrix.com \
    --cc=xen-devel@lists.xensource.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).