Vagrant

Author: e | 2025-04-24

Vagrant 2.3.0 (Bản chuẩn cuối) - Download; Vagrant - Download; Vagrant - Download; Vagrant - Download; Vagrant - Download; Vagrant - Download; Vagrant - Download; Vagrant - Download; Vagrant 2.2.9 - 07

Install Vagrant and Vagrant Plugins

Download Vagrant 2.4.3 Date released: 14 Nov 2024 (4 months ago) Download Vagrant 2.4.2 Date released: 02 Nov 2024 (4 months ago) Download Vagrant 2.4.1 Date released: 20 Jan 2024 (one year ago) Download Vagrant 2.4.0 Date released: 17 Oct 2023 (one year ago) Download Vagrant 2.3.7 Date released: 16 Jun 2023 (one year ago) Download Vagrant 2.3.6 Date released: 21 May 2023 (one year ago) Download Vagrant 2.3.5 Date released: 17 May 2023 (one year ago) Download Vagrant 2.3.4 Date released: 10 Dec 2022 (2 years ago) Download Vagrant 2.3.3 Date released: 16 Nov 2022 (2 years ago) Download Vagrant 2.3.2 Date released: 19 Oct 2022 (2 years ago) Download Vagrant 2.3.1 Date released: 30 Sep 2022 (2 years ago) Download Vagrant 2.3.0 Date released: 10 Aug 2022 (3 years ago) Download Vagrant 2.2.19 Date released: 06 Nov 2021 (3 years ago) Download Vagrant 2.2.18 Date released: 28 Jul 2021 (4 years ago) Download Vagrant 2.2.17 Date released: 08 Jul 2021 (4 years ago) Download Vagrant 2.2.16 Date released: 30 Apr 2021 (4 years ago) Download Vagrant 2.2.15 Date released: 31 Mar 2021 (4 years ago) Download Vagrant 2.2.14 Date released: 20 Nov 2020 (4 years ago) Download Vagrant 2.2.13 Date released: 07 Nov 2020 (4 years ago) Download Vagrant 2.2.11 Date released: 06 Nov 2020 (4 years ago) Vagrant on Windows? Before installing Vagrant on Windows, you need to have VirtualBox or any other provider installed on your system. Vagrant is a tool for building and managing virtual machine environments, and it requires a provider like VirtualBox to create these environments. You also need to have enough storage space on your system to accommodate the virtual machines that Vagrant will create. How do I install Vagrant on Windows? To install Vagrant on Windows, first, download the appropriate installer from the Vagrant downloads page. Once the download is complete, double-click the installer to start the installation process. Follow the prompts in the installation wizard, accepting the default settings unless you have a specific reason to change them. Once the installation is complete, you can verify it by opening a command prompt and typing ‘vagrant –version’. If Vagrant is installed correctly, this command will display the version of Vagrant that you installed. How do I create a new Vagrant project? To create a new Vagrant project, first, create a new directory for your project. Then, navigate to this directory in a command prompt and run the command ‘vagrant init’. This command will create a new Vagrantfile in your project directory, which you can then customize to specify the settings for your virtual machine. How do I start a Vagrant virtual machine? To start a Vagrant virtual machine, navigate to your project directory in a command prompt and run the command ‘vagrant up’. This command will start the virtual machine specified in your Vagrantfile. If this is the first time you’re starting this virtual machine, Vagrant will first download the necessary box file, which can take some time depending on your internet connection. How do I connect to a Vagrant virtual machine? To connect to a Vagrant virtual machine, use the command ‘vagrant ssh’. This command will start a SSH session with your virtual machine, allowing you to run commands on the virtual machine as if you were sitting in front of it. How do I stop a Vagrant virtual machine? To stop a Vagrant virtual machine, use the command ‘vagrant halt’. This command will gracefully shut down the virtual machine, preserving its state for the next time you start it. How do I delete a Vagrant virtual machine? To delete a Vagrant virtual machine, use the command ‘vagrant destroy’. This command will completely remove the virtual machine and all its associated resources. Be careful when using this command, as it cannot be undone. How do I update Vagrant? To update Vagrant, you need to download and install the latest version of Vagrant from the Vagrant downloads page. This will overwrite your existing installation with the latest version. Note that updating Vagrant will not affect your existing Vagrant projects or virtual machines. How do I troubleshoot Vagrant errors? If you encounter errors while using Vagrant, the first step is to check the output of the command that caused the error. Vagrant will often provide error messages that can help you diagnose

