28 lines
1.0 KiB
Markdown
28 lines
1.0 KiB
Markdown
|
---
|
||
|
|
page_title: "vagrant global-status - Command-Line Interface"
|
||
|
|
sidebar_current: "cli-globalstatus"
|
||
|
|
---
|
||
|
|
|
||
|
|
# Global Status
|
||
|
|
|
||
|
|
**Command: `vagrant global-status`**
|
||
|
|
|
||
|
|
This command will tell you the state of all active Vagrant environments
|
||
|
|
on the system for the currently logged in user.
|
||
|
|
|
||
|
|
This command doesn't actively verify the state of the machines listed,
|
||
|
|
and is instead based on a cache. Because of this, it is possible to see
|
||
|
|
stale results (machines say they're running but they're not). For example,
|
||
|
|
if you restart your computer, Vagrant wouldn't know. To prune the invalid
|
||
|
|
entries, run global status with the `--prune` flag.
|
||
|
|
|
||
|
|
The IDs in the output that look like `a1b2c3` can be used to control
|
||
|
|
the Vagrant machine from anywhere on the system. Any Vagrant command
|
||
|
|
that takes a target machine (such as `up`, `halt`, `destroy`) can be
|
||
|
|
used with this ID to control it. For example: `vagrant destroy a1b2c3`.
|
||
|
|
|
||
|
|
## Options
|
||
|
|
|
||
|
|
* `--prune` - Prunes invalid entries from the list. This is much more time
|
||
|
|
consuming than simply listing the entries.
|