Unable to mount /vagrant folder in 1.7.3 #5933

F21 · 2015-07-11T09:15:21Z

I am running vagrant 1.7.3 with VirtualBox 5.0 on a Windows 8.1 64-bit host.

The guest os is Ubuntu 15.04 64-bit.

When doing a vagrant up, it fails to mount the /vagrant folder:

The following SSH command responded with a non-zero exit status.
Vagrant assumes that this means the command failed!

chown `id -u vagrant`:`id -g vagrant` /vagrant

Stdout from the command:



Stderr from the command:

stdin: is not a tty
chown: changing ownership of ���/vagrant���: Not a directory

Relevant part of my vagrant file:

config.vm.define "main" do |main_config|
    main_config.vm.network "private_network", ip: "192.168.50.4"

    main_config.vm.network "forwarded_port", guest: 80, host: 80
    main_config.vm.synced_folder "D:/work", "/work", type: "smb", owner: "www-data", mount_options: ['file_mode=0777', 'dir_mode=0777']

    main_config.vm.provider "virtualbox" do |v|
        v.memory = 2048
        v.cpus = 4
        v.customize ["modifyvm", :id, "--nictype1", "virtio"]
        v.customize ["modifyvm", :id, "--natdnshostresolver1", "on"]
        v.customize ["modifyvm", :id, "--natdnsproxy1", "on"]
    end
  end

The text was updated successfully, but these errors were encountered:

vany-egorov · 2015-07-11T11:35:05Z

+1

==> default: Mounting shared folders...
    default: /vagrant => D:/vm/debian
The following SSH command responded with a non-zero exit status.
Vagrant assumes that this means the command failed!

chown `id -u vagrant`:`id -g vagrant` /vagrant

Stdout from the command:



Stderr from the command:

stdin: is not a tty
chown: changing ownership of ���/vagrant���: Not a directory

JeroenED · 2015-07-11T13:54:19Z

Same on Windows 7. Tried with Cygwin and CMD. + I thought some actions were having a bold font. This does not seem to be there anymore.

==> jeroened.dev: Mounting shared folders...
    jeroened.dev: /vagrant => C:/Users/Jeroen De Meerleer/test-lampstack
The following SSH command responded with a non-zero exit status.
Vagrant assumes that this means the command failed!

chown `id -u vagrant`:`id -g vagrant` /vagrant

Stdout from the command:



Stderr from the command:

chown: changing ownership of ???/vagrant???: Not a directory

tinda · 2015-07-11T14:25:21Z

same problem

The following SSH command responded with a non-zero exit status.
Vagrant assumes that this means the command failed!

chown id -u vagrant:id -g vagrant /vagrant

Stdout from the command:

Stderr from the command:

chown: changing ownership of ��/vagrant��: Not a directory

Ventajou · 2015-07-11T16:38:34Z

Same error for me, this didn't happen with 1.7.2 hacked to work with virtualbox 5

YAmikep · 2015-07-12T02:35:07Z

Same problem here.
I tried to use vagrant 1.7.2 but it does not seem to work with Virtualbox 5 so I guess I'll just downgrade VirtualBox and Vagrant all together.

ghost · 2015-07-12T03:29:17Z

vagrant@vagrant-ubuntu-vivid-64:~$ df -hl
df: ‘/vagrant’: Not a directory

d-ph · 2015-07-12T11:49:39Z

Same problem for me. Vagrant 1.7.3, VirtualBox 5, WIndows 7 x64.

Steps to reproduce:

$ vagrant init hashicorp/precise32
$ vagrant up

output:

PS D:\vagrant5-test> vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Importing base box 'hashicorp/precise32'...
==> default: Matching MAC address for NAT networking...
==> default: Checking if box 'hashicorp/precise32' is up to date...
==> default: Setting the name of the VM: vagrant5-test_default_1436701709476_3435
==> default: Clearing any previously set network interfaces...
==> default: Preparing network interfaces based on configuration...
    default: Adapter 1: nat
==> default: Forwarding ports...
    default: 22 => 2222 (adapter 1)
==> default: Booting VM...
==> default: Waiting for machine to boot. This may take a few minutes...
    default: SSH address: 127.0.0.1:2222
    default: SSH username: vagrant
    default: SSH auth method: private key
    default: Warning: Connection timeout. Retrying...
    default:
    default: Vagrant insecure key detected. Vagrant will automatically replace
    default: this with a newly generated keypair for better security.
    default:
    default: Inserting generated public key within guest...
    default: Removing insecure key from the guest if it's present...
    default: Key inserted! Disconnecting and reconnecting using new SSH key...
==> default: Machine booted and ready!
==> default: Checking for guest additions in VM...
    default: The guest additions on this VM do not match the installed version of
    default: VirtualBox! In most cases this is fine, but in rare cases it can
    default: prevent things such as shared folders from working properly. If you
    default: shared folder errors, please make sure the guest additions within th
    default: virtual machine match the version of VirtualBox you have installed o
    default: your host and reload your VM.
    default:
    default: Guest Additions Version: 4.2.0
    default: VirtualBox Version: 5.0
==> default: Mounting shared folders...
    default: /vagrant => D:/vagrant5-test
The following SSH command responded with a non-zero exit status.
Vagrant assumes that this means the command failed!

chown `id -u vagrant`:`id -g vagrant` /vagrant

Stdout from the command:



Stderr from the command:

