Unable to mount /vagrant folder in 1.7.3

[F21]

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

[vany-egorov]

+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]

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]

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]

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

[YAmikep]

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]

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

[d-ph]

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]

+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]

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

Has anyone found way to fast fix?

[edwin-egalite]

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

[androidjustme]

Exactly the same problem here with VirtualBox 5.0 and Vagrant 1.7.3

[julestruong]

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

[ckulla]

Same here, vagrant 1.7.3, windows 7

[oxygen0211]

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]

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]

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]

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

[vadviktor]

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]

Some more debug info:

• not even root can access /vagrant directory :bomb:
• 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]

+1 on Win8.1 + 1.7.3 + VB5
I have a feeling that the error comes from changes in https://github.com/mitchellh/vagrant/commit/45e14a8dc45cb56b8f50acffb3a6490aa953aec1 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]

+1 on Win7x64 + vbox 5.0

[bylevel]

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]

Hi all,

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

[ptantiku]

I guess because of this workaround, maybe? https://github.com/mitchellh/vagrant/issues/4815

[sethvargo]

This issue is that there is a special "fancy" comma that snuck into the codebase.

[mitchellh]

Fixed with the above commit. I'm not sure why we added the UNC thing so I kept it commented so we can look into it, but just reverting it for 1.7.4 to fix the regression.

[rfc1459]

(Sorry for commenting on a closed bug, just adding some reference)

@mitchellh: a quick search turned up #5495 - essentially, UNC paths are needed because Windows would otherwise cap PATH_MAX to 256 chars and break some setups (long path below PATH_MAX in the guest + long base path below PATH_MAX in the host == complete host path over PATH_MAX).

This seems to be a regression on VirtualBox's end introduced somewhere between 4.3.28 and 5.0.

[thiagotalma]

@mitchellh When can we expect to version 1.7.4?

I look forward. :wink:

[sethvargo]

Hi @thiagotalma

We plan to get 1.7.4 out sometime this week. Thanks!

[simonthum]

@thiagotalma I just fixed this by hand-editing the file in Vagrant/embedded/gems/gems/vagrant-1.7.3/plugins/providers/virtualbox/driver/version_5_0.rb using christoavov's commit. No need to wait.

[cristovaov]

@simonthum 'cris' without an 'h' ;)
I should have perhaps commented here about it but at the same time thought you'd all be notified of my PR. And it's also me being cautious, I wouldn't want to break your installs :)

[simonthum]

@cristovaov Sorry for the h! I will pay more attention next time ;) FWIW I don't think you missed something, all fine.

I just needed a quick fix and what I describe above worked well. Of course no one should follow my suggestion if there is no very immediate need to do so! A Virtualbox downgrade should work just as well and does not fetch you an unsupported installation.

[rfc1459]

@simonthum: there is no point in downgrading Vagrant, the issue at play here is VirtualBox 5.0 rejecting UNC paths. Vagrant 1.7.3 with VirtualBox 4.3.x works just fine.

Just for the record, has anybody raised the issue on vbox's bug tracker?

[tkprocat]

I reckon it's this: https://www.virtualbox.org/ticket/14252

[simonthum]

@rfc1459 I was actually talking about downgrading virtualbox, but left that unstated, sry. For me the issue was caused when upgrading VB (due to security issues of VB).

[cristovaov]

@rfc1459 VB5 is not rejecting UNC paths as the fix I have PR'ed a couple of days ago seems to work.

Some more info I forgot to mention previously in this convo: In a Vagrant install performed with the MSI installer the file I changed with the submitted fix was: C:\HashiCorp\Vagrant\embedded\gems\gems\vagrant-1.7.3\lib\vagrant\util\platform.rb

With all this said I do feel that there was a change in VB how they handle UNC paths for Windows hence the regression we, Windows users are encountering~

[rschuetzler]

@simonthum I don't see any line in Vagrant/embedded/gems/gems/vagrant-1.7.3/plugins/providers/virtualbox/driver/version_5_0.rb to replace. Could you tell me what you did?

[F21]

@rschuetzler Just comment the lines as per this commit: https://github.com/mitchellh/vagrant/commit/b118ab10c8e0f8e62a547249805f05240e6e4ee9

[gccpacman]

Thanks for fixing this, looking forward to version 1.7.4

[denieler]

+1 on Windows 10, Vagrant 1.7.3, Virtual Box 5.0. Thank you for fixing!

[colinwilson]

Thanks. Took me way longer than I'd like to admit to find this. Look forward to v1.7.4

[hydrosquall]

+1 on Windows 7, Virtual Box 5.0, Vagrant 1.7.3. Thanks for fixing!

Filepath for me was this one as well (since multiple filepaths have been floating around) Vagrant/embedded/gems/gems/vagrant-1.7.3/plugins/providers/virtualbox/driver/version_5_0.rb

[F21]

For those looking for 1.7.4 binaries, they are available here: https://bintray.com/mitchellh/vagrant/vagrant/1.7.4/view#files

[USvER]

Still have this issue... Windows 7 + Vagrant 1.7.4 + VirtualBox 5.0

[vadviktor]

Just a feedback here, me on Win 10, VB 5, Vagrant 1.7.4 works great.

On 4 Aug 2015 17:32, "USvER" notifications@github.com wrote:

Still have this issue... Windows 7 + Vagrant 1.7.4 + VirtualBox 5.0

— Reply to this email directly or view it on GitHub https://github.com/mitchellh/vagrant/issues/5933#issuecomment-127650360.

[saraf]

Does the fix for this remove support for long filepaths? (vagrant 1.7.4) Because it says in version_5_0.rb near line 500

Removed for GH-5933 until further research.

UNC long path support is a pretty important use case for vagrant+windows+node.js stacks.

Currently, I am managing by going back to virtualbox 4.3.30 and patching version_4_3.rb with

-       folder[:hostpath]]
+      '\\\\?\\' + folder[:hostpath].gsub(/[\/\\]/,'\\')]

as suggested in https GH-4815 Thanks for all the good work!

(Win 10 host + Virtualbox 4.3.30 r 10610 + Ubuntu trusty 64 guest)

[tn3rb]

Had this same issue using Windows 10 + VirtualBox-5.0.2-102096-Win.exe + Vagrant 1.7.3

Uninstalled Vagrant 1.7.3 then ran the 1.7.4.msi found here: https://bintray.com/mitchellh/vagrant/vagrant/1.7.4/view#files

Confirmed that EVERYTHING WORKS GREAT

[edit] VirtualBox-5.0.2-102096-Win.exe can be found here: https://www.virtualbox.org/wiki/Testbuilds

[keeprock]

Confirm working on:

• Mac OS X 10.10
• Vagrant 1.7.4 https://bintray.com/mitchellh/vagrant/vagrant/1.7.4/view#files
• VirtualBox 5.0.11 r104456 https://www.virtualbox.org/download/testcase/VirtualBox-5.0.11-104456-OSX.dmg

I'm also running Homestead and previously have issues with response time. After installing latest versions of Vagrant and VirtualBox (I'm using nfs mode) response improved significantly.

[exuan]

it is nice

[hickeroar]

This seems to have come back in 1.8.0/1.8.1