adb-atomic-developer-bundle
adb-atomic-developer-bundle copied to clipboard
projectatomic
vagrant suspend sometimes fails (Windows 7)
Test which do repeatedly vagrant suspend/resume sometimes fail (approximatelly in 30% of runs), virtual machine ends in "abort" state. I can see this on Windows7. Fedora21: no problem on libvirt nor in virtualbox Mac OS X: not tested
output:
vagrant suspend
==> default: Saving VM state and suspending execution...
There was an error while executing VBoxManage, a CLI used by Vagrant
for controlling VirtualBox. The command and stderr is shown below.
Command: ["controlvm", "ed7b0b69-7e36-43d3-a361-b6209cd71d1d", "savestate"]
Stderr: 0%...10%...20%...30%...40%...50%...60%...70%...80%...90%... Progress state: RPC_S_CALL_FAILED 0x800706BE VBoxManage.exe: error: Failed to save machine state VBoxManage.exe: error: The object is not ready VBoxManage.exe: error: Details: code E_ACCESSDENIED (0x80070005), component SessionMachine, interface IMachine VBoxManage.exe: error: Context: "enum RTEXITCODE __cdecl handleControlVM(struct HandlerArg *)" at line 276 of file VBoxManageControlVM.cpp
vagrant resume
==> default: Waiting for machine to boot. This may take a few minutes... The guest machine entered an invalid state while waiting for it to boot. Valid states are 'restoring, running'. The machine is in the 'aborted' state. Please verify everything is configured properly and try again.
If the provider you're using has a GUI that comes with it,
it is often helpful to open that and watch the machine, since the
GUI often has more helpful error messages than Vagrant can retrieve.
For example, if you're using VirtualBox, run vagrant up while the
VirtualBox GUI is open.
The primary issue for this error is that the provider you're using is not properly configured. This is very rarely a Vagrant issue.
Sorry for delay, I had to prepare test environment with Windows 10 first. Now I have results with latest version of box (13) (if It depend on other software version, I can provide of course. Windows 10: no problem Windows 7: still happened, this time 2 fails from 15 I should have fresh results from linux system today, but this problem was not on linux before (mac not tested yet)
No problem on linux platform so far, so it's probably only reproducible on windows 7 (win 8/8.1 not tested). Definitely not a blocker, user would just lost unsaved work and has to do "vagrant up".
I would rather keep it open, since it's still reproducible and probably lot of developers use windows 7