stdin: is not a tty
chown: changing ownership of `/vagrant': Not a directory

Could the issue be connected with vb guest addition being in version 4.2.0, where VirtualBox is version 5?

fbezdeka · 2015-07-12T13:32:27Z

+1

The following SSH command responded with a non-zero exit status.
Vagrant assumes that this means the command failed!

chown `id -u vagrant`:`id -g vagrant` /vagrant

Stdout from the command:

Stderr from the command:

stdin: is not a tty
chown: changing ownership of /vagrant: Not a directory

Update:
Host: Win 7 64 Bit + Vagrant 1.7.3 + VirtualBox 5.0

jarosluv · 2015-07-12T15:05:44Z

Windows 8.1 Pro + Vagrant 1.7.3 + VirtualBox 5.0
Same issue.

Has anyone found way to fast fix?

edwin-egalite · 2015-07-13T03:03:27Z

I revert back to Virtualbox 4.3.30 to temporarily fix this problem.

androidjustme · 2015-07-13T06:21:30Z

Exactly the same problem here with VirtualBox 5.0 and Vagrant 1.7.3

julestruong · 2015-07-13T09:12:15Z

Same here on VB 5 , Vagrant 1.7.3 , Windows 8.1 Pro (Hyper V activated)

ckulla · 2015-07-13T09:27:59Z

Same here, vagrant 1.7.3, windows 7

oxygen0211 · 2015-07-13T10:17:15Z

Having the same with Vagrant 1.7.3, Win 7, VB 4.3.28. Also df -h reports "Not a directory" and java applications will get returned null when calling Java.io.File.getUsableSpace().

biemond · 2015-07-13T10:19:58Z

Same problem with solaris 11.2 also build a new packer image with the latest vbox guest and tested it with vbox5

GuestMemoryBalloon=0                                                                                                                                                                                       
GuestOSType="Solaris_64"                                                                                                                                                                                   
GuestAdditionsRunLevel=2                                                                                                                                                                                   
GuestAdditionsVersion="4.3.18 r96516"                                                                                                                                                                      
GuestAdditionsFacility_VirtualBox Base Driver=50,1436779518422                                                                                                                                             
GuestAdditionsFacility_VirtualBox System Service=50,1436779539574                                                                                                                                          
GuestAdditionsFacility_Seamless Mode=0,1436779518422                                                                                                                                                       
GuestAdditionsFacility_Graphics Mode=0,1436779518422                                                                                                                                                       
DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 32000                                                                                                                                 
DEBUG subprocess: Exit status: 0                                                                                                                                                                           
DEBUG virtualbox_5_0:   - [1, "ssh", 2222, 22]                                                                                                                                                             
DEBUG ssh: Checking whether SSH is ready...                                                                                                                                                                
DEBUG ssh: Re-using SSH connection.                                                                                                                                                                        
 INFO ssh: SSH is ready!                                                                                                                                                                                   
DEBUG ssh: Re-using SSH connection.                                                                                                                                                                        
 INFO ssh: Execute:  (sudo=false)                                                                                                                                                                          
DEBUG ssh: Exit status: 0                                                                                                                                                                                  
DEBUG guest: Searching for cap: mount_virtualbox_shared_folder                                                                                                                                             
DEBUG guest: Checking in: solaris11                                                                                                                                                                        
DEBUG guest: Found cap: mount_virtualbox_shared_folder in solaris11                                                                                                                                        
 INFO guest: Execute capability: mount_virtualbox_shared_folder [#<Vagrant::Machine: default (VagrantPlugins::ProviderVirtualBox::Provider)>, "vagrant", "/vagrant", {:mount_options=>["dmode=777", "fmode=
777"], :guestpath=>"/vagrant", :hostpath=>"C:/projects/fmwplatform-samples/vagrant_chef_puppet_solaris11", :disabled=>false, :owner=>"vagrant", :group=>"vagrant"}] (solaris11)                            
DEBUG ssh: Re-using SSH connection.                                                                                                                                                                        
 INFO ssh: Execute: sudo mkdir -p /vagrant (sudo=false)                                                                                                                                                    
DEBUG ssh: Exit status: 0                                                                                                                                                                                  
DEBUG ssh: Re-using SSH connection.                                                                                                                                                                        
 INFO ssh: Execute: sudo /sbin/mount -F vboxfs -o uid=`/usr/xpg4/bin/id -u vagrant`,gid=`/usr/xpg4/bin/id -g vagrant`,dmode=777,fmode=777 vagrant /vagrant (sudo=false)                                    
DEBUG ssh: Exit status: 0                                                                                                                                                                                  
DEBUG ssh: Re-using SSH connection.                                                                                                                                                                        
 INFO ssh: Execute: sudo chown `/usr/xpg4/bin/id -u vagrant`:`/usr/xpg4/bin/id -g vagrant` /vagrant (sudo=false)                                                                                           
DEBUG ssh: stderr: chown:                                                                                                                                                                                  
DEBUG ssh: stderr: /vagrant: Invalid argument                                                                                                                                                              

DEBUG ssh: Exit status: 1                                                                                                                                                                                  
ERROR warden: Error occurred: The following SSH command responded with a non-zero exit status.                                                                                                             
Vagrant assumes that this means the command failed!                                                                                                                                                        

sudo chown `/usr/xpg4/bin/id -u vagrant`:`/usr/xpg4/bin/id -g vagrant` /vagrant                                                                                                                            

Stdout from the command:                                                                                                                                                                                   


vagrant@solaris-vagrant:~$ sudo mount
/ on rpool/ROOT/solaris read/write/setuid/devices/rstchown/dev=45d0002 on Thu Jan  1 10:00:00 1970
/devices on /devices read/write/setuid/devices/rstchown/dev=8940000 on Mon Jul 13 19:25:04 2015
/dev on /dev read/write/setuid/devices/rstchown/dev=8980000 on Mon Jul 13 19:25:04 2015
/system/contract on ctfs read/write/setuid/devices/rstchown/dev=8a40001 on Mon Jul 13 19:25:04 2015
/proc on proc read/write/setuid/devices/rstchown/dev=89c0000 on Mon Jul 13 19:25:04 2015
/etc/mnttab on mnttab read/write/setuid/devices/rstchown/dev=8a80001 on Mon Jul 13 19:25:04 2015
/system/volatile on swap read/write/setuid/devices/rstchown/xattr/dev=8ac0001 on Mon Jul 13 19:25:04 2015
/system/object on objfs read/write/setuid/devices/rstchown/dev=8b00001 on Mon Jul 13 19:25:04 2015
/etc/dfs/sharetab on sharefs read/write/setuid/devices/rstchown/dev=8b40001 on Mon Jul 13 19:25:04 2015
/lib/libc.so.1 on /usr/lib/libc/libc_hwcap1.so.1 read/write/setuid/devices/rstchown/dev=45d0002 on Mon Jul 13 19:25:14 2015
/dev/fd on fd read/write/setuid/devices/rstchown/dev=8c80001 on Mon Jul 13 19:25:17 2015
/var on rpool/ROOT/solaris/var read/write/setuid/devices/rstchown/nonbmand/exec/xattr/atime/dev=45d0003 on Mon Jul 13 19:25:18 2015
/tmp on swap read/write/setuid/devices/rstchown/xattr/dev=8ac0002 on Mon Jul 13 19:25:18 2015
/var/share on rpool/VARSHARE read/write/setuid/devices/rstchown/nonbmand/exec/xattr/atime/dev=45d0004 on Mon Jul 13 19:25:18 2015
/export on rpool/export read/write/setuid/devices/rstchown/nonbmand/exec/xattr/atime/dev=45d0005 on Mon Jul 13 19:25:36 2015
/export/home on rpool/export/home read/write/setuid/devices/rstchown/nonbmand/exec/xattr/atime/dev=45d0006 on Mon Jul 13 19:25:37 2015
/export/home/vagrant on rpool/export/home/vagrant read/write/setuid/devices/rstchown/nonbmand/exec/xattr/atime/dev=45d0007 on Mon Jul 13 19:25:37 2015
/rpool on rpool read/write/setuid/devices/rstchown/nonbmand/exec/xattr/atime/dev=45d0008 on Mon Jul 13 19:25:37 2015
/system/zones on rpool/VARSHARE/zones read/write/setuid/devices/rstchown/nonbmand/exec/xattr/atime/dev=45d0009 on Mon Jul 13 19:25:37 2015
/var/share/pkg on rpool/VARSHARE/pkg read/write/setuid/devices/rstchown/nonbmand/exec/xattr/atime/dev=45d000a on Mon Jul 13 19:25:38 2015
/var/share/pkg/repositories on rpool/VARSHARE/pkg/repositories read/write/setuid/devices/rstchown/nonbmand/exec/xattr/atime/dev=45d000b on Mon Jul 13 19:25:38 2015
/vagrant on vagrant read/write/setuid/devices/rstchown/uid=100/gid=10/dmode=777/fmode=777/stat_ttl=200/dev=8d40001 on Mon Jul 13 19:25:55 2015


vagrant@solaris-vagrant:~$ sudo ls -l /vagrant
/vagrant: Invalid argument

ghost · 2015-07-13T10:22:19Z

I'm able to get around this issue by manually removing the UNC prefix (\?) from the shared folder path. (Running VBox 5.0 on Windows 7, Ubuntu 14.4 guest, latest guest additions)

orf · 2015-07-13T10:23:01Z

I'm hitting this as well on Windows 7. Rolling back to vbox 4 solved it.

vadviktor · 2015-07-13T10:30:44Z

Host Win8.1, guest Ubuntu Trusty. I have tried to build a new machine with packer and this time manually created /vagrant with every right and ownership given to the user vagrant I could, but still I get this (in debug mode). I also checked manually that the directory exists and still full accessible to vagrant, but it still fails.

Note: I think there are some valuable info at the very end, describing unicode chars.

>
ERROR vagrant: The following SSH command responded with a non-zero exit status.
Vagrant assumes that this means the command failed!

chown `id -u vagrant`:`id -g vagrant` /vagrant

Stdout from the command:



Stderr from the command:

stdin: is not a tty
chown: changing ownership of ���/vagrant���: Not a directory

ERROR vagrant: C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.7.3/plugins/communicators/ssh/communicator.rb:236:in `e
xecute'
C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.7.3/plugins/communicators/ssh/communicator.rb:246:in `sudo'
C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.7.3/plugins/guests/linux/cap/mount_virtualbox_shared_folder.rb:79:in `
mount_virtualbox_shared_folder'
C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.7.3/lib/vagrant/capability_host.rb:111:in `call'
C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.7.3/lib/vagrant/capability_host.rb:111:in `capability'
C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.7.3/lib/vagrant/guest.rb:43:in `capability'
C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.7.3/plugins/providers/virtualbox/synced_folder.rb:51:in `block in enab
le'
C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.7.3/plugins/providers/virtualbox/synced_folder.rb:35:in `each'
C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.7.3/plugins/providers/virtualbox/synced_folder.rb:35:in `enable'
C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.7.3/lib/vagrant/action/builtin/synced_folders.rb:92:in `block in call'

C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.7.3/lib/vagrant/action/builtin/synced_folders.rb:89:in `each'
C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.7.3/lib/vagrant/action/builtin/synced_folders.rb:89:in `call'
C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.7.3/lib/vagrant/action/warden.rb:34:in `call'
C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.7.3/lib/vagrant/action/builtin/synced_folder_cleanup.rb:28:in `call'
C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.7.3/lib/vagrant/action/warden.rb:34:in `call'
C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.7.3/plugins/synced_folders/nfs/action_cleanup.rb:19:in `call'
C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.7.3/lib/vagrant/action/warden.rb:34:in `call'
C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.7.3/plugins/providers/virtualbox/action/prepare_nfs_valid_ids.rb:12:in
 `call'
C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.7.3/lib/vagrant/action/warden.rb:34:in `call'
C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.7.3/lib/vagrant/action/builtin/handle_forwarded_port_collisions.rb:160
:in `handle'
C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.7.3/lib/vagrant/action/builtin/handle_forwarded_port_collisions.rb:42:
in `block in call'
C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.7.3/lib/vagrant/environment.rb:516:in `lock'
C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.7.3/lib/vagrant/action/builtin/handle_forwarded_port_collisions.rb:41:
in `call'
C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.7.3/lib/vagrant/action/warden.rb:34:in `call'
C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.7.3/plugins/providers/virtualbox/action/prepare_forwarded_port_collisi
on_params.rb:30:in `call'
C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.7.3/lib/vagrant/action/warden.rb:34:in `call'
C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.7.3/lib/vagrant/action/builtin/env_set.rb:19:in `call'
C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.7.3/lib/vagrant/action/warden.rb:34:in `call'
C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.7.3/lib/vagrant/action/builtin/provision.rb:80:in `call'
C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.7.3/lib/vagrant/action/warden.rb:34:in `call'
C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.7.3/plugins/providers/virtualbox/action/clear_forwarded_ports.rb:15:in
 `call'
