vagrant/plugins/providers/virtualbox
Chris Roberts c999e7c3d4 Update behavior of `snapshot restore` and `snapshot pop`
Both of these commands failed to default the options disabling
the provisioning from ignoring the sentinel file. This resulted
in different behavior than what was seen with the `up` and
`resume` commands which would only provision items with run set
to "always". This defaults the options to proper match the behavior
of `up` and `resume` to be consistent.

This also adds an extra `--no-start` flag to allow users to restore
a snapshot but not start the restored guest immediately.

Fixes #6752
2018-12-07 16:17:44 -08:00
..
action Adjust requirement on warnings for VirtualBox NIC 2018-12-06 15:40:31 -08:00
cap Add public_address cap for VirtualBox 2015-11-23 16:23:22 -05:00
driver Update VM import for VirtualBox 6 driver 2018-11-15 11:04:08 -08:00
model Use .key? instead of .has_key? 2015-01-05 18:29:01 -05:00
util Fix for #4608 2016-02-14 22:16:24 +11:00
action.rb Update behavior of `snapshot restore` and `snapshot pop` 2018-12-07 16:17:44 -08:00
cap.rb Return nil if the VM is not running when looking at forwarded ports 2015-11-24 16:33:09 -05:00
config.rb Update default_nic_type implementation within VirtualBox provider 2018-11-26 15:58:45 -08:00
plugin.rb Add vbox provider driver for 6.0 2018-11-06 16:50:17 -08:00
provider.rb Support running Vagrant within the Windows Subsystem for Linux 2017-05-08 10:21:01 -07:00
synced_folder.rb Ensure true or false for automount option 2018-10-23 09:00:55 -07:00