bixu
commented
9 years ago Confirming this, if I'm already running a Vagrant-controlled zone in VM "A", then when I vagrant up VM "B", the plugin sees the zone in VM "A" and assumes that the zone has been provisioned:
monolith:smartos_hacking blake$ vagrant global-status
id name provider state directory
-------------------------------------------------------------------------
da88659 default virtualbox poweroff /Users/blake/vagrant-smartos
8d9aca0 default virtualbox running /Users/blake/smartos
a8ef6d6 default virtualbox running /Users/blake/smartos_hacking
The above shows information about all known Vagrant environments
on this machine. This data is cached and may not be completely
up-to-date. To interact with any of the machines, you can go to
that directory and run Vagrant, or you can use the ID directly
with Vagrant commands from any directory. For example:
"vagrant destroy 1a2b3c4d"
monolith:smartos_hacking blake$ vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Checking if box 'livinginthepast/smartos-base64' is up to date...
==> default: Clearing any previously set forwarded ports...
==> default: Fixed port collision for 22 => 2222. Now on port 2200.
==> default: Clearing any previously set network interfaces...
==> default: Preparing network interfaces based on configuration...
default: Adapter 1: nat
==> default: Configuring a port forward to talk to the Global Zone
==> default: Forwarding ports...
default: 22 => 2200 (adapter 1)
default: 2222 => 22022 (adapter 1)
==> default: Remapping platform ISO
==> default: SmartOS platform image 20140919T024804Z exists
==> default: Running 'pre-boot' VM customizations...
==> default: Booting VM...
==> default: Waiting for machine to boot. This may take a few minutes...
default: SSH address: 127.0.0.1:2200
default: SSH username: vagrant
default: SSH auth method: private key
default: Warning: Connection timeout. Retrying...
default: Warning: Connection timeout. Retrying...
default: Warning: Connection timeout. Retrying...
default: Warning: Remote connection disconnect. Retrying...
default: Warning: Remote connection disconnect. Retrying...
==> default: Machine booted and ready!
==> default: Installing vnic in global zone
==> default: Installing ZoneGate
==> default: Checking if machine supports zones: yes
==> default: Checking for zone image d34c301e-10c3-11e4-9b79-5f67ca448df0: installed
==> default: Zone base64 exists
==> default: Updating...
==> default: Enabling ZoneGate
==> default: Installing vnic in global zone
==> default: Checking for guest additions in VM...
default: No guest additions were detected on the base box for this VM! Guest
default: additions are required for forwarded ports, shared folders, host only
default: networking, and more. If SSH fails on this machine, please install
default: the guest additions and repackage the box to continue.
default:
default: This is not an error message; everything may continue to work properly,
default: in which case you may ignore this message.
==> default: Machine already provisioned. Run `vagrant provision` or use the `--provision`
==> default: to force provisioning. Provisioners marked to run always will still run.
monolith:smartos_hacking blake$ vagrant ssh
Last login: Wed Oct 8 14:43:35 2014 from 10.0.2.2
- SmartOS Live Image v0.147+ build: 20140919T024804Z
vagrant@08-00-27-ac-b1-65:~$ sudo vmadm list
UUID TYPE RAM STATE ALIAS
sax
Right now the port forward set up for the global zone is hard-coded to 22022. It is configurable in the Vagrantfile, but if it could be run through the port conflict detection in Vagrant hopefully it could be rewritten on the fly to something non-conflicting when multiple VMs are running at the same time.
The internals that use the port forward should all already grab the port dynamically.