An introduction to Vagrant. What is vagrant?

Yesterday, I install this plugin, but it not work.VirtualBox GUI Manager show IDE disk still use vmdk type, and size 10Gmy vagrantFile is:Vagrant.configure("2") do |config| config.vm.box = "centos/8" config.vm.box_version = "1905.1" config.vagrant.plugins = ['vagrant-disksize'] config.disksize.size="50G" config.vm.network "private_network", ip: "192.168.33.10" config.vm.provider "virtualbox" do |vb| vb.memory = "1024" vb.cpus = 2 endendcommand vagrant plugin list show vagrant-disksize (0.1.3, global)then I debug vagrantvagrant up --debug > up.txt 2>&1version and variable log:INFO global: Vagrant version: 2.2.13 INFO global: Ruby version: 2.6.6 INFO global: RubyGems version: 3.0.3 INFO global: VAGRANT_EXECUTABLE="C:\\HashiCorp\\Vagrant\\embedded\\gems\\2.2.13\\gems\\vagrant-2.2.13\\bin\\vagrant" INFO global: VAGRANT_INSTALLER_EMBEDDED_DIR="C:\\HashiCorp\\Vagrant\\embedded" INFO global: VAGRANT_INSTALLER_ENV="1" INFO global: VAGRANT_INSTALLER_VERSION="2" INFO global: VAGRANT_LOG="debug"DEBUG meta: Finding driver for VirtualBox version: 6.1.14 INFO meta: Using VirtualBox driver: VagrantPlugins::ProviderVirtualBox::Driver::Version_6_1load plugin log: INFO manager: Loading plugins...DEBUG manager: Enabling globalized plugins INFO manager: Plugins: INFO manager: - vagrant-disksize = [installed: 0.1.3 constraint: > 0]DEBUG bundler: Enabling prerelease plugin resolution due to dependency: net-ssh-6.2.0.rc1DEBUG signature_file: new solution file instance plugin_file=C:/Users/Administrator/.vagrant.d/plugins.json solution_file=C:/Users/Administrator/Desktop/centos8/.vagrant/bundler/global.solDEBUG signature_file: reading solution file - C:/Users/Administrator/Desktop/centos8/.vagrant/bundler/global.solDEBUG signature_file: solution validation check CHECKSUM 4f900f159ef4286b7a07eca21d54559dfb8b41cdbeb66a3d9d33fbfdcb57b081 4f900f159ef4286b7a07eca21d54559dfb8b41cdbeb66a3d9d33fbfdcb57b081 VERSION 2.2.13 2.2.13DEBUG signature_file: loading solution dependency listDEBUG signature_file: solution dependency list: []DEBUG bundler: solution file in use for init: DEBUG bundler: Generating new builtin set instance.DEBUG bundler: Generating new plugin set instance. Skip gems - []DEBUG bundler: loading cached solution setDEBUG bundler: activating solution setDEBUG bundler: Activating solution set: ["vagrant-disksize-0.1.3"]DEBUG bundler: Activating gem vagrant-disksize-0.1.3 INFO manager: Loading plugins... INFO manager: Loading plugin `vagrant-disksize` with default require: `vagrant-disksize`ERROR manager: Failed to load plugin `vagrant-disksize` with default require. - LoadError: cannot load such file -- vagrant-disksize INFO manager: Loading plugin `vagrant-disksize` with slash require: `vagrant/disksize` INFO manager: Registered plugin: vagrant-disksizeDEBUG manager: Successfully loaded plugin `vagrant-disksize`. INFO loader: Set :root = ["#"]">DEBUG bundler: solution set stored to - INFO manager: Loading plugins...DEBUG manager: Enabling globalized plugins INFO manager: Plugins: INFO manager: - vagrant-disksize = [installed: 0.1.3 constraint: > 0]DEBUG bundler:. Vagrant 2.3.0 (Bản chuẩn cuối) - Download; Vagrant - Download; Vagrant - Download; Vagrant - Download; Vagrant - Download; Vagrant - Download; Vagrant - Download; Vagrant - Download; Vagrant 2.2.9 - 07

GitHub - Varying-Vagrant-Vagrants/VVV: An open source Vagrant

Skip to content Navigation Menu GitHub Copilot Write better code with AI Security Find and fix vulnerabilities Actions Automate any workflow Codespaces Instant dev environments Issues Plan and track work Code Review Manage code changes Discussions Collaborate outside of code Code Search Find more, search less Explore Learning Pathways Events & Webinars Ebooks & Whitepapers Customer Stories Partners Executive Insights GitHub Sponsors Fund open source developers The ReadME Project GitHub community articles Enterprise platform AI-powered developer platform Pricing Provide feedback Saved searches Use saved searches to filter your results more quickly //voltron/issues_fragments/issue_layout;ref_cta:Sign up;ref_loc:header logged out"}"> Sign up Notifications You must be signed in to change notification settings Fork 4.4k Star 26.6k DescriptionTrying to install the vagrant-vbguest plugin fails on 2.2.19, but works on 2.2.18Vagrant version2.2.19Host operating systemDebian 11= 2.6.5"> (FrozenError) from /usr/lib/ruby/vendor_ruby/rubygems/resolver/composed_set.rb:54:in `block in find_all' from /usr/lib/ruby/vendor_ruby/rubygems/resolver/composed_set.rb:53:in `map' from /usr/lib/ruby/vendor_ruby/rubygems/resolver/composed_set.rb:53:in `find_all' from /usr/lib/ruby/vendor_ruby/rubygems/resolver.rb:203:in `find_possible' from /usr/lib/ruby/vendor_ruby/rubygems/resolver.rb:228:in `search_for' from /usr/lib/ruby/vendor_ruby/rubygems/resolver/molinillo/lib/molinillo/delegates/specification_provider.rb:11:in `block in search_for' from /usr/lib/ruby/vendor_ruby/rubygems/resolver/molinillo/lib/molinillo/delegates/specification_provider.rb:77:in `with_no_such_dependency_error_handling' from /usr/lib/ruby/vendor_ruby/rubygems/resolver/molinillo/lib/molinillo/delegates/specification_provider.rb:10:in `search_for' from /usr/lib/ruby/vendor_ruby/rubygems/resolver/molinillo/lib/molinillo/resolution.rb:779:in `possibilities_for_requirement' from /usr/lib/ruby/vendor_ruby/rubygems/resolver/molinillo/lib/molinillo/resolution.rb:761:in `push_state_for_requirements' from /usr/lib/ruby/vendor_ruby/rubygems/resolver/molinillo/lib/molinillo/resolution.rb:744:in `require_nested_dependencies_for' from /usr/lib/ruby/vendor_ruby/rubygems/resolver/molinillo/lib/molinillo/resolution.rb:727:in `activate_new_spec' from /usr/lib/ruby/vendor_ruby/rubygems/resolver/molinillo/lib/molinillo/resolution.rb:684:in `attempt_to_activate' from /usr/lib/ruby/vendor_ruby/rubygems/resolver/molinillo/lib/molinillo/resolution.rb:254:in `process_topmost_state' from /usr/lib/ruby/vendor_ruby/rubygems/resolver/molinillo/lib/molinillo/resolution.rb:182:in `resolve' from /usr/lib/ruby/vendor_ruby/rubygems/resolver/molinillo/lib/molinillo/resolver.rb:43:in `resolve' from /usr/lib/ruby/vendor_ruby/rubygems/resolver.rb:190:in `resolve' from /usr/lib/ruby/vendor_ruby/rubygems/request_set.rb:411:in `resolve' from /usr/share/rubygems-integration/all/gems/vagrant-2.2.19/lib/vagrant/bundler.rb:586:in `internal_install' from /usr/share/rubygems-integration/all/gems/vagrant-2.2.19/lib/vagrant/bundler.rb:350:in `install' from /usr/share/rubygems-integration/all/gems/vagrant-2.2.19/lib/vagrant/plugin/manager.rb:138:in `block in install_plugin' from /usr/share/rubygems-integration/all/gems/vagrant-2.2.19/lib/vagrant/plugin/manager.rb:148:in `install_plugin' from /usr/share/rubygems-integration/all/gems/vagrant-2.2.19/lib/vagrant/environment.rb:1014:in `block in process_configured_plugins' from /usr/share/rubygems-integration/all/gems/vagrant-2.2.19/lib/vagrant/environment.rb:1005:in `each' from /usr/share/rubygems-integration/all/gems/vagrant-2.2.19/lib/vagrant/environment.rb:1005:in `process_configured_plugins' from /usr/share/rubygems-integration/all/gems/vagrant-2.2.19/lib/vagrant/environment.rb:178:in `initialize' from /usr/share/rubygems-integration/all/gems/vagrant-2.2.19/bin/vagrant:194:in `new' from /usr/share/rubygems-integration/all/gems/vagrant-2.2.19/bin/vagrant:194:in `' from /usr/bin/vagrant:25:in `load' from /usr/bin/vagrant:25:in `'">Installing the 'vagrant-vbguest' plugin. This can take a few minutes.../usr/share/rubygems-integration/all/gems/vagrant-2.2.19/lib/vagrant/bundler.rb:855:in `find_all': can't modify frozen Gem::Dependency: = 2.6.5"> (FrozenError) from /usr/lib/ruby/vendor_ruby/rubygems/resolver/composed_set.rb:54:in `block in find_all' from /usr/lib/ruby/vendor_ruby/rubygems/resolver/composed_set.rb:53:in `map' from /usr/lib/ruby/vendor_ruby/rubygems/resolver/composed_set.rb:53:in `find_all' from /usr/lib/ruby/vendor_ruby/rubygems/resolver.rb:203:in `find_possible' from /usr/lib/ruby/vendor_ruby/rubygems/resolver.rb:228:in `search_for' from /usr/lib/ruby/vendor_ruby/rubygems/resolver/molinillo/lib/molinillo/delegates/specification_provider.rb:11:in `block in search_for' from /usr/lib/ruby/vendor_ruby/rubygems/resolver/molinillo/lib/molinillo/delegates/specification_provider.rb:77:in `with_no_such_dependency_error_handling' from /usr/lib/ruby/vendor_ruby/rubygems/resolver/molinillo/lib/molinillo/delegates/specification_provider.rb:10:in `search_for' from /usr/lib/ruby/vendor_ruby/rubygems/resolver/molinillo/lib/molinillo/resolution.rb:779:in `possibilities_for_requirement' from /usr/lib/ruby/vendor_ruby/rubygems/resolver/molinillo/lib/molinillo/resolution.rb:761:in `push_state_for_requirements' from /usr/lib/ruby/vendor_ruby/rubygems/resolver/molinillo/lib/molinillo/resolution.rb:744:in `require_nested_dependencies_for' from /usr/lib/ruby/vendor_ruby/rubygems/resolver/molinillo/lib/molinillo/resolution.rb:727:in `activate_new_spec' from /usr/lib/ruby/vendor_ruby/rubygems/resolver/molinillo/lib/molinillo/resolution.rb:684:in `attempt_to_activate' from /usr/lib/ruby/vendor_ruby/rubygems/resolver/molinillo/lib/molinillo/resolution.rb:254:in `process_topmost_state' from /usr/lib/ruby/vendor_ruby/rubygems/resolver/molinillo/lib/molinillo/resolution.rb:182:in `resolve' from /usr/lib/ruby/vendor_ruby/rubygems/resolver/molinillo/lib/molinillo/resolver.rb:43:in `resolve' from /usr/lib/ruby/vendor_ruby/rubygems/resolver.rb:190:in `resolve' from /usr/lib/ruby/vendor_ruby/rubygems/request_set.rb:411:in `resolve' from /usr/share/rubygems-integration/all/gems/vagrant-2.2.19/lib/vagrant/bundler.rb:586:in `internal_install' from /usr/share/rubygems-integration/all/gems/vagrant-2.2.19/lib/vagrant/bundler.rb:350:in `install' from /usr/share/rubygems-integration/all/gems/vagrant-2.2.19/lib/vagrant/plugin/manager.rb:138:in `block in install_plugin' from /usr/share/rubygems-integration/all/gems/vagrant-2.2.19/lib/vagrant/plugin/manager.rb:148:in `install_plugin' from /usr/share/rubygems-integration/all/gems/vagrant-2.2.19/lib/vagrant/environment.rb:1014:in `block in process_configured_plugins' from /usr/share/rubygems-integration/all/gems/vagrant-2.2.19/lib/vagrant/environment.rb:1005:in `each' from /usr/share/rubygems-integration/all/gems/vagrant-2.2.19/lib/vagrant/environment.rb:1005:in `process_configured_plugins' from /usr/share/rubygems-integration/all/gems/vagrant-2.2.19/lib/vagrant/environment.rb:178:in `initialize' from /usr/share/rubygems-integration/all/gems/vagrant-2.2.19/bin/vagrant:194:in `new' from /usr/share/rubygems-integration/all/gems/vagrant-2.2.19/bin/vagrant:194:in `' from /usr/bin/vagrant:25:in `load' from /usr/bin/vagrant:25:in `' Verify your Vagrant installation by checking the Vagrant version:vagrant --versionIn your output you will see:OutputVagrant 2.3.0Now you have successfully installed Vagrant on Ubuntu 20.04, let’s see how to use it.Create a Vagrant Project on Ubuntu 20.04At this point, we want to show you how to use Vagrant by creating a development environment.First, you need to create a file you want to save the Vagrant file. To do this, run the following command:mkdir ~/vagrant-projectThen, you need to initialize a new Vagrantfile and specify the box you wish to use on Ubuntu 20.04.Boxes are the package format for the Vagrant environments and are provider-specific.You can check the list of available Vagrant Boxes on the Vagrant Catalog page.In this example, we want to use ubuntu/trusty64.Switch to your Vagrant project directory with the following command:cd ~/vagrant-projectNow initialize the Vagrantfile with the following command:vagrant init ubuntu/trusty64In your output you will see:OutputA `Vagrantfile` has been placed in this directory. You are nowready to `vagrant up` your first virtual environment! Please readthe comments in the Vagrantfile as well as documentation on`vagrantup.com` for more information on using Vagrant.You can open the Vagrantfile with your favorite text editor and make changes according to your needs on Ubuntu 20.04.Run the following command to create and configure the virtual machine as defined in the Vagrantfile:vagrant upOutput==> default: Configuring and enabling network interfaces......Vagrant mounts the project directory at /vagrant in the virtual machine. This allows you to work on the project’s files on your host machine.You can use the following command to

Vagrant 2.3.6: Unable to Vagrant up - 3 by dvhirst865 - Vagrant

I am encountering an ERROR in 'vagrant up' when I try to boot a 'generic/openbsd7' (virtualbox) VM obtained here: have installed 'generic/openbsd*' VMs from app.vagrantup.com several times previously on this FreeBSD-12 host, most recently for OpenBSD-6.9. The installations were smooth, so I am surprised at the problem I am experiencing.Here is partial output from 'vagrant up --debug':##### INFO loader: Set "2580_machine_default" = [] INFO loader: Loading configuration in order: [:home, :root, "2580_machine_default"]ERROR loader: Unknown config sources: [:"2720_generic/openbsd7_virtualbox", :"2580_vm_default_generic/openbsd7_virtualbox"]DEBUG loader: Loading from: root (cache)DEBUG loader: Configuration loaded successfully, finalizing and returning.../usr/local/lib/ruby/gems/2.7/gems/vagrant-2.2.14/lib/vagrant/environment.rb:290:in `cli'/usr/local/lib/ruby/gems/2.7/gems/vagrant-2.2.14/bin/vagrant:210:in `'/usr/local/bin/vagrant:23:in `load'/usr/local/bin/vagrant:23:in `' INFO interface: error: The VirtualBox VM was created with a user that doesn't match thecurrent user running Vagrant. VirtualBox requires that the same userbe used to manage the VM that was created. Please re-run Vagrant withthat user. This is not a Vagrant issue.The UID used to create the VM was:Your UID is: [XXXX]The VirtualBox VM was created with a user that doesn't match thecurrent user running Vagrant. VirtualBox requires that the same userbe used to manage the VM that was created. Please re-run Vagrant withthat user. This is not a Vagrant issue....INFO interface: Machine: error-exit ["Vagrant::Errors::VirtualBoxUserMismatch"#####Comments:1. The ultimate error is the alleged UID mismatch at the bottom of the output above. I don't know whether the 'ERROR loader' output above is relevant or connected to the ultimate failure.2. The UID elided at XXXX above is the correct UID for the user with which I always execute 'vagrant' commands.3. Note that there is no output next to "The UID used to create the VM was: ". Why would 'vagrant' be unable to detect the "UID used to create the VM"?Has anyone seen this problem before? Any suggestions?Thank you very much.James Keenan

