Closed axos88 closed 7 years ago
Hi there. Please provide the --debug
output of a vagrant provision
that hangs so we can better attempt to determine the root cause. Thanks!
Will do, as soon as it occurs again
Hey there,
I am going to close this due to lack of response. If this is still occurring, please open a new issue and follow the provided issue template that appears when you click the "New Issue" button. This will help us in getting a reproduction and fix. Thanks! 😄
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.
When using vagrant with the chef-zero provisioner, during the provisioning of a windows guest, the provisioning hangs around 20-30% of the time during the "resolving dependencies" phase.
This never happens when vagrant is out of the picture, so I'm pretty confident something is up with Vagrant itself.
After the hang, the vagrant does not clean up (when stopped with CTRL+C), and it seems that there is a powershell process on the guest that hangs. Stopping that service (whenever windows lets us to) makes the vagrant clean up. I have a suspicion that something is up with filesharing, and that may cause the process to hang on I/O maybe?
We usually try working around the issue by reload --provision-ing, but this a pretty bad workaround.
Vagrant version
1.8.6
Host operating system
Windows & Linux
Guest operating system
Windows
Vagrantfile