I upgraded from ubunutu 16 to Ubuntu 18.04.1 desktop (what i really did was reinstalled ubuntu, because i kinda destroy my system) yesterday, and now i want get vagrant back up and running, the problem is that vagrant doesn't recognize the plugin disksize any more. It is installed as you can see (with vagrant plugin list) but vagrant doesn't see it.
keep on getting * Unknown configuration section 'disksize'.
I also tried installing a older version of vagrant (1.8.5) but it looks like that doens't work with the new virtualbox (doesn't recognize the provider).
i saw the post Vagrant: * Unknown configuration section 'disksize' but that is the way i installed disksize so that doesn't help.
if more information is required let met know.
Today I updated both virtualbox and vagrant to their latest versions. Had the same problem like you just different plugin.
After downgrading vagrant to 2.10 it works again, no issue with virtualbox (no need to downgrade). Hopefully vagrant will fix this with its new release.
Related
I've recently installed VirtualBox, Vagrant and Chef DK and when I run kitchen converge my VM comes up properly provisioned with my cookbook using vagrant and the Virtualbox provider however I am unable to view or manage the vm from the VirtualBox Manager
I can however view see the vm running via kitchen list or vagrant global-status
Upon reviewing where the .vbox is being loaded I can see that its going in the ~/my_cookbook/.kitchen/nameofvm/ folder
When I review the default Machine location set in Virtual box i can see it's located in the /Users//VirtualBox VMs/ folder however it does not appear to be following this attribute
So far i've reinstalled vagrant, VirtualBox and Chef DK
I'm running MacOS Sierra 10.12.6 and only have started having this issue since upgrading to MacOS Sierra.
Anyone have any recommendations or some extra steps that I could take to potentially resolve this issue?
Chef Development Kit Version: 2.1.11
chef-client version: 13.2.20
delivery version: master (73ebb72a6c42b3d2ff5370c476be800fee7e5427)
berks version: 6.3.0
kitchen version: 1.17.0
inspec version: 1.33.1
vboxmanage -v
5.1.26r117224
Vagrant 1.9.8
This was an inadvertent mis-feature of a change in kitchen-vagrant, which has since been reverted. ChefDK 2.2 includes this fixed version of kitchen-vagrant and should be released either later today or tomorrow morning. You can also roll back to ChefDK 2.0. Sorry for the trouble.
I have scoured the internet up and down for this issue and always consider asking here a last resort. That being said if this has been asked and solved before please point me in the right direction.
I am using Virtualbox 5.1.22 on macOS Sierra 10.12.5 with vagrant version 1.9.6
Yesterday I upgraded my homestead box from version 2.0.0 to 2.1.0. I only upgraded after running vagrant up and it did its thing and was fine until I come in today and turn my machine one and try booting up the vagrant machine again. I get the following error at the end of the normal stuff:
Vagrant was unable to mount VirtualBox shared folders. This is usually
because the filesystem "vboxsf" is not available. This filesystem is
made available via the VirtualBox Guest Additions and kernel module.
Please verify that these guest additions are properly installed in the
guest. This is not a bug in Vagrant and is usually caused by a faulty
Vagrant box. For context, the command attempted was:
mount -t vboxsf -o uid=900,gid=900 vagrant /vagrant
The error output from the command was:
/sbin/mount.vboxsf: mounting failed with the error: No such device
I have tried vagrant reload, vagrant halt and then vagrant up, restarting the machine and re-running, vagrant reload --provision
Any help is greatly appreciated.
Thanks.
EDIT: Why the downvote? This seems like a perfectly reasonable question?
The box comes with VirtualBox Guest Addition for a given version of VirtualBox, which is not the one you're running on your host.
what you need to do is update the Guest Additions in your guest VM to the same version of VirtualBox that you run on your host machine.
The easy way as mentioned in my comments is to use the vagrant vbguest plugin, it will compare the version from your host and guest software and will automatically aligned if needed. I find it pretty convenient and there are options to disable the update if you need.
In case you do not want to run an additional plugin, you can make the update on the guest VM manually.
You will need to download the Guest Addition for the same version of your VirtualBox (5.1.22 in your case) and follow the instructions to install
So I found and installed this: https://github.com/dotless-de/vagrant-vbguest
I have no idea why I need a plugin now when it was working just fine before updating but hey...it works.
This is my error and I couldn't fix it. I need help, my virtual box is on the lastest version.
The list of vagrant plugins:
I tried to update them but every time I restart my vagran, they get the default version. What do I need to do?
At the time of writing this, the latest version of VirtualBox (5.1.16) on Windows is having problems mounting any drives from Vagrant, and the only solution so far is to wait for an update that resolves this, or manually downgrade VirtualBox to 5.1.14.
There's more information about other people having similar problems in this GitHub issue: https://github.com/laravel/homestead/issues/510
You can update to the 5.1.18 version. It works in this version
I am trying to add the laravel/homestead box to my vagrant installation and keep getting the error "The program 'vagrant' is currently not installed. You can install it by typing: sudo apt-get install vagrant"
I have virtual box installed and working (I use it regularly) and I just downloaded vagrant and it DID say it downloaded successfully. Some forums suggest my installation is not up to date but I installed it about 15 minutes ago so I don't think that could be the case.
Also, I have already created a new directory using mkdir, then used "vagrant init hashicorp/precise32" and then "vagrant ssh" which have all been successful. The next thing I try to do is add the box and it won't work. I have never used vagrant before so I am unfamiliar with this. Any help is appreciated!
PS I'm on OSX El Capitan
Not sure if this is useful after so many months, but I ran into this same problem yesterday. There appears to be a lot of information about this in the vagrant git forums.
As a workaround (not fix) I downgraded to virtualBox 5.0, and vagrant 1.7.4
Trying to install Vagrant on Windows 7 X64 with installer from Vagrant - vagrant_1.7.0.msi
Installation goes fine, however unable to use vagrant. On any command, for example vagrant -v the below is shown:
Failed to find Vagrant!
What I did:
Googled. Only 1 link with such an error on github regarding to installer. Not sure if this is relevant.
Checked that vagrant in PATH. Yes it is. Otherwise it would not start at all.
Reinstalled, and repaired - few times.
All the above with no luck. Any idea where to dig?
Thank you.
just to add my own version of this problem too:
i installed version 1.7.0
error message after a "vagrant up": "Failed to find Vagrant!"
checked paths, other environment variables in win7, should work..
so i uninstalled it and installed an older version (1.6.5)
and yes, the older version solved the problem.
i got it from their official website: https://www.vagrantup.com/download-archive/v1.6.5.html
i guess the problem was in this file:
https://github.com/mitchellh/vagrant-installers/blob/master/substrate/launcher/main.go
Same Issue on Windows 7 64.
Downgraded back to Vagrant 1.6.5
Have you gone through the installation instructions on vagrant side listed here :
https://docs.vagrantup.com/v2/installation/index.html
This is what I see listed at their site:
The installer will automatically add vagrant to your system path so that it is available in terminals. If it is not found, please try logging out and logging back in to your system (this is particularly necessary sometimes for Windows).
Please try running it from Git Bash too and let me know if it works for you.
And if you still run into issues, try using an older version of vagrant https://www.vagrantup.com/download-archive/v1.6.5.html
Vagrant 1.7.1 should fix this. https://github.com/mitchellh/vagrant/issues/4924#issuecomment-66808666