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). Thanks! jlc _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
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) See /etc/xen/xmexample1 for more info (/etc/xen/examples/xmexample1 on SUSE). _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Thu, Apr 10, 2008 at 8:43 PM, jim burns <jim_burn@bellsouth.net> 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@gmail.com _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users