I suddenly got issue with Windows while trying to import Win-based boxes:
Vagrant version:
vagrant version
Installed Version: 2.2.19
Latest Version: 2.2.19
You're running an up-to-date version of Vagrant!
Virtualbox version:
VBoxManage --version
6.1.32r149290
vagrant up win-1:
win-1:
==> win-1: Box download was interrupted. Exiting.
win-1: Calculating and comparing box checksum...
The checksum of the downloaded box did not match the expected
value. Please verify that you have the proper URL setup and that
you're downloading the proper file.
Expected: 7f2fc9026add89da8fa8049d8b36280e7e05c8d6ef50d9658cfdf2b6771ef116
Received: f01e7920016b75a903d0cb9ac79dabc801e49032e33028ee7cef31758a04a91e
It will get stuck there and with CTRL+C I'll get that checksum error.
Everything worked just fine two weeks back, but I think I updated both the vbox and vagrant, and after that I'm not able to import any windows-based boxes.
Any ideas?
Thanks :)
Related
I am trying to install laravel homestead and can't get past adding the homestead box.
The instruction is: vagrant box add laravel/homestead
After completing the download process following error appears.
C:\Users\HARSHA - PC PRO>vagrant box add laravel/homestead
==> box: Loading metadata for box 'laravel/homestead'
box: URL: https://vagrantcloud.com/laravel/homestead
==> box: Adding box 'laravel/homestead' (v9.0.1) for provider: virtualbox
box: Downloading: https://vagrantcloud.com/laravel/boxes/homestead/versions/9.0.1/providers/virtualbox.box
==> box: Box download is resuming from prior download progress
box: Download redirected to host: vagrantcloud-files-production.s3.amazonaws.com
box: Progress: 100% (Rate: 188k/s, Estimated time remaining: --:--:--)
box: Calculating and comparing box checksum...
The specified checksum type is not supported by Vagrant: sha512.
Vagrant supports the following checksum types:
md5, sha1, sha256
I'm on Windows 10 64 bit PC and have tried these instructions with the virtualbox(Version 6.0.0 r127566 (Qt5.6.2)) and vagrant_2.2.2_x86_64 version.
I'm trying to install Laravel homestead and am not aware of resolving this since I am new to the Laravel vagrant. I searched the web for the particular problem and I could not find any solution pertaining to the above, so any help is appreciated.
As mentioned in Vagrant's CHANGELOG.md file, new checksum types are now supported. Simply updating Vagrant to its latest version (2.2.6) should do the trick.
You can then do vagrant box update to upgrade the Homestead box.
In my case I saw in the logs that the version trying to get installed was v9.2.2-alpha1
box: Adding box 'laravel/homestead' (v9.2.2-alpha1) for provider:
virtualbox
What worked for me is defining the version by using the following parameter
--box-version=9.1.1
i.e.
vagrant box add laravel/homestead --checksum-type=sha256 --box-version=9.1.1
Also, try to download and install the latest version of vagrant.
You are using the unsupported checksum type.try installing with --checksum-type parameter. Given below,
vagrant box add laravel/homestead --checksum-type sha256
Here is the Docs to refer to while using command-line.
Try 2.2.7 version.
vagrant -v
Vagrant 2.2.7
==> box: Successfully added box 'laravel/homestead' (v9.3.0) for 'virtualbox'!
I had the same problem and it took multiple attempts.
Problems
Couldn't update the vagrant box.
Once I downloaded it wouldn't switch to the new box.
Once I switched Laravel threw a Facade error.
Solution
(with many thank you's to the answers in this thread):
Navigate to the Homestead/Vagrant folder.
Then run "vagrant -v" to check your Vagrant version (ex. "Vagrant 2.1.5").
In a web browser go to https://www.vagrantup.com/downloads.html .
Download the latest Vagrant version.
On your computer, run and install the new version.
Go to: https://www.virtualbox.org/
Download the lastest Virtual Machine.
On your computer, run and install the new version.
Back in the terminal, check the vagrant version again "vagrant -v" (ex. "Vagrant 2.2.10").
Make sure your Vagrant is stopped by running "vagrant halt".
Purge and reinstall your vagrant plugins to be safe with "vagrant plugin expunge --reinstall" (and confirm "Y").
Now run "vagrant box update" to update your box.
Now load your box with "vagrant up".
With your box loaded run "vagrant destroy".
Now run "vagrant up" again to rebuild your box from scratch.
This worked for me. Let me know if this works for you.
For many months I had been successfully using VirtualBox 5.xx.xx along with Vagrant 2.xx (don't remember the rest of the version numbers) on a Windows 10 host with Ubuntu 16 guest. At some point in the past six weeks, on vagrant up Guest Additions started being reported as different versions on the host and guest, and changes I would make to my synced files from the Windows side would not always be realized on Ubuntu. To try to fix this problem, I upgraded Vagrant to the latest version, and then tried upgrading and downgrading VirtualBox from as low as 5.0.18 (generates an error on vagrant up) to as high as the latest (6.0.4). Trying 5.2.24 and 5.2.26 yielded messages upon Vagrant startup stating that Guest Additions on the host were reported as 5.0.18 but on the guest were reported as 5.2.24 (or .26). Then a final startup message stated that the Virtualbox version was at 5.2 and the Guest Additions version was 5.1.30 - so at times I've gotten a total of three different versions of Guest Additions reported. I have the vagrant-vbguest plugin installed. I downloaded the matching Guest Additions ISO version for the VBox versions, and loaded the Guest Additions ISO into the virtual optical drive in VirtualBox (as well as specified config.vbguest.iso_path = "VBoxGuestAdditions_5.x.x.iso" in my Vagrantfile.
My Vagrant/VirtualBox setup had been working fine for probably at last a year, and I never wanted to "upgrade" because I've been through this mess before when "upgrading" to newer versions. From too-long searching online, I'm pretty sure this problem has been caused from doing dist-upgrade to Ubuntu (which I do regularly) because I've changed nothing in the Vagrant/VBox setup for a long time. I was hoping that the upgrade to the latest VirtualBox (6) would solve the problem but, sadly, this version is even worse - Ubuntu cranks SLOWLY through the boot process, and it's been taking so long that I haven't even let it finish after trying several times.
It would be great to see if this latest VirtualBox 6 would solve the problem, so maybe someone has an idea about why that would be so slow (I have an 8 core 16Gb machine, and I've assigned 4 cores and plenty of RAM to VBox - and it starts up fine under 5.2.xx).
The vagrant up output:
SSH username: vagrant
SSH auth method: private key
Warning: Connection reset. Retrying...
default: Machine booted and ready! Got different reports about
installed GuestAdditions version: Virtualbox on your host claims:
5.0.18 VBoxService inside the vm claims: 5.2.26 Going on, assuming VBoxService is correct...
GuestAdditions seems to be installed (5.2.26) correctly, but not
running. Got different reports about installed GuestAdditions version:
Virtualbox on your host claims: 5.0.18 VBoxService inside the vm
claims: 5.2.26
Going on, assuming VBoxService is correct...
Job for vboxadd-service.service failed because the control process
exited with error code. See "systemctl status vboxadd-service.service"
and "journalctl -xe" for details.
Got different reports about installed GuestAdditions version:
Virtualbox on your host claims: 5.0.18 VBoxService inside the vm
claims: 5.2.26 Going on, assuming VBoxService is correct... bash: line
4: setup: command not found
Checking for guest additions in VM...
The guest additions on this VM do not match the installed version of
VirtualBox! In most cases this is fine, but in rare cases it can
prevent things such as shared folders from working properly. If you
see shared folder errors, please make sure the guest additions within
the virtual machine match the version of VirtualBox you have installed
on your host and reload your VM.
Guest Additions Version: 5.1.30
VirtualBox Version: 5.2 The following SSH command responded with a
non-zero exit status. Vagrant assumes that this means the command
failed!
After many hours of searching and trying different suggestions, the following is what solved the problem:
downloaded the latest unofficial release build of VirtualBox (in my case 5.2.27) and installed it
Placed the following in my Vagrantfile: config.vbguest.iso_path = "https://www.virtualbox.org/download/testcase/VBoxGuestAdditions_5.2.27-129578.iso"
Ran vagrant up
Ubuntu booted OK, but on the host side Vagrant was displaying an error message something like this:
Failed to mount folders in Linux guest. This is usually because the
"vboxsf" file system is not available.
So next, on the booted Ubuntu guest:
sudo apt autoremove to clean up the Linux headers
And then:
Run vagrant vbguest from the host
vbguest then went through a process of uninstalling the existing Guest Additions and installing VBoxGuestAdditions_5.2.27 from the config.vbguest.iso_path.
To verify that Guest Additions are installed properly, run vagrant vbguest --status (or just vagrant vbguest again). Both commands returned:
[default] GuestAdditions 5.2.27 running --- OK.
The above operations resulted in a folder named VBoxGuestAdditions-5.2.27 being placed within the /opt folder. This VBoxGuestAdditions-5.2.27 folder has seven subfolders, two files (uninstall.sh and routines.sh) and a LICENSE file. I can find no documentation about vagrant-vbguest placing the installed items into the /opt folder, but I did find a small mention here.
I suspect that this process would have worked for any of the 5.2.xx versions (available here), but I had already installed 5.2.27 so went ahead with that.
I had he same issue after updating laravel/homestead box to v7.2.1 . This blog post helped me solve it.
in summary, this is what you have to do:
navigate to the directory that contains your Vagrantfile and run vagrant plugin install vagrant-vbguest
The first time I executed the command, it disabled my WiFi adapter and the installation failed. If this happens, re-activate it back and rerun the command.
when it is done installing, run vagrant up to boot the VM. It will update the Guest Additions
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.
Where to find the url for the ubuntu/xenial64.box?
I only see version-info at https://app.vagrantup.com/ubuntu/boxes/xenial64. But what is the url for the box download?
I simply do:
$ vagrant init ubuntu/xenial64
$ vagrant up
But get:
The box 'ubuntu/xenial64' could not be found.
So I guess I need to put something in config.vm.box_url, but what?
If you keep clicking around and following the links on the Vagrant Cloud website, then eventually you find that the box is hosted at http://cloud-images.ubuntu.com
From there, you can find the latest version of the xenial box specifically hosted at:
http://cloud-images.ubuntu.com/xenial/current/
Direct link to Vagrant box: http://cloud-images.ubuntu.com/xenial/current/xenial-server-cloudimg-amd64-vagrant.box
Sorry, was version mismatch. Newer vagrant works just fine.
I had Vagrant 1.4.x (on linux mint 17.1) and virtualbox 5. Online boxes were not found. Now I have Vagrant 1.8.1 (on linux mint 18.2) and virtualbox 5 and everything works as expected from the Vagrant manual (no url needed).
Thanks and sorry for waisting your time..
--
Oscar.
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.