Date: Tue, 02 Feb 2010 07:42:43 +0100 From: =?UTF-8?B?R3VzdGF1IFDDqXJleg==?= <gperez@entel.upc.edu> To: Hubert Tournier <hubert@frbsd.org> Cc: freebsd-emulation@freebsd.org Subject: Re: [PATCH] VirtualBox headless VNC support by LibVNCServer Message-ID: <4B67C963.2080705@entel.upc.edu> In-Reply-To: <27411112.post@talk.nabble.com> References: <18D68DBE18AC435984C5F66597A869D3@artemis> <B9B52D71C91E45B0BC0671061CA8C11C@artemis> <201001280000.16773.doconnor@gsoft.com.au> <F01C782F57DB41878576E58615F1DB53@artemis> <201001290913.36223.doconnor@gsoft.com.au> <27396532.post@talk.nabble.com> <4B66CF4E.1000709@entel.upc.edu> <27411112.post@talk.nabble.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> Daisuke's patch only applies to VBoxHeadless. There are no modifications in > VBoxManage (shouldn't be very complicated to put the VNC options there too, > though). > > You can launch several VM with embedded VNC servers provided that you use > different binding IP addresses or ports. You'll want to use the "-p, > -vncport, --vncport <port>" option to do that. The default port is 5900, but > you can use the following ones (supposedly up to 5906) or any port you want. > With the VNC client I mentioned, you can use a syntax like IP:port to > specify a non standard port. > > You are right, it was my mistake not to check VBoxHeadless. Then I did check it and it works flawlessly ! Best regards, Gustau > Best regards, > > Hubert > -- PGP KEY : http://www-entel.upc.edu/gus/gus.asc
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4B67C963.2080705>