[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-users] vncdisplay #


  • To: "jim burns" <jim_burn@xxxxxxxxxxxxx>
  • From: "Freddie Cash" <fjwcash@xxxxxxxxx>
  • Date: Fri, 11 Apr 2008 09:50:35 -0700
  • Cc: xen-users@xxxxxxxxxxxxxxxxxxx
  • Delivery-date: Fri, 11 Apr 2008 09:51:06 -0700
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=O3zjmqczohM5upfwIBxpP5TrUniKpbJ8rL/t0ksi6hDSXrbS/98PeGeHbxMpyf1sCLP6i3mXwsJfaxJvAL9XkY0G3+8hoIQESewz67p2MpnL7DZeszmghJQ7yqhKWSWweMD4B5IFFjgg52jSwalI24hneZTJFkJ/HVX5xVoh/PA=
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

On Thu, Apr 10, 2008 at 8:43 PM, jim burns <jim_burn@xxxxxxxxxxxxx> wrote:
> On Thursday April 10 2008 09:16:07 pm Joseph L. Casale wrote:
>  > How does this setting work? I was hoping to use it to make connections
>  > predictable. I have vncunused = 1 as well, but xen never starts the server
>  > on the expected port (dom-u id).
>
>  With vncunused=1, you get the first unused vnc port #. With:
>
>  vncunused=0
>  vncdisplay=1
>
>  you get the domid # (+ 5900)

You actually get vncdisplay+5900 on Xen 3.2.  All the docs mention you
are supposed to get the domID as the VNC display number, but it
doesn't actually work that way.  At least not on Debian or Ubuntu.

-- 
Freddie Cash
fjwcash@xxxxxxxxx

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


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.