Date: Mon, 1 Feb 2010 12:47:51 -0800 (PST) From: Hubert Tournier <hubert@frbsd.org> To: freebsd-emulation@freebsd.org Subject: Re: [PATCH] VirtualBox headless VNC support by LibVNCServer Message-ID: <27411112.post@talk.nabble.com> In-Reply-To: <4B66CF4E.1000709@entel.upc.edu> 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>
next in thread | previous in thread | raw e-mail | index | archive | help
Hello, Gustau P=C3=A9rez wrote: >=20 >> I made an integrated copy of virtualbox-ose port with Daisuke's patches, >> called virtualbox-ose-vnc, adding libvncserver as a lib dependency. > I tried the modified port. If works fine to some extend. > [...] > But when starting a vm with VBoxManage, i can't see those startvm's > options. > [...] > So you can only have one vm with the vnc-server, can not have a second vm > with vnc > activated. >=20 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, bu= t 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. Best regards, Hubert --=20 View this message in context: http://old.nabble.com/-PATCH--VirtualBox-head= less-VNC-support-by-LibVNCServer-tp27288796p27411112.html Sent from the freebsd-emulation mailing list archive at Nabble.com.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?27411112.post>