It is often the case that some VMs may be left in an "inconsistent" state after system restart: some running VMs may have been killed while this will be not tracked in vagrant's machine-index, which is used as the data source for the indicator. As a result, after restart, Vagrant AppIndicator shows VMs as running, while they are actually shut down.
As Vagrant's machine-index doesn't provide means to track these changes made outside of Vagrant, AppIndicator might query Vagrant to find out the states of all known machines. Querying just once att AppIndicator start will cover most of the desynchronization cases.
It is often the case that some VMs may be left in an "inconsistent" state after system restart: some running VMs may have been killed while this will be not tracked in vagrant's machine-index, which is used as the data source for the indicator. As a result, after restart, Vagrant AppIndicator shows VMs as running, while they are actually shut down.
As Vagrant's machine-index doesn't provide means to track these changes made outside of Vagrant, AppIndicator might query Vagrant to find out the states of all known machines. Querying just once att AppIndicator start will cover most of the desynchronization cases.