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
..
docker	Add test for syncing folders with docker provider	2018-10-17 14:14:27 -07:00
hyperv	Merge pull request #10410 from chrisroberts/f-hyperv-net-typo	2018-11-13 15:43:03 -08:00
virtualbox	Update behavior of `snapshot restore` and `snapshot pop`	2018-12-07 16:17:44 -08:00