Ticket #14434 (closed defect: fixed)
VirtualBox on Windows10 creates symlinks as backslashes => Fixed in SVN
Reported by: | kouik | Owned by: | |
---|---|---|---|
Component: | other | Version: | VirtualBox 5.0.0 |
Keywords: | vbox, links, symlinks, ubuntu | Cc: | |
Guest type: | Windows | Host type: | Linux |
Description
Hi,
Running Windows 10 Home edition, vagrant 1.7.4, vbox 5.0.1, and an Ubuntu14.04 64bits box.
Just noticed the following behavior : When logged in on the VM as vagrant user, i cannot create a symlink, it will create a symlink using backslashes instead of forward slashes.
See commands below.
vagrant@vvv:/srv/www/wordpress-default/wp-content$ ln -s /srv/wpca-plugins plugins vagrant@vvv:/srv/www/wordpress-default/wp-content$ ls -al total 13 drwxrwxr-x 1 www-data vagrant 4096 Aug 13 12:23 . drwxrwxr-x 1 www-data vagrant 4096 Aug 13 12:20 .. -rwxrwxr-- 1 www-data vagrant 28 Aug 13 12:03 index.php drwxrwxr-x 1 www-data vagrant 4096 Aug 13 12:04 languages lrwxrwxr-- 1 www-data vagrant 0 Aug 13 12:23 plugins -> \srv\wpca-plugins lrwxrwxr-- 1 www-data vagrant 0 Aug 13 12:07 themes -> \srv\wpca-themes drwxrwxr-x 1 www-data vagrant 0 Aug 13 12:04 upgrade vagrant@vvv:/srv/www/wordpress-default/wp-content$ cd plugins -bash: cd: plugins: No such file or directory vagrant@vvv:/srv/www/wordpress-default/wp-content$ cd \srv\wpca-plugins -bash: cd: srvwpca-plugins: No such file or directory vagrant@vvv:/srv/www/wordpress-default/wp-content$ cd /srv/wpca-plugins vagrant@vvv:/srv/wpca-plugins$ ls -al total 136
Attachments
Change History
comment:2 Changed 7 years ago by frank
Actually the latest Windows test build (>= 102224) which can be found here contains a fix. No update of the Guest Additions is required. Please confirm!
comment:3 Changed 7 years ago by AndyBren
I'm using the latest production version of Windows 10 Pro (fully updated) with VirtualBox 5.0.2. My VM is Ubuntu 14.04.3 64-bit server being launched using Vagrant.
The same configuration (i.e. same type of VM instantiated using my Vagrant+Ansible scripts) worked fine on Windows 8.1.
Will attach log as per instructions (refer to lines 1033 and 1045 for two failed ln -s attempts).
comment:4 Changed 7 years ago by AndyBren
I've just tested the latest test build 5.0.3-102322 and this is now RESOLVED for me.
comment:6 Changed 7 years ago by frank
- Summary changed from VirtualBox on Windows10 creates symlinks as backslashes to VirtualBox on Windows10 creates symlinks as backslashes => Fixed in SVN
comment:7 Changed 7 years ago by gggeek
I've just tested the latest test build 5.0.3-102322 and this is not fixed for me :-(
Win 8.1 64 host - vagrant 1.7.4 (but I tested starting the VM directly from VBox as well) - ubuntu trusty 64 guest
Running "VBoxManage getextradata VMNAME enumerate", I see that the 2 shares (pointing to the same folder on the host) do have set SharedFoldersEnableSymlinksCreate to 1.
Running VBox 5.0.2, I got bad symlinks created in the guest (paths were using backslash as separator).
Running 5.0.3-102322, I get:
ln: failed to create symbolic link ‘something’: Protocol error
comment:8 Changed 7 years ago by frank
gggeek, please attach a VBox.log file from such a VM session to this ticket.
comment:10 Changed 7 years ago by frank
Fix is part of VBox 5.0.4.
comment:11 Changed 6 years ago by sunlover
- Status changed from new to closed
- Resolution set to fixed
Please get a debug log:
VBoxManage debugvm VMNAME log --release "+shared_folders.e.l2,-shared_folders.restrict"
ln -s /srv/vboxtest vboxtest-link