-
Notifications
You must be signed in to change notification settings - Fork 51
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Stuck on refresh #49
Comments
same |
https://github.com/deveres/vagrant-manager-windows/releases or |
I downloaded yesterday from the website. |
@deveres didn't work. Now I upgraded to Vagrant 2.0.3 and installed your 1.0.0.7. Doesn't even find any machines. |
@mathewrapid Just went from Vagrant 2.0.1 to 2.0.3, using Vagrant Manager 1.0.0.7, and have run two machines. It works fine. If you started the machines elsewhere from Vagrant Manager, you'll need to use Refresh to allow it to detect that they're running, Not sure what you believe you're seeing, but Refresh might well be the cue needed. |
@narration-sd then it must be my computer that is acting up. This started when I updated to Vagrant 2.x and the manager stopped working. Reverted back to Vagrant 1.9.6 and hoped for the best. Under this switcharoo, something went awry. Now no version of the manager shows any of my virtual machines. |
Does not work for me either. First tried
Then installed a chocolatey package:
Still the same, always refreshing. Although, worth mentioning, macOS version seems to have the same issue lanayotech/vagrant-manager#167 |
Works fine with Vagrant 2.0.1 and Vagrant Manager 1.0.0.7 from deveres. After updating to Vagrant 2.1.1 it still seems to work fine. |
New update for vagrant 2.2.3 and virtualbox 6.0.2 https://github.com/deveres/vagrant-manager-windows/releases |
@deveres Thanks, looks good. |
PR #48 has been merged and this is working as of 1.0.2.2 |
Tested with vagrant 1.9.6 and 1.9.8. Vagrant Manager 1.0.0.6 run with admin privileges.
Vagrant manager is stuck on refresh. It spawns four ruby and vagrant processes. If the processes are then forcefully stopped, then Vagrant Manager will list all my vm's, but their state is not shown. Some machines can be started but not halt command is listed etc.
The text was updated successfully, but these errors were encountered: