How Do You Create a Windows 2016 Server with Vagrant and Oracle VirtualBox?

Problem scenario
You want to use Windows 2016 with 2 GB of RAM. You have Oracle VirtualBox installed on a Linux server. You want the VM to be able to communicate with the host or other VMs on the host. You have a license for Windows 2016. What should you do?

Prerequisite: You have Oracle VirtualBox set up. You know what adapters you can attach a VM to. (Options may include enp1s0, virbr0, virbr0-nic or others.)

  1. Install Vagrant.
  2. Run this command:
    gem list | grep libvirt
  3. Verify that libvirt's version is at least 0.6 or higher. If it is, go to step #2. If it is lower than that, use the following two commands (uncommented out):
# gem uninstall fog-libvirt
# gem install fog-libvirt

4. Run these two commands:

vagrant plugin install winrm
vagrant plugin install winrm-elevated

5. Use this as the Vagrantfile (but not for commercial purposes unless you have a license):

# -*- mode: ruby -*-
# vi: set ft=ruby :

# All Vagrant configuration is done below. The "2" in Vagrant.configure
# configures the configuration version (we support older styles for
# backwards compatibility). Please don't change it unless you know what
# you're doing.
Vagrant.configure("2") do |config|
  # The most common configuration options are documented and commented below.
  # For a complete reference, please see the online documentation at

  # Every Vagrant development environment requires a box. You can search for
  # boxes at = "mwrock/Windows2016"
  config.vm.provider "virtualbox" :public_network, :bridge => "enp1s0", adapter: "1"
  # Disable automatic box update checking. If you disable this, then
  # boxes will only be checked for updates when the user runs
  # `vagrant box outdated`. This is not recommended.
  # config.vm.box_check_update = false

  # Create a forwarded port mapping which allows access to a specific port
  # within the machine from a port on the host machine. In the example below,
  # accessing "localhost:8080" will access port 80 on the guest machine.
  # NOTE: This will enable public access to the opened port
  # "forwarded_port", guest: 80, host: 8080

  # Create a forwarded port mapping which allows access to a specific port
  # within the machine from a port on the host machine and only allow access
  # via to disable public access
  # "forwarded_port", guest: 80, host: 8080, host_ip: ""

  # Create a private network, which allows host-only access to the machine
  # using a specific IP.
  # "private_network", ip: ""

  # Create a public network, which generally matched to bridged network.
  # Bridged networks make the machine appear as another physical device on
  # your network.
  # "public_network"

  # Share an additional folder to the guest VM. The first argument is
  # the path on the host to the actual folder. The second argument is
  # the path on the guest to mount the folder. And the optional third
  # argument is a set of non-required options.
  # config.vm.synced_folder "../data", "/vagrant_data"

  # 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|
  #   # Display the VirtualBox GUI when booting the machine
  #   vb.gui = true
  #   # Customize the amount of memory on the VM:
     vb.memory = "2048"
  # View the documentation for the provider you are using for more
  # information on available options.

  # Enable provisioning with a shell script. Additional provisioners such as
  # Ansible, Chef, Docker, Puppet and Salt are also available. Please see the
  # documentation for more information about their specific syntax and use.
  # config.vm.provision "shell", inline: <<-SHELL
  #   apt-get update
  #   apt-get install -y apache2
  1. Run this command: vagrant up
    Do not be alarmed if it hangs at the "default WinRM transport: negotiate" step.

You may see this (because there is only one adapter and it is a bridged adapter):

default: WinRM address:
default: WinRM username: vagrant
default: WinRM execution_time_limit: PT2H
default: WinRM transport: negotiate
Timed out while waiting for the machine to boot. This means that
Vagrant was unable to communicate with the guest machine within
the configured ("config.vm.boot_timeout" value) time period.

If you look above, you should be able to see the error(s) that
Vagrant had when attempting to connect to the machine. These errors
are usually good hints as to what may be wrong.

If you're using a custom box, make sure that networking is properly
working and you're able to connect to the machine. It is a common
problem that networking isn't setup properly in these boxes.
Verify that authentication configurations are also setup properly,
as well.

If the box appears to be booting properly, you may want to increase
the timeout ("config.vm.boot_timeout") value.

Join the Conversation

1 Comment

Leave a comment

Your email address will not be published. Required fields are marked *