Skip to content
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

Add Content under Step 2 Vagrant Tutorial Troubleshooting Section #1525

Closed
YangLou1 opened this issue Jan 18, 2018 · 3 comments
Closed

Add Content under Step 2 Vagrant Tutorial Troubleshooting Section #1525

YangLou1 opened this issue Jan 18, 2018 · 3 comments

Comments

@YangLou1
Copy link
Member

YangLou1 commented Jan 18, 2018

I run the Windows 8.1 and Above script to install all BeLL's Dependencies including VirtualBox and Vagrant.
I suspended my virtual machine using the command vagrant suspend. Then I issued the command vagrant up in order to restart my machine. However, I got an error message saying "Vagrant up: There was an error while executing VBoxManage, a CLI used by Vagrant". My OS is Windows 8.1.

@vishwakarmaanil
Copy link
Member

Re installing other version of virtual box ( 5.1.x ) solves this problem. Don’t install 5.2 version of virtual box since it is not supported by vagrant installations.

@YangLou1
Copy link
Member Author

YangLou1 commented Jan 18, 2018

I found the same error that someone was facing and its possible solutions at this link: hashicorp/vagrant#1809.
I fixed the error by killing the process "VBoxHeadless" in Task Manager (Windows 8.1), and the command vagrant up worked afterwards.

We can add the following content under Step 2 Vagrant Tutorial Troubleshooting Section as the 4th item:
4. When you run vagrant up from command prompt on windows after running vagrant suspend, you might get the following error: "Vagrant up: There was an error while executing VBoxManage, a CLI used by Vagrant". A possible solution is killing the process "VBoxHeadless" in Windows Task Manager, and the command vagrant up might work afterwards. For more information visit here

@kylemathias
Copy link
Member

I would say a fix is in order for this problem, but i don't think the problem is best fix by adding a solution to when something goes wrong. Try to fix the original install process instead.

Kuljeet1998 pushed a commit to Kuljeet1998/Kuljeet1998.github.io that referenced this issue Jun 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants