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-users

Re: [Xen-users] static vnc port

On Monday 10 March 2008 10:55:41 jim burns wrote:
> On Sunday 09 March 2008 10:19:22 pm Jonathan Ervine wrote:
> > My best guess here would be that you've got both vncunused and
> > vncdisplay set. The vncunused parameter normally binds the VNC
> > display to 5900+N where N is the number specified by vncunused (in
> > other words 5901 in your case). I'd check to see if VNC is
> > listening on port 5901. I'm not sure if having both parameters
> > breaks both or if the second one is simply ignored, however I think
> > you should remove the vncunused setting.
>
> Actually, vncunused=1 says use the first unused vnc port. vncunused=0
> shuts off that behavior. From SuSE's /etc/xen/examples/xmexample1:
>
> # The backend listens on 127.0.0.1 port 5900+N by default, where N is
> # the domain ID.  You can override both address and N:
> #
> # vfb = [ 'type=vnc,vnclisten=127.0.0.1,vncdisplay=1' ]
> #
> # Or you can bind the first unused port above 5900:
> #
> # vfb = [ 'type=vnc,vnclisten=0.0.0.0,vnunused=1' ]

Yes, I saw that. However the OP has both vncunused and also vncdisplay 
parameters and he wants to hard set a specific port for his VM. Having 
both of these parameters set seems incorrect to me, and he should 
remove the vncunused parameter (as per the first vfb example in the 
xmexample1 file).

Jon

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

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