Virtualbox provider should be able to use `vboxmanage guestcontrol` as a communicator #1

New issue

Open

opened 2019-01-24 23:27:32 +00:00 by karthanistyr · 0 comments

karthanistyr commented

2019-01-24 23:27:32 +00:00

Owner

In order to support static IP nat network interfaces as a primary interface (no NAT primary adapter), vagrant should be able to apply network interface configuration on the guest without an operational network stack, which forbids using ssh (which is the current, expected behaviour).

Virtualbox's management tool vboxmanage has a guestcontrol command which allows passing commands to a user's shell, as well a uploading and downloading files, and this roughly describes a "vagrant communicator" responsibilities.

Therefore, there should be a communicator, available to machines backed by the Virtualbox provider, implemented to use vboxmanage guestcontrol...-type commands to execute scripts and pass configuration to guests.

In order to support static IP *nat network* interfaces as a primary interface (no NAT primary adapter), vagrant should be able to apply network interface configuration on the guest without an operational network stack, which forbids using ssh (which is the current, expected behaviour). Virtualbox's management tool `vboxmanage` has a `guestcontrol` command which allows passing commands to a user's shell, as well a uploading and downloading files, and this roughly describes a "vagrant communicator" responsibilities. Therefore, there should be a communicator, available to machines backed by the Virtualbox provider, implemented to use `vboxmanage guestcontrol...`-type commands to execute scripts and pass configuration to guests.