Turning sandbox on kills env

[miketheman]

When running a new vagrant instance, executing sandbox on produces the following:

mike-mba:rubyapp michael$ vagrant sandbox on
[default] - Enabling sandbox
0%...
Progress state: NS_ERROR_FAILURE
VBoxManage: error: Failed to take snapshot. Error message: Failed to save the machine state to '/Users/michael/VirtualBox VMs/rubyapp_1312908797/Snapshots/2011-08-09T17-24-27-576715000Z.sav' (VERR_SSM_LIVE_GURU_MEDITATION)

mike-mba:rubyapp michael$ vagrant status
Current VM states:

default stuck

The VM is "stuck!" This is a very rare state which means that
VirtualBox is unable to recover the current state of the VM.
The only known solution to this problem is to restart your
machine, sorry.

Machine must be restarted, vagrant machine must be demolished (removed, deleted, etc).

[gregwork]

@miketheman - I've submitted a pull request to sort this; it's a VirtualBox bug. Details here.

[miketheman]

Thanks. I'll leave this open until it gets pulled in.
In other news, is there a way I can "gem install" from your branch?

[dcarley]

Hit this too. Sometimes snapshot on would complete successfully but the running VM would then become uncontactable. Would be good to see the new version pushed to rubygems.

In other news, is there a way I can "gem install" from your branch?

Gregwork's fix is now in master. You can build from a clone with gem build sahara.spec and then install the resulting gem.

[AlekSi]

Please release new version with this fix.

[ryuzee]

It's very old issue so that I would like to close the issue.