C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.7.3/lib/vagrant/action/warden.rb:34:in `call'
C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.7.3/plugins/providers/virtualbox/action/set_name.rb:50:in `call'
C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.7.3/lib/vagrant/action/warden.rb:34:in `call'
C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.7.3/plugins/providers/virtualbox/action/clean_machine_folder.rb:17:in
`call'
C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.7.3/lib/vagrant/action/warden.rb:34:in `call'
C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.7.3/plugins/providers/virtualbox/action/check_accessible.rb:18:in `cal
l'
C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.7.3/lib/vagrant/action/warden.rb:34:in `call'
C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.7.3/lib/vagrant/action/warden.rb:95:in `block in finalize_action'
C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.7.3/lib/vagrant/action/warden.rb:34:in `call'
C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.7.3/lib/vagrant/action/warden.rb:34:in `call'
C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.7.3/lib/vagrant/action/builder.rb:116:in `call'
C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.7.3/lib/vagrant/action/runner.rb:66:in `block in run'
C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.7.3/lib/vagrant/util/busy.rb:19:in `busy'
C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.7.3/lib/vagrant/action/runner.rb:66:in `run'
C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.7.3/lib/vagrant/action/builtin/call.rb:53:in `call'
C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.7.3/lib/vagrant/action/warden.rb:34:in `call'
C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.7.3/lib/vagrant/action/warden.rb:95:in `block in finalize_action'
C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.7.3/lib/vagrant/action/warden.rb:34:in `call'
C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.7.3/lib/vagrant/action/warden.rb:34:in `call'
C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.7.3/lib/vagrant/action/builder.rb:116:in `call'
C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.7.3/lib/vagrant/action/runner.rb:66:in `block in run'
C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.7.3/lib/vagrant/util/busy.rb:19:in `busy'
C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.7.3/lib/vagrant/action/runner.rb:66:in `run'
C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.7.3/lib/vagrant/action/builtin/call.rb:53:in `call'
C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.7.3/lib/vagrant/action/warden.rb:34:in `call'
C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.7.3/lib/vagrant/action/warden.rb:95:in `block in finalize_action'
C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.7.3/lib/vagrant/action/warden.rb:34:in `call'
C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.7.3/lib/vagrant/action/warden.rb:34:in `call'
C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.7.3/lib/vagrant/action/builder.rb:116:in `call'
C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.7.3/lib/vagrant/action/runner.rb:66:in `block in run'
C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.7.3/lib/vagrant/util/busy.rb:19:in `busy'
C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.7.3/lib/vagrant/action/runner.rb:66:in `run'
C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.7.3/lib/vagrant/action/builtin/call.rb:53:in `call'
C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.7.3/lib/vagrant/action/warden.rb:34:in `call'
C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.7.3/lib/vagrant/action/builtin/box_check_outdated.rb:23:in `call'
C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.7.3/lib/vagrant/action/warden.rb:34:in `call'
C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.7.3/lib/vagrant/action/builtin/config_validate.rb:25:in `call'
C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.7.3/lib/vagrant/action/warden.rb:34:in `call'
C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.7.3/plugins/providers/virtualbox/action/check_virtualbox.rb:17:in `cal
l'
C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.7.3/lib/vagrant/action/warden.rb:34:in `call'
C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.7.3/lib/vagrant/action/warden.rb:95:in `block in finalize_action'
C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.7.3/lib/vagrant/action/warden.rb:34:in `call'
C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.7.3/lib/vagrant/action/warden.rb:34:in `call'
C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.7.3/plugins/providers/virtualbox/action/match_mac_address.rb:16:in `ca
ll'
C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.7.3/lib/vagrant/action/warden.rb:34:in `call'
C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.7.3/plugins/providers/virtualbox/action/import.rb:32:in `call'
C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.7.3/lib/vagrant/action/warden.rb:34:in `call'
C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.7.3/plugins/providers/virtualbox/action/customize.rb:40:in `call'
C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.7.3/lib/vagrant/action/warden.rb:34:in `call'
C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.7.3/plugins/providers/virtualbox/action/check_accessible.rb:18:in `cal
l'
C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.7.3/lib/vagrant/action/warden.rb:34:in `call'
C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.7.3/lib/vagrant/action/warden.rb:95:in `block in finalize_action'
C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.7.3/lib/vagrant/action/warden.rb:34:in `call'
C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.7.3/lib/vagrant/action/warden.rb:34:in `call'
C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.7.3/lib/vagrant/action/builder.rb:116:in `call'
C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.7.3/lib/vagrant/action/runner.rb:66:in `block in run'
C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.7.3/lib/vagrant/util/busy.rb:19:in `busy'
C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.7.3/lib/vagrant/action/runner.rb:66:in `run'
C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.7.3/lib/vagrant/action/builtin/call.rb:53:in `call'
C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.7.3/lib/vagrant/action/warden.rb:34:in `call'
C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.7.3/lib/vagrant/action/builtin/config_validate.rb:25:in `call'
C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.7.3/lib/vagrant/action/warden.rb:34:in `call'
C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.7.3/lib/vagrant/action/warden.rb:95:in `block in finalize_action'
C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.7.3/lib/vagrant/action/warden.rb:34:in `call'
C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.7.3/lib/vagrant/action/warden.rb:34:in `call'
C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.7.3/lib/vagrant/action/builtin/handle_box.rb:56:in `call'
C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.7.3/lib/vagrant/action/warden.rb:34:in `call'
C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.7.3/lib/vagrant/action/warden.rb:95:in `block in finalize_action'
C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.7.3/lib/vagrant/action/warden.rb:34:in `call'
C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.7.3/lib/vagrant/action/warden.rb:34:in `call'
C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.7.3/lib/vagrant/action/builder.rb:116:in `call'
C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.7.3/lib/vagrant/action/runner.rb:66:in `block in run'
C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.7.3/lib/vagrant/util/busy.rb:19:in `busy'
C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.7.3/lib/vagrant/action/runner.rb:66:in `run'
C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.7.3/lib/vagrant/action/builtin/call.rb:53:in `call'
C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.7.3/lib/vagrant/action/warden.rb:34:in `call'
C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.7.3/plugins/providers/virtualbox/action/check_virtualbox.rb:17:in `cal
l'
C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.7.3/lib/vagrant/action/warden.rb:34:in `call'
C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.7.3/lib/vagrant/action/builder.rb:116:in `call'
C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.7.3/lib/vagrant/action/runner.rb:66:in `block in run'
C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.7.3/lib/vagrant/util/busy.rb:19:in `busy'
C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.7.3/lib/vagrant/action/runner.rb:66:in `run'
C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.7.3/lib/vagrant/machine.rb:214:in `action_raw'
C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.7.3/lib/vagrant/machine.rb:191:in `block in action'
C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.7.3/lib/vagrant/environment.rb:516:in `lock'
C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.7.3/lib/vagrant/machine.rb:178:in `call'
C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.7.3/lib/vagrant/machine.rb:178:in `action'
C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.7.3/lib/vagrant/batch_action.rb:82:in `block (2 levels) in run'
 INFO interface: error: The following SSH command responded with a non-zero exit status.
