Symbolic link issue on Windows host

[MEPhillips]

I installed a virtual box using a Vagrant script which we have been using successfully with VirtualBox 4.3. This is with Windows 7 64-bit host and Centos 7 64-bit guest.

Part of the provisioning creates a symbolic link within an area which is a shared folder: cd /opt/sufia ln -s /tmp/fcrepo4-data jetty/

The target /tmp/fcrepo4-data is on the virtual machine's disc image, not the Windows host file system.

After this command has been run, the symbolic link exists on the Linux guest, but "ln -s" reveals that it is targetted at \tmp\fcrepo4-data (i.e. the slashes have changed to backslashes) and the symbolic link fails to work under Linux.

I reverted to VirtualBox 4.3 and everything is functioning properly after recreating the symbolic link.

Sorry: I do not have the VBox.log file as I uninstalled everything.

[sunlover]

Please let us know if this build helps: https://www.virtualbox.org/download/testcase/VirtualBox-5.0.3-102224-Win.exe

[Sae1962]

Unfortunately, it doesn't solve the problem at my PC (10-year-old hp, running Windows 10 since yesterday). The message is the same:

Failed to open a session for the virtual machine Debian810.

Interface ('VirtualBox Host-Only Ethernet Adapter') is not a Host-Only Adapter interface (VERR_INTERNAL_ERROR).

Result Code: E_FAIL (0x80004005) Component: ConsoleWrap Interface: IConsole {872da645-4a9b-1727-bee2-5585105b9eed}

[Frank Mehnert]

Sae1962, that's a completely different issue. You might want to go to #14437.

[sunlover]

Fixed in VirtualBox 5.0.4.