Troubleshooting the Skytap provider for Vagrant and known issues

Troubleshooting timeout errors during vagrant up commands

If you get a timeout error after vagrant up, check the following:

  • Get the hostname of the VM using the command line vagrant ssh-config, and then use traceroute to make sure that you can connect to the VM.
  • Make sure your local machine is connected to a VPN in the same region as the source VM.
  • Make sure that the VM is able to accept a connection.



To enable logging while troubleshooting, see

Known issues

  • If an older version of Vagrant can’t find the box file, set an environment variable for the alternative host with export VAGRANT_SERVER_URL=
  • If you try to install the provider with vagrant up --provider skytap --install-provider the process will fail. Install the provider before invoking vagrant up.
  • Windows VMs must be configured for WinRM access. For more information about WinRM configurations, see Windows Boxes at
  • WinRM credentials stored in Skytap VMs aren’t used. The user name and password for WinRM connections must be stored in the Vagrantfile: config.winrm.username and config.winrm.password (unless you use the default vagrant/vagrant).
  • If you get a stale NFS file handle error after reloading a Skytap VM, use vagrant up [<vm-name>] to refresh any NFS mounts for that VM. This is a Vagrant known issue.
  • Vagrant public and private networks aren’t supported.
  • UDP port forwarding isn’t supported.
  • vagrant port isn’t supported.
  • You can’t change a VPN connection for a VM after it has been created.

Reporting problems

When you report an issue with the Skytap provider for Vagrant, include the output when using VAGRANT_LOG=debug.

Remove your API token from the log file before sending or posting the log output.