On Tue, Mar 13, 2007 at 09:57:33PM +0200, Alexey Eremenko wrote: > > Well, this is on Kubuntu Edgy, though that's also a popular distro. Some > > other particulars: > > Video card is nvidia 7600 and X screen is very large -- 2560 x 1600 > > > > I'm surprised that vbox needs guest additions to handle the mouse and > > keyboard. It's very hard to use it without them. A number of other > > virtualizers I have seen have no problem with having their synthetic mouse > > and keyboard devices simply act idle when the window does not have focus, > > and provide mouse events when the mouse passes over the window and keyboard > > events when the window has focus. I realize that guest additions are > > needed for advanced video modes, and much easier for sound and shared > > drives. > > > > For my linux guests, I don't even want them to run X. Without that, > > at least for me, the guest additions did not appear to work in console mode. > > What I end up doing is creating an ssh tunnel into the VM. That would be > > another handy feature, in natted mode, to allow the specification of port > > forwarding. That would mean that, for example, I could forward a port on > > the host machine I specify to port 22 on the guest machine. Then I could > > fire up the guest machine as a virgin machine, no guest additions, and no > > keyboard interaction of any kind, and ssh to it, pretty much the way you > > connect to remote servers anyway. If one is testing from there you can > > copy in files, or create other forwarded ports via ssh if that's easier > > to test web serving, email etc. > > Well - actually VirtualBox does not supports port-forwarding natively > (unlike VMware and Qemu), but as a workaround, you can use > host-networking (as described in the VBox official docs, and my > VBOX-on-SUSE article) and then use iptables to forward ports. > > My article can be downloaded here: (NOTE: link will expire in 7 days) > http://download.yousendit.com/6E957103384F0318
Yeah, I read the docs on putting in bridging. It's not particularly hard but "zero root level work" is always better than even a modest amount of use of tap/tun and the rest. For guests that will just be servers, basic port forwarding (even if just ssh) is sufficient. In addition, with windows xp guests, should I ever get them working, though I have not yet tested it, I presume you want to be careful and not have them have a different MAC address, since windows xp activation/genuine advantage look at that to decide if you are running windows on a different machine. With a virtualizer, I am not violating my licence in that I am running the different copies on the same machine, so damned if I am going to have to get more licences just to do that. (Or does does WinXP tolerate machines that are identical except for MAC and minor parameters like memory size?) _______________________________________________ vbox-users mailing list [email protected] http://vbox.innotek.de/mailman/listinfo/vbox-users