vagrant/CHANGELOG.md at main hashicorp/vagrant

In this guide, we want to teach you How To Install Vagrant on Ubuntu 20.04.Vagrant is an open-source software product used to manage any development environment. Using Vagrant, you can install any virtual OS using the CLI (Command Line Interface), run it, do some work, and shut it down.Vagrant works with any virtualization engine, such as VirtualBox, VMware, libvirt (Linux), etc.You need to have one of these virtualization engines for Vagrant to run a virtual OS.To install Vagrant, you must log in to your server as a non-root user with sudo privileges. To do this, you can follow our guide the Initial Server Setup with Ubuntu 20.04.Now follow the steps below to complete this guide.Installing VirtualBox We’ll use VirtualBox, which is the default provider for Vagrant. If VirtualBox is not installed on your system you can install it by running the command below:#sudo apt update#sudo apt install virtualboxWhen your VirtualBox installation is completed, proceed to the next step to install Vagrant on your server.Set up Vagrant on Ubuntu 20.04You can install Vagrant in the latest version as a deb file from the Vagrant official site.To check the latest version of Vagrant, you can visit the Vagrant Release page.First, download the Vagrant package by using the curl command, just remember to replace the version that you have checked in the following command:curl -O your download is completed, update your local package index with the following command:sudo apt updateThen, you can install Vagrant with the following command:sudo apt install ./vagrant_2.3.0-1_amd64.debNow you can. Vagrant 2.3.0 (Bản chuẩn cuối) - Download; Vagrant - Download; Vagrant - Download; Vagrant - Download; Vagrant - Download; Vagrant - Download; Vagrant - Download; Vagrant - Download; Vagrant 2.2.9 - 07 Steps to reproduce Install vagrant vagrant install plugin vagrant-libvirt vagrant status Expected behaviour Vagrant starts Actual behaviour $ vagrant status Vagrant failed to

