Ticket #8038 (new defect)

Opened 7 years ago

Last modified 6 years ago

Symbolic links in shared folders

Reported by: dglsquaid Owned by:
Priority: major Component: shared folders
Version: VirtualBox 4.0.0 Keywords: symlinks
Cc: Guest type: Linux
Host type: Windows

Description (last modified by frank) (diff)

Hi all !

Virtualbox 4.0.0 windows host, linux guest.

If I made with windows a simlink from folder c:\Documents to d:\shared_folder\documents... under linux this symlink doesn't works... is not accessible ( red color 0 byte )... linux can't access to c:\Documents. In the past releases this kind of symlink worked.

For testing windows simlinks I used mklink from cmd line and a specific ( awesome ) program like Link Shell Extension ( ... ml#contact ) that allow making different kinds of links... but nothing working...

Change History

comment:1 Changed 7 years ago by Technologov

Topic should be changed to "Windows Symbolic links in shared folders"


comment:2 Changed 7 years ago by imcotton

The same problem with v4.1.2, and it's working fine in v3.2.12 or before.

This capability is very helpful, I hope it could be got fixed in the future, otherwise I'm gonna stuck along with v3.2.12.

comment:3 Changed 7 years ago by benb

This appears to have been fixed somewhere between 4.1.2 and 4.1.6.

comment:4 Changed 6 years ago by theshowmecanuck

This issue still exists in 4.1.18.

This really needs to be addressed. Not allowing Windows host symlinks and junctions to be used by the guest creates a nightmare for secure and reasonable administration of the system. If this is not a bug, it is a glaringly huge omission of a very important feature.

comment:5 Changed 6 years ago by cbsmith

Just wanted to bump this bug again. This is a big pain. Looking at layering another filesystem ON TOP in order to fix this.

comment:6 Changed 6 years ago by frank

  • Description modified (diff)

All the relevant source code is open-source. Contributions are welcome.

Note: See TracTickets for help on using tickets.
ContactPrivacy policyTerms of Use