andrew clarke wrote:
On Sun 2012-11-18 08:50:34 UTC-0500, Fbsd8 (fb...@a1poweruser.com) wrote:

By design virtualbox requires a desktop on the host to use the
virtualbox built in config screens and the only way to access a
configured and installed guest VM is from a remote PC with a desktop.

No, you can create and configure VirtualBox VMs using the command-line
VBoxManage. I do this over SSH. See the VirtualBox manual (PDF).


You did not pay close attention to what was written. What was written is stands as true. The key works are "virtualbox built in config screens".

Using ssh from remote pc only works if ssh is run from a desktop. IE: you can not start ssh from a freebsd host command line to connect to a remote VB to create Virtual machines.

Incidentally it's possible to use RDP (Remote Desktop Protocol) to
connect and control any VirtualBox guest - including OSes that don't
natively support RDP connections - provided VRDP is enabled for that
guest VM. I do this running when VirtualBox on a Linux host, and can't
confirm it works for FreeBSD hosts, but assume it does.

AH now it gets interesting. RDP only talks to a fully configured virtual machine, not to the virtualbox built in config screens. So on a freebsd host without a desktop the vbheadless commands have to be used to create virtual machines.

My final goal was to create virtual machines using the vb headless commands, which worked. But then I wanted to run rpd from a second host session [F2] and connect to the newly created VM which was not possible because the rpd program is not contained in the virtualbox-additions port and when installing the virtualbox-additions port had to use the force flag.

So how can I run rpd on the freebsd host running the virtualbox server system so I can access the configured vm? I this configuration even possible?

_______________________________________________
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Reply via email to