Vagrant assumes that this means the command failed!

chown `id -u vagrant`:`id -g vagrant` /vagrant

Stdout from the command:



Stderr from the command:

stdin: is not a tty
chown: changing ownership of ���/vagrant���: Not a directory

The following SSH command responded with a non-zero exit status.
Vagrant assumes that this means the command failed!

chown `id -u vagrant`:`id -g vagrant` /vagrant

Stdout from the command:



Stderr from the command:

stdin: is not a tty
chown: changing ownership of ���/vagrant���: Not a directory
 INFO interface: Machine: error-exit ["Vagrant::Errors::VagrantError", "The following SSH command responded with a non-z
ero exit status.\nVagrant assumes that this means the command failed!\n\nchown `id -u vagrant`:`id -g vagrant` /vagrant\
n\nStdout from the command:\n\n\n\nStderr from the command:\n\nstdin: is not a tty\nchown: changing ownership of \xE2\x8
0\x98/vagrant\xE2\x80\x99: Not a directory\n"]

vadviktor · 2015-07-13T10:37:28Z

Some more debug info:

not even root can access /vagrant directory 💣
mount shows vagrant on /vagrant type vboxsf (uid=1000,gid=1000,rw)
shows in /etc/mtab : vagrant /vagrant vboxsf uid=1000,gid=1000,rw 0 0
does not work even if I use admin account on host to issue vagrant up (like in the case of Vmware)

Anyone knows how to debug this further please share the steps I should make to provide more info, thanks!

cristovaov · 2015-07-13T12:04:03Z

+1 on Win8.1 + 1.7.3 + VB5
I have a feeling that the error comes from changes in 45e14a8 but I have yet to test this by reverting the changes to the previous version. If somebody wants to give it a go?
I determined this by comparing the shared folders in the VB GUI - the paths look different.

rapliandras · 2015-07-13T13:58:00Z

+1 on Win7x64 + vbox 5.0

bylevel · 2015-07-13T14:38:18Z

in C:\HashiCorp\Vagrant\embedded\gems\gems\vagrant-1.7.3\plugins\providers\virtualbox\driver\version_5_0.rb

to temporarily fix this problem.

sethvargo · 2015-07-13T14:45:38Z

Hi all,

We have confirmed this is a bug and will fix it in 1.7.4 ASAP. Sorry about the regression!

ptantiku · 2015-07-13T14:57:04Z

I guess because of this workaround, maybe? #4815

RobWin · 2016-01-19T14:42:31Z

Windows 7 + Vagrant 1.8.1 + VirtualBox 5.0.12 works for me as well.

BlurryFlurry · 2016-01-24T10:18:30Z

@TehJoE
I am confirming windows 10 + Vagrant 1.8.1 + VirtualBox 5.0.4 have this issue, but upgrading to VirtualBox-5.0.14 fixed it.

rvoortman · 2016-01-26T13:24:20Z

Confirmed Windows 7 + Vagrant 1.8.1 + VirtualBox 5.0.4rc1
I am now trying to update to Virtualbox 5.0.14

EDIT: Update fixed the problems too

lindblandro · 2016-01-26T14:21:09Z

I have this on Windows 7 + Vagrant 1.8.1 + Virtualbox 4.3.32. The fix proposed by @lookfwd resolved the issue.

metuero · 2016-01-26T16:09:02Z

Windows 7 + Vagrant 1.8.1 + VirtualBox updated to 5.0.14 works. Thanks @TehJoE.

fabMrc · 2016-02-02T09:52:11Z

windows 7 64bits + vagrant 1.8.1 + virtualbox 5.0.8 with the fix proposed bu @lookfwd is ok
thanks

mittork · 2016-02-07T17:38:11Z

Can confirm the issue is present in Windows 10 + Vagrant 1.8.1 + VirtualBox 5.0.8, but updating to VirtualBox 5.0.14 fixed it for me. Thanks @TehJoE

Maelstromeous · 2016-02-14T14:47:43Z

This is still an issue on Windows 7 + Vagrant 1.8.1 + Virtualbox 5.0.2. Updating Virtualbox to 5.0.14 corrects the issue.

danabrey · 2016-02-21T15:48:36Z

Updating VirtualBox from 5.0.2 to 5.0.14 fixed this issue for me, too.

donpapa26 · 2016-02-24T15:12:41Z

Updating VirtualBox from 5.0.8 to 5.0.14 fixed this issue for m.

mablae · 2016-02-27T22:57:29Z

@donpapa26 @danabrey Thanks. Also for me. Windows 7 x64 Host.

andrevanwinssen · 2016-02-28T15:13:42Z

I am using vagrant 1.8.1, win10, VB 5.0.14 but I still get this error: INFO interface: Machine: error-exit ["Vagrant::Errors::VagrantError", "The SSH command responded with a non-zero exit status. Vagrant\nassumes that this means the command failed. The output for this command\nshould be in the log above. Please read the output to determine what\nwent wrong."]

Suui · 2016-03-01T18:27:34Z

Updating VirtualBox to 5.0.14 also fixed the issue for me.

michaelpanco · 2016-03-02T09:20:26Z

I also updated my VirtualBox to 5.0.14, and works fine now. 👍

mufid · 2016-03-14T08:14:20Z

Happened to me, too. I am using Windows 7 and Virtual Box 5.0.4

Then i upgraded to 5.0.16. Works like a charm 👍

rhabegger · 2016-03-17T08:12:55Z

Happened to me too on Windows 7 - Vagrant 1.8.1 - Virtualbox 5.0.16 r105871 ....

I had to apply the patch of @lookfwd and everything worked ... Thanks a lot !

[EDIT] => problem seem to be varying ...

new error log :
timeout during server version negotiating
ERROR vagrant: C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.1/plugins/communicators/ssh/communicator.rb:429:in `rescue in connect'

Marabyte · 2016-03-31T11:18:25Z

Updating Virtualbox to 5.0.16 did the trick.

sohilsharma · 2016-04-01T06:47:20Z

Same issue Window 8 Pro, Vagrant 1.8.1 , Virtual Box : 5.0.4

kamito300 · 2016-04-11T11:07:16Z

Updating virtualbox from 5.0.6 to 5.0.16 can fix this issue for me.:+1:

apollo-io · 2016-04-13T21:16:20Z

Same as @biemond for me, running Solaris 11 vbox (on windows client).

I've tried VirtualBox 5.0.12, 14 and 16. Re-installing vagrant, as well as Ruby 1.9.3 and 2.1.6. I don't get this with CentOS boxes.

00;32m==> solaris-11-x64-agent: Mounting shared folders...
00;32m solaris-11-x64-agent: /vagrant => C:/Users/mcreed1/sandbox-2015-12-23/loglogic/.vagrant/be
aker_vagrant_files/solaris11.yml
C:/apps/ruby/2.1.6/Ruby21-x64/lib/ruby/gems/2.1.0/gems/beaker-2.39.0/lib/beaker/hypervisor/vagrant.rb:196:in `
block (2 levels) in vagrant_cmd'
: Failed to exec 'vagrant up'. Error was The following SSH command responded with a non-zero exit status. (Run
timeError)
Vagrant assumes that this means the command failed!

sudo chown /usr/xpg4/bin/id -u vagrant:/usr/xpg4/bin/id -g vagrant /vagrant

Stdout from the command:

Stderr from the command:

chown: /vagrant: Invalid argument
from C:/apps/ruby/2.1.6/Ruby21-x64/lib/ruby/2.1.0/open3.rb:199:in popen_run' from C:/apps/ruby/2.1.6/Ruby21-x64/lib/ruby/2.1.0/open3.rb:93:inpopen3'
from C:/apps/ruby/2.1.6/Ruby21-x64/lib/ruby/gems/2.1.0/gems/beaker-2.39.0/lib/beaker/hypervisor/vagrant.rb
:191:in block in vagrant_cmd' from C:/apps/ruby/2.1.6/Ruby21-x64/lib/ruby/gems/2.1.0/gems/beaker-2.39.0/lib/beaker/hypervisor/vagrant.rb :189:inchdir'
from C:/apps/ruby/2.1.6/Ruby21-x64/lib/ruby/gems/2.1.0/gems/beaker-2.39.0/lib/beaker/hypervisor/vagrant.rb
:189:in vagrant_cmd' from C:/apps/ruby/2.1.6/Ruby21-x64/lib/ruby/gems/2.1.0/gems/beaker-2.39.0/lib/beaker/hypervisor/vagrant.rb :151:inprovision'
from C:/apps/ruby/2.1.6/Ruby21-x64/lib/ruby/gems/2.1.0/gems/beaker-2.39.0/lib/beaker/hypervisor.rb:75:in create' from C:/apps/ruby/2.1.6/Ruby21-x64/lib/ruby/gems/2.1.0/gems/beaker-2.39.0/lib/beaker/network_manager.rb:69 :inblock in provision'
from C:/apps/ruby/2.1.6/Ruby21-x64/lib/ruby/gems/2.1.0/gems/beaker-2.39.0/lib/beaker/network_manager.rb:68
:in each_key' from C:/apps/ruby/2.1.6/Ruby21-x64/lib/ruby/gems/2.1.0/gems/beaker-2.39.0/lib/beaker/network_manager.rb:68 :inprovision'
from C:/apps/ruby/2.1.6/Ruby21-x64/lib/ruby/gems/2.1.0/gems/beaker-rspec-5.3.0/lib/beaker-rspec/beaker_shi
m.rb:35:in provision' from C:/apps/ruby/2.1.6/Ruby21-x64/lib/ruby/gems/2.1.0/gems/beaker-rspec-5.3.0/lib/beaker-rspec/spec_helpe r.rb:46:inblock in <top (required)>'
from C:/apps/ruby/2.1.6/Ruby21-x64/lib/ruby/gems/2.1.0/gems/rspec-core-3.4.4/lib/rspec/core.rb:97:in conf igure' from C:/apps/ruby/2.1.6/Ruby21-x64/lib/ruby/gems/2.1.0/gems/beaker-rspec-5.3.0/lib/beaker-rspec/spec_helpe r.rb:5:in<top (required)>'
from C:/Users/mcreed1/sandbox-2015-12-23/loglogic/spec/spec_helper_acceptance.rb:1:in require' from C:/Users/mcreed1/sandbox-2015-12-23/loglogic/spec/spec_helper_acceptance.rb:1:in<top (required)>'
from C:/Users/mcreed1/sandbox-2015-12-23/loglogic/spec/acceptance/class_spec.rb:1:in require' from C:/Users/mcreed1/sandbox-2015-12-23/loglogic/spec/acceptance/class_spec.rb:1:in<top (required)>'
from C:/apps/ruby/2.1.6/Ruby21-x64/lib/ruby/gems/2.1.0/gems/rspec-core-3.4.4/lib/rspec/core/configuration.
rb:1361:in load' from C:/apps/ruby/2.1.6/Ruby21-x64/lib/ruby/gems/2.1.0/gems/rspec-core-3.4.4/lib/rspec/core/configuration. rb:1361:inblock in load_spec_files'
from C:/apps/ruby/2.1.6/Ruby21-x64/lib/ruby/gems/2.1.0/gems/rspec-core-3.4.4/lib/rspec/core/configuration.
rb:1359:in each' from C:/apps/ruby/2.1.6/Ruby21-x64/lib/ruby/gems/2.1.0/gems/rspec-core-3.4.4/lib/rspec/core/configuration. rb:1359:inload_spec_files'
from C:/apps/ruby/2.1.6/Ruby21-x64/lib/ruby/gems/2.1.0/gems/rspec-core-3.4.4/lib/rspec/core/runner.rb:106:
in setup' from C:/apps/ruby/2.1.6/Ruby21-x64/lib/ruby/gems/2.1.0/gems/rspec-core-3.4.4/lib/rspec/core/runner.rb:92:i nrun'
from C:/apps/ruby/2.1.6/Ruby21-x64/lib/ruby/gems/2.1.0/gems/rspec-core-3.4.4/lib/rspec/core/runner.rb:78:i
n run' from C:/apps/ruby/2.1.6/Ruby21-x64/lib/ruby/gems/2.1.0/gems/rspec-core-3.4.4/lib/rspec/core/runner.rb:45:i ninvoke'
from C:/apps/ruby/2.1.6/Ruby21-x64/lib/ruby/gems/2.1.0/gems/rspec-core-3.4.4/exe/rspec:4:in `

'

atanl · 2016-04-28T08:19:48Z

Windows 10 + Vagrant 1.8.1 + VirtualBox updated to 5.0.18 works. Thanks @TehJoE.

GreatYYX · 2016-05-10T05:12:37Z

Win 7 + Vagrant 1.8.1 + VBox 5.0.4 has the same problem, @bylevel 's method could solve it.
Updating VBox to 5.0.20 works well.

SNathJr · 2016-06-28T06:23:45Z

SOLUTION-1[level-easy]
Assuming you do not have some important files in your box; simply
WARNING - This process all data in your vagrant-box

Open Git Bash
Go to the folder where your vagrant file is
Remove your box by vagrant destroy
remove your old vagrantfile manually
uninstall Virtualbox - resets network interfaces
restart your system
re-do your vagrant init ubuntu/trusty64; vagrant up
[this will download and install virtualbox and your vagrant-box (for me it was ubuntu/trusty64; you may choose your own box)]
and voila your shared folder works

SOLUTION-2:
This problem is due to a disabled virtualbox network interface
Re-enable the networking interfaces to get things worked.

csi0n · 2016-07-12T10:57:51Z

@bylevel his anwser fix my problem,thank you!

sethvargo added the bug label Jul 11, 2015

sethvargo added this to the 1.7.4 milestone Jul 11, 2015

sethvargo added the host/windows label Jul 12, 2015

danwall mentioned this issue Jul 12, 2015

Homestead does not work on VirtualBox 5 laravel/framework#9594

Closed

okinaka mentioned this issue Jul 13, 2015

Default /vagrant shared folder fails on Virtualbox #5952

Closed

cristovaov mentioned this issue Jul 13, 2015

should fix https://github.com/mitchellh/vagrant/issues/5933 #5955

Closed

dakotabenjamin mentioned this issue Feb 3, 2016

vagrant up ... chown fails. OpenDroneMap/ODM#241

Closed

Maelstromeous mentioned this issue Feb 14, 2016

Error: chown: changing ownership of â?~/var/wwwâ?T: Not a directory puphpet/puphpet#2171

Closed

frdmn mentioned this issue Feb 18, 2016

SSH Command failed mohatt/dashbrew#48

Closed

rossi-fi mentioned this issue Jul 12, 2016

vagrant unable to mount UNC path in 1.8 or 1.8.1 #7011

Closed

lukasz-karolewski mentioned this issue Mar 10, 2017

Windows UNC path is crashing with \\\\?\\ prefix #8352

Closed

ghost locked and limited conversation to collaborators Apr 4, 2020

Unable to mount /vagrant folder in 1.7.3 #5933

Unable to mount /vagrant folder in 1.7.3 #5933

Comments

F21 commented Jul 11, 2015

vany-egorov commented Jul 11, 2015

JeroenED commented Jul 11, 2015

tinda commented Jul 11, 2015

Ventajou commented Jul 11, 2015

YAmikep commented Jul 12, 2015

ghost commented Jul 12, 2015

d-ph commented Jul 12, 2015

fbezdeka commented Jul 12, 2015

jarosluv commented Jul 12, 2015

edwin-egalite commented Jul 13, 2015

androidjustme commented Jul 13, 2015

julestruong commented Jul 13, 2015

ckulla commented Jul 13, 2015

oxygen0211 commented Jul 13, 2015

biemond commented Jul 13, 2015

ghost commented Jul 13, 2015

orf commented Jul 13, 2015

vadviktor commented Jul 13, 2015

vadviktor commented Jul 13, 2015

cristovaov commented Jul 13, 2015

rapliandras commented Jul 13, 2015

bylevel commented Jul 13, 2015

sethvargo commented Jul 13, 2015

ptantiku commented Jul 13, 2015

RobWin commented Jan 19, 2016

BlurryFlurry commented Jan 24, 2016

rvoortman commented Jan 26, 2016

lindblandro commented Jan 26, 2016

metuero commented Jan 26, 2016

fabMrc commented Feb 2, 2016

mittork commented Feb 7, 2016

Maelstromeous commented Feb 14, 2016

danabrey commented Feb 21, 2016

donpapa26 commented Feb 24, 2016

mablae commented Feb 27, 2016

andrevanwinssen commented Feb 28, 2016

Suui commented Mar 1, 2016

michaelpanco commented Mar 2, 2016

mufid commented Mar 14, 2016

rhabegger commented Mar 17, 2016

Marabyte commented Mar 31, 2016

sohilsharma commented Apr 1, 2016

kamito300 commented Apr 11, 2016

apollo-io commented Apr 13, 2016

atanl commented Apr 28, 2016

GreatYYX commented May 10, 2016

SNathJr commented Jun 28, 2016

csi0n commented Jul 12, 2016