Vagrant 2.2.2
Windows 10
# -*- mode: ruby -*-
# vi: set ft=ruby :
# Testing an ArduPilot VM:
# sim_vehicle.py # in the starting directory should start a Copter simulation
# xterm # X11 forwarding should work
# sim_vehicle.py --debug --gdb
# sim_vehicle.py --valgrind
# time (cd /vagrant && ./waf configure --board=px4-v2 && ./waf build --target=bin/ardusub) # ~17 minutes
# time (cd /vagrant && ./waf configure --board=fmuv2 && ./waf build --target=bin/ardusub) # ~9 minutes
# time (cd /vagrant && ./waf configure --board=fmuv3 && ./waf build --target=bin/ardusub) # ~ minutes (after building fmuv2)
# time (cd /vagrant && ./waf configure --board=navio2 && ./waf build --target=bin/arduplane)
# time (cd /vagrant && ./Tools/autotest/sim_vehicle.py --map --console -v ArduPlane -f jsbsim # should test JSBSim)
# time (cd /vagrant && ./Tools/autotest/autotest.py build.APMrover2 drive.APMrover2)
# Vagrantfile API/syntax version. Don't touch unless you know what you're doing!
VAGRANTFILE_API_VERSION = "2"
Vagrant.configure(VAGRANTFILE_API_VERSION) do |config|
# Provider-specific configuration so you can fine-tune various
# backing providers for Vagrant. These expose provider-specific options.
# Example for VirtualBox:
#
config.vm.provider "virtualbox" do |vb|
# Don't boot with headless mode
# vb.gui = true
#
# # Use VBoxManage to customize the VM. For example to change memory:
vb.customize ["modifyvm", :id, "--memory", "3192"]
vb.customize ["modifyvm", :id, "--ioapic", "on"]
vb.customize ["modifyvm", :id, "--cpus", "2"]
# Make some effort to avoid clock skew
vb.customize ["guestproperty", "set", :id, "/VirtualBox/GuestAdd/VBoxService/--timesync-set-threshold", "5000"]
vb.customize ["guestproperty", "set", :id, "/VirtualBox/GuestAdd/VBoxService/--timesync-set-start"]
vb.customize ["guestproperty", "set", :id, "/VirtualBox/GuestAdd/VBoxService/--timesync-set-on-restore", "1"]
end
# If you are on windows then you must use a version of git >= 1.8.x
# to update the submodules in order to build. Older versions of git
# use absolute paths for submodules which confuses things.
# removing this line causes "A box must be specified." error
# and this is the default box that will be booted if no name is specified
config.vm.box = "ubuntu/artful32"
# LTS, EOL April, 2019:
config.vm.define "trusty32", autostart: false do |trusty32|
config.vm.box = "ubuntu/trusty32"
config.vm.provision "trusty32", type: "shell", path: "Tools/vagrant/initvagrant.sh"
config.vm.provider "virtualbox" do |vb|
vb.name = "ArduPilot (trusty32)"
vb.gui = true
end
end
# 14.04.5 LTS, EOL April, 2019:
config.vm.define "trusty64", autostart: false do |trusty64|
config.vm.box = "ubuntu/trusty64"
config.vm.provision "trusty64", type: "shell", path: "Tools/vagrant/initvagrant.sh"
config.vm.provider "virtualbox" do |vb|
vb.name = "ArduPilot (trusty64)"
vb.gui = true
end
end
# LTS, EOL April 2021
# this VM is useful for running valgrind on!
config.vm.define "xenial32", autostart: false do |xenial32|
config.vm.box = "ubuntu/xenial32"
config.vm.provision :shell, path: "Tools/vagrant/initvagrant.sh"
config.vm.provider "virtualbox" do |vb|
vb.name = "ArduPilot (xenial32)"
vb.gui = true
end
end
# NO LONGER AVAILABLE FOR DOWNLOAD, EOL January 2018
# EOL January 2018
# Only kept around for those few dev's who have already got this image and continue to use it.
config.vm.define "zesty32", autostart: false do |zesty32|
config.vm.box = "ubuntu/zesty32"
config.vm.provision :shell, path: "Tools/vagrant/initvagrant.sh"
config.vm.provider "virtualbox" do |vb|
vb.name = "ArduPilot (zesty32)"
vb.gui = true
end
end
# 17.10, EOL July 2018
config.vm.define "artful32", primary: true do |artful32|
config.vm.box = "ubuntu/artful32"
config.vm.provision :shell, path: "Tools/vagrant/initvagrant.sh"
config.vm.provider "virtualbox" do |vb|
vb.name = "ArduPilot (artful32)"
vb.gui = true
end
end
# 18.04 LTS , bleeding edge.
config.vm.define "bionic32", autostart: false do |bionic32|
config.vm.box = "ubuntu/bionic32"
config.vm.provision :shell, path: "Tools/vagrant/initvagrant.sh"
config.vm.provider "virtualbox" do |vb|
vb.name = "ArduPilot (bionic32)"
vb.gui = true
end
end
# 18.04 LTS , bleeding edge.
config.vm.define "bionic64", autostart: false do |bionic64|
config.vm.box = "ubuntu/bionic64"
config.vm.provision :shell, path: "Tools/vagrant/initvagrant.sh"
config.vm.provider "virtualbox" do |vb|
vb.name = "ArduPilot (bionic64)"
vb.gui = true
end
end
# 18.10 bleeding edge
config.vm.define "cosmic32", autostart: false do |cosmic32|
config.vm.box = "ubuntu/cosmic32"
config.vm.provision :shell, path: "Tools/vagrant/initvagrant.sh"
config.vm.provider "virtualbox" do |vb|
vb.name = "ArduPilot (cosmic32)"
vb.gui = true
end
end
# 18.10 bleeding edge
config.vm.define "cosmic64", autostart: false do |cosmic64|
config.vm.box = "ubuntu/cosmic64"
config.vm.provision :shell, path: "Tools/vagrant/initvagrant.sh"
config.vm.provider "virtualbox" do |vb|
vb.name = "ArduPilot (cosmic64)"
vb.gui = true
end
end
end
Trying to run vagrant up
sets up vagrant
$ vagrant up
Bringing machine 'artful32' up with 'virtualbox' provider...
==> artful32: Box 'ubuntu/artful32' could not be found. Attempting to find and install...
artful32: Box Provider: virtualbox
artful32: Box Version: >= 0
==> artful32: Loading metadata for box 'ubuntu/artful32'
artful32: URL: https://vagrantcloud.com/ubuntu/artful32
==> artful32: Adding box 'ubuntu/artful32' (v20180718.0.0) for provider: virtualbox
artful32: Downloading: https://vagrantcloud.com/ubuntu/boxes/artful32/versions/20180718.0.0/providers/virtualbox.box
artful32: Download redirected to host: cloud-images.ubuntu.com
artful32:
An error occurred while downloading the remote file. The error
message, if any, is reproduced below. Please fix this error and try
again.
The requested URL returned error: 404 Not Found
http://ardupilot.org/dev/docs/setting-up-sitl-using-vagrant.html
I'm seeing the same thing this morning. However I'm using MacOSX 10.14.1 with Vagrant version 2.2.2 and trying to download ubuntu/bionic64.
$ vagrant box add ubuntu/bionic64
==> box: Loading metadata for box 'ubuntu/bionic64'
box: URL: https://vagrantcloud.com/ubuntu/bionic64
==> box: Adding box 'ubuntu/bionic64' (v20181203.0.0) for provider: virtualbox
box: Downloading: https://vagrantcloud.com/ubuntu/boxes/bionic64/versions/20181203.0.0/providers/virtualbox.box
box: Download redirected to host: cloud-images.ubuntu.com
An error occurred while downloading the remote file. The error
message, if any, is reproduced below. Please fix this error and try
again.
OpenSSL SSL_connect: SSL_ERROR_SYSCALL in connection to cloud-images.ubuntu.com:443
@sebrandon1, your's is ssl problem. Mine is 404.
Do you think it's somehow related?
I think so. It's performing a redirect:
Download redirected to host: cloud-images.ubuntu.com
Something about that domain seems busted.
EDIT: I was able to get an image to download using:
vagrant box add http://cloud-images.ubuntu.com/bionic/20181203/bionic-server-cloudimg-amd64-vagrant.box --name bionic64
It's not specifically the image I'm trying to download, but at least it looks like the domain is working.
Hey all, this is because it looks like the box is now missing on Ubuntus server:
brian@localghost:vagrant-sandbox % be vagrant box add ubuntu/artful32 ±[●][master]
==> box: Loading metadata for box 'ubuntu/artful32'
box: URL: https://vagrantcloud.com/ubuntu/artful32
==> box: Adding box 'ubuntu/artful32' (v20180718.0.0) for provider: virtualbox
box: Downloading: https://vagrantcloud.com/ubuntu/boxes/artful32/versions/20180718.0.0/providers/virtualbox.box
box: Download redirected to host: cloud-images.ubuntu.com
An error occurred while downloading the remote file. The error
message, if any, is reproduced below. Please fix this error and try
again.
The requested URL returned error: 404 Not Found
Ubuntu hosts their boxes externally outside of Vagrant Cloud. I recommend going to their support for more information.
The SSL issue seems like something intermittent, as I was able to download the ubuntu/bionic64 box just fine.
Anyway I'm going to go ahead and close this since it's not a Vagrant bug, thanks!
@briancain, do you know where can I find ubuntu support on this issue?
@kossumov - Here I think: https://www.ubuntu.com/support/community-support
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.