Discover Vagrant Boxes - Vagrant Cloud

Key TakeawaysVagrant is a powerful tool that allows developers to create virtual machines on-the-fly through reusable configuration files, making it ideal for testing programs, learning new tools, or preparing changes for a production system.To get started with Vagrant on Windows, you need to install VirtualBox, Vagrant, and PuTTY, and PuTTYGen. After installation, you can create your first Vagrant project by creating a project folder and running Vagrant commands from within these folders.The primary commands to start using Vagrant are ‘vagrant init’ and ‘vagrant up’. These create a Vagrantfile in your directory, which holds a basic starter configuration. You can then find a base box to use from the Vagrant Cloud, and spin up your VM using ‘vagrant up’.Vagrant automatically sets up the SSH forwarding port as ‘2222’, and the username is always ‘vagrant’. It also generates a new set of keys, replacing the default key in the VM and placing the private key in a new folder in your project folder. You can then use PuTTY to connect to the new server over SSH.Vagrant creates a shared folder between your project folder and a folder in your VM, which can be changed or added to as needed. Any changes made to the VM from VirtualBox may cause Vagrant to lose association with the VM. Vagrant also doesn’t automatically forward a web port, such as 80, so you’ll need to manually enable it in your Vagrantfile.This popular article was fully updated in 2017. Changes include information on public keys, troubleshooting tips, and updates for Windows 10 and other relevant software.Vagrant has quickly become the ubiquitous go-to tool for local development across Mac, Windows, and Linux operating systems.Vagrant helps you create virtual machines on-the-fly via a set of reusable configuration files. Developers can share their configurations and scripts via GitHub and elsewhere, so that other devs can spin up an identical environment and tooling.It’s a great tool if you want to spring up servers for testing programs, learn how to use Linux tools, or work in a test environment before applying changes on a production system. Do you want to learn to install the PHP/Apache/MySQL stack from scratch on Ubuntu? Or play with setting up a cache server like Varnish in front of Apache? Try your hand at Nginx? Learn PHP 7? Vagrant makes things quite a bit simpler than using VirtualBox alone.Let’s take a look at how to get Vagrant set up in a Windows environment.Installing the Megabits and PiecesTo get started, go ahead and install these core tools:VirtualBox (the software that creates virtual machines)Vagrant (our hero, the software that deploys virtual machines and runs provisioning scripts)PuTTY and PuTTYGen (SSH client and a generator for security keys)VirtualBox and Vagrant install like any other Windows program. Vagrant will install itself to your global path so you can run it from anywhere. Create Your ProjectsNow that you have it all set up, you can start your first Vagrant project by creating a project folder which will house the various configurations for each of