﻿ticket,summary,version,guest,created,modified,_changetime,_description,_reporter
21410,RIP: 0010:vbsf_inode_revalidate_worker+0x542/0x580 [vboxsf],VirtualBox-7.0.4,Linux,2023-01-16T09:54:46Z,2023-01-19T08:30:56Z,2023-01-19T08:30:56Z,"Hi,

I am seeing below error with kernel 6.1.5-200.fc37.x86_64.
{{{
------------[ cut here ]------------
memcpy: detected field-spanning write (size 14) of single field ""&pReq->StrPath"" at /tmp/vbox.0/utils.c:591 (size 6)
WARNING: CPU: 0 PID: 2470 at /tmp/vbox.0/utils.c:591 vbsf_inode_revalidate_worker+0x542/0x580 [vboxsf]
Modules linked in: vboxsf(OE) snd_seq_dummy snd_hrtimer vboxvideo(OE) nft_fib_inet nft_fib_ipv4 nft_fib_ipv6 nft_fib nft_reject_inet nf_reject_ipv4 nf_reject_ipv6 nft_reject nft_ct nft_chain_nat ip6table_nat ip6table_mangle ip6table_raw ip6table_security iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 iptable_mangle iptable_raw iptable_security ip_set rfkill nf_tables nfnetlink ip6table_filter ip6_tables iptable_filter ip_tables qrtr sunrpc snd_intel8x0 snd_ac97_codec ac97_bus snd_seq snd_seq_device snd_pcm intel_rapl_msr snd_timer intel_rapl_common pktcdvd pcspkr snd soundcore i2c_piix4 joydev zram crct10dif_pclmul crc32_pclmul crc32c_intel polyval_clmulni polyval_generic virtio_net ghash_clmulni_intel vmwgfx net_failover sha512_ssse3 drm_ttm_helper video serio_raw failover vboxguest(OE) ttm wmi ata_generic pata_acpi scsi_dh_rdac scsi_dh_emc scsi_dh_alua fuse dm_multipath
CPU: 0 PID: 2470 Comm: ls Tainted: G        W  OE      6.1.5-200.fc37.x86_64 #1
Hardware name: innotek GmbH VirtualBox/VirtualBox, BIOS VirtualBox 12/01/2006
RIP: 0010:vbsf_inode_revalidate_worker+0x542/0x580 [vboxsf]
Code: cf fd ff ff b9 06 00 00 00 4c 89 fe 4c 89 14 24 48 c7 c2 e0 a8 a5 c0 48 c7 c7 90 a8 a5 c0 c6 05 04 a6 00 00 01 e8 42 4c 31 d7 <0f> 0b 4c 8b 14 24 e9 9e fd ff ff 83 f8 98 41 bb b9 ff ff ff b8 fe
RSP: 0018:ffffb046852bbb58 EFLAGS: 00010282
RAX: 0000000000000074 RBX: ffff986681154e00 RCX: 0000000000000000
RDX: 0000000000000001 RSI: ffffffff9874a863 RDI: 00000000ffffffff
RBP: ffff9866874a0144 R08: 0000000000000000 R09: ffffb046852bb9f8
R10: 0000000000000003 R11: ffffffff99146488 R12: ffff98667f8b6f00
R13: ffff98668100d6c0 R14: ffff986682574c00 R15: 000000000000000e
FS:  00007f85aafd3c40(0000) GS:ffff98675bc00000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000056279ce6f718 CR3: 00000000011ce000 CR4: 00000000000506f0
Call Trace:
 <TASK>
 vbsf_dentry_revalidate+0x4f/0xb0 [vboxsf]
 lookup_fast+0x74/0xe0
 walk_component+0x1f/0x150
 path_lookupat+0x67/0x190
 filename_lookup+0xd3/0x1c0
 vfs_statx+0x8e/0x150
 do_statx+0x50/0x80
 __x64_sys_statx+0x62/0x80
 do_syscall_64+0x5b/0x80
 ? do_syscall_64+0x67/0x80
 ? fpregs_restore_userregs+0x12/0xe0
 ? exit_to_user_mode_prepare+0x18f/0x1f0
 ? syscall_exit_to_user_mode+0x17/0x40
 ? do_syscall_64+0x67/0x80
 ? do_syscall_64+0x67/0x80
 ? exc_page_fault+0x70/0x170
 entry_SYSCALL_64_after_hwframe+0x63/0xcd
RIP: 0033:0x7f85ab16ca5e
Code: 83 0d 00 ba ff ff ff ff 64 c7 00 16 00 00 00 e9 a5 fd ff ff e8 d3 0f 02 00 0f 1f 00 f3 0f 1e fa 41 89 ca b8 4c 01 00 00 0f 05 <48> 3d 00 f0 ff ff 77 2a 89 c1 85 c0 74 0f 48 8b 05 9d 83 0d 00 64
RSP: 002b:00007ffda585f578 EFLAGS: 00000246 ORIG_RAX: 000000000000014c
RAX: ffffffffffffffda RBX: 000056279ce5fee8 RCX: 00007f85ab16ca5e
RDX: 0000000000000900 RSI: 00007ffda585f6b0 RDI: 00000000ffffff9c
RBP: 000000000000025e R08: 00007ffda585f580 R09: 0000000000000020
R10: 000000000000025e R11: 0000000000000246 R12: 0000000000000000
R13: 0000000000000001 R14: 000056279ce5fed0 R15: 0000000000000000
 </TASK>
---[ end trace 0000000000000000 ]---
}}}",Srini8987
21351,GetFileInformationByHandleExfor VBoxSharedFolderFS  works incorrectly,VirtualBox-7.0.4,other,2022-12-21T13:12:21Z,2023-01-04T12:13:46Z,2023-01-04T12:13:46Z,"it returns ERROR_FILE_NOT_FOUND, while there are files in a directory

details:


https://github.com/boostorg/filesystem/issues/261#issuecomment-1335574338",basiliscos
21303,exception in module VBoxMRXNP.dll => Fixed in SVN,VirtualBox-7.0.4,Windows,2022-11-23T13:10:14Z,2022-12-23T17:12:29Z,2022-12-23T17:12:29Z,"application running in MS Visual Studio 2019 crashes if it tries to access the file system (retrieve folder structure). In VirtualBox 6.1 it works fine.

windows Event log:
Faulting application name: EstiCon.Client.exe, version: 22.3.4.100, time stamp: 0x637e116c
Faulting module name: VBoxMRXNP.dll, version: 7.0.4.4605, time stamp: 0x6375102d
Exception code: 0x4000001f
Fault offset: 0x000132b0
Faulting process id: 0x448c
Faulting application start time: 0x01d8ff37dd906849
Faulting application path: c:\projekty\EstDevTest\Client\EstiCon.Client\bin\Debug\EstiCon.Client.exe
Faulting module path: C:\WINDOWS\system32\VBoxMRXNP.dll
Report Id: 7eb1303a-fddb-4eb3-a7ef-848370c48846
Faulting package full name: 
Faulting package-relative application ID: ",medved
21197,Make Shared Folder accessible by default in at least certain Linux variants,VirtualBox-7.0.2,Linux,2022-10-23T22:35:12Z,2022-10-23T22:35:12Z,2022-10-23T22:35:12Z,"As explained [https://forums.virtualbox.org/viewtopic.php?t=103322 here], it takes a running special command line in order to be able to enter shared folders instead of only getting ""permission denied"" messages.

It's explained there it might be different for each flavor of Linux, but how about giving solutions to at least popular packages like Ubuntu and Lubuntu?

As seen [https://unix.stackexchange.com/a/400137 here] in Lubunto the command (that also saved the day for me) is:

{{{
sudo usermod -a -G vboxsf $(whoami)
}}}

If not, then maybe at least produce a message after installing Guest Additions in Linux to invite the user to look up how to make shared folders work.",l-w-c
21061,Shared folder Automount not working properly Linux Mint 21 Cinnamon,VirtualBox 6.1.36,Linux,2022-08-13T09:15:34Z,2023-02-04T08:53:42Z,2023-02-04T08:53:42Z,"Automount works perfectly in my older Linux Mint 20.3 Cinnamon VM.
I installed Linux Mint 21 Cinnamon. But automount does not work properly.
It mounts the folder and I gave permissions to my user to vboxsf
But the sub folders or files are randomly locked without permissions to read/write. It seems some files/folder are owned by root, those works and some are unknown owner those don't work.
Rebooting will randomly change which file/folder have root or unknown owner.

Latest VBox and guest additions is installed.

I tried disabling automount and doing a manual mount or adding to /etc/fstab and both work perfectly.
",Munch
20979,machine folder share corrupts data,VirtualBox 6.1.34,Linux,2022-06-11T01:27:45Z,2022-06-11T01:27:45Z,2022-06-11T01:27:45Z,"After upgrading to 6.1.32, machine folder shares started showing corruption when being written to. Also happens in 6.1.34. Happens on new install of ubuntu 22.04 as guest on ubuntu 22.04 host.",illk
20702,"Execution of "".exe"" fails in shared folders, with Windows 10 or 11",VirtualBox 6.1.30,Windows,2021-12-01T14:42:25Z,2021-12-01T14:42:25Z,2021-12-01T14:42:25Z,"Host Windows 10. Guest Windows 10 or 11.
(Windows XP x32 and Windows 7 x64, work fine)

When an "".exe"" is run inside a shared folder, it gives the error ""The specified path does not exist"" depending on the number of characters in the path + the file name, and the text entered in ""Folder name"" (sharename).

Examples with mountpoint = ""X:"":

sharename = ""1"":
  OK    X:\1234567.exe

  NOK  X:\12345678.exe
sharename = ""12"":
  OK    X:\12345678.exe

  NOK  X:\123456789.exe
sharename = ""123"":
  OK    X:\123456789.exe

  NOK  X:\1234567890.exe
...
sharename = ""12345678"":
  OK    X:\12345678901234.exe

  NOK  X:\123456789012345.exe

Interestingly, the more characters sharename has, the more characters the "".exe"" file name allows.",FelixG
20272,Windows 10 guest freezes randomly on Windows 10 host when accessing files on shared folders,VirtualBox 6.1.18,Windows,2021-03-24T12:53:05Z,2021-03-24T12:53:05Z,2021-03-24T12:53:05Z,"Weeks ago, after updating from 6.1.12 to 6.1.16 my VM started freezing when I accessed files from a shared host folder. It mostly happens when I trie to browse the shared folder from an application's open file dialog. Reverting back to 6.1.12 did not resolve the issue. This started to happened more frequently, so that I finally could no longer work with that VM and had to recover an older state from a backup. 
Now that some weeks have passed, the issues start again. I upgraded to 6.1.18 without success. Note that I already had issues with shared folders (e.g. can't start executables because they don't exist, copying several files will only copy some files etc) 
But now the issue completly freezes the client each time with increasing frequency.
",bartislartfass
20168,Linux guest / Mac host - uid option stopped working,VirtualBox 6.1.18,Linux,2021-02-02T17:35:41Z,2021-02-02T17:35:41Z,2021-02-02T17:35:41Z,"MacOS Catalina host, OpenSUSE Tumbleweed guest.

With Virtualbox 6.1.14, manually mounting a shared folder worked correctly with the ""uid"" option (owner of directories and files being set to the specified user).

After upgrading VBox, this parameter stopped working - mounted data is now owned by root.
Latest test done with VBox 6.1.18 host and 6.1.18 guest tools.

{{{
> sudo mount -t vboxsf -o uid=$UID,gid=100 macroot ~/files/macroot
> ls -ld /home/rich/files/macroot/Users/
drwxr-xr-x 1 root root 192 sep 22 00:27 /home/rich/files/macroot/Users/
}}}

This was discussed in SUSE bug https://bugzilla.suse.com/show_bug.cgi?id=1180761, with a working fix for Linux host in place - but apparently not working as expected on a Mac host.",Richlv
20061,"""Permission denied"" error at linux-guest on Windows10-host when execute a file on a shared folders immediately after creation or 'chmod +x'",VirtualBox 6.1.14,Linux,2020-11-24T10:45:10Z,2020-11-24T10:45:10Z,2020-11-24T10:45:10Z,"
Following script reproduces the error on my virtual linux-machine when working on a share folder (in my case the '/vagrant'):

Script:


{{{

set -x

# switch to shared folder
cd /vagrant/ || exit 1

# create simple script
echo ""echo 'Hello World'"">PrintHelloWorld.sh
cat PrintHelloWorld.sh || exit 1
ls -l PrintHelloWorld.sh || exit 1

echo ""start failing tests...""
touch PrintHelloWorld.sh
./PrintHelloWorld.sh

chmod +x PrintHelloWorld.sh
./PrintHelloWorld.sh

chmod +r PrintHelloWorld.sh
./PrintHelloWorld.sh
}}}


Output:


{{{
++ cd /vagrant/
++ echo 'echo '\''Hello World'\'''
++ cat PrintHelloWorld.sh
echo 'Hello World'
++ ls -l PrintHelloWorld.sh
-rwxrwxrwx 1 vagrant vagrant 19 Nov 24  2020 PrintHelloWorld.sh
++ echo 'start failing tests...'
start failing tests...
++ touch PrintHelloWorld.sh
++ ./PrintHelloWorld.sh
/vagrant/RunCommands.sh: line 14: ./PrintHelloWorld.sh: Permission denied
++ chmod +x PrintHelloWorld.sh
++ ./PrintHelloWorld.sh
/vagrant/RunCommands.sh: line 17: ./PrintHelloWorld.sh: Permission denied
++ chmod +r PrintHelloWorld.sh
++ ./PrintHelloWorld.sh
/vagrant/RunCommands.sh: line 20: ./PrintHelloWorld.sh: Permission denied
}}}


The second part of the script shows some 'workarounds' to the problem:


{{{
echo ""start successful tests...""
touch PrintHelloWorld.sh
sleep 1
./PrintHelloWorld.sh

touch PrintHelloWorld.sh
cat PrintHelloWorld.sh
./PrintHelloWorld.sh

echo ""echo 'Hello World'"">PrintHelloWorld2.sh
./PrintHelloWorld2.sh

echo ""cleanup...""
rm PrintHelloWorld.sh
rm PrintHelloWorld2.sh

}}}


and creates following output:


{{{
++ echo 'start successful tests...'
start successful tests...
++ touch PrintHelloWorld.sh
++ sleep 1
++ ./PrintHelloWorld.sh
Hello World
++ touch PrintHelloWorld.sh
++ cat PrintHelloWorld.sh
echo 'Hello World'
++ ./PrintHelloWorld.sh
Hello World
++ echo 'echo '\''Hello World'\'''
++ ./PrintHelloWorld2.sh
Hello World
++ echo cleanup...
cleanup...
++ rm PrintHelloWorld.sh
++ rm PrintHelloWorld2.sh
}}}

The complete repro-environment including script and logs are attached.



",progger98
19920,/bin/ls: reading directory : Protocol error for asian fonts,VirtualBox 6.1.14,Linux,2020-09-26T09:37:26Z,2020-09-26T09:37:26Z,2020-09-26T09:37:26Z,"On my Windows 10 host I am not able to 'ls' a directory with these Asian characters: 

HID_Miniport_Device_￿࿘낖彴.hid

These characters appear in the ProtableApps version of Mixxx.
This is my error message.

neo:~/PortableApps/MixxxPortable/Data/MixxxSettings$ ls controller
/bin/ls: reading directory 'controller': Protocol error

After I delete such files 'ls' works well again.",Frank Breitling
19545,"Regression related to shared folders, npm install",VirtualBox 6.1.6,Linux,2020-05-01T04:53:28Z,2020-10-05T09:04:34Z,2020-10-05T09:04:34Z,"After upgrading from 5.x to 6.x, I get the following error related to a shared filesystem when running npm install:

npm ERR! enoent ENOENT: no such file or directory, open '/home/kyle/share/devel/test/node_modules/argparse/node_modules/sprintf-js/package.json.226652263'
npm ERR! enoent This is related to npm not being able to find a file.

Steps to reproduce:

On the linux guest, in a shared folder:
  mkdir test
  cd test
  npm init -y
  npm install grunt --save-dev

On 5.x VB, I would see an error like this when I did not have guest symlinks properly enabled so I think it might be related to a problem with symlinks.  But I can create symlinks in 6.x from within the guest manually and they seem to work, at least from the command line.

I revert to VB 5.x and the problem goes away.  Unfortunately VB 5.x doesn't work on MacOS Catalina so trying to get this working under 6.x now.
",keb
19507,Shared folders in Guest OS (Windows 10) also occupy unused drive letters,VirtualBox 6.1.6,Windows,2020-04-17T17:11:36Z,2020-04-17T17:11:36Z,2020-04-17T17:11:36Z,"Drive letters are occupied even if they are not assigned in Windows 20 Guest OS! The Shared Folder are correctly connected to the designated drive letters in the Guest OS. Unfortunately, the other drive letters are also occupied. This leads for example to problems with other NAS SHARES that should be connected to drive letters. (Letters are occupied!!). 
The problem does not exist in the same environment with Virtualbox 5.2.40.

Shared Folder - Host OS Windows 10 (Build 1909) - Guest OS Windows 10 (Build 1909).  ",RonaldMcDonald
19454,Transfer of large files from guest to host causes hang,VirtualBox 6.1.4,Windows,2020-04-01T18:48:28Z,2020-04-01T18:48:28Z,2020-04-01T18:48:28Z,"Host: Windows 10, Guest: Debian
Mount shared folder on from host.
Write large (>10GB) file.
Processes on guest will begin to hang.
Attempt to reboot may hang as well.",eng3
19249,aclocal (and probably other tools) not working in shared folder,VirtualBox 6.1.2,Linux,2020-01-21T16:33:17Z,2020-02-04T14:08:24Z,2020-02-04T14:08:24Z,"How to reproduce using Vagrant:

* Use a minimal `Vagrantfile`:
{{{
$script = <<SCRIPT
    yum install -y epel-release
    yum install -y automake libtool
SCRIPT

Vagrant.configure('2') do |config|
    config.vm.box = 'allenta/bento.centos-7.4'
    config.vm.box_version = '=201803.24.0'
    config.vm.synced_folder '.', '/vagrant', :nfs => false
    config.vm.provision :shell, :privileged => true, :inline => $script
end
}}}
* Create a minimal `configure.ac` file in `/vagrant/` (i.e. shared folder):
{{{
AC_INIT([helloworld], [0.1], [hello@example.com])
AM_INIT_AUTOMAKE
AC_PROG_CC
AC_CONFIG_FILES([Makefile])
AC_OUTPUT
}}}
* Try to run `aclocal`:
{{{
$ cd /vagrant

$ aclocal
/usr/bin/m4:/tmp/am4tHcrP6s/traces.m4:320: ERROR: end of file in string
Use of uninitialized value $msg in concatenation (.) or string at /usr/bin/autom4te line 1026.
Use of uninitialized value $stacktrace in pattern match (m//) at /usr/bin/autom4te line 1026.
unknown channel X])])])dnl
])
igure.ac:1: -1- m4_pattern_allow(^mandir$)
 at /usr/share/autoconf/Autom4te/Channels.pm line 638.
    Autom4te::Channels::msg('X])])])dnl\x{a}])\x{a}igure.ac:1: -1- m4_pattern_allow(^mandir$)\x{a}', undef, 'warning: ', 'partial', 0) called at /usr/bin/autom4te line 1026
aclocal: error: echo failed with exit status: 1
}}}

* Try same thing moving `/vagrant/configure.ac` to a different non-shared location (e.g. `/tmp`). The command will work as expected (i.e. not output and some files generated).

This has been tested in the following combinations. It only worked when using Ubuntu 19.10:
* macOS Catalina 10.15.2 + VirtualBox 6.0.16 + Vagrant 2.2.6
* macOS Catalina 10.15.2 + VirtualBox 6.1.2 + Vagrant 2.2.6 + https://github.com/oracle/vagrant-boxes/issues/178#issuecomment-575936662
* Ubuntu 18.04 + VirtualBox 6.0.14 + Vagrant 2.2.6
* Ubuntu 18.04 + VirtualBox 6.1.2 + Vagrant 2.2.6 + https://github.com/oracle/vagrant-boxes/issues/178#issuecomment-575936662
* Ubuntu 19.10 + VirtualBox 6.1.0 + Vagrant 2.2.6 + https://github.com/oracle/vagrant-boxes/issues/178#issuecomment-575936662

In the past this worked fine.",carlos.abalde
19133,VM lockup when guest opens a named pipe in a shared folder,VirtualBox 6.0.14,all,2019-12-06T16:29:53Z,2021-07-07T11:16:29Z,2021-07-07T11:16:29Z,"I discovered this bug because I was `rsync`ing a shared folder containing a named pipe, and this hung my machine.

Repro steps:
 - Set up a Linux guest on a Mac host. I have Ubuntu 18.04 running on VBox 6.0.14 (latest stable as of now).
 - Set up a shared folder 
 - On the host, `mkfifo TEST_PIPE` in the folder
 - On the guest, `cat TEST_PIPE`

At this point, the guest is (partially) locked up. Specifically:
 - Ctrl-C nor SIGKILL will work for `cat` — it is hung in D state, unkillable
 - Any process touching the shared folder hangs likewise
 - `dmesg` will show the following stack for the hung `cat` https://pastebin.com/WjKQaZys [1]
 - The guest cannot be cleanly rebooted because shutdown requires tearing down the guest additions module, which is blocked on talking to the VM.
 - Powering off the VM (not from the guest, but from the UI!) will hang.

So this is not a hang in guest additions, but in the VM code itself.

My guess is that the thread handling shared folders is locked up trying to read from the named pipe.

What confirms this is that the hang is resolved the moment that I do `echo > TEST_PIPE` on the host.

The reason this is **not** expected behavior is that the guest sees the named pipe as a regular file:

$ ls -l TEST_PIPE 
-rwxrwx--- 1 root vboxsf 0 Dec  6 16:21 TEST_PIPE

Two fixes seem possible:
 - Make named pipes act as true named pipes to the host. If you google ""vboxsf named pipe"", this is actually a feature that was previously requested.
 - Make the `open` syscall fail in this context. This is worse than working pipes, but better than a lockup. At the moment, data does not actually travel down the named pipe, if the host does `echo foo > TEST_PIPE` and the guest does `cat TEST_PIPE`, the guest simply says `cat: TEST_PIPE: Protocol error`.

[1]
{{{
$ sudo cat /proc/7376/stack
[<0>] rtR0SemEventMultiLnxWait.isra.2+0x33d/0x370 [vboxguest]
[<0>] VBoxGuest_RTSemEventMultiWaitEx+0xe/0x10 [vboxguest]
[<0>] VBoxGuest_RTSemEventMultiWait+0x28/0x30 [vboxguest]
[<0>] vgdrvHgcmAsyncWaitCallbackWorker+0x1c3/0x210 [vboxguest]
[<0>] VGDrvCommonIoCtl+0x489/0x18e0 [vboxguest]
[<0>] VBoxGuestIDC+0x149/0x160 [vboxguest]
[<0>] VbglR0IdcCallRaw+0x13/0x20 [vboxsf]
[<0>] VbglR0HGCMFastCall+0x1c/0x20 [vboxsf]
[<0>] vbsf_reg_open+0x291/0x4f0 [vboxsf]
[<0>] do_dentry_open+0x1c2/0x310
[<0>] vfs_open+0x4f/0x80
[<0>] path_openat+0x6bf/0x1900
[<0>] do_filp_open+0x9b/0x110
[<0>] do_sys_open+0x1bb/0x2c0
[<0>] SyS_openat+0x14/0x20
[<0>] do_syscall_64+0x73/0x130
[<0>] entry_SYSCALL_64_after_hwframe+0x3d/0xa2
[<0>] 0xffffffffffffffff
}}}",lesha
19126,Hard freeze on Centos Host system with Guest using Shared Folders,VirtualBox 6.0.14,Windows,2019-12-03T15:38:08Z,2019-12-09T15:33:25Z,2019-12-09T15:33:25Z,"Running Centos 7.7 Host with a Windows 10 Guest using a Shared Folder. I have experienced issues in the past with Shared Folders, but in the past it only seemed to affect the Guest systems. This issue is hard to troubleshoot since the Host system freezes, I can only resolve it by unplugging the power. I have tried using the SysRq keys to no avail. In troubleshooting the issue, I have stopped all other host applications except VirtualBox and disconnected the Shared folder. For a week, I did not experience any freezing of the host the system. If I connect the Shared Folder I will randomly experience a hard freeze in a couple of hours or a couple of days.

The host system has 16GB RAM and 4 cores. I am using 4GB and 2 cores for my Windows 10 1909 guest.

I do not know how to troubleshoot this any further since the Host system hard freezes, I do not get any indications of problems in any of the host logs. It most likely freezes before documenting the problem. I welcome any tests or settings which you want me to implement in order to determine the problem or fixes.
 ",jim.rather
19110,Windows 10 KMODE_EXCEPTION_NOT_HANDLED with mapped shared folder,VirtualBox 6.0.14,Windows,2019-11-26T21:46:32Z,2019-11-26T21:46:32Z,2019-11-26T21:46:32Z,"Mapped folder:
{{{
              Z:        \\VBoxSvr\Downloads       VirtualBox Shared Folders
}}}

Steps:
1. Turn on win 10 (1809/17763.805) -- this is VM is from modern.ie (it's ~45 days old and updates on its own), it has a persistent mapped shared folder
2. Log in (IEUser...)
3. Open Windows explorer
4. Browse to This PC
5. Browse to Downloads ({{{\\VBoxSvr}}})(Z:)
6. Click the files pane
7. type `zap` (I have ZAP_2_8_0_windows.exe in this shared folder)

Consistently rebooted a couple of times. Since copying the file from the drive to c: using `cmd`, this hasn't happened.

I do have a full kernel dump (4GB).",Garner
19099,openSUSE Leap 42.3 - cannot compile vboxsf module,VirtualBox 6.0.14,Linux,2019-11-20T14:53:44Z,2020-09-25T18:24:02Z,2020-09-25T18:24:02Z,"Using the current 6.0.14 we cannot compile the shared folder module from the guest additions in the guest with a compile error and as such no shared folder functionality is available:

openSUSE Leap 42.3
Linux linux-ntkd 4.4.180-102-default #1 SMP Mon Jun 17 13:11:23 UTC 2019 (7cfa20a) x86_64 x86_64 x86_64 GNU/Linux

cat vboxadd-install.log
{{{
VirtualBox Guest Additions: Starting.
VirtualBox Guest Additions: Building the VirtualBox Guest Additions kernel
modules.  This may take a while.
VirtualBox Guest Additions: To build modules for other installed kernels, run
VirtualBox Guest Additions:   /sbin/rcvboxadd quicksetup <version>
VirtualBox Guest Additions: or
VirtualBox Guest Additions:   /sbin/rcvboxadd quicksetup all
VirtualBox Guest Additions: Building the modules for kernel 4.4.180-102-default.

VirtualBox Guest Additions: Look at /var/log/vboxadd-setup.log to find out what
went wrong
VirtualBox Guest Additions: modprobe vboxsf failed

cat vboxadd-setup.log
Installing X.Org Server 1.18 modules
}}}

### the service in general worked:
{{{
 systemctl status vboxadd-service.service
● vboxadd-service.service
   Loaded: loaded (/opt/VBoxGuestAdditions-6.0.14/init/vboxadd-service; enabled; vendor preset: disabled)
   Active: active (running) since Wed 2019-11-20 09:22:25 CET; 13min ago
    Tasks: 8 (limit: 512)
   CGroup: /system.slice/vboxadd-service.service
           └─1457 /usr/sbin/VBoxService --pidfile /var/run/vboxadd-service.sh
}}}

XXX but shared folder support does not work:
{{{
fbatschu@linux-ntkd:~> lsmod|grep vbox
vboxguest             368640  6

[    4.253318] vboxguest: misc device minor 57, IRQ 20, I/O port d040, MMIO at 00000000f2400000 (size 0x400000)
[    4.253319] vboxguest: Successfully loaded version 6.0.14 (interface 0x00010004)
[    4.258614] XFS (sda3): Ending clean mount
[    4.296429] systemd-journald[403]: Received request to flush runtime journal from PID 1
[    4.553802] snd_intel8x0 0000:00:05.0: white list rate for 1028:0177 is 48000
[    5.217573] No iBFT detected.
[    5.243033] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[    6.353076] 08:22:25.818744 main     VBoxService 6.0.14 r133895 (verbosity: 0) linux.amd64 (Oct 10 2019 20:44:32) release log
               08:22:25.818746 main     Log opened 2019-11-20T08:22:25.818741000Z
[    6.353107] 08:22:25.818807 main     OS Product: Linux
[    6.353121] 08:22:25.818824 main     OS Release: 4.4.180-102-default
[    6.353134] 08:22:25.818838 main     OS Version: #1 SMP Mon Jun 17 13:11:23 UTC 2019 (7cfa20a)
[    6.353157] 08:22:25.818855 main     Executable: /opt/VBoxGuestAdditions-6.0.14/sbin/VBoxService
               08:22:25.818855 main     Process ID: 1452
               08:22:25.818856 main     Package type: LINUX_64BITS_GENERIC
[    6.353791] 08:22:25.819485 main     6.0.14 r133895 started. Verbose level = 0
[    6.354534] 08:22:25.820219 main     vbglR3GuestCtrlDetectPeekGetCancelSupport: Supported (#1)
[    6.361318] 08:22:25.826993 automount Error: vbsvcAutomounterMountIt: Failed to mount 'Downloads' on '/media/sf_Downloads': No such device (-1,19)
[    6.362301] 08:22:25.827991 automount Error: vbsvcAutomounterMountIt: Failed to mount 'Music' on '/media/sf_Music': No such device (-1,19)
[    7.249769] e1000: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX
[    7.250592] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[    7.371502] 08:22:26.837466 automount Error: vbsvcAutomounterMountIt: Failed to mount 'Downloads' on '/media/sf_Downloads': No such device (-1,19)
[    7.381974] 08:22:26.847947 automount Error: vbsvcAutomounterMountIt: Failed to mount 'Music' on '/media/sf_Music': No such device (-1,19)
[    7.643712] NET: Registered protocol family 17
[   23.841175] fuse init (API version 7.23)
[  529.556954] VBGL_IOCTL_ACQUIRE_GUEST_CAPABILITIES failed rc=-138
[  530.941517] VBGL_IOCTL_ACQUIRE_GUEST_CAPABILITIES failed rc=-138
[  548.804519] VBGL_IOCTL_ACQUIRE_GUEST_CAPABILITIES failed rc=-138
[  550.120040] VBGL_IOCTL_ACQUIRE_GUEST_CAPABILITIES failed rc=-138
}}}

### try to test this manually:
{{{
linux-ntkd:/opt/VBoxGuestAdditions-6.0.14/bin # VBoxControl sharedfolder list
Oracle VM VirtualBox Guest Additions Command Line Management Interface Version 6.0.14
(C) 2008-2019 Oracle Corporation
All rights reserved.

Shared Folder mappings (2):

01 - Downloads [idRoot=0 writable auto-mount host-icase]
02 - Music [idRoot=1 writable auto-mount host-icase]

linux-ntkd:/opt/VBoxGuestAdditions-6.0.14/sbin # ./VBoxService --enable-automount
08:44:57.202537 main     VBoxService 6.0.14 r133895 (verbosity: 0) linux.amd64 (Oct 10 2019 20:44:32) release log
08:44:57.202545 main     Log opened 2019-11-20T08:44:57.202521000Z
08:44:57.202777 main     OS Product: Linux
08:44:57.202865 main     OS Release: 4.4.180-102-default
08:44:57.202935 main     OS Version: #1 SMP Mon Jun 17 13:11:23 UTC 2019 (7cfa20a)
08:44:57.203002 main     Executable: /opt/VBoxGuestAdditions-6.0.14/sbin/VBoxService
08:44:57.203004 main     Process ID: 3724
08:44:57.203006 main     Package type: LINUX_64BITS_GENERIC
08:44:57.209167 main     6.0.14 r133895 started. Verbose level = 0

[ 1356.851990] 08:44:57.202537 main     VBoxService 6.0.14 r133895 (verbosity: 0) linux.amd64 (Oct 10 2019 20:44:32) release log
               08:44:57.202545 main     Log opened 2019-11-20T08:44:57.202521000Z
[ 1356.852141] 08:44:57.202777 main     OS Product: Linux
[ 1356.852213] 08:44:57.202865 main     OS Release: 4.4.180-102-default
[ 1356.852282] 08:44:57.202935 main     OS Version: #1 SMP Mon Jun 17 13:11:23 UTC 2019 (7cfa20a)
[ 1356.852371] 08:44:57.203002 main     Executable: /opt/VBoxGuestAdditions-6.0.14/sbin/VBoxService
               08:44:57.203004 main     Process ID: 3724
               08:44:57.203006 main     Package type: LINUX_64BITS_GENERIC
[ 1356.858567] 08:44:57.209167 main     6.0.14 r133895 started. Verbose level = 0
[ 1356.881822] 08:44:57.232459 main     vbglR3GuestCtrlDetectPeekGetCancelSupport: Supported (#1)
[ 1356.882025] 08:44:57.232708 main     Error: Failed to become guest control master: VERR_RESOURCE_BUSY
[ 1356.882273] 08:44:57.232954 main     Error: Service 'control' failed to initialize: VERR_RESOURCE_BUSY
[ 1356.882528] 08:44:57.233216 main     Session 0 is about to close ...
[ 1356.882548] 08:44:57.233241 main     Stopping all guest processes ...
[ 1356.882579] 08:44:57.233272 main     Closing all guest files ...
[ 1356.882631] 08:44:57.233292 main     Ended.

fbatschu@linux-ntkd:/opt/VBoxGuestAdditions-6.0.14/bin> mount -v|grep vbox
fbatschu@linux-ntkd:/opt/VBoxGuestAdditions-6.0.14/bin>

linux-ntkd:/opt/VBoxGuestAdditions-6.0.14/other # ./mount.vboxsf Downloads /mnt
./mount.vboxsf: mounting failed with the error: No such device
linux-ntkd:/opt/VBoxGuestAdditions-6.0.14/other # echo $?
1

mount(""Downloads"", ""/mnt"", ""vboxsf"", MS_NODEV, """") = -1 ENODEV (No such device)
write(2, ""./mount.vboxsf: mounting failed ""..., 46./mount.vboxsf: mounting failed with the error) = 46
write(2, "": No such device\n"", 17: No such device
)      = 17

linux-ntkd:/opt/VBoxGuestAdditions-6.0.14 # find / -name vboxguest -ls
  1066    0 drwxr-xr-x   1 root     root          656 Oct 10 20:44 /opt/VBoxGuestAdditions-6.0.14/src/vboxguest-6.0.14/vboxguest
 13625    0 crw-rw----   1 vboxadd  root      10,  57 Nov 20 09:22 /dev/vboxguest
4026532203    0 dr-xr-xr-x   2 root     root            0 Nov 20 09:52 /proc/irq/20/vboxguest
 11526    0 drwxr-xr-x   2 root     root            0 Nov 20 09:22 /sys/bus/pci/drivers/vboxguest
 12374    0 drwxr-xr-x   3 root     root            0 Nov 20 09:22 /sys/devices/virtual/misc/vboxguest
 12377    0 lrwxrwxrwx   1 root     root            0 Nov 20 09:52 /sys/class/misc/vboxguest -> ../../devices/virtual/misc/vboxguest
 11450    0 drwxr-xr-x   7 root     root            0 Nov 20 09:22 /sys/module/vboxguest

linux-ntkd:/opt/VBoxGuestAdditions-6.0.14 # find / -name vboxsf -ls
  1268    0 drwxr-xr-x   1 root     root          850 Oct 10 20:44 /opt/VBoxGuestAdditions-6.0.14/src/vboxguest-6.0.14/vboxsf
}}}

XXX see how the compilation of the vboxsf module fails:
{{{
linux-ntkd:/opt/VBoxGuestAdditions-6.0.14/src/vboxguest-6.0.14/vboxsf # make
make V=1 CONFIG_MODULE_SIG= -C /lib/modules/4.4.180-102-default/build M=/opt/VBoxGuestAdditions-6.0.14/src/vboxguest-6.0.14/vboxsf SRCROOT=/opt/VBoxGuestAdditions-6.0.14/src/vboxguest-6.0.14/vboxsf -j2 modules
make[1]: Entering directory '/usr/src/linux-4.4.180-102-obj/x86_64/default'
make -C ../../../linux-4.4.180-102 O=/usr/src/linux-4.4.180-102-obj/x86_64/default/. modules
make -C /usr/src/linux-4.4.180-102-obj/x86_64/default KBUILD_SRC=/usr/src/linux-4.4.180-102 \
-f /usr/src/linux-4.4.180-102/Makefile modules
test -e include/generated/autoconf.h -a -e include/config/auto.conf || (		\
echo >&2;							\
echo >&2 ""  ERROR: Kernel configuration is invalid."";		\
echo >&2 ""         include/generated/autoconf.h or include/config/auto.conf are missing."";\
echo >&2 ""         Run 'make oldconfig && make prepare' on kernel src to fix it."";	\
echo >&2 ;							\
/bin/false)
mkdir -p /opt/VBoxGuestAdditions-6.0.14/src/vboxguest-6.0.14/vboxsf/.tmp_versions ; rm -f /opt/VBoxGuestAdditions-6.0.14/src/vboxguest-6.0.14/vboxsf/.tmp_versions/*
make -f /usr/src/linux-4.4.180-102/scripts/Makefile.build obj=/opt/VBoxGuestAdditions-6.0.14/src/vboxguest-6.0.14/vboxsf
  gcc -Wp,-MD,/opt/VBoxGuestAdditions-6.0.14/src/vboxguest-6.0.14/vboxsf/.vfsmod.o.d  -nostdinc -isystem /usr/lib64/gcc/x86_64-suse-linux/4.8/include -I/usr/src/linux-4.4.180-102/arch/x86/include -Iarch/x86/include/generated/uapi -Iarch/x86/include/generated  -I/usr/src/linux-4.4.180-102/include -Iinclude -I/usr/src/linux-4.4.180-102/arch/x86/include/uapi -Iarch/x86/include/generated/uapi -I/usr/src/linux-4.4.180-102/include/uapi -Iinclude/generated/uapi -include /usr/src/linux-4.4.180-102/include/linux/kconfig.h   -I/opt/VBoxGuestAdditions-6.0.14/src/vboxguest-6.0.14/vboxsf -D__KERNEL__ -Wall -Wundef -Wstrict-prototypes -Wno-trigraphs -fno-strict-aliasing -fno-common -Werror-implicit-function-declaration -Wno-format-security -std=gnu89 -fno-PIE -mno-sse -mno-mmx -mno-sse2 -mno-3dnow -mno-avx -m64 -falign-jumps=1 -falign-loops=1 -mno-80387 -mno-fp-ret-in-387 -mpreferred-stack-boundary=3 -mtune=generic -mno-red-zone -mcmodel=kernel -funit-at-a-time -maccumulate-outgoing-args -DCONFIG_X86_X32_ABI -DCONFIG_AS_CFI=1 -DCONFIG_AS_CFI_SIGNAL_FRAME=1 -DCONFIG_AS_CFI_SECTIONS=1 -DCONFIG_AS_FXSAVEQ=1 -DCONFIG_AS_SSSE3=1 -DCONFIG_AS_CRC32=1 -DCONFIG_AS_AVX=1 -DCONFIG_AS_AVX2=1 -DCONFIG_AS_AVX512=1 -DCONFIG_AS_SHA1_NI=1 -DCONFIG_AS_SHA256_NI=1 -pipe -Wno-sign-compare -mindirect-branch=thunk-extern -mindirect-branch-register -DRETPOLINE -fno-delete-null-pointer-checks -Wno-maybe-uninitialized -O2 --param=allow-store-data-races=0 -DCC_HAVE_ASM_GOTO -Wframe-larger-than=2048 -fstack-protector -Wno-unused-but-set-variable -fno-var-tracking-assignments -fasynchronous-unwind-tables -g -gdwarf-4 -pg -mfentry -DCC_USING_FENTRY -fno-inline-functions-called-once -Wdeclaration-after-statement -Wno-pointer-sign -fno-strict-overflow -fno-merge-all-constants -fmerge-constants -fno-stack-check -fconserve-stack -Werror=implicit-int -Werror=strict-prototypes -Wno-declaration-after-statement -fno-pie -include /opt/VBoxGuestAdditions-6.0.14/src/vboxguest-6.0.14/vboxsf//include/VBox/VBoxGuestMangling.h -fshort-wchar   -I/usr/src/linux-4.4.180-102/include   -I/opt/VBoxGuestAdditions-6.0.14/src/vboxguest-6.0.14/vboxsf/   -I/opt/VBoxGuestAdditions-6.0.14/src/vboxguest-6.0.14/vboxsf/include   -I/opt/VBoxGuestAdditions-6.0.14/src/vboxguest-6.0.14/vboxsf/r0drv/linux -D__KERNEL__ -DMODULE -DRT_WITHOUT_PRAGMA_ONCE -DRT_OS_LINUX -DIN_RING0 -DIN_RT_R0 -DIN_SUP_R0 -DVBOX -DVBOX_WITH_HGCM -DIN_MODULE -DIN_GUEST -DIN_GUEST_R0 -DRT_NO_EXPORT_SYMBOL -DVBOX_WITH_64_BITS_GUESTS -DRT_ARCH_AMD64  -DMODULE  -D""KBUILD_STR(s)=#s"" -D""KBUILD_BASENAME=KBUILD_STR(vfsmod)""  -D""KBUILD_MODNAME=KBUILD_STR(vboxsf)"" -c -o /opt/VBoxGuestAdditions-6.0.14/src/vboxguest-6.0.14/vboxsf/.tmp_vfsmod.o /opt/VBoxGuestAdditions-6.0.14/src/vboxguest-6.0.14/vboxsf/vfsmod.c
  gcc -Wp,-MD,/opt/VBoxGuestAdditions-6.0.14/src/vboxguest-6.0.14/vboxsf/.dirops.o.d  -nostdinc -isystem /usr/lib64/gcc/x86_64-suse-linux/4.8/include -I/usr/src/linux-4.4.180-102/arch/x86/include -Iarch/x86/include/generated/uapi -Iarch/x86/include/generated  -I/usr/src/linux-4.4.180-102/include -Iinclude -I/usr/src/linux-4.4.180-102/arch/x86/include/uapi -Iarch/x86/include/generated/uapi -I/usr/src/linux-4.4.180-102/include/uapi -Iinclude/generated/uapi -include /usr/src/linux-4.4.180-102/include/linux/kconfig.h   -I/opt/VBoxGuestAdditions-6.0.14/src/vboxguest-6.0.14/vboxsf -D__KERNEL__ -Wall -Wundef -Wstrict-prototypes -Wno-trigraphs -fno-strict-aliasing -fno-common -Werror-implicit-function-declaration -Wno-format-security -std=gnu89 -fno-PIE -mno-sse -mno-mmx -mno-sse2 -mno-3dnow -mno-avx -m64 -falign-jumps=1 -falign-loops=1 -mno-80387 -mno-fp-ret-in-387 -mpreferred-stack-boundary=3 -mtune=generic -mno-red-zone -mcmodel=kernel -funit-at-a-time -maccumulate-outgoing-args -DCONFIG_X86_X32_ABI -DCONFIG_AS_CFI=1 -DCONFIG_AS_CFI_SIGNAL_FRAME=1 -DCONFIG_AS_CFI_SECTIONS=1 -DCONFIG_AS_FXSAVEQ=1 -DCONFIG_AS_SSSE3=1 -DCONFIG_AS_CRC32=1 -DCONFIG_AS_AVX=1 -DCONFIG_AS_AVX2=1 -DCONFIG_AS_AVX512=1 -DCONFIG_AS_SHA1_NI=1 -DCONFIG_AS_SHA256_NI=1 -pipe -Wno-sign-compare -mindirect-branch=thunk-extern -mindirect-branch-register -DRETPOLINE -fno-delete-null-pointer-checks -Wno-maybe-uninitialized -O2 --param=allow-store-data-races=0 -DCC_HAVE_ASM_GOTO -Wframe-larger-than=2048 -fstack-protector -Wno-unused-but-set-variable -fno-var-tracking-assignments -fasynchronous-unwind-tables -g -gdwarf-4 -pg -mfentry -DCC_USING_FENTRY -fno-inline-functions-called-once -Wdeclaration-after-statement -Wno-pointer-sign -fno-strict-overflow -fno-merge-all-constants -fmerge-constants -fno-stack-check -fconserve-stack -Werror=implicit-int -Werror=strict-prototypes -Wno-declaration-after-statement -fno-pie -include /opt/VBoxGuestAdditions-6.0.14/src/vboxguest-6.0.14/vboxsf//include/VBox/VBoxGuestMangling.h -fshort-wchar   -I/usr/src/linux-4.4.180-102/include   -I/opt/VBoxGuestAdditions-6.0.14/src/vboxguest-6.0.14/vboxsf/   -I/opt/VBoxGuestAdditions-6.0.14/src/vboxguest-6.0.14/vboxsf/include   -I/opt/VBoxGuestAdditions-6.0.14/src/vboxguest-6.0.14/vboxsf/r0drv/linux -D__KERNEL__ -DMODULE -DRT_WITHOUT_PRAGMA_ONCE -DRT_OS_LINUX -DIN_RING0 -DIN_RT_R0 -DIN_SUP_R0 -DVBOX -DVBOX_WITH_HGCM -DIN_MODULE -DIN_GUEST -DIN_GUEST_R0 -DRT_NO_EXPORT_SYMBOL -DVBOX_WITH_64_BITS_GUESTS -DRT_ARCH_AMD64  -DMODULE  -D""KBUILD_STR(s)=#s"" -D""KBUILD_BASENAME=KBUILD_STR(dirops)""  -D""KBUILD_MODNAME=KBUILD_STR(vboxsf)"" -c -o /opt/VBoxGuestAdditions-6.0.14/src/vboxguest-6.0.14/vboxsf/.tmp_dirops.o /opt/VBoxGuestAdditions-6.0.14/src/vboxguest-6.0.14/vboxsf/dirops.c
  if [ ""-pg"" = ""-pg"" ]; then if [ /opt/VBoxGuestAdditions-6.0.14/src/vboxguest-6.0.14/vboxsf/vfsmod.o != ""scripts/mod/empty.o"" ]; then ./scripts/recordmcount  ""/opt/VBoxGuestAdditions-6.0.14/src/vboxguest-6.0.14/vboxsf/vfsmod.o""; fi; fi;
  gcc -Wp,-MD,/opt/VBoxGuestAdditions-6.0.14/src/vboxguest-6.0.14/vboxsf/.lnkops.o.d  -nostdinc -isystem /usr/lib64/gcc/x86_64-suse-linux/4.8/include -I/usr/src/linux-4.4.180-102/arch/x86/include -Iarch/x86/include/generated/uapi -Iarch/x86/include/generated  -I/usr/src/linux-4.4.180-102/include -Iinclude -I/usr/src/linux-4.4.180-102/arch/x86/include/uapi -Iarch/x86/include/generated/uapi -I/usr/src/linux-4.4.180-102/include/uapi -Iinclude/generated/uapi -include /usr/src/linux-4.4.180-102/include/linux/kconfig.h   -I/opt/VBoxGuestAdditions-6.0.14/src/vboxguest-6.0.14/vboxsf -D__KERNEL__ -Wall -Wundef -Wstrict-prototypes -Wno-trigraphs -fno-strict-aliasing -fno-common -Werror-implicit-function-declaration -Wno-format-security -std=gnu89 -fno-PIE -mno-sse -mno-mmx -mno-sse2 -mno-3dnow -mno-avx -m64 -falign-jumps=1 -falign-loops=1 -mno-80387 -mno-fp-ret-in-387 -mpreferred-stack-boundary=3 -mtune=generic -mno-red-zone -mcmodel=kernel -funit-at-a-time -maccumulate-outgoing-args -DCONFIG_X86_X32_ABI -DCONFIG_AS_CFI=1 -DCONFIG_AS_CFI_SIGNAL_FRAME=1 -DCONFIG_AS_CFI_SECTIONS=1 -DCONFIG_AS_FXSAVEQ=1 -DCONFIG_AS_SSSE3=1 -DCONFIG_AS_CRC32=1 -DCONFIG_AS_AVX=1 -DCONFIG_AS_AVX2=1 -DCONFIG_AS_AVX512=1 -DCONFIG_AS_SHA1_NI=1 -DCONFIG_AS_SHA256_NI=1 -pipe -Wno-sign-compare -mindirect-branch=thunk-extern -mindirect-branch-register -DRETPOLINE -fno-delete-null-pointer-checks -Wno-maybe-uninitialized -O2 --param=allow-store-data-races=0 -DCC_HAVE_ASM_GOTO -Wframe-larger-than=2048 -fstack-protector -Wno-unused-but-set-variable -fno-var-tracking-assignments -fasynchronous-unwind-tables -g -gdwarf-4 -pg -mfentry -DCC_USING_FENTRY -fno-inline-functions-called-once -Wdeclaration-after-statement -Wno-pointer-sign -fno-strict-overflow -fno-merge-all-constants -fmerge-constants -fno-stack-check -fconserve-stack -Werror=implicit-int -Werror=strict-prototypes -Wno-declaration-after-statement -fno-pie -include /opt/VBoxGuestAdditions-6.0.14/src/vboxguest-6.0.14/vboxsf//include/VBox/VBoxGuestMangling.h -fshort-wchar   -I/usr/src/linux-4.4.180-102/include   -I/opt/VBoxGuestAdditions-6.0.14/src/vboxguest-6.0.14/vboxsf/   -I/opt/VBoxGuestAdditions-6.0.14/src/vboxguest-6.0.14/vboxsf/include   -I/opt/VBoxGuestAdditions-6.0.14/src/vboxguest-6.0.14/vboxsf/r0drv/linux -D__KERNEL__ -DMODULE -DRT_WITHOUT_PRAGMA_ONCE -DRT_OS_LINUX -DIN_RING0 -DIN_RT_R0 -DIN_SUP_R0 -DVBOX -DVBOX_WITH_HGCM -DIN_MODULE -DIN_GUEST -DIN_GUEST_R0 -DRT_NO_EXPORT_SYMBOL -DVBOX_WITH_64_BITS_GUESTS -DRT_ARCH_AMD64  -DMODULE  -D""KBUILD_STR(s)=#s"" -D""KBUILD_BASENAME=KBUILD_STR(lnkops)""  -D""KBUILD_MODNAME=KBUILD_STR(vboxsf)"" -c -o /opt/VBoxGuestAdditions-6.0.14/src/vboxguest-6.0.14/vboxsf/.tmp_lnkops.o /opt/VBoxGuestAdditions-6.0.14/src/vboxguest-6.0.14/vboxsf/lnkops.c
  if [ ""-pg"" = ""-pg"" ]; then if [ /opt/VBoxGuestAdditions-6.0.14/src/vboxguest-6.0.14/vboxsf/dirops.o != ""scripts/mod/empty.o"" ]; then ./scripts/recordmcount  ""/opt/VBoxGuestAdditions-6.0.14/src/vboxguest-6.0.14/vboxsf/dirops.o""; fi; fi;
  gcc -Wp,-MD,/opt/VBoxGuestAdditions-6.0.14/src/vboxguest-6.0.14/vboxsf/.regops.o.d  -nostdinc -isystem /usr/lib64/gcc/x86_64-suse-linux/4.8/include -I/usr/src/linux-4.4.180-102/arch/x86/include -Iarch/x86/include/generated/uapi -Iarch/x86/include/generated  -I/usr/src/linux-4.4.180-102/include -Iinclude -I/usr/src/linux-4.4.180-102/arch/x86/include/uapi -Iarch/x86/include/generated/uapi -I/usr/src/linux-4.4.180-102/include/uapi -Iinclude/generated/uapi -include /usr/src/linux-4.4.180-102/include/linux/kconfig.h   -I/opt/VBoxGuestAdditions-6.0.14/src/vboxguest-6.0.14/vboxsf -D__KERNEL__ -Wall -Wundef -Wstrict-prototypes -Wno-trigraphs -fno-strict-aliasing -fno-common -Werror-implicit-function-declaration -Wno-format-security -std=gnu89 -fno-PIE -mno-sse -mno-mmx -mno-sse2 -mno-3dnow -mno-avx -m64 -falign-jumps=1 -falign-loops=1 -mno-80387 -mno-fp-ret-in-387 -mpreferred-stack-boundary=3 -mtune=generic -mno-red-zone -mcmodel=kernel -funit-at-a-time -maccumulate-outgoing-args -DCONFIG_X86_X32_ABI -DCONFIG_AS_CFI=1 -DCONFIG_AS_CFI_SIGNAL_FRAME=1 -DCONFIG_AS_CFI_SECTIONS=1 -DCONFIG_AS_FXSAVEQ=1 -DCONFIG_AS_SSSE3=1 -DCONFIG_AS_CRC32=1 -DCONFIG_AS_AVX=1 -DCONFIG_AS_AVX2=1 -DCONFIG_AS_AVX512=1 -DCONFIG_AS_SHA1_NI=1 -DCONFIG_AS_SHA256_NI=1 -pipe -Wno-sign-compare -mindirect-branch=thunk-extern -mindirect-branch-register -DRETPOLINE -fno-delete-null-pointer-checks -Wno-maybe-uninitialized -O2 --param=allow-store-data-races=0 -DCC_HAVE_ASM_GOTO -Wframe-larger-than=2048 -fstack-protector -Wno-unused-but-set-variable -fno-var-tracking-assignments -fasynchronous-unwind-tables -g -gdwarf-4 -pg -mfentry -DCC_USING_FENTRY -fno-inline-functions-called-once -Wdeclaration-after-statement -Wno-pointer-sign -fno-strict-overflow -fno-merge-all-constants -fmerge-constants -fno-stack-check -fconserve-stack -Werror=implicit-int -Werror=strict-prototypes -Wno-declaration-after-statement -fno-pie -include /opt/VBoxGuestAdditions-6.0.14/src/vboxguest-6.0.14/vboxsf//include/VBox/VBoxGuestMangling.h -fshort-wchar   -I/usr/src/linux-4.4.180-102/include   -I/opt/VBoxGuestAdditions-6.0.14/src/vboxguest-6.0.14/vboxsf/   -I/opt/VBoxGuestAdditions-6.0.14/src/vboxguest-6.0.14/vboxsf/include   -I/opt/VBoxGuestAdditions-6.0.14/src/vboxguest-6.0.14/vboxsf/r0drv/linux -D__KERNEL__ -DMODULE -DRT_WITHOUT_PRAGMA_ONCE -DRT_OS_LINUX -DIN_RING0 -DIN_RT_R0 -DIN_SUP_R0 -DVBOX -DVBOX_WITH_HGCM -DIN_MODULE -DIN_GUEST -DIN_GUEST_R0 -DRT_NO_EXPORT_SYMBOL -DVBOX_WITH_64_BITS_GUESTS -DRT_ARCH_AMD64  -DMODULE  -D""KBUILD_STR(s)=#s"" -D""KBUILD_BASENAME=KBUILD_STR(regops)""  -D""KBUILD_MODNAME=KBUILD_STR(vboxsf)"" -c -o /opt/VBoxGuestAdditions-6.0.14/src/vboxguest-6.0.14/vboxsf/.tmp_regops.o /opt/VBoxGuestAdditions-6.0.14/src/vboxguest-6.0.14/vboxsf/regops.c
/opt/VBoxGuestAdditions-6.0.14/src/vboxguest-6.0.14/vboxsf/regops.c: In function ‘vbsf_lock_user_pages’:
/opt/VBoxGuestAdditions-6.0.14/src/vboxguest-6.0.14/vboxsf/regops.c:1440:52: warning: passing argument 1 of ‘get_user_pages_unlocked’ makes integer from pointer without a cast [enabled by default]
                                                    fWrite ? FOLL_WRITE | FOLL_FORCE : FOLL_FORCE);
                                                    ^
In file included from /opt/VBoxGuestAdditions-6.0.14/src/vboxguest-6.0.14/vboxsf/r0drv/linux/the-linux-kernel.h:101:0,
                 from /opt/VBoxGuestAdditions-6.0.14/src/vboxguest-6.0.14/vboxsf/vfsmod.h:43,
                 from /opt/VBoxGuestAdditions-6.0.14/src/vboxguest-6.0.14/vboxsf/regops.c:35:
/usr/src/linux-4.4.180-102/include/linux/mm.h:1294:6: note: expected ‘long unsigned int’ but argument is of type ‘struct task_struct *’
 long get_user_pages_unlocked(unsigned long start, unsigned long nr_pages,
      ^
/opt/VBoxGuestAdditions-6.0.14/src/vboxguest-6.0.14/vboxsf/regops.c:1440:52: warning: passing argument 2 of ‘get_user_pages_unlocked’ makes integer from pointer without a cast [enabled by default]
                                                    fWrite ? FOLL_WRITE | FOLL_FORCE : FOLL_FORCE);
                                                    ^
In file included from /opt/VBoxGuestAdditions-6.0.14/src/vboxguest-6.0.14/vboxsf/r0drv/linux/the-linux-kernel.h:101:0,
                 from /opt/VBoxGuestAdditions-6.0.14/src/vboxguest-6.0.14/vboxsf/vfsmod.h:43,
                 from /opt/VBoxGuestAdditions-6.0.14/src/vboxguest-6.0.14/vboxsf/regops.c:35:
/usr/src/linux-4.4.180-102/include/linux/mm.h:1294:6: note: expected ‘long unsigned int’ but argument is of type ‘struct mm_struct *’
 long get_user_pages_unlocked(unsigned long start, unsigned long nr_pages,
      ^
/opt/VBoxGuestAdditions-6.0.14/src/vboxguest-6.0.14/vboxsf/regops.c:1440:52: warning: passing argument 3 of ‘get_user_pages_unlocked’ makes pointer from integer without a cast [enabled by default]
                                                    fWrite ? FOLL_WRITE | FOLL_FORCE : FOLL_FORCE);
                                                    ^
In file included from /opt/VBoxGuestAdditions-6.0.14/src/vboxguest-6.0.14/vboxsf/r0drv/linux/the-linux-kernel.h:101:0,
                 from /opt/VBoxGuestAdditions-6.0.14/src/vboxguest-6.0.14/vboxsf/vfsmod.h:43,
                 from /opt/VBoxGuestAdditions-6.0.14/src/vboxguest-6.0.14/vboxsf/regops.c:35:
/usr/src/linux-4.4.180-102/include/linux/mm.h:1294:6: note: expected ‘struct page **’ but argument is of type ‘uintptr_t’
 long get_user_pages_unlocked(unsigned long start, unsigned long nr_pages,
      ^
/opt/VBoxGuestAdditions-6.0.14/src/vboxguest-6.0.14/vboxsf/regops.c:1440:52: error: too many arguments to function ‘get_user_pages_unlocked’
                                                    fWrite ? FOLL_WRITE | FOLL_FORCE : FOLL_FORCE);
                                                    ^
In file included from /opt/VBoxGuestAdditions-6.0.14/src/vboxguest-6.0.14/vboxsf/r0drv/linux/the-linux-kernel.h:101:0,
                 from /opt/VBoxGuestAdditions-6.0.14/src/vboxguest-6.0.14/vboxsf/vfsmod.h:43,
                 from /opt/VBoxGuestAdditions-6.0.14/src/vboxguest-6.0.14/vboxsf/regops.c:35:
/usr/src/linux-4.4.180-102/include/linux/mm.h:1294:6: note: declared here
 long get_user_pages_unlocked(unsigned long start, unsigned long nr_pages,
      ^
/opt/VBoxGuestAdditions-6.0.14/src/vboxguest-6.0.14/vboxsf/regops.c: At top level:
/opt/VBoxGuestAdditions-6.0.14/src/vboxguest-6.0.14/vboxsf/regops.c:3780:5: warning: initialization from incompatible pointer type [enabled by default]
     .direct_IO      = vbsf_direct_IO,
     ^
/opt/VBoxGuestAdditions-6.0.14/src/vboxguest-6.0.14/vboxsf/regops.c:3780:5: warning: (near initialization for ‘vbsf_reg_aops.direct_IO’) [enabled by default]
/usr/src/linux-4.4.180-102/scripts/Makefile.build:278: recipe for target '/opt/VBoxGuestAdditions-6.0.14/src/vboxguest-6.0.14/vboxsf/regops.o' failed
make[4]: *** [/opt/VBoxGuestAdditions-6.0.14/src/vboxguest-6.0.14/vboxsf/regops.o] Error 1
make[4]: *** Waiting for unfinished jobs....
  if [ ""-pg"" = ""-pg"" ]; then if [ /opt/VBoxGuestAdditions-6.0.14/src/vboxguest-6.0.14/vboxsf/lnkops.o != ""scripts/mod/empty.o"" ]; then ./scripts/recordmcount  ""/opt/VBoxGuestAdditions-6.0.14/src/vboxguest-6.0.14/vboxsf/lnkops.o""; fi; fi;
/usr/src/linux-4.4.180-102/Makefile:1462: recipe for target '_module_/opt/VBoxGuestAdditions-6.0.14/src/vboxguest-6.0.14/vboxsf' failed
make[3]: *** [_module_/opt/VBoxGuestAdditions-6.0.14/src/vboxguest-6.0.14/vboxsf] Error 2
Makefile:152: recipe for target 'sub-make' failed
make[2]: *** [sub-make] Error 2
Makefile:24: recipe for target '__sub-make' failed
make[1]: *** [__sub-make] Error 2
make[1]: Leaving directory '/usr/src/linux-4.4.180-102-obj/x86_64/default'
/opt/VBoxGuestAdditions-6.0.14/src/vboxguest-6.0.14/vboxsf/Makefile-footer.gmk:111: recipe for target 'vboxsf' failed
make: *** [vboxsf] Error 2
}}}

XXX the error is around the usage of get_user_pages_unlocked()
{{{
/opt/VBoxGuestAdditions-6.0.14/src/vboxguest-6.0.14/vboxsf/regops.c:1440:52: warning: passing argument 2 of ‘get_user_pages_unlocked’ makes integer from pointer without a cast [enabled by default]
                                                    fWrite ? FOLL_WRITE | FOLL_FORCE : FOLL_FORCE);
                                                    ^
In file included from /opt/VBoxGuestAdditions-6.0.14/src/vboxguest-6.0.14/vboxsf/r0drv/linux/the-linux-kernel.h:101:0,
                 from /opt/VBoxGuestAdditions-6.0.14/src/vboxguest-6.0.14/vboxsf/vfsmod.h:43,
                 from /opt/VBoxGuestAdditions-6.0.14/src/vboxguest-6.0.14/vboxsf/regops.c:35:
/usr/src/linux-4.4.180-102/include/linux/mm.h:1294:6: note: expected ‘long unsigned int’ but argument is of type ‘struct mm_struct *’
 long get_user_pages_unlocked(unsigned long start, unsigned long nr_pages,
      ^
/opt/VBoxGuestAdditions-6.0.14/src/vboxguest-6.0.14/vboxsf/regops.c:1440:52: warning: passing argument 3 of ‘get_user_pages_unlocked’ makes pointer from integer without a cast [enabled by default]
                                                    fWrite ? FOLL_WRITE | FOLL_FORCE : FOLL_FORCE);

In file included from /opt/VBoxGuestAdditions-6.0.14/src/vboxguest-6.0.14/vboxsf/r0drv/linux/the-linux-kernel.h:101:0,
                 from /opt/VBoxGuestAdditions-6.0.14/src/vboxguest-6.0.14/vboxsf/vfsmod.h:43,
                 from /opt/VBoxGuestAdditions-6.0.14/src/vboxguest-6.0.14/vboxsf/regops.c:35:
/usr/src/linux-4.4.180-102/include/linux/mm.h:1294:6: note: expected ‘struct page **’ but argument is of type ‘uintptr_t’
 long get_user_pages_unlocked(unsigned long start, unsigned long nr_pages,
      ^
/opt/VBoxGuestAdditions-6.0.14/src/vboxguest-6.0.14/vboxsf/regops.c:1440:52: error: too many arguments to function ‘get_user_pages_unlocked’
                                                    fWrite ? FOLL_WRITE | FOLL_FORCE : FOLL_FORCE);
                                                    ^
}}}
",Frank Batschulat (Oracle)
19086,rm / rmdir  not working correctly in shared folders,VirtualBox 6.0.14,Linux,2019-11-14T07:22:32Z,2021-04-15T22:30:27Z,2021-04-15T22:30:27Z,"As it seems that comments to existing tickets are not enough, I make a ticket out of my comment to #18569.

Since the beginning of VirtualBox v6.x the ""rm -r"" command is not working correctly in shared folder within a Linux guest.

I attach a screen shot of an example what happens.

Host: Windows 10 1903
Guest: CentOS 6.6, kernel 2.6.32-504.el6.x86_64",Reiner Brodbeck
18908,The access to shared folder hangs the vmachine and makes it to restart itself,VirtualBox 6.0.10,Windows,2019-09-05T06:31:47Z,2019-09-05T09:07:55Z,2019-09-05T09:07:55Z,"Sometimes when I connect to the shared folder the vmachine W1064bits hangs and 1 or 2 seconds after, restarts itself. I change the host machine, I reinstall a new vmachine but I got the same issue.
I updates the guestaddit from 6.0.10 to 6.0.12 but no change",llazare
18877,binary in shared folder loses executable permission while running,VirtualBox 6.0.10,Linux,2019-08-29T07:36:41Z,2019-08-29T07:36:41Z,2019-08-29T07:36:41Z,"After upgrading from virtualbox v5.0 to v6.0.10 I was not able to execute a binary from a shared folder (host Windows, guest Ubuntu) twice in parallel: while executing its permission would change from -rwxrwxrwx to -rw-rw-rw-.

I had mounted it via a line in /etc/fstab:
{{{
FolderName  /home/somewhere vboxsf rw,uid=1000,gid=1000,dmode=755  0  0
}}}

how to reproduce: with that mount:
{{{
cp /bin/cat /home/somewhere/cat2
ls -l /home/somewhere/cat2 # => permissions -rwxrwxrwx, owner me:me
/home/somewhere/cat2 &
ls -l /home/somewhere/cat2 # => permissions -rw-rw-rw-
/home/somewhere/cat2   # => 'permission denied'
}}}
After stopping the running executable the permissions return to -rwxrwxrwx again.

Mounting as an automount instead resolves the problem: cat2 has owner root:vboxsf, and permissions -rwxrwx--- - and that doesn't change while running.

",nijhof
18798,Virtual machine windows 10 auto restart  when click on one folder in shared disk (internal disk host or USB),VirtualBox 6.0.10,Windows,2019-07-31T17:52:49Z,2019-08-16T06:59:35Z,2019-08-16T06:59:35Z,"* I'm working with a zip compressed file at a shared disk (on host is a USB DIsk 4 TB)
* Try expand, and crash
* Try another, and crash.
* Move to other shared folder (in host is a internal disk 3TB)
* Uncompressed well.
* After click on folder Setup, crash other time.
",Abdelkarim Mateos Sánchez
18776,"Vagrant shared folders unable to install Package Management Plugins (Composer, PHP)",VirtualBox 6.0.10,Linux,2019-07-21T16:22:45Z,2021-04-15T22:28:48Z,2021-04-15T22:28:48Z,"## Versions

* MacOS: Mojave 10.14.5 (18F132)
* Virtualbox: `6.0.10 r132072 (Qt5.6.3) (And Exentions)`
* Vagrant: 2.2.5
* Vagrant box: bento/ubuntu-18.04 201906.18.0

## Problem

Unable to install Composer (PHP Package Manager) plugins on folders shared via Virtualbox (vboxsf)

## Steps To Reproduce:

Clone: https://github.com/svpernova09/vagrant-test

* Adjust folder share of `~/Code/fresh-laravel` to a fresh [Laravel](https://github.com/laravel/laravel) installation
* Run `vagrant up`
* Run `vagrant ssh`
* Run `cd larvel`
* Run `composer require ocramius/package-versions`
* See ""Could not delete /home/vagrant/laravel/vendor/ocramius/package-versions/src/PackageVersions:""
* Run `cd`
* Run `composer create-project laravel/laravel not-vbox-share`
* Run `cd not-vbox-share`
* Run `composer require ocramius/package-versions`
* See ""Package manifest generated successfully.""

## Logs

Here is a gist of the relevant actions: https://gist.github.com/svpernova09/17f7a2c9aba316e24bb063a25010d6f6",Svpernova09
18704,Windows-KB890830-x64-V5.73 (current Windows malicious software removal tool) in the shared folder causes crush  of the guest OS,VirtualBox 6.0.8,Windows,2019-06-12T07:29:21Z,2019-08-17T06:43:06Z,2019-08-17T06:43:06Z,"As I wrote, during the today’s Windows updates I downloaded the current version of t x64 MSRT and put it in the shared folder. As soon as I access the shared folder afterwards, the shared folder is shown empty. Shortly after that, the display (not the window) of the guest resizes to something very small like 640 × 480; couple of seconds later the BSOD happens and guest would be restarted.

I put my logs, directory listing of the shared folders and BSOD numbers in the archive. If something else is needed, just let me know. The logs clearly shows the detection of the critical condition. As soon as this file is removed from the shard folders, everything works as it should. This is Windows 10 1809 x64 guest and host combination.",boxer01
18680,Create symbolic links in shared folders without administrator priviledges using new Windows 10 Developer Mode,VirtualBox 6.0.8,Linux,2019-05-29T13:27:20Z,2022-04-02T12:16:40Z,2022-04-02T12:16:40Z,"Starting with [https://blogs.windows.com/buildingapps/2016/12/02/symlinks-windows-10/#jiIm1mzyjuXxAFXr.97 Windows 10 Insiders build 14972] symlinks can be created without needing to elevate the console as administrator. The prerequisite is to enable ''Developer Mode'', and after that any user on the machine can
1. Run the `mklink` command without elevating a command-line console
2. Use CreateSymbolicLink API '''if''' additional ''dwFlags'' option `SYMBOLIC_LINK_FLAG_ALLOW_UNPRIVILEGED_CREATE` is set to `0x2`.

Since even after enabling the ''Developer Mode'' VirtualBox has to be run as Administrator in order to create symlinks in shard folders, I assume the method 2 i.e. API calls are used to create them.

My enhancement request: Please add the `SYMBOLIC_LINK_FLAG_ALLOW_UNPRIVILEGED_CREATE` to the API call when creating symlinks to shared folders under Windows 10 so Administrator priviledges are not required when ''Developer Mode'' is enabled.",asmala
18675,File corruption on shared folder - Linux host + Windows 7 guest,VirtualBox 6.0.8,Windows,2019-05-24T17:16:26Z,2019-06-05T00:38:48Z,2019-06-05T00:38:48Z,"Setup :
Host : Ubuntu 16.04 x64
Guest : Windows 7 x64
Shared folder (on ext4 partition) between host and guest

I'm using a Windows 7 virtual machine only for Adobe Photoshop CS6 x64.

Before v6.0.8 I installed v6.0.6 only briefly, I had to revert back to 6.0.4 because of the mouse integration bug. So I for the present issue I installed 6.0.8 over 6.0.4.

I encountered a strange behaviour with the shared folder I'm using to exchange files between the host and the guest. 
In Photoshop CS6 x64, after I installed VirtualBox v6.0.8, sometimes Photoshop tells me it couldn't read the TIFF files I had worked on before. And when it could, sometimes the content was scrambled.
I checked my images in other software (under Windows ''and'' Ubuntu) : correct.
I opened the files in the VM with Photoshop CS6 x32 this time : correct.
I checked my TIFF files with an utility called jHove, which checks the TIF file integrity : no errors.
So my image files are without flaws. I can save them in Photoshop but not read them back, at least in the x64 version. Weird.
I also copied the files directly on the guest : this time Photoshop CS6 x64 was happy.

For 2 days I have tested many things. It only occurs in Photoshop CS6 x64, when I'm using the shared folder.

So I decided to revert back to VirtualBox v6.0.4, and dang! Photoshop CS6 x64 was happy again with my files...

So my conclusion is the problem comes from the shared folder functions, but only when reading my files, not when I'm writing.

I'm including my v6.0.4 last log file, I didn't think about saving one when I was under v6.0.8 sorry.",Parazythum
18631,Win10/Win 10 Error 0x80070032: Can't copy file from VM to Host through Shared Folders,VirtualBox 6.0.6,Windows,2019-05-08T23:07:38Z,2019-05-08T23:07:38Z,2019-05-08T23:07:38Z,"This looks a lot like https://forums.virtualbox.org/viewtopic.php?f=2&t=84800&sid=99e7dde8811ab1c34e06e7a4e5057507 except for VirtualBox 6.0.6 r130049 (Qt5.6.2)

 Windows 10 Host (Surfacebook Laptop) [Version 10.0.17763.475][[BR]]

 Windows 10 VM [Version 10.0.17763.437][[BR]]

 VirtualBox 6.0.6 r130049 (Qt5.6.2)

The issue is I can't copy a file from the VM to the Host through the Shared folders path, both from the GUI and the command line with Host filesystems permissions set to [Everyone - Full Access].

Command Line Example:[[BR]]

C:\Users\v-crarno>copy C:\Users\v-crarno\Desktop\Redcley\iotil-hanford-rpi-core\c-sharp\EnvironmentMonitoringApp\EnvironmentMonitoringApp\bin\ARM\Debug\Microsoft.Maker.Sparkfun.WeatherShield.winmd Z:\Users\craig\Documents\Redcley\iotil-hanford-rpi-core\c-sharp\EnvironmentMonitoringApp\EnvironmentMonitoringApp\bin\ARM[[BR]]

'''The request is not supported.'''
        0 file(s) copied.

C:\Users\v-crarno>ver

Microsoft Windows [Version 10.0.17763.437]

From the GUI I get the File Copy Error 0x80070032.

What I -can- do from the VM on the Shared folder is ""Create a file"", and ""Delete a file"".  And I can make a copy of a remote file [copy z:\... z:\...].  I just can't copy from C:\... to Z:\... [VM to Host]

Another important difference is I'm logged into a Domain Joined system in the VM, and Windows Networking with a different userID on the host system. I opened up security on the destination folder to [Everyone-Full Access]",craiga
18616,Shared Folder error when using reposync,VirtualBox 6.0.6,Linux,2019-05-02T02:51:55Z,2019-05-07T05:39:21Z,2019-05-07T05:39:21Z,"I have a couple of VMs (specifically CentOS6 and CentOS7) that I use to sync repositories for a disconnected network. EPEL, Cloudera, MySQL, etc. I keep these VMs pretty lean and but mount Shared Folders to a USB so that I can transfer the files. I download the files in the repos directly to the Shared Folder. For example to update the EPEL6 repository. I cd into a directory on the Shared Folder and use the command, reposync -n -d -r epel6. Since 6.0.6 this causes errors. To test it I tried a created a new directory and here is a sample output from one of the first attempted download:

[jrather@localhost sat]$ reposync -n -d -r epel6
[epel6: 1     of 12532 ] Downloading Packages/2/2048-cli-0.9.1-1.el6.x86_64.rpm
Could not retrieve package 2048-cli-0.9.1-1.el6.x86_64. Error was failure: Packages/2/2048-cli-0.9.1-1.el6.x86_64.rpm from epel6: [Errno 256] No more mirrors to try.

I get errors on every file. If I try the command within a directory on the VM (for example, /tmp or my user's home directory) everything is fine. It is only with the Shared Folder or trying to write to it. This error occurs with the CentOS7 guest too. I have tried it from both CentOS7 host and Ubuntu 18.04 host both with Guest Additions installed. I have also tried using a physical disk for the Shared Folder instead of USB drive with the same results. This used to work fine with 6.0.4 and previous versions.

I am not sure what else to submit but would be more than happy to if instructed.",jim.rather
18559,shared folder host system locks virtual machine,VirtualBox 6.0.4,Windows,2019-04-15T01:22:56Z,2019-04-15T09:19:54Z,2019-04-15T09:19:54Z,"I am having problems with 32 bit virtual machines in folder sharing, when I go to any shared system main folder the virtual machine hangs and all applications",jair pinho
18554,systemd startup script not updated during guest additions install,VirtualBox 6.0.4,Linux,2019-04-09T21:12:47Z,2019-07-29T12:30:00Z,2019-07-29T12:30:00Z,"Environment:[[BR]]
Host: Windows 10 Enterprise[[BR]]
Guest: Linux Mint 19.1[[BR]]

I upgraded my host Virtualbox install from version 5.2.26 to 6.0.4[[BR]]
 
After booting the Linux Mint guest I was prompted to update the virtualbox guest additions.

This appears to install correctly, however when rebooting the guest, vbox shared folders don't appear to mount.

I eventually traced the issue down to the systemd startup script located in /etc/systemd/system/vboxadd-service.service 

When querying the status of the service startup after updating to guest additions version 6.0.4 this error is shown:

Apr 09 14:06:21 Mint-19 systemd[4423]: vboxadd-service.service: Failed at step EXEC spawning /opt/VBoxGuestAdditions-5.2.26/init/vboxadd-service: No such file or directory


I then manually edited the /etc/systemd/system/vboxadd-service.service service file and changed all entries for the path /opt/VBoxGuestAdditions-5.2.26/ to the path /opt/VBoxGuestAdditions-6.0.4/

I then reloaded systemd and started up the vboxadd-service successfully, with host shared folders mounting on the guest as expected",Chuck Donahue
18546,If a rootFolder of a Novell eDir is Shared it can not be accessed,VirtualBox 6.0.4,Windows,2019-04-05T08:53:10Z,2019-04-05T08:53:10Z,2019-04-05T08:53:10Z,"This happens since Oracle VirtualBox version 5.2.2 (so 5.2.0 is the last version where access to a Novell eDirectory Root Folder is possible!)

If you share a subdirectory of the eDir-Root it works!

This happens with Shared Server-Directorys from:
Novell E-Directrory Version 8.8. SP5
NDS Version: 20219.15

Host = Windows 7 Pro x64
Guest = Windows 10 LTSB x64",SO4620
18478,"Impossible to copy files or dir beginning with a dot from guest to host, the 2 ones being Windows machines.",VirtualBox 6.0.4,Windows,2019-03-06T10:05:14Z,2019-03-08T05:04:48Z,2019-03-08T05:04:48Z,"Impossible to copy '''files or dir beginning with a dot''' from guest to host, the 2 ones being Windows machines. 

This is the summary of several existing tickets : #17859, #17067, #16762.

",JLB
18469,Version 6.0.4 r128413 (Qt5.6.2) Shared Folders not Accessible,VirtualBox 6.0.4,Windows,2019-03-04T07:37:36Z,2019-03-05T09:47:01Z,2019-03-05T09:47:01Z,"When the save machine state on Version 6.0.4 r128413 (Qt5.6.2) shared folders disconnected and is not reconnect until system complete restart. Saved state is not possible with shared folders.
Shared folders drive letter seems in Win7 Explorer but not connected. User is not enter to the drive. 

Host: Windows 7 Ultimate 64 Bit
Guest: Windows 7 Ultimate 64 Bit
All extension package and VirtualBox Guest Additions installed.
",Flu
18379,New OS/2 shared folders feature locks up the guest => Fixed in SVN,VirtualBox 6.0.4,other,2019-01-29T05:44:57Z,2019-05-19T05:04:23Z,2019-05-19T05:04:23Z,"After adding the new shared folders installable file system (VBoxSF.IFS) the guest GUI started to lock up just a second after VBoxService is executed from STARTUP.CMD. The mouse cursor still moves, so this is not a hard lock, but any interaction with GUI is impossible. The guest has to be powered off. The only workaround is to comment out the IFS statement in CONFIG.SYS.
",Rafcio
18332,Windows 10 Guest additions 6.0.2 scramble drive mappings into shared folders,VirtualBox 6.0.2,Windows,2019-01-19T02:50:26Z,2019-01-20T02:17:18Z,2019-01-20T02:17:18Z,"Running Win 10 Pro (October 2018 Update, build 17763) on both host and guests, updated host from 5.2.22 to 6.0.2 with 6.0.2 guest additions.  Upgrading guest VMs to 6.02 guest additions scrambled the mapped drives into shared folders.  The windows drive mappings no longer corresponded to the originally assigned shared folders,.  Rolling back to a previous version of the VM (which still had 5.2.22 guest additions installed restored correct behavior.  

FWIW:
  net use v: \\vboxsrv\bbj5-c /persistent:yes
  net use w: \\vboxsrv\data   /persistent:yes
  net use x: \\vboxsrv\bbj5-e /persistent:yes
  net use y: \\vboxsrv\a      /persistent:yes
  net use z: \\vboxsrv\aa     /persistent:yes


Reproduced this behavior on a second (and different) vin 10 pro vm: changing nothing other than upgrading guest additions from 5.2.22 to 6.0.2 corrupted the mappings into shared folders.  

two logs
w10p-1-2019-01-18-21-21-45.log  scrambled VM 6.02 guest additions
w10p-1-2019-01-18-21-41-13.log	correctly mapped VM 5.2.22 guest additions					",BBoyar
18322,Shared folders hang while R/W access,VirtualBox 6.0.2,Windows,2019-01-17T13:07:17Z,2019-08-29T07:37:09Z,2019-08-29T07:37:09Z,"Host `lsb_release -a` is 
{{{
Distributor ID: Debian
Description:    Debian GNU/Linux 8.11 (jessie)
Release:        8.11
Codename:       jessie
}}}


I'm using shared folders in Windows 7 x86 guest and Mentor Expedition PCB hangs if I try to open project, placed on shared disk.

This behavior is not observed if I replace guest additions with version 5.2.22. Versions 6.0.0 and 6.0.2 show exactly the same behavior.

Other read/write operations doesn't show any problem (at this time).

I've tried to investigate hanging I/O operation in Expedition PCB and with the Process Monitor (Sysinternals) found, that last unfinished call was '''QueryDirectory'''. This event description from ProcMon is

{{{
Date & Time:	17.01.2019 14:58:38
Event Class:	File System
Operation:	QueryDirectory
Result:	
Path:	\Device\VBoxMiniRdr\VBOXSVR\VM_Shared\KiberLock-NET\20190115\KibLck-NET_v1p0\PCB\.lck_dir\*.lckreq
TID:	4996
Duration:	
Filter:	*.lckreq
}}}

Call stack (reported by ProcMon) is

{{{
0	fltmgr.sys	FltRequestOperationStatusCallback + 0xe8f	0xca0b3df7	C:\Windows\system32\drivers\fltmgr.sys
1	fltmgr.sys	FltGetIrpName + 0xc56	0xca0b6d38	C:\Windows\system32\drivers\fltmgr.sys
2	fltmgr.sys	FltGetIrpName + 0x116f	0xca0b7251	C:\Windows\system32\drivers\fltmgr.sys
3	fltmgr.sys	FltGetIrpName + 0x162e	0xca0b7710	C:\Windows\system32\drivers\fltmgr.sys
4	ntkrnlpa.exe	IofCallDriver + 0x64	0xe323c117	C:\Windows\system32\ntkrnlpa.exe
5	ntkrnlpa.exe	NtSetEvent + 0x2c1	0xe3439f12	C:\Windows\system32\ntkrnlpa.exe
6	ntkrnlpa.exe	NtQueryDirectoryFile + 0x5b	0xe3444528	C:\Windows\system32\ntkrnlpa.exe
7	ntkrnlpa.exe	ZwYieldExecution + 0xf4e	0xe3242b8e	C:\Windows\system32\ntkrnlpa.exe
8	ntdll.dll	NtQueryDirectoryFile + 0xc	0x77825acc	C:\Windows\System32\ntdll.dll
9	KernelBase.dll	FindFirstFileExW + 0x276	0x7598b355	C:\Windows\System32\KernelBase.dll
10	KernelBase.dll	FindFirstFileA + 0x4a	0x7599a956	C:\Windows\System32\KernelBase.dll
11	xf_Os.dll	xf_Os.dll + 0x4f3d	0x10004f3d	C:\MentorGraphics\7.9.5EE\SDD_HOME\common\win32\lib\xf_Os.dll
}}}

And another similar hang event from ProcMon and another process, tried to call the '''WriteFile''':

{{{
Date & Time:	17.01.2019 16:02:08
Event Class:	File System
Operation:	WriteFile
Result:	
Path:	\Device\VBoxMiniRdr\VBOXSVR\VM_Shared\KIBERLOCK-NET\20190115\KIBLCK-NET_V1P0\database\cdbsvr\log\2019-01-17 16.02.07-1536\2019.01.17.txt
TID:	2648
Duration:	
Offset:	6,109
Length:	82
Priority:	Normal
}}}

Call stack is very similar to the '''QueryDirectory''' one:
{{{
0	fltmgr.sys	FltRequestOperationStatusCallback + 0xe8f	0xca0b3df7	C:\Windows\system32\drivers\fltmgr.sys
1	fltmgr.sys	FltGetIrpName + 0xc56	0xca0b6d38	C:\Windows\system32\drivers\fltmgr.sys
2	fltmgr.sys	FltGetIrpName + 0x116f	0xca0b7251	C:\Windows\system32\drivers\fltmgr.sys
3	fltmgr.sys	FltGetIrpName + 0x162e	0xca0b7710	C:\Windows\system32\drivers\fltmgr.sys
4	ntkrnlpa.exe	IofCallDriver + 0x64	0xe323c117	C:\Windows\system32\ntkrnlpa.exe
5	ntkrnlpa.exe	NtSetEvent + 0x2c1	0xe3439f12	C:\Windows\system32\ntkrnlpa.exe
6	ntkrnlpa.exe	NtWriteFile + 0x6fe	0xe3480994	C:\Windows\system32\ntkrnlpa.exe
7	ntkrnlpa.exe	ZwYieldExecution + 0xf4e	0xe3242b8e	C:\Windows\system32\ntkrnlpa.exe
8	ntdll.dll	ZwWriteFile + 0xc	0x7782659c	C:\Windows\System32\ntdll.dll
9	KernelBase.dll	WriteFile + 0x5f	0x759875ad	C:\Windows\System32\KernelBase.dll
10	kernel32.dll	WriteFile + 0x4e	0x768d56e4	C:\Windows\System32\kernel32.dll
11	msvcr90.dll	lseeki64 + 0x56b	0x71cc99ad	C:\Windows\winsxs\x86_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.6161_none_50934f2ebcb7eb57\msvcr90.dll
12	msvcr90.dll	write + 0x9f	0x71cc9d37	C:\Windows\winsxs\x86_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.6161_none_50934f2ebcb7eb57\msvcr90.dll
13	msvcr90.dll	fdopen + 0x1c0	0x71c8fea2	C:\Windows\winsxs\x86_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.6161_none_50934f2ebcb7eb57\msvcr90.dll
14	msvcr90.dll	fflush_nolock + 0x1c	0x71c8fef0	C:\Windows\winsxs\x86_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.6161_none_50934f2ebcb7eb57\msvcr90.dll
15	msvcr90.dll	fflush + 0x30	0x71c90030	C:\Windows\winsxs\x86_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.6161_none_50934f2ebcb7eb57\msvcr90.dll
16	iCDBNetServer.exe	iCDBNetServer.exe + 0x47fe6d	0x87fe6d	C:\MentorGraphics\7.9.5EE\SDD_HOME\common\win32\bin\iCDBNetServer.exe

}}}


",makc
18252,RFE. VirtualBox 6 MacOS 10.14.2 host with 10.12.6 guest - network share doesn't appear,VirtualBox 6.0.0,other,2018-12-30T20:43:01Z,2019-01-08T17:58:48Z,2019-01-08T17:58:48Z,"1. Guest Additions was added (copy/paste works).
2. A Share was setup and as many times as I go into settings for the VM I can see the share as I set it up.

Yes there's no directory on the guest OS
",paul_h
18251,Unable to mount shared windows folder to Linux via VirtualBox,VirtualBox 5.2.20,Linux,2018-12-30T17:54:34Z,2018-12-30T20:57:08Z,2018-12-30T20:57:08Z,"Unable to mount shared windows folder to Linux via VirtualBox

I am following steps mentioned in the below below blog 
https://blogs.sap.com/2017/09/04/newbies-guide-installing-abap-as-751-sp02-on-linux/

I am using Version 5.2.22 r126460 (Qt5.6.2) VirtualBox - I installed Linux  openSUSE-Leap-42.3-DVD-x86_64.iso version. 

The config goes through fine in Virtual Box but when I look for the cd /media/sf_s4installer folder ( media folder) - it is not available in Linux. 

Please help. 

Thanks,
Rama 
",Rama
18245,Prevent boot if Shared folder is not available or Require Shared folder in order to boot,VirtualBox 6.0.0,Windows,2018-12-28T18:52:56Z,2019-01-03T16:01:54Z,2019-01-03T16:01:54Z,"I searched but could not find an answer for this. Is there a way to prevent a guest system from booting if the attached Shared Folder is unavailable? I realize you get a prompt disclosing this fact, but I would like to prevent the VM from booting.",jim.rather
18189,"VirtualBox created ""System Volume Information"" folder in all Shared Folders on Host on Version 6.0 RC1",,Windows,2018-12-16T17:33:38Z,2018-12-16T17:54:34Z,2018-12-16T17:54:34Z,"I've got 4 shared folders on my VM
VirtualBox 6.0 RC1 created a ""System Volume Information"" folder in all Shared Folders on my Host 
I'm on Mac OS X MOJAVE 
The Guest is Windows 10 64bits",jlavancier
18167,"Shared Folders: if disk removed from host, all disks don't auto-mount in guest",VirtualBox 5.2.22,Linux,2018-12-04T00:30:30Z,2018-12-04T00:30:30Z,2018-12-04T00:30:30Z,"Host: Win7 + VBox 5.2.22 (tried 6.0-BETA3)

Guest: Debian Linux 9

I have multiple mounts enabled:
1. DRIVE_C
2. DRIVE_D
3. DRIVE_E
4. DRIVE_F


now... I have removed drive D from host (physically disconnecting HDD).
what happens next is that Auto-mount only works for Disk C, then it fails for D (expected), but also for Disk E and F... (which must not happen).
Every letter is physically separate HDD.

{{{
root@deb9ws:~# ls /media/sf_C_DRIVE/                                                                                                                                                                              
$Recycle.Bin  Documents and Settings  Install-UltraISO  PerfLogs             Python26                   Temp        WinBoard-4.8.0  hiberfil.sys  virtualbox-opennodes-2018-12-03                                 
$WINDOWS.~BT  Dropbox                 Install.log       Program Files        Recovery                   Temp-Music  Windows         log.log       win32-loader                                                    
$Windows.~WS  Fraps                   Intel             Program Files (x86)  SIERRA                     Temp2       csb.log         log.txt                                                                       
Config.Msi    Games                   NeroHistory_All   ProgramData          System Volume Information  Users       found.000       pagefile.sys                                                                  
root@deb9ws:~# ls /media/sf_D_DRIVE/
root@deb9ws:~# ls /media/sf_E_DRIVE/
root@deb9ws:~# ls /media/sf_F_DRIVE/
}}}


-Technologov. 04.12.2018.",Technologov
18117,vboxsf filesystem doesn't handle no extension file name,VirtualBox 5.2.20,Linux,2018-11-08T20:33:06Z,2018-11-12T16:32:23Z,2018-11-12T16:32:23Z,"I am using VirtualBox version 5.2.20. 
My virtual machine (Ubuntu Linux) is running Windows 10.
I set up shared folders and it mounted with -t vboxsf on the Ubuntu.

Here is error case with vboxsf filesystem: I created "".new.test1."" file but it created "".new.test1"" file.
{{{
chwon@chwon-VirtualBox:~/sandbox/tmp$ echo ""hello"" > .new.test1.
chwon@chwon-VirtualBox:~/sandbox/tmp$ ls -la
total 5
drwxrwxrwx 1 chwon chwon    0 Nov  8 15:12 .
drwxrwxrwx 1 chwon chwon 4096 Nov  8 15:11 ..
-rwxrwxrwx 1 chwon chwon    6 Nov  8 15:12 .new.test1
chwon@chwon-VirtualBox:~/sandbox/tmp$ 
chwon@chwon-VirtualBox:~/sandbox/tmp$ ls .new.test1.
ls: cannot access .new.test1.: No such file or directory
chwon@chwon-VirtualBox:~/sandbox/tmp$ ls .new.test1
.new.test1
}}}

I did same test on Linux ext4 filesystem.
{{{
chwon@chwon-VirtualBox:~/tmp/test$ echo ""hello"" > .new.test1.
chwon@chwon-VirtualBox:~/tmp/test$ ls -la
total 12
drwxrwxr-x 2 chwon chwon 4096 Nov  8 15:28 .
drwxrwxr-x 4 chwon chwon 4096 Nov  8 15:28 ..
-rw-rw-r-- 1 chwon chwon    6 Nov  8 15:28 .new.test1.
chwon@chwon-VirtualBox:~/tmp/test$ ls .new.test1. 
.new.test1.
chwon@chwon-VirtualBox:~/tmp/test$ ls .new.test1
ls: cannot access .new.test1: No such file or directory
}}}

",Arirang
17972,vboxsf module crashes guest OS after accessing host-side symlinks in shared folder,VirtualBox 5.2.18,Linux,2018-09-07T16:21:10Z,2018-09-07T17:11:50Z,2018-09-07T17:11:50Z,"Host OS: Windows 7 x64 Enterprise[[BR]]
Guest OS: CentOS 7 x64, kernel 3.10.0-862.11.6.el7.x86_64

Scenario:
* A shared folder is configured, with host path ""d:\VirtualBox Shared"", under name ""shared"".
* HOST: Create a file symlink d:\VirtualBox Shared\2\test.txt pointing to a file C:\Temp\test.txt:[[BR]]
{{{
C:\>mklink ""d:\VirtualBox Shared\2\test.txt"" c:\Temp\test.txt
symbolic link created for d:\VirtualBox Shared\2\test.txt <<===>> c:\Temp\test.txt
}}}
* GUEST: try to access the symlink (in the last output, the link target is blinking, indicating it's inaccessible):
{{{
flint@localhost / $ cp /media/sf_shared/2/test* /tmp
cp: cannot stat ‘/media/sf_shared/2/test.txt’: No such file or directory
flint@localhost / $ ls -l /media/sf_shared/2/test.txt
lrwxrwx--- 1 root vboxsf 0 Sep  7 18:39 /media/sf_shared/2/test.txt -> C:/Temp/test.txt
}}}
* HOST: Delete the link and replace it with a plain file:
{{{
C:\>del ""d:\VirtualBox Shared\2\test.txt""

C:\>copy nul ""d:\VirtualBox Shared\2\test.txt""
        1 file(s) copied.
}}}
* GUEST: try to acccess the replaced file again:
{{{
flint@localhost / $ cp /media/sf_shared/2/test* /tmp
}}}

Result: guest OS crashes and reboots. My friend helped with analyzing the dump, and concluded that the crash occurred in the vboxsf.ko module. Most of the dentry->d_inode->i_op callback fields on this file have zero values (all of them, except for getattr and setattr).

The dmesg is attached; kernel core dump can be downloaded from here:
https://drive.google.com/open?id=1yFrDInJg8bgWXv-8kErs31W8Vn90aRYo",Konstantin Vlasov
17971,Protocol error when using PHP rename over shared folders.,VirtualBox 5.2.18,Windows,2018-09-06T18:45:34Z,2018-09-06T18:45:34Z,2018-09-06T18:45:34Z,"I am trying to rename/move a file that is living in a directory and I am giving a new name to the file and a new directory as well. Below is an snippet of such code:

{{{
rename($currentFilePath, $newname);
}}}

For some reason `rename()` is returning an error like the following:

> Protocol error var/www/html/editor/application/models/forms_model.php 455

I am trying now executing the command `mv` directly into the VM and this is the result:

{{{
$ mv /var/www/html/epa_editor/public/epa_forms/archive/Clone_16621_SamplePDFFile_5mb.pdf ""/var/www/html/epa _editor/public/epa_forms/stage/testing (Clone of Form #: 15615).pdf""
    mv: cannot move `/var/www/html/epa_editor/public/epa_forms/archive/Clone_16621_SamplePDFFile_5mb.pdf' to `/var/www/html/epa_editor/public/epa_forms/stage/testing (Clone of Form #: 15615).pdf': Protocol error
}}}

So apparently is a VBox issue with shared folders that has not been fixed. 

Related issues closed as ""fixed"":

 * https://www.virtualbox.org/ticket/1393
 * https://www.virtualbox.org/ticket/8463
 * https://www.virtualbox.org/ticket/1393
 * https://www.virtualbox.org/ticket/1321

The original issue was reported at SO (https://stackoverflow.com/questions/52209856/php-5-3-3-rename-function-fails-with-protocol-error) looking for help but it's not a PHP error but VBox.

  [1]: http://php.net/manual/en/function.rename.php
  [2]: https://stackoverflow.com/questions/19139434/php-move-a-file-into-a-different-folder-on-the-server
  [3]: https://www.virtualbox.org/ticket/1393",reynierpm
17949,Mac OS High Sierra Host - Windows 10 Guest - Shared folder is read-only,VirtualBox 5.2.18,Windows,2018-08-22T17:26:45Z,2018-08-27T23:52:12Z,2018-08-27T23:52:12Z,"I have created a shared folder. I made sure that read-only is not checked. Virtualbox guest additions is installed. When shared folder is mounted, all directories in the Windows 10 guest are marked as read-only. Unchecking them, to make writable does nothing.",MB2
17886,VM self-terminates on MacOS,VirtualBox 5.2.16,Linux,2018-07-24T00:59:32Z,2018-11-15T16:50:17Z,2018-11-15T16:50:17Z,"Note: ''' I have only witnessed this behavior since upgrading''' to the last version I was prompted for.

Since upgrading to this version of VirtualBox, my VM disappears from the Dock, and its status is 'Aborted' in the VM manager window.

I am unable to identify any particular action taken by me that causes it, since I am never looking or using the VM when it happens.

----
'''MacOS:''' 10.13.6[[BR]]
'''VirtualBox:''' 5.2.16 r123759 (Qt5.6.3)[[BR]]
'''VM:''' Ubuntu 16.04 x64[[BR]]
'''Hardware:''' 2016 15"" MBP, 2.9GHz, 16GB 2133MHz, Raedon Pro 460 4GB/Intel HD 530 1.5GB [[BR]]
----

I'm attaching the logs I saved through the GUI, and a cursory grep through `/var/log/system.log` yielded the following (''I have no idea if it's related to the shutdown or not''):

{{{
VirtualBox[26651]: objc[26651]: Class FIFinderSyncExtensionHost is implemented in
both /System/Library/PrivateFrameworks/FinderKit.framework/Versions/A/FinderKit (0x7fff8e04cc90)
and /System/Library/PrivateFrameworks/FileProvider.framework/OverrideBundles/FinderSyncCollaborationFileProviderOverride.bundle/Contents/MacOS/FinderSyncCollaborationFileProviderOverride (0x10dc79cd8).
One of the two will be used. Which one is undefined.
VirtualBox[26651]: notify name ""user.uid.501.BRNotificationServerAvailabilityChanges""
has been registered 20 times - this may be a leak
VirtualBox[26651]: assertion failed: 17G65: libxpc.dylib + 75013
 [0BC7AD67-671D-31D4-8B88-C317B8379598]: 0x89
}}}",Ryan Lederman
17848,editing of shared folders is very annoying - folder name changes arbitrarily,VirtualBox 5.2.12,all,2018-07-02T15:45:14Z,2018-07-02T15:45:14Z,2018-07-02T15:45:14Z,"When editing an existing share, changing the folder path changes the folder name

so... If I have a folder z:\codebase\dev mapped to a 'code' share, all is well... but when I update the folder to z:\codebase\prod, the name changes to 'prod'

This copy-down from (leaf name from folder path) to folder name should only happen if the folder name is empty - otherwise... leave it alone!!",tim61
17844,shared folders not working correctly on Lubuntu 18.0.4 guest,VirtualBox 5.2.12,Linux,2018-06-28T23:02:40Z,2020-02-18T09:05:18Z,2020-02-18T09:05:18Z,"Shared folders worked on Lubuntu 16 but failed after I upgraded to 18.0.4 (thankfully I have a backup copy of 16).
The shared folders mount points do not show up on reboot, and I have to re-run the installer script from the additions CD image after each reboot.  The mount points (sf_source) then show up in /media/... but get a permission denied error trying to view them.   This appears to be a permission (or access list) problem in creating the mountpoint directories, and I can view the contents of the directories with ""sudo ls /media/sf_source'.  This sudo workaround, is, of course, not something I can actually live with.
I have tried reinstalling/rebuilding the guest additions multiple times, without a change in behavior.
",ccox
17728,Can't mount shared folder from fstab,VirtualBox 5.2.10,Linux,2018-05-03T19:36:50Z,2018-05-07T19:01:37Z,2018-05-07T19:01:37Z,"I an Arch Linux guest on a MacOS install of VirtualBox. I mount the shared folder using the following line in my Arch installation's fstab file:

{{{archway /home/josh/archway vboxsf uid=1000,gid=1000 0 0}}}

Recently Arch began booting into emergency mode with the error:

{{{vboxsf: Old binary mount data not supported, remove obsolete mount.vboxsf and/or update your VBoxService.}}}

This is the same issue described by a user on the Arch Linux forums:
https://bugs.archlinux.org/task/58272

Commenting out the aforementioned line in the fstab file allows the guest to boot normally, but this is not a desirable fix.
",professed
17605,VirtualBox does not see 255 char filename,VirtualBox 5.2.6,Linux,2018-03-08T04:29:47Z,2018-03-08T04:29:47Z,2018-03-08T04:29:47Z,"The following file in a shared folder was invisible to VirtualBox, even though the filename should be short enough:

5b494649325c42726f6b6572506f7274616c42756e646c655c4d616e616765725c42726f6b6572506172746e65724167656e63794d616e6167657223676574436f6272616e6451756572794275696c646572466f7242726f6b6572506172746e65724167656e63794964405b416e6e6f745d5d5b315d.doctrinecache.data

The file cannot be viewed using ls, nor can directories containing it be removed using rm -R",shkkmo
17482,Windows 7 guest - Shared Folders empty,VirtualBox 5.2.6,Windows,2018-01-19T11:50:29Z,2018-02-01T12:40:51Z,2018-02-01T12:40:51Z,"Upgrading from Virtualbox 5.2.0 shared folders on windows 7 guest machine stops to play. 
VBOXSVR network resource is still visible but it's empty.
Adding ""homegroup"" on ""home network"" Windows configuration enable folders, but on machine restart stops again.

Host is Ubuntu 17.10.",pmonaco
17455,Host USB is locked after shared folders were added,VirtualBox 5.2.4,Windows,2018-01-14T22:47:04Z,2019-01-27T22:12:20Z,2019-01-27T22:12:20Z,"I have a USB Stick with Windows 10 Installation files on it. If this stick is attached and I added some folders in the VM, I simply can’t eject it in the host Windows, because it is constantly locked. Even if I add some folders not on the USB drive. After I used a Process Explorer I could see, that there is a handle to the setup.exe on the USB. I attached the logs, because there one can see, that this is hardening issue. The only way to solve it right now is either kill the handle or close VM. This started way back, as hardening was added.",boxer01
17362,Cannot map network drive to vboxsvr file,VirtualBox 5.2.0,Windows,2017-12-09T15:41:43Z,2017-12-09T16:03:06Z,2017-12-09T16:03:06Z,"I am using VirtualBox on a macOS Host running a Windows 7 guest. I would like to map a network drive to Network\VBOXSVR\then a subdirectory. Windows objects with ""Windows cannot access \\VBOXSVR\the subdirectory"".
",Horatio
17285,Mapping shared folder fails if USB drive is connected after VM is started,VirtualBox 5.1.30,Windows,2017-11-18T05:44:24Z,2017-11-30T06:50:57Z,2017-11-30T06:50:57Z,"This basically is ""reopening"" of ticket #11445 (https://www.virtualbox.org/ticket/11445#comment:1) . The issue is still present in version 5.2.
",Rafcio
17159,vboxsf file timestamp not set properly,VirtualBox 5.1.28,Linux,2017-10-12T15:40:37Z,2017-10-12T15:40:37Z,2017-10-12T15:40:37Z,"Setting file modification timestamp on a file seated in shared folder does not work properly.

The case description:

{{{
$ df -h .
Filesystem      Size  Used Avail Use% Mounted on
Shared          932G  317G  616G  34% /media/sf_Shared
$ mount -l | grep Shared
Shared on /media/sf_Shared type vboxsf (rw,nodev,relatime)
$ touch -md ""1970-01-01 00:00:00""   test
$ ls -l test
-rwxrwx--- 1 root vboxsf 0 '''Jul 22  2554''' test

}}}

Doing the same on a native fs does work as expected.",Norbert Novotny
17044,Doing network copy from shared folder does not transfer file correctly: wrong md5sum,VirtualBox 5.1.26,other,2017-08-30T02:50:26Z,2019-08-29T10:40:50Z,2019-08-29T10:40:50Z,"When I copy file from shared folder to remote target with scp, scp exists with success 0, yet the md5sum on the remote target is different from the source.
Coping / scp'ing the same file from non-shared folder within same Vm works correctly: same md5sum on remote target.
Scp transfers different file sizes in the two cases.

E.g. 
md5sum  /media/sf_dloads/dhnc_m4_fw.tar.bz2

403f9fe21ed74762923d3d7c2087d62a  /media/sf_dloads/dhnc_m4_fw.tar.bz2

md5sum dhnc_m4_fw.tar.bz2 

403f9fe21ed74762923d3d7c2087d62a  dhnc_m4_fw.tar.bz2

scp -v /media/sf_dloads/test/dhnc_m4_fw.tar.bz2  root@192.168.1.110:/tmp/

.....
Transferred: sent 455796, received 1796 bytes, in 1.2 seconds
Bytes per second: sent 367895.7, received 1449.6
debug1: Exit status 0

on target:

md5sum  /tmp/dhnc_m4_fw.tar.bz2

ed67bef761dbfb2b35f62510b2c930c5  /tmp/dhnc_m4_fw.tar.bz2

scp -v dhnc_m4_fw.tar.bz2  root@192.168.1.110:/tmp/

.....
Transferred: sent 456788, received 1856 bytes, in 1.6 seconds
Bytes per second: sent 291460.5, received 1184.2
debug1: Exit status 0

on target:

 md5sum  /tmp/dhnc_m4_fw.tar.bz2

403f9fe21ed74762923d3d7c2087d62a  /tmp/dhnc_m4_fw.tar.bz2
",dry
16905,Shared folders hangs by configuration,VirtualBox 5.1.22,Windows,2017-07-16T19:14:14Z,2017-07-19T22:32:44Z,2017-07-19T22:32:44Z,"I have windows 10 host with windows 10 guest and when I try to configure the shared folders it hangs always and I have to kill the process.
It is the same where I configure it, in the VM manager (guest turned off) after choosing the folder on the host it hangs, in the virtual machine menu as soon as I try to configure a shared folder it hangs and I can't choose any folder on the host.
I was checking the log file of both (VM manager and virtual machine) but there is exactly nothing. I saw other similar tickets about shared folders hanging, but not really my problem, in my case it freezes during the configuration of the shared folder, and moreover the other tickets have been resolved.",spamme1
16762,Folder copy silently fails to copy children when folder name begins with a dot (“.”) and the destination resides in a shared folder,VirtualBox 5.1.22,Windows,2017-05-16T08:00:08Z,2019-06-04T06:05:24Z,2019-06-04T06:05:24Z,"'''Setup:'''[[BR]]
VB version 5.1.22 or 5.1.23 !r115382[[BR]]
Host: macOS Sierra 10.12.5 or 10.12.4[[BR]]
Guest: Windows 10[[BR]]
[[BR]]
'''Issue:'''[[BR]]
On Windows 10 guest copying a folder with a name beginning with a dot (“.”) to a shared folder results in an incomplete copy. For example a Visual Studio project folder with a “.vs” child folder. VBox seems to stop copying once it hits the .vs folder children. No error is displayed in File Explorer. Win 7 guest does not have this issue.[[BR]]
[[BR]]
'''Steps to reproduce:'''
 * Setup Win 10 guest.
 * Install Guest additions.
 * Create a shared folder on host and mount it in guest.
 * Using a command prompt to create a folder with a name beginning with a dot (e.g. md “.test”).
 * Create a file under .test such as “New Test Document.txt”.
 * In File Explorer right-click .test and select copy.
 * Right-click a destination folder on a shared folder, right-click and and paste.

Notice .test is created but “New Test Document.txt” is not present under it. [[BR]]
Also, using the command prompt to rename .test results in “The system cannot find the file specified”.[[BR]]
",pupSci
16572,shared folders can not be mount,VirtualBox 5.1.16,Linux,2017-03-16T06:32:30Z,2017-03-23T11:14:28Z,2017-03-23T11:14:28Z,"I use Linux Mint LMDE2 (Jessie) as Host with some Linux Guests.

Since VirtualBox 5.1.16 can shared folders not be mounted on the guests.
Until Version 5.1.14 its well done.
(5.1.18 don't work too) 

I gone back to 5.1.14 and it works fine.",Alex175
16487,Shared Folder /copying an overwriting modified text file causes error on Ubuntu 16 guest,VirtualBox 5.1.14,Linux,2017-02-16T03:10:30Z,2017-02-16T03:10:30Z,2017-02-16T03:10:30Z,"== Summary ==
*copying an overwriting modified text file causes error on Ubuntu 16 guest
after overwriting, file contains invalid characters. (can be check with Ubuntu's gedit) and sometimes missing characters.
One thing I found weird is, if you open the modified file in the shared folder from guest, it doesn't contain any invalid characters. Invalid character problem only rise when the file is overwritten to the folder in guest env.

*copying an overwritten text file steps can be found under 'How to reproduce the problem'

== How to reproduce the problem ==
1. (host OR guest) create a text file from the host shared folder
2. (guest) copy the shared file to any folder
3. (host) modify the file and save (if you modify the file from guest, it won't happen)
4. (guest) copy the modified file and overwrite it

== Attach a (full) log file ==
see the attached log file

Thank you for the great SW!",haku
16467,Unlink of locked file fails on shared folder,VirtualBox 5.1.14,Linux,2017-02-08T16:42:00Z,2017-02-08T16:42:00Z,2017-02-08T16:42:00Z,"I noticed that some programs crash, when working on data in a shared folder. I recorded the file operations with strace and was able to write a small program, that reproduces the error. The attached program basically acquires a lock on a file and then tries to delete it before closing.

To reproduce the error, execute the attached program in a Linux guest, on a Windows host. It prints ""Test failed"" when being executed in a shared folder. When executed outside the shared folder, it prints ""Test passed.""",egooo
16463,"""Operation not permitted"" on file in shared folder",VirtualBox 5.0.26,Linux,2017-02-07T21:33:01Z,2017-02-28T19:41:09Z,2017-02-28T19:41:09Z,"* Host: Windows 7 x64
* Guest: Linux CentOS 6.7 x64 ( VirtualBox Guest Additions 5.0.26 r108824 )

If you look at ticket #4890, which is very likely the same underlying issue, the most recent comment is still reporting the issue on 5.1.12

In a vbox shared folder:
{{{
[user@server ~]$ mount | grep vboxsf
sv on /sv type vboxsf (uid=500,gid=500,rw)
[user@server ~]$ sudo touch /sv/a.txt
[user@server ~]$ sudo chmod a-w /sv/a.txt
[user@server ~]$ sudo rm -f /sv/a.txt
rm: cannot remove `/sv/a.txt': Operation not permitted
[user@server ~]$ sudo chmod a+w /sv/a.txt
[user@server ~]$ sudo rm -f /sv/a.txt
[user@server ~]$
}}}

Not in a vbox shared folder:
{{{
[user@server ~]$ sudo touch /a.txt
[user@server ~]$ sudo chmod a-w /a.txt
[user@server ~]$ sudo rm -f /a.txt
[user@server ~]$
}}}

Possible related tickets:
* https://www.virtualbox.org/ticket/4890
* https://www.virtualbox.org/ticket/5568
* https://www.virtualbox.org/ticket/15083",bompus
16441,Kernel Panic on Mac host when doing file operations on shared NFS drives,VirtualBox 5.1.14,other,2017-02-01T23:19:30Z,2017-02-27T21:25:34Z,2017-02-27T21:25:34Z,"Virtualbox causes a kernel panic on Mac OSX Sierra host when doing file operations on a shared NFS folder. There are many things that can trigger the panic, but deleting files is the easiest to reproduce.

Steps to reproduce:
{{{ 
# create a new folder
mkdir vagrant; cd vagrant
# copy both the attached vagrant box image (freebds-10.3-amd64-virtualbox.box) and the vagrantfile into this folder

# add the box to vagrant (this is the easiest way to reproducibly set up a vm)
vagrant box add freebsd-10.3-amd64-virtualbox.box --name local/freebsd
# provision the virtual machine (this will take a while)
vagrant up

# ssh into the virtual machine
vagrant ssh
# we have mounted a shared folder at /vagrant
cd /vagrant
# we need to perform file operations, and the most reproducible way I've found to do this is by creating and destroying a virtualenv
virtualenv venv
rm -rf venv  # this should crash the host
}}}

 ",logan-ncc
16432,Unable to open sqlite database on shared folder,VirtualBox 5.1.14,Linux,2017-01-28T15:32:50Z,2018-08-22T16:43:17Z,2018-08-22T16:43:17Z,"When attempting to open an sqlite database on a shared folder it fails with ""Error: disk I/O error""

If I copy that same database from the shared folder locally to the VM then the open succeeds.
{{{
jlmcgraw@mate1604:~$ sqlite3 /media/sf_Shared_Folder/Recordings.db 
 SQLite version 3.14.1 2016-08-11 18:53:32
 Enter "".help"" for usage hints.
 sqlite> .tables
 
 Error: disk I/O error
 sqlite> .q

jlmcgraw@mate1604:~$ cp /media/sf_Shared_Folder/Recordings.db .

jlmcgraw@mate1604:~$ sqlite3 Recordings.db 
 SQLite version 3.14.1 2016-08-11 18:53:32
 Enter "".help"" for usage hints.

 sqlite> .tables
 ZDATABASEPROPERTY  ZRECORDING         Z_MODELCACHE     
 ZENTITYREVISION    Z_METADATA         Z_PRIMARYKEY     

 sqlite> .q
}}}",jlm
16417,vboxsf crashes process or VM in case of many file stat operations on shared vboxsf file system in a short time,VirtualBox 5.1.14,Linux,2017-01-23T08:42:05Z,2017-07-20T17:23:49Z,2017-07-20T17:23:49Z,"We use a vagrant based toolchain to automatically generate VMs for executing unit tests. They run on Ubuntu 16.04 LTS 64-bit hosts, and the VMs themselves contain various different older and newer Linux distributions. We use current VirtualBox 5.1.14 and also the 5.1.14 guest tools.

Quite a significant percentage (10-20%) of our VM deployments was not successful. In case of ""default"" paravirtualization using KVM, the whole VM freezes, and the VBox.log file just says:

{{{
00:00:42.027263 VMMDev: vmmDevHeartbeatFlatlinedTimer: Guest seems to be unresponsive. Last heartbeat received 4 seconds ago
}}}

If using the ""minimal"" paravirtualization, VM operation continues, just the unit test process itself dies (see log below). This happens consistently at the same place where there are many stat() calls made to get the ctime information of many thousands of (empty) cache files on a shared vboxsf file system, before outdated files are supposed to be cleaned up. If I remove this code part, the error does not occur any more. Therefore my (uneducated) assumption is that it could be related to running many stat operations in a short time. Here's the stack trace as found in /var/log/kern.log in the instance.

{{{
Jan 21 22:23:14 vagrant kernel: [    8.021389] vboxsf: Successfully loaded version 5.1.14 (interface 0x00010004)
Jan 21 22:23:14 vagrant kernel: [    8.328536] VBoxService 5.1.14 r112924 (verbosity: 0) linux.amd64 (Jan 16 2017 17:38:46) release log
Jan 21 22:23:14 vagrant kernel: [    8.328536] 00:00:00.000093 main     Log opened 2017-01-21T22:23:14.323839000Z
Jan 21 22:23:14 vagrant kernel: [    8.328566] 00:00:00.000154 main     OS Product: Linux
Jan 21 22:23:14 vagrant kernel: [    8.328578] 00:00:00.000170 main     OS Release: 3.16.0-4-amd64
Jan 21 22:23:14 vagrant kernel: [    8.328589] 00:00:00.000182 main     OS Version: #1 SMP Debian 3.16.39-1 (2016-12-30)
Jan 21 22:23:14 vagrant kernel: [    8.328614] 00:00:00.000193 main     Executable: /opt/VBoxGuestAdditions-5.1.14/sbin/VBoxService
Jan 21 22:23:14 vagrant kernel: [    8.328614] 00:00:00.000194 main     Process ID: 1028
Jan 21 22:23:14 vagrant kernel: [    8.328614] 00:00:00.000195 main     Package type: LINUX_64BITS_GENERIC
Jan 21 22:23:14 vagrant kernel: [    8.329284] 00:00:00.000860 main     5.1.14 r112924 started. Verbose level = 0
Jan 21 22:27:01 vagrant kernel: [  233.348410] VBOXGUEST_IOCTL_HGCM_CALL: 64 Failed. rc=-228.
Jan 21 22:27:01 vagrant kernel: [  233.348430] general protection fault: 0000 [#1] SMP 
Jan 21 22:27:01 vagrant kernel: [  233.348461] Modules linked in: vboxsf(O) nfsd auth_rpcgss oid_registry nfs_acl nfs lockd fscache sunrpc vboxvideo(O) ttm drm_kms_helper ppdev drm evdev vboxguest(O) crc32_pclmul i2c_piix4 pcspkr i2c_core serio_raw aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd parport_pc battery processor parport video thermal_sys ac button autofs4 ext4 crc16 mbcache jbd2 dm_mod sg sd_mod crc_t10dif crct10dif_generic ata_generic crct10dif_pclmul crct10dif_common crc32c_intel e1000 psmouse ata_piix libata scsi_mod
Jan 21 22:27:01 vagrant kernel: [  233.348614] CPU: 1 PID: 1925 Comm: otrs.UnitTest.p Tainted: G           O  3.16.0-4-amd64 #1 Debian 3.16.39-1
Jan 21 22:27:01 vagrant kernel: [  233.348661] Hardware name: innotek GmbH VirtualBox/VirtualBox, BIOS VirtualBox 12/01/2006
Jan 21 22:27:01 vagrant kernel: [  233.348689] task: ffff8800797bcce0 ti: ffff88007bdcc000 task.ti: ffff88007bdcc000
Jan 21 22:27:01 vagrant kernel: [  233.348718] RIP: 0010:[<ffffffffa02666c1>]  [<ffffffffa02666c1>] VGDrvCommonIoCtl+0x261/0x1bf0 [vboxguest]
Jan 21 22:27:01 vagrant kernel: [  233.348763] RSP: 0018:ffff88007bdcfb98  EFLAGS: 00010282
Jan 21 22:27:01 vagrant kernel: [  233.348784] RAX: 00000000ffffff1c RBX: 0000a0007bdcfc84 RCX: 0000000000000001
Jan 21 22:27:01 vagrant kernel: [  233.348813] RDX: 0000000000000000 RSI: 000000000000002f RDI: ffff88007bdcf9a0
Jan 21 22:27:01 vagrant kernel: [  233.348842] RBP: 5f7c81f4149bd010 R08: 000000000000000a R09: 00000000000001c0
Jan 21 22:27:01 vagrant kernel: [  233.348870] R10: 0000000000000000 R11: ffff88007bdcf6be R12: 0000b00000000000
Jan 21 22:27:01 vagrant kernel: [  233.348898] R13: 1b3eed7500000000 R14: 5f7c81f4149bd064 R15: 5f7c81f4149bd010
Jan 21 22:27:01 vagrant kernel: [  233.348927] FS:  00007ff073ca7700(0000) GS:ffff88007fd00000(0000) knlGS:0000000000000000
Jan 21 22:27:01 vagrant kernel: [  233.348958] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Jan 21 22:27:01 vagrant kernel: [  233.348981] CR2: 00007ffec82d3ff8 CR3: 000000007bcd8000 CR4: 00000000000406e0
Jan 21 22:27:01 vagrant kernel: [  233.349008] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
Jan 21 22:27:01 vagrant kernel: [  233.349033] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Jan 21 22:27:01 vagrant kernel: [  233.349072] Stack:
Jan 21 22:27:01 vagrant kernel: [  233.349082]  001041ed149bd010 000003e900000000 00000002000003e9 013aa00300000902
Jan 21 22:27:01 vagrant kernel: [  233.349114]  0000000000000000 0000000000000000 ffff880023350880 0000006c00000004
Jan 21 22:27:01 vagrant kernel: [  233.349147]  ffff88007bdcfbfc 0000a00000020830 ffff88007b0c6000 ffffffffa03f877c
Jan 21 22:27:01 vagrant kernel: [  233.349178] Call Trace:
Jan 21 22:27:01 vagrant kernel: [  233.349194]  [<ffffffffa03f877c>] ? sf_stat+0x5c/0x110 [vboxsf]
Jan 21 22:27:01 vagrant kernel: [  233.349219]  [<ffffffffa03f88b0>] ? sf_inode_revalidate+0x80/0xd0 [vboxsf]
Jan 21 22:27:01 vagrant kernel: [  233.349246]  [<ffffffff811b5192>] ? __inode_permission+0x22/0xb0
Jan 21 22:27:01 vagrant kernel: [  233.349269]  [<ffffffff811b58e6>] ? link_path_walk+0x256/0x870
Jan 21 22:27:01 vagrant kernel: [  233.349292]  [<ffffffff811c281a>] ? __d_lookup+0x7a/0x150
Jan 21 22:27:01 vagrant kernel: [  233.349979]  [<ffffffffa03f8914>] ? sf_dentry_revalidate+0x14/0x20 [vboxsf]
Jan 21 22:27:01 vagrant kernel: [  233.350641]  [<ffffffff811b47de>] ? lookup_fast+0x25e/0x2b0
Jan 21 22:27:01 vagrant kernel: [  233.351302]  [<ffffffff811b6055>] ? path_lookupat+0x155/0x780
Jan 21 22:27:01 vagrant kernel: [  233.351927]  [<ffffffffa03fa6ee>] ? VbglR0SfCreate+0x7e/0xa0 [vboxsf]
Jan 21 22:27:01 vagrant kernel: [  233.352603]  [<ffffffff811b66a6>] ? filename_lookup+0x26/0xc0
Jan 21 22:27:01 vagrant kernel: [  233.353267]  [<ffffffff811ba8e4>] ? user_path_at_empty+0x54/0x90
Jan 21 22:27:01 vagrant kernel: [  233.353855]  [<ffffffff810ed71e>] ? from_kgid_munged+0xe/0x20
Jan 21 22:27:01 vagrant kernel: [  233.354431]  [<ffffffff811af53a>] ? cp_new_stat+0x13a/0x160
Jan 21 22:27:01 vagrant kernel: [  233.354976]  [<ffffffff811af0e6>] ? vfs_fstatat+0x46/0x90
Jan 21 22:27:01 vagrant kernel: [  233.355536]  [<ffffffff811af57a>] ? SYSC_newstat+0x1a/0x40
Jan 21 22:27:01 vagrant kernel: [  233.356067]  [<ffffffff8151adcd>] ? system_call_fast_compare_end+0x10/0x15
Jan 21 22:27:01 vagrant kernel: [  233.356577] Code: 01 b9 ff ff ff ff 48 89 da 4c 89 d6 4c 89 ef e8 b6 df ff ff 41 89 c7 0f 1f 00 48 83 c4 40 44 89 f8 5b 41 5c 41 5d 41 5e 41 5f 5d <c3> 66 0f 1f 44 00 00 49 83 f8 17 0f 86 34 0c 00 00 48 8d 83 00 
Jan 21 22:27:01 vagrant kernel: [  233.358611] RIP  [<ffffffffa02666c1>] VGDrvCommonIoCtl+0x261/0x1bf0 [vboxguest]
Jan 21 22:27:01 vagrant kernel: [  233.359118]  RSP <ffff88007bdcfb98>
Jan 21 22:27:01 vagrant kernel: [  233.359636] ---[ end trace 54b9778e1a5d744b ]---
}}}

For reference, here's the Perl code that is used to cleanup the (empty cache files):

{{{
my $Wanted = sub {

    # Skip nonregular files and directories.
    return if ( !-f $File::Find::name );
    my $Stat = File::stat::stat($File::Find::name);
    if ( $Stat && ( time() - $Stat->ctime() > $CacheTTLSeconds ) ) {    ## no critic
        unlink $File::Find::name;    # Don't die here, this could be removed in the background by another process too.
    }
};
File::Find::find( $Wanted, $CacheDir );
}}}

Less often, a similar error occurs during the vagrant provisioning of the instances, where we copy the source code of our project from the /vagrant shared vboxsf folder into the VM. Here just a simple ""cp -r"" is used during the deployment. It could be the same problem:

{{{
==> default: Copying OTRS code to /opt/otrs
==> default: cp: cannot stat â/vagrant/Sources/otrs/var/httpd/htdocs/js/thirdparty/ckeditor-4.5.6/plugins/mathjax/lang/cy.jsâ: Protocol error
}}}

Please let me know if I should try to provide additional information, and thanks a lot for taking a look at this.",mrtngrnr
16329,Corruption when accessing files via Shared Folders,VirtualBox 5.1.12,Linux,2016-12-26T01:20:30Z,2016-12-28T19:36:57Z,2016-12-28T19:36:57Z,"I am seeing intermittent file corruption when checking a borgbackup repository via a Shared Folder

Host is Ubuntu x64 16.04 using Virtualbox 5.1.12
Guest is Ubuntu Mint x64 16.10

Here is the output of 5 sequential runs of the same command to verify the repository, you can see that some detect errors and others don't.  The errors that are detected are different between runs as well.


{{{
jlmcgraw@mate1604:~$ borgbackup check /media/sf_Shared_Folder/borg_vm_backups/
Segment entry checksum mismatch [segment 273, offset 8]
Index object count mismatch. 117954 != 117952
Completed repository check, errors found.

jlmcgraw@mate1604:~$ borgbackup check /media/sf_Shared_Folder/borg_vm_backups/
Enter passphrase for key /media/sf_Shared_Folder/borg_vm_backups: 

jlmcgraw@mate1604:~$ borgbackup check /media/sf_Shared_Folder/borg_vm_backups/
Enter passphrase for key /media/sf_Shared_Folder/borg_vm_backups: 

jlmcgraw@mate1604:~$ borgbackup check /media/sf_Shared_Folder/borg_vm_backups/
Segment entry checksum mismatch [segment 155, offset 2726665]
Index object count mismatch. 117954 != 117951
Completed repository check, errors found.

jlmcgraw@mate1604:~$ borgbackup check /media/sf_Shared_Folder/borg_vm_backups/
Enter passphrase for key /media/sf_Shared_Folder/borg_vm_backup
}}}


I'm unable to recreate the errors when checking the repository from the host machine.

I've also noticed occasional errors in files hosted on the shared folder in other applications as well.  E.g. unzipping a file, errors about duplicity archive errors etc etc so the problem isn't just limited to borg

I will run memory diagnostics again tonight just to be sure, I've run them before and found no errors.

",jlm
16293,memory can't be written,VirtualBox 5.1.4,Windows,2016-12-15T13:50:37Z,2016-12-15T13:50:37Z,2016-12-15T13:50:37Z,"tried to create common folder and got bug with nulls and message ""memory can't be written"".
i remove this version of VBox and install 4.1.4, and now it works
fix this bug in 5.1.4 pls :)",ilyarik
16262,shared folder not write-able for non-root users for special windows folders,VirtualBox 5.1.10,Linux,2016-12-03T16:01:53Z,2016-12-05T08:13:01Z,2016-12-05T08:13:01Z,"I would like to mount the Windows ''Downloads'' directory as a shared folder, but the mounted folder is not writable to regular users. Yet the root user can still write to it.

Played all mount options but to no avail: the permissions of all files and sub-folders in the mounted folder are correctly set, and the issue is about the permission bits of the mount point itself. Tried to mount a sub-folder in the ''Downloads'', then the permission bit is correct.

{{{
    C:\Users\opensrc\Downloads     -> Downloads: dr-xr-xr-x
    C:\Users\opensrc\Downloads\Sub -> Subfolder: drwxr-xr-x
}}}

Wonder why the ''Downloads'' folder is treated differently.
",opensrc
16205,Can't open a Word document located in shared folder,VirtualBox 5.1.8,Windows,2016-11-19T17:27:39Z,2016-11-19T17:27:39Z,2016-11-19T17:27:39Z,"I upgraded to 5.1.8, but I can't open Word files (.docx or .doc) located on the shared folder anymore (message: ""non è possibile aprire"" is ""it is not possible open""). Moreover if I try to move a Word file from the shared folder to the desktop an error message come out (error 0x80070057: the parameter is incorrect).
Excel files open and move without problem. 

Didn't have any problem with previous issue (don't remember exactly the last, but sure 4 and something else)",reboox
16167,Clipper directory() and shared folders inconsistency,VirtualBox 5.1.8,Windows,2016-11-07T19:56:28Z,2016-11-07T19:56:28Z,2016-11-07T19:56:28Z,"Hi,
I'm using a VM with xp sp3 (home edition) as guest and Win10 Home as host.
Under the VM I develop using the old Ca-clipper compiler: the compiler and the sources, together with the files for testing, are stored on the hd of Win10 and I access them by shared folders on the VM.
When I use CA-Clipper directory() function to get a list of files stored on a shared folder, the return value (directory() returns an array of filenames) is empty, like in the folder there isn't any file.
I investigated deeply and I found that if in the folders there are no more than 8 files the function returns a correct array.
Then I copied all the test shared folder, locally on the hd of the VM, and when I launched the program and tested the directory() function, it runs without any problem and returns all the filenames that are stored on the folder, no matter if they are more then 8, 1000, or more.
To be sure that it's not a Clipper related problem (maybe with shared folders), I tested the program with WMWare. I exported the Virtualbox VM and then imported in WmWare, created the shared folders (like in Virtualbox) and launched the program to read the content of shared folder: in this case there was any problem and the content of the test (shared) folder was returned entirely. So I think the problem is related to VirtualBox.
Regards,
Marco",mark63
16065,Cannot create symlink inside shared folder on Windows host,VirtualBox 5.1.6,Linux,2016-10-12T20:59:18Z,2016-10-18T22:37:51Z,2016-10-18T22:37:51Z,"Symlinks do not work inside a VirtualBox Shared Folder when running on Windows 10 host with a Linux guest (Fedora 24)


{{{
$ mount  | grep vboxsf
home_vagrant_sync on /home/vagrant/sync type vboxsf (rw,nodev,relatime)
home_vagrant_sync on /home/vagrant/sync type vboxsf (rw,nodev,relatime)

$ pwd
/home/vagrant/sync
$ mkdir a
$ ln -s a b
ln: failed to create symbolic link 'b': Protocol error
}}}

Outside shared folder:

{{{
$ cd ..
$ pwd
/home/vagrant
$ mkdir c
$ ln -s c d
$ ls -ld d
lrwxrwxrwx 1 vagrant vagrant 1 Oct 12 20:51 d -> c
}}}

Environment:

{{{
$ uname -a
Linux guest 4.5.7-300.fc24.x86_64 #1 SMP Wed Jun 8 18:12:45 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
$ VBoxClient --version
5.1.6r110634

>""C:\Program Files\Oracle\VirtualBox\VBoxManage.exe"" --version
5.1.6r110634
}}}
",g_tirloni
15897,Symfony clearing cache fails when done through shared folder (rmdir fails),VirtualBox 5.1.4,Linux,2016-09-07T03:33:41Z,2018-03-06T15:58:02Z,2018-03-06T15:58:02Z,"I have opened a bug on the Symfony bug tracker (https://github.com/symfony/symfony/issues/19851), however, I believe this is an issue between Linux and Windows with a shared folder.

I am using RHEL7 on the guest machine and windows 8 on the host. The /var/www/ dir is a mount of a shared folder on the windows machine (a Virtual Box share). I have installed Symfony on the guest, so its files are done through the share (I can browse them on the host).

Everything seems to run fine except clearing of cache. This fails saying that there are files in the dir that it is trying to run an rmdir on:
{{{
(Failed to remove directory ""/var/www/html/tut1/var/cache/pro~/twig"": rmdir(/var/www/html/tut1/var/cache/pro~/twig): Directory not empty.)
}}}
Looking in windows, I can see that there are a bunch of files still showing there, however, when I try list (dir, ll and a bunch of other options attempted), it shows no files. Yet if I try to do an rm -R on the dir:
{{{
rm -R /var/www/html/tut1/var/cache/pro~/twig/
}}}
it says that it can't:
{{{
rm: cannot remove ‘/var/www/html/tut1/var/cache/pro~/twig/’: Directory not empty
}}}

If I remount the /var/www/ mount (or reboot the guest), the files all show and I can run the rm command without any issues.

It's like in the Symfony script it is sending the unlink command that is being reported as successful even though on the host the files are not deleted.

I will attach an strace log if that is of any help. The main lines I looked at are copied into the Symfony bug report.

If you want to replicate this, install with a linux guest, windows host and install and run Symfony on it. Browse to a prod page (go to /project-name/web/app.php) and then clear the cache with the following command:
{{{
php bin/console cache:clear --env=prod
}}}
if you then delete the /project-name/var/cashe/pro~ dir and try that command again (or remount the share) it will work.",MicWit
15857,Defect: 5.1.4 Shared Folders not showing in Ubuntu Linux Guest from  Win7 Host,VirtualBox 5.1.4,Linux,2016-08-27T07:12:42Z,2016-09-01T13:37:14Z,2016-09-01T13:37:14Z,"After creating a share folder in Ubuntu 16 Guest,
  we cannot see it in Media

2) Same for bi-directionnal copy/paste not working.

",brook245
15818,Windows 10 guest VM has shared folder hang,VirtualBox 5.1.4,Windows,2016-08-18T10:33:07Z,2016-08-18T14:56:33Z,2016-08-18T14:56:33Z,"
== The Issue ==

On using Visual Studio 2013 on my Windows 10 VM to build a project located on a VirtualBox shared folder, Visual Studio will hang during some file I/O operation such as scanning files for intellisense or compiling the C++ source files. Once it is hanging, I cannot access the shared folder via the Windows file explorer which suggests something has failed in the shared folder file operation(s), and the Visual Studio process cannot be terminated. Indeed, even shutting down the VM hangs on the shutdown screen and I must manually force a VM power off. Interestingly or not, copying the entire project folder from the shared folder to the guest C: drive worked without any issues, and then subsequent build operations from the C: drive work fine without any hanging.

This problem appears to have started happening since version 5.1.x. It was happening after I initially upgraded to 5.1.2 but then seemed to sort itself out, but since upgrading to 5.1.4 it is happening constantly (or maybe I'm just being lucky / unlucky depending on timings).

There doesn't appear to be anything in the VM host syslog related to disk I/O at the time that the VM shared folder access hangs but VM startup does produce the following in the syslog:

{{{
Aug 18 11:21:35 centurion kernel: [69073.711857] vboxdrv: ffffffffc0121020 VMMR0.r0
Aug 18 11:21:35 centurion kernel: [69073.783744] vboxdrv: ffffffffc0220020 VBoxDDR0.r0
Aug 18 11:21:35 centurion kernel: [69074.056132] vboxdrv: ffffffffc023f020 VBoxEhciR0.r0
}}}

The VM log (attached) doesn't appear to me to have anything in there related to the shared folder hang. Is there any more verbose logging that can be enabled for the VM?

== About the VirtualBox setup ==

I'm running a Windows 10 (64bit) guest on Linux Mint 17.3 (64bit) host running Linux Kernel 3.19.0-32. The Windows 10 VM is run using a raw disk vmdk file which points to an SSD. The VirtualBox Guest Additions are up-to-date with the version of VirtualBox (5.1.4).",neilc34
15535,Host files with (illegal) colon in filename not visible in shared folder,VirtualBox 5.0.22,Linux,2016-06-20T09:53:47Z,2016-06-20T09:53:47Z,2016-06-20T09:53:47Z,In Windows files are created (through CygWin) having a (illegal) colon in their name. I added this folder as Shared Folder in Virtualbox. All subdirs are visible (not having a colon) but none of the files with the colon are. When the colon is removed from the filename they become visible.,CornePlas
15149,"Files are not deleted when deleting many files, but VM thinks they are",VirtualBox 5.0.14,Linux,2016-02-14T14:11:57Z,2018-03-06T15:54:46Z,2018-03-06T15:54:46Z,"When we try delete many individual files in the VM on a shared folder, the files still exists but the VM reports them as not existant. The Symfony cache:clear command does this and fails because directory's can't be removed (the VM thinks they are empty but they are not).

Host: tested with Windows and OSX
Guest: tested with Debian 8 64, Ubuntu 14.04 64, Ubuntu 14.04 32
Note: Debian 7 64 does not have this problem.

To reproduce:
- Clone https://github.com/marijnotte/file-delete-test
- Install Vagrant
- Do vagrant up in the project folder
- When provisioned login into the box (vagrant ssh)
- cd /vagrant
- php composer.phar install

Error message:

{{{
  [RuntimeException]                                                                                                                                                                                                                        
  Error Output:                                                                                                                                                                                                                             
                                                                                                                                                                                                                                            
  [Symfony\Component\Filesystem\Exception\IOException]                                                                                                                                                                                    
  Failed to remove directory ""/vagrant/app/cache/pro~/doctrine"".    
}}}

- cd /vagrant/app/cache/pro~/doctrine
- ls --> directory is empty
- Go to the same directory on your host --> directory is not empty",Marijn
15137,Clearing read-only file attribute from Windows guest result in world writable permission.,VirtualBox 5.0.14,Windows,2016-02-10T10:11:10Z,2016-02-10T10:11:10Z,2016-02-10T10:11:10Z,"The shared folders of VirtualBox blindly maps read-only attribute of Windows guest to POSIX write permission. This behavior cause dangerous and undesired file permissions are set in the host system.

=== Steps to Reproduce ===
{{{
$ umask
0022
$ ls -l a.txt
-rw-r--r-- 1 user1 user1 0 Feb 10 00:00 a.txt
}}}
 1. Set read-only attribute of the file ""a.txt"", from a Windows guest with the shared folder mounted.
{{{
$ ls -l a.txt
-r--r--r-- 1 user1 user1 0 Feb 10 00:00 a.txt
}}}
 1. Unset read-only attribute of the same file, from the same Windows guest.
{{{
$ ls -l a.txt
-rw-rw-rw- 1 user1 user1 0 Feb 10 00:00 a.txt
}}}

----
VirtualBox respects umask when only creating new files, but it should do the same when mapping read-only attribute (or something similar). Leaving files world writable is simply unacceptable.",JackieKu
14884,Cannot chmod directories within guesLinux guest/host,VirtualBox 5.0.10,other,2015-12-02T02:50:20Z,2015-12-02T02:50:20Z,2015-12-02T02:50:20Z,"I have a Linux guest in Virtualbox with a directory tree mounted rw using vboxsf. Today I noticed that running chmod on a directory from within the guest has no effect. This is a problem for me, because I was trying to use git annex, which relies heavily on being able to modify directory modes during the drop operation, for example. 

I did some searching and found lots of commentary implying that other people were seeing the same problem, but no solutions anywhere, so I dug into the source code and gradually drilled down into vboxsf until I found the host-side implementation of mode change for directories, in vbsf.cpp on line 1444:
{{{
    /* TODO: mode for directories */
}}}

I have to give it credit for its conciseness, but I'd be very appreciative if a new release of VirtualBox included a more effective implementation :)",Simon Ruggier
14852,Grouped command output lost when redirecting to file on shared folder,VirtualBox 5.0.10,Solaris,2015-11-20T21:43:27Z,2015-11-20T22:25:42Z,2015-11-20T22:25:42Z,"I am not entirely sure how to describe this issue, but see the comments in the attached test file on how to reproduce.  What appears to happen is that I have a group of commands in a shell script that produce output that is redirected to a file, e.g.

{{{
{
  command1
  command2
} > some_file.txt
}}} 

regardless of whether the commands are shell built-ins or external, only the output of the last command ends up in the redirect file.  This only happens when the redirect file is on a shared-folder mount within the guest.  It does not happen in other directories within the guest.  It also does not happen if the commands are not grouped, i.e. they do not share access to the output file.

In all cases, the test script is run from within the guest, the difference being the current working directory.  I have observed this behavior on both Oracle Solaris 11.3 and OmniOS !r151006 guests. OmniOS is an illumos distribution, similar to Solaris.  In both cases, the Solaris Guest Additions are installed:

{{{
# modinfo | grep vbox
187 fffffffff8115000  29210 265   1  vboxguest (VirtualBox GstDrv 5.0.10r104061)
200 fffffffff8151000   3b28 266   1  vboxms (VBoxMouseIntegr 5.0.10r104061)
201 fffffffff8155000   88a8  24   1  vboxfs (VirtualBox ShrdFS 5.0.10r104061)
}}}

This was discovered while trying to run an autoconf ""configure"" script, which tried to echo a string, pipe it to sed, echo something else, and redirect all the output to a file.  The output from sed never made it to the file.  The attached test script is a condensed version of this.  The effect is that we cannot run configure in a shared folder.

I have verified with truss(1M) that in both cases, identical write(2) syscalls are issued with the same arguments, and succeed in all cases.  I also cannot reproduce this on a Linux guest.  I therefore suspect that the issue lies in the particular VFS implementation provided by the vboxfs Solaris driver.",Eric Sproul
14704,Windows special folders mount as read only when shared,VirtualBox 5.0.6,Linux,2015-10-15T08:46:37Z,2015-10-15T08:46:37Z,2015-10-15T08:46:37Z,"Windows uses the 'read only' attribute for folders to indicate that the folder is a special folder such as 'Downloads', 'Documents, 'Pictures', 'Videos' and 'Music'.  Consequently this attribute is not intended to indicate that the folder is actually read only or that files should not be able to be created within it (https://support.microsoft.com/en-gb/kb/326549).  Unfortunately Virtual Box does not respect this behavior when mounting a shared folder that contains such folders.

An example of this problem is that if the 'Downloads' special folder is moved to the root directory of drive 'D:' and then drive 'D:' is shared with an Ubuntu client, then it will be impossible to create files or folders within the 'Downloads' folder from within the Ubuntu client. Nor will it be possible to change the permissions from within the Ubuntu client.

There is a workaround (https://forums.virtualbox.org/viewtopic.php?f=3&t=46541), which involves removing the read only attribute from within Windows using the command line 'attrib' command (Explorer does not permit the read only attribute to be removed from folders).

This is not an ideal solution as it removes some of the special folder behavior within Windows.  Ideally, VirtualBox should respect the normal Windows behavior of the read only attribute and ignore it.  This should be a very simple matter to fix.
",TrevorW
14652,Symbolic links cannot go up file tree on shared folder.,VirtualBox 5.0.4,Linux,2015-10-02T02:14:13Z,2015-10-02T02:14:13Z,2015-10-02T02:14:13Z,"I've set up a vagrant VM with ubuntu/trusty64 on OS X.

Attempting to create symbolic links in the shared folder that use .. to reference a directory up the tree results in a protocol error (EPROTO).

Symlinks with absolute or relative paths without going up the tree still work. 

",mstone121
14568,Regression: protocol error if the host folder name differs from share name,VirtualBox 5.0.4,Linux,2015-09-10T13:15:38Z,2015-09-10T13:44:00Z,2015-09-10T13:44:00Z,"I remember many years ago in VBox 2 or 3 there was an issue that name of the folder on host system has to match the name of the share for it to work properly. In 4 it worked properly though. Now on 5.0.4 I've encountered the same issue again:

on host:
1. mkdir ~/vm-shared
2. mkdir ~/test

in VBox UI:
1. add folder ~/vm-shared with name ""shared""
2. add folder ~/test with name ""test""

on guest (under root):
1. mkdir /mnt/shared && mount -t vboxsf -o uid=1000,gid=100 shared /mnt/shared
2. mkdir /mnt/test && mount -t vboxsf -o uid=1000,gid=100 test /mnt/test

now on guest, try to execute following command:
1. mkdir /mnt/shared/somedir
2. mkdir /mnt/test/somedir

Second command executed successfully, but first command fails with protocol error.",indifferent
14540,No files for DOS applications in VBox shared folder,VirtualBox 5.0.2,Windows,2015-09-04T09:14:48Z,2015-09-04T09:14:48Z,2015-09-04T09:14:48Z,"A DOS application (Foxpro, XtreeGold) can't read list of files in a shared folder. Windows app can see all files. This problem is properly described in https://www.virtualbox.org/ticket/8551 - but there is no solution.

Host (32 bite): Windows 8, Windows 10
Guest (32 bite): Win XP",DanielR
14537,Linux grsecurity guest kernel will not mount shared folders,VirtualBox 5.0.2,Linux,2015-09-03T15:44:23Z,2015-09-03T15:44:23Z,2015-09-03T15:44:23Z,"My guest is an Arch Linux 64-bit VM running kernel 4.1.6.201508230818-1-grsec (latest from official Arch repos as of this report). Since installing the grsecurity kernel, mount.vboxsf will fail with a Protocol error. The following is logged to dmesg when attempting a mount:

{{{
VbglR0HGCMInternalCall: vbglR0HGCMInternalPreprocessCall failed. rc=-5
VBOXGUEST_IOCTL_HGCM_CALL: 64 Failed. rc=-5.
sf_read_super_aux err=-71
VbglR0HGCMInternalCall: vbglR0HGCMInternalPreprocessCall failed. rc=-5
VBOXGUEST_IOCTL_HGCM_CALL: 64 Failed. rc=-5.
sf_read_super_aux err=-71
VbglR0HGCMInternalCall: vbglR0HGCMInternalPreprocessCall failed. rc=-5
VBOXGUEST_IOCTL_HGCM_CALL: 64 Failed. rc=-5.
sf_read_super_aux err=-71
}}}",kballen
14464,dwFileAttributes Incorrectly Reports FILE_ATTRIBUTE_REPARSE_POINT,VirtualBox 5.0.2,Windows,2015-08-17T19:54:27Z,2015-08-17T19:54:27Z,2015-08-17T19:54:27Z,"With a Windows guest running within a Windows host, executing the FindFirstFile Win32 API function on the guest returns the incorrect dwFileAttributes with FILE_ATTRIBUTE_REPARSE_POINT for symlinks on the vboxsf.

With symlinks on Linux & Mac hosts, FILE_ATTRIBUTE_REPARSE_POINT is set to false.

With symlinks on Windows hosts, FILE_ATTRIBUTE_REPARSE_POINT is set to true.

FILE_ATTRIBUTE_REPARSE_POINT should be set to false for all vboxsf files/folders, because being a symlink should only be relevant to the host, and the information should be hidden to the guest.

This is causing us some issues doing PHP development involving symlinked folders, because PHP likes to try and follow the reparse points to convert relative paths to canonical paths.  It attempts to retrieve the reparse point info to conver to the canonical path, then fails.


To reproduce the issue:

On the Windows host, create a folder at c:\test

Create a subdirectory at c:\test\myDir

Create a symlink:

{{{
mklink /D c:\test\myLink c:\test\myDir
}}}

Create a VirtualBox shared folder pointing to c:\test , and mount it to X: within the guest.

Run the attached Python script:

{{{
python find_data.py X:\myLink
}}}

On the Windows host, this outputs:

{{{
Target file is X:\myLink
Found file: myLink
Reparse point: 1024
Attributes: 1040
}}}

On a Linux/Max host, this outputs:

{{{
Target file is X:\myLink
Found file: myLink
Reparse point: 0
Attributes: 16
}}}",Matt Hopkins
14463,Symlinks in shared folders don't work after upgrading to 5.0.2,VirtualBox 5.0.2,Linux,2015-08-17T19:39:47Z,2015-08-20T20:35:47Z,2015-08-20T20:35:47Z,"I'm running CentOS 7 as a guest on a Windows 10 host machine. When using 5.0.0 or the test build, 5.0.1, symlinks work fine but once I upgraded to 5.0.2, they stopped working.

The symlink is relative to 2 directories up and was created in Windows 10 as follows:
mklink /D rpclib ..\..\node-rpclib

I tried downgrading the Guest Additions from 5.0.2 to 5.0.0 and that didn't fix the problem so it seems related to the VirtualBox 5.0.2 program itself since after downgrading to 5.0.0 it went back to working

Here's the VBox.log from 5.0.0: http://gobin.io/mTII
Here's the VBox.log from 5.0.2: http://gobin.io/ZJuK

Let me know if you need any more information.",fastest963
14424,Shared folder seems to cache old file content for the guest after editing host files,VirtualBox 5.0.0,Linux,2015-08-10T13:39:45Z,2015-12-08T17:42:12Z,2015-12-08T17:42:12Z,"I have VirtualBox 5.0.0 running on a Windows 7 SP1 x64 host, with an Ubuntu MATE 15.04 Linux as guest.

To exchange script files in development, I mounted a share manually to a shared folder (""sudo mount -t vboxsf {sharename} {targetname}"", because I did not know where to look for the auto-mounted share), where I copied files to in the hosting Windows, and copied files out of the share into a local directory in the guest Linux.

I found that the script files contained some bugs, which I fixed using Windows tools I have more experience with, which reduced the size of some files (e.g. converting CRLF line breaks to LF only, and deleting some text content).

Then I copied the files with the same name and location in the guest Linux out of the share and into the local directory again, overwriting the old versions of these files. So I thought. But I had to discover that the scripts still contained the buggy parts. And on top, the size was now reduced to the new file size, means, a part of the last script line was truncated now.

The only reliable way to edit the files inside the guest Linux was to empty the files, save with 0 bytes, close, re-open (in gedit or similar fork), then copy the text in a Windows text editor in the host, and paste the text into the Linux text editor via shared clipboard in the guest.",LigH
14403,Symlinks are created incorrectly on shared directories,VirtualBox 5.0.0,Linux,2015-08-06T08:59:44Z,2015-08-26T08:04:54Z,2015-08-26T08:04:54Z,"I have a trusted environment for development and I have activated symlink support for shared folders as desribed here: https://www.virtualbox.org/ticket/10085

This solution worked great so far, however since VirtualBox 5 (in combination with Win 10 host), the creation is incorrect.

If I create a symlink on a shared folder with the command

{{{
ln -s /media/sf_data/file.js /media/sf_data/test.js
}}}

The symlink is created but using readlink, I can see that the created path is incorrect:

{{{
\media\sf_data\test.js
}}}

The backslash should be replaced by a slash.

If I create a symlink outside the shared folder, everything is correct. Also if I create a symlink pointing to a file in a shared folder. However if I create a symlink within a shared folder to a file outside the shared folder, the bug exists.",MathiasB
14169,vboxsf: files with illegal (:) characters truncated on host's NTFS shared folder / results in data loss,VirtualBox 4.3.28,Linux,2015-06-03T06:50:04Z,2015-06-03T06:50:04Z,2015-06-03T06:50:04Z,"Moving a file from a Linux guest filesystem that is tolerant of e.g. the colon character (:) in a filename, to a Windows-hosted NTFS filesystem using vboxsf results in truncation ('''DATA LOSS''') and odd naming behavior.

== Steps to reproduce: ==

1. Create a file on a Linux filesystem in a guest; e.g.
{{{
# dd if=/dev/random of='/tmp/1mega:byte' bs=1M count=1
}}}

2. Mount NTFS shared folder:
{{{
# mount -t vboxsf SHARE /mnt
}}}

3. Move file to vboxsf shared filesystem
{{{
# mv '/tmp/1mega:byte' /mnt
}}}

== RESULT: ==
a file in /mnt of zero size and truncated filename

{{{
# du /mnt/1mega
0       /mnt/1mega

# du '/tmp/1mega:byte'
du: cannot access '/tmp/1mega:byte': no such file or directory
}}}

== EXPECTED RESULT: ==
An error that does not result in the truncation of the /tmp/1mega:byte file in the above example OR a renaming of the file in /mnt, along with preservation of the contents of the file.",baitisj
13986,Shared folder accessible after removed from list of shared folders,VirtualBox 4.3.26,all,2015-03-25T16:00:08Z,2015-03-25T16:00:08Z,2015-03-25T16:00:08Z,"When removing a 'permanent' shared folder while it is mounted, it is removed from the list of shared folders but it's still fully accessible in the VM. There is a pop up warning that this will result in 'broken shared folder', which only offers to click 'OK'. The folder is even accessible after rebooting the guest system and host system. Tested this with Linux and Windows guest systems.

Steps to reproduce:
1. Add shared folder in shared folder settings, check 'Make Permanent'
2. Mount shared folder in guest system
3. Remove shared folder in shared folder settings",A_Dombeck
13930,"Shared folders: ""umount -f"" required",VirtualBox 4.3.24,Linux,2015-03-06T12:53:56Z,2015-03-06T12:53:56Z,2015-03-06T12:53:56Z,"Host: openSUSE 13.1 (64bit)
Guest: openSUSE 13.2 (64bit)",robert spitzenpfeil
13798,Junctions to host,VirtualBox 4.3.20,Windows,2015-01-29T09:42:36Z,2015-01-29T09:42:36Z,2015-01-29T09:42:36Z,"Hello

I don't know if it is a bug or a technical restriction.
I tried to make a link (junction) to a folder from win 8.1 (guest) to my windows 7 (host).
My idea was, instead to add a drive to an UNC Path (\\vboxsrv\hostshare), I make a link to this folder.
But when I access to this folder (double click in explorer), folling message appears (see attachment).

What do you this?
Should this work or isn't possible to do this?

Thanks",Michael
13779,vobxsf breaks on long paths (> 260) with Windows host,VirtualBox 4.3.20,Linux,2015-01-22T21:00:44Z,2015-01-22T21:00:44Z,2015-01-22T21:00:44Z,"Linux guest (Ubuntu 14.10), Windows (8.1) host.

When using shared folders, if the path length of a file is greater than 260, the file doesn't appear correctly in the guest. Note that the problem appears to be related to the path length in the host (Windows), rather than the path length in the mounted filesystem in the guest.

Here is an example of the problem:

{{{

$ ls -l
ls: cannot access 22-20131023143021.zip: No such file or directory
ls: cannot access properties.xml: No such file or directory
total 4
?????????? ? ?   ?      ?            ? 22-20131023143021.zip
-rwxr-xr-x 1 abc abc 3819 Jan 20 10:26 content.txt
?????????? ? ?   ?      ?            ? properties.xml

}}}

In the host, the length of the path (in the host fs) of context.txt is 258. It is readable in the guest (Linux). The other two files have a path length > 260 and are not accessible
",__cc__
13727,can't run a program with Transient Folders with Windows 10 Technical Preview Build 9841,VirtualBox 4.3.20,Windows,2015-01-03T01:03:45Z,2015-01-03T01:03:45Z,2015-01-03T01:03:45Z,"I am using the modern.IE Windows 10 with Internet Explorer 11 VirtualBox download.

I am using VirtualBox 4.3.20 r96996 on Fedora 20 x86_64.

I updated Windows 10 with the available Windows Updates.

I installed the VirtualBox Guest Additions for 4.3.20.

I changed a few of the settings as they come from Microsoft (modern.IE):

1) Chipset -> ICH9
2) Enable I/O APIC
3) IDE -> ICH6
4) switch the HD to the SATA controller
  a) SATA is set to AHCI
  b) enable Use Host I/O Cache

Once the guest is booted, I go to Devices -> Shared Folders Settings...

I add a Transient Folders that maps to my local (ext4) Linux filesystem. A ""Downloads"" directory in my home directory.

I then ""browse"" to \\VBOXSVR\Downloads in Windows Explorer.

I get the file listing.

I doulbe-click on an installer program for a PDF Viewer.

I get an error:
""ShellExecuteEX failed; code 1.
Incorrect function.""

If I copy the file from \\VBOXSVR\Downloads to a local guest directory, it runs fine.

But I have ran this same installer the same way with all of the other modern.IE VirtualBox images, i.e. running the installer from the \\VBOXSVR\Downloads share works on all the other modern.IE images but Windows 10 w/IE 11.",allenatdecisiv
13568,"mount vboxsf won't accept option ""user""",VirtualBox 4.3.18,Linux,2014-10-29T12:30:33Z,2014-11-02T20:32:51Z,2014-11-02T20:32:51Z,"Even though the vbox shared folders can be mounted through mount(8) and a usual /etc/fstab entry can be created, some options accepted by mount won't work for vboxsf, e.g. ""user"" and ""group"".

{{{
juanlu@minted ~ $ tail /etc/fstab
# mint shared folder
mint /media/sf_mint vboxsf defaults,user,uid=1000,gid=999 0 0
juanlu@minted ~ $ mount mint
Only root can mount shared folders from the host.
juanlu@minted ~ $ sudo !!
sudo mount mint
unknown mount option `user'
valid options:
  rw         mount read write (default)
  ro         mount read only
  uid       =<arg> default file owner user id
  gid       =<arg> default file owner group id
  ttl       =<arg> time to live for dentry
  iocharset =<arg> i/o charset (default utf8)
  convertcp =<arg> convert share name from given charset to utf8
  dmode     =<arg> mode of all directories
  fmode     =<arg> mode of all regular files
  umask     =<arg> umask of directories and regular files
  dmask     =<arg> umask of directories
  fmask     =<arg> umask of regular files
}}}

This might be just a non-implemented feature in mount.vboxsf.c. If it's not, then probably a clarification is needed in the user manual that not all mount(8) options are allowed for vboxsf, and in that case it would be nice to have a rationale of why is that.
 ",juanlu001
13135,File corruption with shared folders using VB 4.3.12,VirtualBox 4.3.12,Windows,2014-06-20T13:57:44Z,2015-11-24T05:26:13Z,2015-11-24T05:26:13Z,"Virtual Box 4.3.12r93733
Host Mac OS X 10.8.5
Guest Windows Server Data Center 2012 R2 (4.3.12 Guest Additions Installed)
I have a large ZIP file (837MB) in a directory on my host.

To reproduce:
1) Create a shared folder mapped to the directory containing the zip on the host
2) Copy the ZIP to a local guest directory (IMPORTANT)
3) Attempt to unzip the file using windows native tools, Java's jar.exe or 7zip.  
They will each fail with fairly meaningless error message.  
Windows Extract All... says: ""Error 0x80004005: Unspecified error""
Java's jar says: ""java.util.zip.ZipException: invalid stored block lengths""

Note that step #2 is important.  Unziping the file in place from the share seems to work so something is occurring when the file is copied.
I've also confirmed that MD5 hash of the file does indeed change after it is copied from the share.  I used this tool from Microsoft to compute the hash.  http://support.microsoft.com/kb/841290/en-us",kminder
12819,Host fails to read NTFS folder which is mounted to some partition,VirtualBox 4.3.8,Linux,2014-03-13T18:14:42Z,2015-01-27T08:14:56Z,2015-01-27T08:14:56Z,"Steps to reproduce:
* On Windows host, mount some partition (USB drive in my case) to NTFS folder, (say, to `C:\shared\usb`)
* Create new shared folder, ""shared"" = ""C:\shared"".
* Mount the folder in Linux guest.

Result:
* When listing the directory, ""usb"" is shown as symlink.
* When trying to `cd /mnt/shared/usb` the following error occurs:
{{{
-bash: cd: /mnt/shared/usb: Protocol error
}}}
",dmak
12605,Slow accesses for XP guest shared folders,VirtualBox 4.2.20,Windows,2014-01-13T10:42:10Z,2014-11-27T14:30:31Z,2014-11-27T14:30:31Z,"This problem appears to have a long history (see ""Archaeology"" below).  

'''The symptom:''' XP guest accesses to shared folders at !\\vboxsvr are intermittently stalled, apparently for name resolution.  This happens on both Win7 and CentOS hosts.

'''To replicate:'''
* Fresh install of XP SP3 guest.
* Install Guest Additions
* Add a shared folder - a temp directory with a folder tree (e.g. directories a, b, and c, each with subdirectories 1, 2, and 3) will be convenient.
* In Start -> Run, open a !\\vboxsvr explorer window.  Initial access will stall for 5-10 seconds, after which response is speedy (browse down the folder tree to a/1, b/2, c/3, etc.)
* Doing something else (open a My Computer window) and returning to !\\vboxsvr explorer window will usually result in the next action (e.g. browsing back to directory a/1) being delayed.

'''Affected systems:'''
* VBox 4.1.18 Host: Win 7 64bit Guest: WinXP SP3
* VBox 4.2.20 Host: CentOS 6 64bit Guest: WinXP SP3

'''Unaffected systems:'''
* VBox 4.1.18 Host: Win 7 64bit Guest: Win2K
* VBox 4.2.20 Host: CentOS 6 64bit Guest: Win2K

'''Observations:'''

I have tried each of the following workarounds (both separately and in various combinations).
* Added 255.255.255.255 vboxsvr #PRE to lmhosts; rebooted; '''problem still occurs'''
* Added 127.0.0.1 vboxsvr to hosts; rebooted; '''problem still occurs'''
* Turned off NetBIOS and Windows file sharing (Network Connection -> Properties -> uncheck Client, File Sharing) ; '''problem resolves''' (no stalls, but no Samba access either, of course).
* Turned off all networking (Network Connection -> disable connection) ; '''problem resolves'''
* Disconnected (virtual) network cable via VBox network adapter menu ; '''problem resolves'''
* ipconfig /all shows Node Type is ""Unknown"".  Forced to ""Broadcast"" to match Win2K configuration by setting HLM\SYSTEM\CurrentControlSet\Services\NetBT\Parameters\NodeType = 1.  '''Problem still occurs'''.
* Verified HLM\SYSTEM\CurrentControlSet\Control\NetworkProvider\Order lists VBoxSF.  Although VBoxSF is listed first, netbios broadcasts for vboxsvr still go out when lmhosts is not ""patched"".  Broadcasts do not occur if lmhosts is patched, but access stalls still occur.  Note that Win2K apparently caches the name lookup - Win2K will broadcast on initial access attempt, but never again.  I think XP is retrying the name lookups, leading to the periodic delays.
* My local network does not have any name servers (DNS/WINS).

'''Archaeology:'''

Most of the tickets below have been closed as duplicates of ticket 1728, and relate to speed of file transfers.  Arguably *this* ticket is probably a duplicate of 1728.  I figured I'd try a new ticket since it's been 2 years since 1728 showed any activity, and I have a simpler reproduction method - delays can be observed merely navigating the shared folder's directory tree.

http://www.virtualbox.org/ticket/1728

http://www.virtualbox.org/ticket/2256

http://www.virtualbox.org/ticket/5353

http://www.virtualbox.org/ticket/5599

http://www.virtualbox.org/ticket/6146

http://forums.virtualbox.org/viewtopic.php?f=6&t=56768

http://forums.virtualbox.org/viewtopic.php?p=33519
",shuttlefan
12167,Security Tab is missing in shared folders,VirtualBox 4.2.18,other,2013-10-08T03:09:04Z,2017-02-13T01:40:27Z,2017-02-13T01:40:27Z,"When you open properties of file in shared folder (via VirtualBox sharing), it's security tab is missing. This produces problems when you want read ACL of that file so applications that need such capabilities (like Visual Studio) get an exception trying to access file placed there. I suggest that files in shared folder will have permissions for all to read or to modify according to the settings of that folder.

I post 2 screenshots: the first of VirtualBox shared folder and the second of folder shared via SMB protocol.",Hopungo
11947,High I/O on SharedFolders hangs system,VirtualBox 4.2.16,other,2013-07-09T15:52:02Z,2016-08-17T15:05:50Z,2016-08-17T15:05:50Z,"Running a deep file scan (IdentityFinder) within a 32bit Windows XP guest on a Shared Folder is causing multiple VMs to independently hang. Guest OS remains somewhat responsive (right click on start bar provides menu) but Explorer or other applications remain unresponsive. 

Task Manager is still running/updating and shows 0% CPU usage.

I've included virtual box log. Machine went unresponsive at 10 minutes. Resized window at 35 minutes to provide timeline. Host OS shows vmware process as utilizing between 13-40% cpu utilization.

Host OS is Fedora 19 with yum packages ""akmod-VirtualBox Virtualbox"" installed.



",dsiercks
11900,Windows host cannot see / follow symlinks in shared folder from Linux guest,VirtualBox 4.2.12,Linux,2013-06-25T15:36:49Z,2014-04-24T11:14:35Z,2014-04-24T11:14:35Z,"I'm running an ubuntu guest on a windows 7 host. I have shared folders setup and working via a Vagrant file. My shared folder has a bunch of development files in it created using the Ubuntu guest, nearly all of which I can access from the windows host. 

{{{
$ ls -lah                              
total 13                                                                                  
drwxrwxrwx 1 vagrant vagrant 4096 Jun 25 14:06 ./                                         
drwxrwxrwx 1 vagrant vagrant 8192 Jun 24 19:49 ../                                        
lrwxrwxrwx 1 vagrant vagrant    0 Jun 24 19:51 brunch -> ../brunch/bin/brunch*            
lrwxrwxrwx 1 vagrant vagrant    0 Jun 24 19:49 cake -> ../coffee-script/bin/cake*         
lrwxrwxrwx 1 vagrant vagrant    0 Jun 24 19:50 cleancss -> ../clean-css/bin/cleancss*     
lrwxrwxrwx 1 vagrant vagrant    0 Jun 24 19:49 coffee -> ../coffee-script/bin/coffee*     
lrwxrwxrwx 1 vagrant vagrant    0 Jun 24 19:50 express -> ../express/bin/express*         
lrwxrwxrwx 1 vagrant vagrant    0 Jun 24 19:50 grunt -> ../grunt-cli/bin/grunt*           
lrwxrwxrwx 1 vagrant vagrant    0 Jun 24 19:50 jade -> ../jade/bin/jade*                  
lrwxrwxrwx 1 vagrant vagrant    0 Jun 24 19:50 nodemailer -> ../nodemailer/bin/nodemailer*
lrwxrwxrwx 1 vagrant vagrant    0 Jun 24 19:50 stylus -> ../stylus/bin/stylus*            
-rwxrwxrwx 1 vagrant vagrant   20 Jun 25 14:04 test*                                      
lrwxrwxrwx 1 vagrant vagrant    0 Jun 25 14:02 test2 -> test*                             
lrwxrwxrwx 1 vagrant vagrant    0 Jun 25 14:05 test3 -> ../brunch/bin/brunch*             
lrwxrwxrwx 1 vagrant vagrant    0 Jun 24 19:50 uglifyjs -> ../uglify-js/bin/uglifyjs*     
vagrant@mwalters:~/development/clp-web/node_modules/.bin$                                                                                                 
}}}

What's shown above (ls -lah run on Ubuntu guest) - 

1. 'test' file, created on Ubuntu guest is visible on Windows 7 host
2. 'test2' symlink to 'test', created on Ubuntu guest is visible on Windows 7 host
3. 'test3' symlink to file in another directory, created on Ubuntu guest is *not* visible on Windows 7 host (nor are any of the others which follow the same pattern). 

{{{
$ ls -lah                                                                  
ls: brunch: No such file or directory                                      
ls: cake: No such file or directory                                        
ls: cleancss: No such file or directory                                    
ls: coffee: No such file or directory                                      
ls: express: No such file or directory                                     
ls: grunt: No such file or directory                                       
ls: jade: No such file or directory                                        
ls: nodemailer: No such file or directory                                  
ls: stylus: No such file or directory                                      
ls: test3: No such file or directory                                       
ls: uglifyjs: No such file or directory                                    
total 7.0k                                                                 
drwxr-xr-x   15 mwalters Administ     4.0k Jun 25 10:06 ./                 
drwxr-xr-x   37 mwalters Administ     8.0k Jun 24 15:50 ../                
-rwxr-xr-x    1 mwalters Administ       20 Jun 25 10:04 test*              
-rwxr-xr-x    1 mwalters Administ       20 Jun 25 10:04 test2*                                                                             
}}}

What's shown above (ls -lah run on Windows 7 host) - 

Notice none of the files are recognized as symlinks. test2 is a symlink to test and all of the other files, including test3, are symlinks to files in other directories. None of them are registering or followable from the Windows host. 

Here is a copy of my Vagrant file: 

{{{
# -*- mode: ruby -*-
# vi: set ft=ruby :

Vagrant.configure(""2"") do |config|
  config.vm.box = ""precise32""
  config.vm.box_url = ""removed to allow me to post""

  # Create a forwarded port mapping which allows access to a specific port
  # within the machine from a port on the host machine. In the example below,
  # accessing ""localhost:8080"" will access port 80 on the guest machine.
  config.vm.network :forwarded_port, guest: 9983, host: 9983

  config.vm.hostname = ""#{ENV['USERNAME']}.dev""

  # Create a private network, which allows host-only access to the machine
  # using a specific IP.
  config.vm.network :private_network, ip: ""192.168.33.10""

  # Create a public network, which generally matched to bridged network.
  # Bridged networks make the machine appear as another physical device on
  # your network.
  config.vm.network :public_network

  # Share an additional folder to the guest VM. The first argument is
  # the path on the host to the actual folder. The second argument is
  # the path on the guest to mount the folder. And the optional third
  # argument is a set of non-required options.
  config.vm.synced_folder ""../../"", ""/home/vagrant/development""


  # Provider-specific configuration so you can fine-tune various
  # backing providers for Vagrant. These expose provider-specific options.
  # Example for VirtualBox:
  #
  config.vm.provider :virtualbox do |vb|
  #   # Don't boot with headless mode
  #   vb.gui = true
  #
  #   # Use VBoxManage to customize the VM. For example to change memory:
    vb.customize [""modifyvm"", :id, ""--cpus"", ""8""]
    vb.customize [""modifyvm"", :id, ""--memory"", ""12288"", ""--ioapic"", ""on""]
    vb.customize ['storagectl', :id, '--name', 'SATA Controller', '--hostiocache', 'on' ]
    vb.customize ['setextradata', :id, 'VBoxInternal2/SharedFoldersEnableSymlinksCreate/v-root', '1' ]
    vb.customize ['setextradata', :id, 'VBoxInternal2/SharedFoldersEnableSymlinksCreate/home/vagrant/development', '1' ]
    vb.customize ['setextradata', :id, 'VBoxInternal2/SharedFoldersEnableSymlinksCreate/home/vagrant/development/*', '1' ]
    vb.customize [""modifyvm"", :id, ""--natdnshostresolver1"", ""on""]
    vb.customize [""modifyvm"", :id, ""--natdnsproxy1"", ""on""]
  end

config.vm.provision :puppet do |puppet|
    puppet.manifests_path = ""manifests""
    puppet.manifest_file  = ""init.pp""
  end
end
}}}

Additional info here: https://forums.virtualbox.org/viewtopic.php?f=6&t=56097&p=259861#p259861",mateodelnorte
11640,"vboxsf does not support noatime,nodiratime,discard options",VirtualBox 4.2.10,Linux,2013-03-25T01:30:53Z,2013-03-25T01:30:53Z,2013-03-25T01:30:53Z,"When using a mount (/etc/fstab), for example as follows:

ssd /ssd vboxsf noatime,nodiratime,discard 0 0

And trying to mount, you get:

[roel@localhost /]$ sudo mount -a
unknown mount option `noatime'

Removing the options one by one shows it does not support any:

unknown mount option `nodiratime'
unknown mount option `discard'

Yet, using 'defaults', i.e.:

ssd /ssd vboxsf defaults 0 0

Works fine.

This is very significant, as it does not allow for mounting a SSD with SSD recommended options (noatime,nodiratime,discard).",RoelV
11475,Shared Folders with OS/2 as guest.,VirtualBox 4.2.6,other,2013-02-09T03:23:38Z,2016-10-29T05:00:20Z,2016-10-29T05:00:20Z,"Shared folders with an OS/2 guest are apparently are not implemented or maybe just broken. This makes for a very awkward process of getting data into and out of the VM in many instances. Please consider fixing or implementing this. I as well as any other OS/2 user would be very glad to test what ever was done. OS/2 in general runs very well in VBox for which I am very thankful. If this issue was fixed it would be a great help.

Thank you for your consideration.",OS2Bud
10999,extended error 234 when trying to list directory,VirtualBox 4.1.22,Windows,2012-09-28T12:27:24Z,2016-10-16T20:04:08Z,2016-10-16T20:04:08Z,"Running host windows 7 64 bit
running guest win xp 32 bit, dos program foxprox doing a command prompt from within the program and a dir of a mapped drive or shared vbox folder

extended error 234 and no directory listing",itguru2
10261,Shared Folder symlnks now broken with Windows Host<-> Linux Guest,VirtualBox 4.1.8,Linux,2012-02-18T17:47:07Z,2012-05-03T08:01:19Z,2012-05-03T08:01:19Z,"One of the most annoying things over the holidays was when I upgraded to the Virtual Box 4.1.8 release and it broke the ability to create symlinks inside shared folders on a Windows 7 host.  Normally prior, I would run Virtual Box as administrator and symlinks were creatable and would function properly.  We use symlinks to link our django project settings files to be a source file checked into our code repots.  Now I have to copy the file direct and use a differ tool.

Unfortunately I did try down grading to the previous version but the xml structure of the machine file definitions changed and there was no documentation or inisight on how to correct it so my machines could now only run in the current version that has this broken functionality.  I consider this defect major because it is functionality that is useful to developers, does not pose a security risk, and is now completely broken in the latest point release.

I love VirtualBox and I will be truly satisfied if this issue can be fixed.  Now to file a different report with the PyCharm people ...",Matteius
10085,making a symlink fails on a shared folder with EROFS,VirtualBox 4.1.8,Linux,2011-12-26T14:02:52Z,2020-05-27T16:34:18Z,2020-05-27T16:34:18Z,"it is impossible to create a symlink within a shared folder from guest OS.

guest shell output:

----------------------

[user@centos sf_sources]$ mount

/dev/sda1 on / type ext4 (rw)

proc on /proc type proc (rw)

sysfs on /sys type sysfs (rw)

devpts on /dev/pts type devpts (rw,gid=5,mode=620)

tmpfs on /dev/shm type tmpfs (rw,rootcontext=""system_u:object_r:tmpfs_t:s0"")

/dev/sda3 on /home type ext4 (rw)

none on /proc/sys/fs/binfmt_misc type binfmt_misc (rw)

sunrpc on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw)

sources on /media/sf_sources type vboxsf (gid=501,rw)

[user@centos sf_sources]$ ln ./test ./test2

ln: creating hard link `./test2' => `./test': Operation not permitted

[user@centos sf_sources]$ ln -s ./test ./test2

ln: creating symbolic link `./test2': Read-only file system

[user@centos sf_sources]$ touch test2

[user@centos sf_sources]$ ls test*

test  test2

-------------------

host FS for the shared folder is ext4.

same operation worked fine in ver. 4.1.6",Vlad Bespalov
10014,"Linux (64-bit) host, Windows 7 64-bit guest: can't execute files from shared folders",VirtualBox 4.1.6,Windows,2011-12-10T14:46:58Z,2017-03-24T20:32:11Z,2017-03-24T20:32:11Z,"With a Linux (debian 64-bit) host and a Windows 7 64-bit guest, I've enabled shared folders.  Most access works fine, and the performance is great.  However, I am not able to execute programs (.exe, etc.) or do certain other operations such as opening pdf files by double-clicking on them.  Instead, I have to copy the folders locally in order to operate on them.

I have seen other reports similar to this with Windows host and Linux or Solaris guest that can be resolved by specifying permissions at the time of mounting, but I don't see any options like this for attaching a Windows share.  (My Linux experience is much deeper than my Windows experience.)  I know that when sharing a volume on Windows, you can set things up this way, so perhaps this is intentional.  My shared folder is set as ""full"" access. ",Jay Berkenbilt
10001,Short file names missing from \vboxsvr\share,VirtualBox 4.1.6,Windows,2011-12-07T08:16:23Z,2011-12-07T08:16:23Z,2011-12-07T08:16:23Z,"short file names are missing via shared folders whether the drive is mapped or the unc is used.  for example: 

dir \vboxsvr\share /x 

should list short file names along with the name, but the short file names are missing.  this is causing problems with 16 bit utilities including source code builds that have to use the short name.
",dfatvb
9846,Virtualbox 4.1.4r74291 - shared folders disappear and reappear randomly between reboots,VirtualBox 4.1.4,Windows,2011-11-02T17:22:48Z,2011-11-02T17:22:48Z,2011-11-02T17:22:48Z,"Virtualbox 4.1.4r74291 - shared folder to drive letter mappings disappear and reappear randomly between reboots.
They always show up in the VM's Settings --> Shared Folders section, no problem displaying or editing them.   But, when you start the VM, sometimes they show in Windows Explorer as mapped drive letters, sometimes they don't.   They are always accesible when referenced as UNC paths, i.e. \vboxsrv\sharedfolder, but they are not always accesible as drive letters.",Pedro Serrano
9634,programatically wiring binary data to a file on a VBoxSharedFolderFS disk fails,VirtualBox 4.1.2,Windows,2011-09-22T07:09:28Z,2011-09-22T07:09:28Z,2011-09-22T07:09:28Z,"I made a python program to write binary data to a file on my shared disk. It has the filesystem VBoxSharedFolderFS. '''When the data became over a certain size only 0s was written.''' 
I used the numpy.tofile() method and also used a more direct way writing the data.
f = open('z:\some_file.bin', 'wb')
f.write(data.tostring())
which also failed on the shared disk, but there was no problem on the local disk. 


",exoer
9345,Personalized Settings in Windows NT / XP can not be stored in the shared folder via Junction,VirtualBox 4.1.0,Windows,2011-07-29T18:03:11Z,2011-08-02T19:15:03Z,2011-08-02T19:15:03Z,"Hello,

if you use Windows XP in a VM and shut down after loading the snapshot, you want to retain settings (folders and files) from the Windows profile. There are the shared folder. Problem but if its Windows software in the Windows user settings constant user settings stores. With Linux, you could now create a symbolic link (ln-s newLink Target) but in Windows NT / XP, there is no symbolic links by default. It can also create tools using junctions but it does not work with network sources. ""vboxsvr"" is but an emulated network adapter. Symbolic links with a common goal in order Windows NT / XP do not work also. This is a critical problem. For Windows <NT / XP would be necessary to integrate different shared folder in Windows (mount).




Original text:

Hallo,

wenn man Windows XP in einer vM benutzt und es nach dem starten/beenden immer wieder auf einen Snapshot zurück setzten lässt, möchte man Einstellungen (Ordner und Dateien) aus dem Windows Profil beibehalten. Dafür gibt es den Gemeinsamen Ordner. Problem ist aber wenn Windows Software ihre Benutzereinstellungen konstant im Windows Profil abspeichert. Bei Linux könnte man nun einen symbolischen Link erstellen (ln -s neuerLink Ziel) aber bei Windows NT/XP gibt es standartmäßig keine symbolischen Links. Es lassen sich aber mittels Tools Junctions erstellen aber es funktioniert nicht mit Netzwerkquellen. ""vboxsvr"" ist aber ein emulierter Netzwerkadapter. Symbolische Verknüpfungen mit Ziel in einem Gemeinsamen Order in Windows NT/XP funktionieren also nicht. Das ist ein kritisches Problem. Für Windows < NT/XP müsste man die Gemeinsamen Ordner anders in Windows einbinden (mounten).",Codename
9307,VBox 4.1.0 GA --  shared folder fails manual mount with sf_read_super_aux err=-22,VirtualBox 4.1.0,Linux,2011-07-25T23:50:42Z,2011-07-29T23:43:31Z,2011-07-29T23:43:31Z,"'''VBox 4.1.0 GA gets this error when mounting manually.'''

{{{
mount -t vboxsf vm-shared /mnt/shared
mount: wrong fs type, bad option, bad superblock on vm-shared,
            missing codepage or helper program, or other error
...
}}}

dmesg|tail shows:

{{{
sf_read_super_aux error=-22
}}}

Host: MacOSX 10.6.8
Guest: Oracle Linux 6

'''The following changes work:[[BR]]'''
1. Do not install 4.1.0 GA.  I upgraded VBox from 4.0.12 to 4.1.0.  My Oracle Linux 6.1 guest was using VBox GA 4.0.8 and shared folders were working fine.  After upgrading GA from 4.0.8 to 4.1.0, they now do not work when manually trying to mount shared folders.  This is all against the 2.6.32-100.34.1.el6uek.x86_64 kernel.[[BR]]

2. If I boot the same system into the Redhat kernel 2.6.32-131.0.15.el6.x86_64, and rebuild the 4.1.0 GA, then manual mounting works.[[BR]]


'''Also note:[[BR]]'''

A. Oracle Linux 5, with kernel 2.6.32-100.0.19.el5 and 4.1.0 GA gets: ""mount: Protocol error"" and dmesg says ""sf_read_super_aux err=-71"".  But if I set the VBox GUI setting ""Auto-mount"" for the shared folder, then the shared folder mounts fine at /media/sf_vm-shared.  Meanwhile, ""Auto-mount"" does not work on the OL 6.1 uek kernel (listed in 1. above).[[BR]]

B. If I use Debian guest with kernel 2.6.32-5, then 4.1.0 GA works fine.[[BR]]

C. I created a new VM from scratch (in case there were some issue with the other VMs having been created in an earlier version), did a fresh install of Oracle Linux 6.1, and built the 4.1.0 GA.  Manual mounting of shared folder fails.  '''I will upload the log for this guest''' since it is fresh with basically nothing else done to it.[[BR]]


",jguerrero
9219,Shared Folder Enhancement,VirtualBox 4.0.12,other,2011-07-17T21:35:30Z,2011-07-18T06:52:38Z,2011-07-18T06:52:38Z,"Would it be possible to implement a feature for Windows guests in the Shared Folders to allow a user to define the drive letter for the auto-mount to use when mapping the shared folder? This could also be useful for Linux guests being able to set where you want the shared folder to be mounted.

Thanks!",TheShiv
9066,Shared folders lose guest access to folder contents when folders renamed,VirtualBox 4.0.8,other,2011-06-13T14:10:19Z,2016-02-23T05:50:40Z,2016-02-23T05:50:40Z,"On a Win7 x64 host and Ubuntu 11.04 x64 guest, whenever I rename a shared folder directory, the guest OS loses references to the files therein. The files are still there (and correct on the host OS) but somehow inaccessible on the guest: ls shows the filename, but gives ""no such file or directory"" errors for each file therein (so it would appear that it's there in the filesystem tables, but the pointer to the actual location has got broken somehow). This therefore definitely appears to be a vboxsf error.

The file access can be ""restored"" by remounting the folder, or by renaming the folder back to its original name. The error always occurs, however the renaming is done (console or file manager). It also occurs if the folder is renamed on the host.

This is a pretty serious error, especially because many apps put things in hidden folders and then rename these (e.g. backup utilities such as Unison).",Stuart Rossiter
9036,"kernel WARNING ""sysfs: cannot create duplicate filename /devices/virtual/bdi/vboxsf-$SHARENAME""",VirtualBox 4.0.8,Linux,2011-06-06T19:12:45Z,2011-10-19T18:15:16Z,2011-10-19T18:15:16Z,"The following kernel messages are regularly logged since upgrading to 4.0. They appear harmless.

{{{
Jun  6 20:00:41 wintermute kernel: [   18.074041] ------------[ cut here ]------------
Jun  6 20:00:41 wintermute kernel: [   18.074048] WARNING: at /build/buildd-linux-2.6_2.6.39-1+b1-amd64-h9EWBu
/linux-2.6-2.6.39/debian/build/source_amd64_none/fs/sysfs/dir.c:455 sysfs_add_one+0x86/0x98()
Jun  6 20:00:41 wintermute kernel: [   18.074051] Hardware name: VirtualBox
Jun  6 20:00:41 wintermute kernel: [   18.074052] sysfs: cannot create duplicate filename 
'/devices/virtual/bdi/vboxsf-vmshare'
Jun  6 20:00:41 wintermute kernel: [   18.074054] Modules linked in: bridge stp bnep rfcomm bluetooth rfkill binfmt_misc 
ppdev lp sha256_generic cryptd aes_x86_64 aes_generic cbc dm_crypt dm_mod joydev snd_intel8x0 snd_ac97_codec ac97_bus 
snd_pcm snd_seq snd_timer snd_seq_device pcspkr snd processor soundcore psmouse ac thermal_sys power_supply button 
serio_raw parport_pc parport snd_page_alloc evdev fuse vboxsf(O) vboxguest(O) loop autofs4 ext4 mbcache jbd2 crc16 
nbd usbhid hid sg sd_mod sr_mod cdrom crc_t10dif ohci_hcd ahci libahci libata ehci_hcd virtio_net scsi_mod usbcore 
virtio_pci virtio_ring virtio [last unloaded: scsi_wait_scan]
Jun  6 20:00:41 wintermute kernel: [   18.074089] Pid: 1226, comm: mount.vboxsf Tainted: G           O 2.6.39-1-amd64 #1
Jun  6 20:00:41 wintermute kernel: [   18.074091] Call Trace:
Jun  6 20:00:41 wintermute kernel: [   18.074097]  [<ffffffff810458b4>] ? warn_slowpath_common+0x78/0x8c
Jun  6 20:00:41 wintermute kernel: [   18.074100]  [<ffffffff81045966>] ? warn_slowpath_fmt+0x45/0x4a
Jun  6 20:00:41 wintermute kernel: [   18.074102]  [<ffffffff8114f8aa>] ? sysfs_add_one+0x86/0x98
Jun  6 20:00:41 wintermute kernel: [   18.074105]  [<ffffffff811500cd>] ? create_dir+0x67/0x9f
Jun  6 20:00:41 wintermute kernel: [   18.074108]  [<ffffffff81150196>] ? sysfs_create_dir+0x91/0xa5
Jun  6 20:00:41 wintermute kernel: [   18.074112]  [<ffffffff811a34fc>] ? kobject_add_internal+0xc8/0x181
Jun  6 20:00:41 wintermute kernel: [   18.074114]  [<ffffffff811a3745>] ? kobject_add+0x66/0x6b
Jun  6 20:00:41 wintermute kernel: [   18.074118]  [<ffffffff81331dc0>] ? mutex_lock+0xd/0x33
Jun  6 20:00:41 wintermute kernel: [   18.074120]  [<ffffffff811a3376>] ? kobject_get+0x12/0x17
Jun  6 20:00:41 wintermute kernel: [   18.074124]  [<ffffffff81242cfa>] ? device_add+0xcf/0x5d7
Jun  6 20:00:41 wintermute kernel: [   18.074127]  [<ffffffff8124329f>] ? device_create_vargs+0x8b/0xbc
Jun  6 20:00:41 wintermute kernel: [   18.074131]  [<ffffffff810cbb0f>] ? bdi_register+0x5a/0x183
Jun  6 20:00:41 wintermute kernel: [   18.074133]  [<ffffffff810cb794>] ? bdi_init+0x12b/0x157
Jun  6 20:00:41 wintermute kernel: [   18.074137]  [<ffffffff8110d9c1>] ? inode_sb_list_add+0x10/0x4b
Jun  6 20:00:41 wintermute kernel: [   18.074141]  [<ffffffffa01914fc>] ? sf_read_super_26+0x44f/0x514 [vboxsf]
Jun  6 20:00:41 wintermute kernel: [   18.074144]  [<ffffffff811a2788>] ? ida_get_new_above+0x196/0x1b7
Jun  6 20:00:41 wintermute kernel: [   18.074147]  [<ffffffff811a2bb3>] ? idr_pre_get+0x57/0x6b
Jun  6 20:00:41 wintermute kernel: [   18.074151]  [<ffffffff810fd06a>] ? unlock_super+0x21/0x21
Jun  6 20:00:41 wintermute kernel: [   18.074154]  [<ffffffff810fd0b8>] ? set_anon_super+0x4e/0xe1
Jun  6 20:00:41 wintermute kernel: [   18.074157]  [<ffffffff810fdf6a>] ? sget+0x35d/0x372
Jun  6 20:00:41 wintermute kernel: [   18.074160]  [<ffffffffa01910ad>] ? sf_glob_free+0x2a/0x2a [vboxsf]
Jun  6 20:00:41 wintermute kernel: [   18.074163]  [<ffffffff810fe05c>] ? mount_nodev+0x45/0x79
Jun  6 20:00:41 wintermute kernel: [   18.074165]  [<ffffffff810fdb2f>] ? mount_fs+0x6c/0x14a
Jun  6 20:00:41 wintermute kernel: [   18.074168]  [<ffffffff81112ce9>] ? vfs_kern_mount+0x61/0x97
Jun  6 20:00:41 wintermute kernel: [   18.074171]  [<ffffffff81112d7e>] ? do_kern_mount+0x49/0xd6
Jun  6 20:00:41 wintermute kernel: [   18.074173]  [<ffffffff81113533>] ? do_mount+0x728/0x792
Jun  6 20:00:41 wintermute kernel: [   18.074176]  [<ffffffff810e6260>] ? alloc_pages_current+0xa7/0xca
Jun  6 20:00:41 wintermute kernel: [   18.074179]  [<ffffffff81113625>] ? sys_mount+0x88/0xc3
Jun  6 20:00:41 wintermute kernel: [   18.074182]  [<ffffffff81338c12>] ? system_call_fastpath+0x16/0x1b
Jun  6 20:00:41 wintermute kernel: [   18.074184] ---[ end trace 8683823577cfa94a ]---
Jun  6 20:00:41 wintermute kernel: [   18.074186] kobject_add_internal failed for vboxsf-vmshare with -EEXIST, don't try to 
register things with the same name in the same directory.
}}}

This may be a duplicate of #8056, but for me the shared folders work fine, whereas in that bug the user cannot mount them.

Guest is Linux 2.6.32 through 2.6.39.",Sam Morris
8789,Shared Folders doesn't honor guest OS DAC settings,VirtualBox 4.0.2,Windows,2011-04-25T15:43:28Z,2011-05-09T19:33:13Z,2011-05-09T19:33:13Z,"When using VBoxHeadless vrdp -off and set a mount point on the NFS shared (/export/home/COMMON_SHARE) we noticed that the files that are copied to NFS share from the guest OS show DAC root:root instead of the user DAC settings from the guest OS. The user account exists on both Host and Guest (same UID/GID) example testuser1/staff.

Guest OS: Windows Server 2003 STD R2
Host OS: Solaris 10 v10/09
Extension pack for 4.0.2 installed",Ronald MacDonald
8761,Silent failure to delete files on Shared Folders,VirtualBox 4.0.6,Linux,2011-04-21T22:50:42Z,2021-07-21T08:05:07Z,2021-07-21T08:05:07Z,"When running bonnie++ bechmark on Linux guest (Fedora 14) in a shared folder under Windows XP host, the benchmark fails due to ""directory not empty"" at the end. 

The benchmark creates thousands of small files, and then deletes them. The problem is that after all deletions are done (and no error is reported), the benchmark directory is not empty.

Running the same benchmark on the same guest, but on a Linux native folder (VDI disk), the benchmark runs OK. No files left over.

VirtualBox 4.0.6 (the problem also occurred on VirtualBox 4.0.4, I just hadn't reported it yet, sorry)[[BR]]
Host: Windows XP Professional SP3[[BR]]
Guest: Fedora 14 kernel 2.6.35.11-83.fc14.i686[[BR]]
bonnie++-1.96-1.fc13.i686

Terminal session:

{{{
# cd /media/sf_some_shared_folder
# bonnie++ -u root -n 3 -s 0
Using uid:0, gid:0.
Create files in sequential order...done.
Stat files in sequential order...done.
Delete files in sequential order...Bonnie: drastic I/O error (rmdir): Directory not empty
Cleaning up test directory after error.
# ls
Bonnie.1733
# ls Bonnie.1733/ | wc -l
1106
# for i in `seq 1 5`; do bonnie++ -u root -n 3 -s 0; done
Using uid:0, gid:0.
Create files in sequential order...done.
Stat files in sequential order...done.
Delete files in sequential order...Bonnie: drastic I/O error (rmdir): Directory not empty
Cleaning up test directory after error.
...[snip, cut 4x repeated output]...
# for dir in `ls -d Bonnie*`; do \
    echo -n ""files left over in $dir: ""; \
    ls $dir | wc -l; done
files left over in Bonnie.1733: 1106
files left over in Bonnie.1743: 1111
files left over in Bonnie.1744: 1102
files left over in Bonnie.1745: 1102
files left over in Bonnie.1746: 1102
files left over in Bonnie.1747: 1108
# rm -rf Bonnie.*
# ls
}}}

Notes:[[BR]]
- bonnie++ option [-n 3] creates 3 * 1024 files[[BR]]
- The command [rm -rf Bonnie.*] successfully deletes all left over files. That said, as stated above the benchmark runs OK on native Linux guest disk instead of shared folder, so it seems the problem is not in bonnie++ code.[[BR]]
- There's no error / no message appearing at VBox.log for the running VM right before, during or after the benchmark. See attached file VBox-20110421-1939.log.


// BTM3505 (self reference, please ignore)
",Edmar (Macrovita)
8664,vboxsf causing kernel panic with mounted loopback file system after restore from suspend,VirtualBox 4.0.4,other,2011-04-01T18:28:38Z,2011-04-01T18:28:38Z,2011-04-01T18:28:38Z,"My CentOS 5.5 guest O/S uses a read/write NTFS shared folder from my Windows XP Pro SP3 host operating system drive.  This shared folder is automatically mounted on boot via /etc/fstab to /mnt/host.  Within that shared folder is a 100MB file that functions as a loopback filesystem which was created like this:
{{{
dd if=/dev/zero of=/mnt/host/my-loopback-fs.img bs=1M count=100 && mke2fs -F -j /mnt/host/my-loopback-fs.img
}}}

It can be mounted like:
{{{
mount /mnt/host/my-loopback-fs.img -o loop /mnt/lo-fs
}}}

Once mounted, I close the VM and save the state. 

I then bring the VM back to life. A kernel panic usually sets in seconds after the VM is reloaded. Sometimes it takes 2 minutes, sometimes it is immediate.  Odd things appear with the mounted loopback filesystem if I try to use it such as I/O errors. I've managed to unmount it and remount it before the kernel panic sets in, but I cannot seem to get around the fact that it will eventually occur.

Here's uname -a:
{{{
Linux ffm-023631-vm1.example.tld 2.6.18-194.32.1.el5 #1 SMP Wed Jan 5 17:53:09 EST 2011 i686 i686 i386 GNU/Linux
}}}

I've attached the kernel panic screen and a compiled version of vboxsf.ko.",Greg McLearn
8551,DOS applications dosn't work with VBox Guest Additions shared folders,VirtualBox 4.0.4,Windows,2011-03-13T00:38:18Z,2011-03-13T00:38:18Z,2011-03-13T00:38:18Z,"Hello,

There is a problem with DOS applications working on folders shared through VBox Guest Additions.

The test configuration is:
  Host:  Win XP, 32-bit /problem also confirmed on Win7 64-bit host/

  Guest: Win XP, 32-bit

  Shared folder: 'D:\' on host shared as 'D'; Drive F: on the guest is mapped to \vboxsvr\D;
  
Problem: A DOS application running on the guest cannot find any file residing on a shared folder. The standard DOS FindFirst function call (INT 21/AH=4E) always fails despite there is files matching to the search criteria. For example FindFirst(""F:\Temp\*.*"") always got error is 0x12 (NO MORE FILES), but there are files in F:\Temp. Furthermore if you call GetExtendedError (INT 21/AH=59h) afterwards it reports error 0xEA which looks meaningless and unrelated to the error returned by FindFirst.

The problem occurs only if you are searching for files on a shares through VirtualBox Guest Additions. It's working correctly with classic SMB network shares.

I tested FindFirst for files on a network drive (e.g. drive 'G:' mapped to a network share) and it works. But if you map G: to \vboxsvr\some-shared-folder then you always got error as described above.

Another test by running 4DOS command shell on the guest shows similar behaviour (4DOS is a popular 16-bit DOS shell like COMMAND.COM). If you type ""dir F:\*.*"", where F: is mapped to \vboxsvr\some-shared-folder you see empty directory listing.

Described problem also appears also on a different machine with Windows 7, 64-bit host.",Dimitar Nanev
8481,Failure when non-existing uppercase and underscore directory,VirtualBox 4.0.4,Windows,2011-03-03T09:18:43Z,2011-03-03T09:18:43Z,2011-03-03T09:18:43Z,"1. Ubuntu 10.10 Host
2. Windows XP Guest
3. VirtualBox-Guest-Tools 4.0.4
4. Shared Folder called ""Share"" pointing to ~/Share

5. Do this:
{{{
cd ~/Share
rm -rf /tmp/HELLO_WORLD #yes, the directory must not exist
ln -s /tmp/HELLO_WORLD HELLO_WORLD
}}}

6. Try to access \VBOXSVR\Share:

""Auf \VBOXSVR\Share kann nicht zugegriffen werden. Sie haben eventuell keine Berechtigung, diese Netzwerkressource zu verwenden. Wenden Sie sich an den Administrator des Servers, um herauszufinden, ob Sie über Berechtigungen verfügen.

Falscher Parameter."" 

Unfortunately my Windows is german and i didn't find an exact translation in google...
""Unable to access \vboxscr\share. You might have unsufficent privileges to use this ressource. Consult your admin blah blah

Wrong parameter.""


If you try the same with ""hello_world"" or ""HELLO"" or ""HELLO_WORLd"", there will be no error.",garfield
8038,Symbolic links in shared folders,VirtualBox 4.0.0,Linux,2011-01-08T19:37:48Z,2012-08-21T09:45:45Z,2012-08-21T09:45:45Z,"
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 (http://schinagl.priv.at/nt/hardlinkshel ... ml#contact ) that allow making different kinds of links... but nothing working...",Quaid
7804,"When mounting shared host files with vboxsf, softlinks fail to be copied.",VirtualBox 3.2.12,Linux,2010-12-07T20:23:47Z,2010-12-07T20:23:47Z,2010-12-07T20:23:47Z,"Description:

A host OS Ubuntu 9.10 shares out files in a directory Engineering_85 as an OracleVirtualBox 'device'. A guest OS Ubuntu 9.10 mounts the host files, thus:

{{{ 
sudo mount -t vboxsf -o rw,gid=1000,uid=1000,dmode=0777,fmode=0777 Engineering_85  /home/ddade/mounts
}}} 
 
The mount is listed in the guest OS, thus: 

{{{
ddade@UbuntuBlade01:~/mounts/test/server/sql_performance$ ls -lt
ls: cannot access test_database: No such file or directory
ls: cannot access refresh_database: No such file or directory
ls: cannot access test_sql_performance: No such file or directory
total 24
-rwxrwxrwx 1 ddade ddade  578 2010-12-07 14:31 l.txt
-rwxrwxrwx 1 ddade ddade  518 2010-12-06 17:10 Jamfile
-rwxrwxrwx 1 ddade ddade 2717 2010-12-06 17:10 refresh_database.cpp
-rwxrwxrwx 1 ddade ddade  423 2010-12-06 17:10 run-me-first.sh
-rwxrwxrwx 1 ddade ddade 2170 2010-12-06 17:10 test_database.cpp
-rwxrwxrwx 1 ddade ddade 4093 2010-12-06 17:10 test_sql_performance.cpp
?????????? ? ?     ?        ?                ? refresh_database
?????????? ? ?     ?        ?                ? test_database
?????????? ? ?     ?        ?                ? test_sql_performance
}}}
 
Problem:
Links show up as ""No such file or directory"".  This is an error.  Linux 'inodes' that represent softlinks should be copied as directory entries (regular files).  It appears that OracleBox insists on following the links to their target.  

If the target does not actually exist, that is OK.  The link should be shared-out to the guest OS, and presented correctly as if the file were on the original (host) OS file system.

",V
7749,Vboxsf has no read caching on linux,VirtualBox 3.2.10,Linux,2010-11-21T15:20:48Z,2010-11-21T15:20:48Z,2010-11-21T15:20:48Z,"There is no read caching implemented on volumes mounted via vboxsf on linux guest.
Read cache may improve vboxfs performance dramatically.

For testing try executing 
{{{
time cat any_long_file > /dev/null
}}}
on mounted host fs multiple times. Time to read file does not change. That means there is no caching done on that file.
Dong the same i.e. on vmware fusion shares makes subsequent reading almost instant.",Slava Nadvorny
7642,[feature-request] Reverse Shared Folders,VirtualBox 3.2.10,other,2010-10-24T19:17:20Z,2011-04-28T20:29:56Z,2011-04-28T20:29:56Z,"Hello,

I really would like to be able to work on Guest's hard disk from Host. (when guest is running)

This way I could use host's programs to search in guest's HDD, plus process data located on guest's HDD.

For example using Norton Commander on Windows host, is much nicer to manipulate _all_ the data on both Host and Linux guest, rather than use KDE Krusader or Midnight Commander in Linux guest. This simplifies my workflow.

Guest's filesystems should be mountable on host's filesystems (and as Driver Letters).

-Alexey ""Technologov"", 24.10.2010.",Technologov
7361,Windows XP UNC Benutzername und Passwort läst sich nicht über Ordner suchen hinzufügen,VirtualBox 3.2.8,Windows,2010-08-21T14:38:55Z,2010-08-21T14:38:55Z,2010-08-21T14:38:55Z,"Auf einem Windows XP Host, kann man bei einem ""Durchuschen""(Ordner suchen)-Dialog(Fenster) auch einen Netzwerkort angeben. Das ist UNC. Normalerweise dann, bei einem Datenzugrif auf diesen Ort, fordert dann Windows XP die Zugangsdaten per Fenster auf, ein zu geben. Jedoch wird bei dem ""Durchsuchen""-Dialog bei Virtual Box nur der Path-String ausgelesen und als lokale Adresse behandelt. Somit erkennt Windows nicht, dass es nötig ist, ein Fenster zu erstellen um die Zugangsdaten (Benutzername, passwort) eingeben zu können.

Jedoch könnte man die Funktion von Virtual Box umschreiben. So dass man da bei dem Fenster ""Gemeinsame Ordner"" gleich die Zugangsdaten mit angeben kann und diese dann entsprechend der Paramter-Syntax mit einer UNC-Connection Funktion übernommen werden.

So mit würde folgender Leistungs-Belastener Schritt nicht mehr nötig:

1. Netzlaufwerk zur Netzwerkquelle auf dem Host erstellen (net use).

2. Erstelltes Netzlaufwerk von Punkt 1, als Quelle bei den Gemeinsamen Ordnern (Virtual Box) eintragen.

3. Netzlaufwerk im Gast-Betriebsystem (Virtual Box Computer) erstellen (net use).",Ines
7288,"Shared Folders: on windows guest, linux host. case-sensitive directoryes, but not files.",VirtualBox 3.2.6,Windows,2010-08-09T09:12:43Z,2010-09-22T12:28:31Z,2010-09-22T12:28:31Z,"
example of bug:

    Microsoft Windows XP [Version 5.1.2600][[BR]]
    (C) Microsoft Corporation 1985-2001.[[BR]]
    C:\> net use S: \vboxsvr\user[[BR]]
    S:\TEMP> mkdir tst[[BR]]
    S:\TEMP> mkdir TST[[BR]]
    Subdirectory or file TST already exists. ''<---- normal for WinXP. case insensitive''[[BR]]
    S:\TEMP> mkdir TST\SECOND[[BR]]
    The system can not find the path specified. '''<---- abnormal. case sensitive ! '''[[BR]]
    S:\TEMP> mkdir tst\SECOND[[BR]]
    S:\TEMP> echo 123> TST\SECOND\file '''<---- abnormal. case sensitive ! '''[[BR]]
    Can not find the file specified.[[BR]]
    S:\TEMP> echo 123> tst\SECOND\file[[BR]]
    S:\TEMP> echo 123>> tst\SECOND\FILE ''<---- normal. case insensitive''[[BR]]
    S:\TEMP> erase tst\SECOND\FILE ''<---- normal. case insensitive.''  '''bug does not affect the files, only directories!!! '''[[BR]]


shared folder placed on XFS partition of host.

i found similar ticket [http://www.virtualbox.org/ticket/437 437], but is associated with a very old version of vbox

Why are the directory names are case-sensitive, but filenames not? How to fix?",Jury
6148,international characters cannot be created on mounted linux guest shared folder,VirtualBox 3.1.2,Linux,2010-02-09T14:16:21Z,2010-02-09T14:16:21Z,2010-02-09T14:16:21Z,"Im using linux ubuntu as guest running on linux host ubuntu. shared folder mount perfectly and I can copy move and delete any files on it, but files with caracters with acentos gives me ""protocol error"" see the command:

suporte@lanhelpdataserver:~$ touch test.txt
suporte@lanhelpdataserver:~$ 

the above creates the file test.txt

suporte@lanhelpdataserver:~$ touch testé.txt
touch: cannot touch `testé.txt': Protocol error
suporte@lanhelpdataserver:~$ 

the above returns the error, the only change is the addition of character ""é"" on filename.

thanks.",Marcus Leandro
6074,Permission denied to access shared folders on Windows when folder contains broken symbolic link,VirtualBox 3.1.2,Windows,2010-01-26T13:39:36Z,2011-05-25T12:52:29Z,2011-05-25T12:52:29Z,"Host: Ubuntu 9.10 AMD64 Guest: Windows XP 32bits

For some reason, Windows prevented me to access a shared folder by telling me I need administraor privileges to access it (while I have them).
I noticed that I have some broken symbolic links on the ext4 filesystem of that folder. After removing them, access to the folder was granted by Windows guest os.",Ankhterus
5856,Can not write to VBox shared folders until someone logs in,VirtualBox 3.1.2,Windows,2009-12-27T21:36:34Z,2009-12-27T21:36:34Z,2009-12-27T21:36:34Z,"Vbox 3.1.2
Host: CentOS 5.4
Guest: Windows Server 2003 as a Terminal Server
Guest Additions: 3.1.2

Hi All,

Would you please fix this for me?

I have Cobian Backup (http://www.cobian.se/cobianbackup.htm) set to backup certain files on my Guest in the middle of the night to my host's VBox shared drive (\VBOXSVR\Drivers-Windows\pro-backup). Before I do my backups on the Host, I shut the Guest down.  After the backups are complete, I restart the Guest.  So, the Guest gets reboot once a day.

Problem: Cobian can not see the drive, unless someone logs in (any account will do).  This has shown up mightily during the holidays as no one is using the Guest.

Cobian error:
    12/25/2009 10:20:17 PM The destination directory ""\VBOXSVR\Drivers-Windows\pro-backup\pro60 2009-12-25 22;20;10"" doesn't exist. Trying to create it

    ERR 12/25/2009 10:20:17 PM Cannot create the destination directory ""\VBOXSVR\Drivers-Windows\pro-backup\pro60 2009-12-25 22;20;10""

Many thanks,
-T",ToddAndMargo
5732,Many executables refuse to run fom Shared Folders,VirtualBox 3.1.0,Windows,2009-12-11T22:30:13Z,2019-12-27T16:03:57Z,2019-12-27T16:03:57Z,"About 50% of all Windows executables refuse to run from Shared Folders (vboxsf).

The same executable work perfectly from mounted SMB shares.

Host: Windows XP, Core 2 Q6600, VBox 3.1.0

Guest: Windows 7, 64-bit.

-Technologov, 12.12.2009.",Technologov
5568,unable to perform some svn operations on shared folders from guest,VirtualBox 3.0.12,Linux,2009-11-26T06:32:34Z,2016-02-01T21:02:56Z,2016-02-01T21:02:56Z,"Host: Windows Vista


Guest: Gentoo


Description:

In the development, I need to use some collaboration system whose gui client in windows sucks. So I plan to share the project direcotries with my guest gentoo and then use the command line client in unix instead.[[BR]]
However, because the client depends on the result of 'svn status' and my netbeans uses its own SCM instead of the native one, I have to do this manually, which fails.[[BR]]
This is the error message when I perform some svn operation like 'svn add':
{{{
svn: Can't move '.svn/tmp/entries' to '.svn/entries': Operation not permitted
}}}
This will never happen if the underlying file system is local since I care little about anything inside the .svn directory. I try to chmod it 777 and find that somehow its permission will get ""reverted"" before svn starts its job.[[BR]]
The shared folders are mounted manually with default options. I can do whatever I wish but not with svn, which sounds weird. I hope this does help.[[BR]]
BTW, vbox rocks!",Marvin
5122,Can't access shared folder without login on Windows 2003,VirtualBox 3.0.6,Windows,2009-10-05T12:47:20Z,2009-10-05T12:47:20Z,2009-10-05T12:47:20Z,"Try to access shared folder from autorun service (not with !LocalSystem account but a User account) using net command or UNC but doesn't work until someone login and must maintain login for the access to work.

Issue mentioned in thread:
http://forums.virtualbox.org/viewtopic.php?f=2&t=22032
",Cplaisstw
4890,"Linux guest, ""mv -f file1 file2"" fails on shared folder without write permissions on file2 (Windows hosts)",VirtualBox 3.2.10,Linux,2009-09-01T12:28:38Z,2017-02-07T21:35:02Z,2017-02-07T21:35:02Z,"Test case:

touch file1 file2
chmod a-w file2
mv -f file1 file2

On the guest disk, there is no message whatsoever and file2 is replaced by file1. This is the behavior I expect.


On a shared folder pointing to a directory on the host's local hard disk drive, I get this error from the mv command and file1 remains:

mv: cannot move `file1' to `file2': Operation not permitted


When the shared folder is pointing to a network drive, I get this error from the mv command and file1 remains:

mv: cannot move `file1' to `file2': File exists

",David
4862,"Files in shared folder which open in mode ""w+b""(Linux guest) could not be read(Protocol Error)",VirtualBox 3.0.4,Linux,2009-08-27T02:25:21Z,2017-02-25T16:48:42Z,2017-02-25T16:48:42Z,"I am using a python programe(ZODB) to read file's content in shared folder.But I got a [IOError]Protocl Error when I run the programe.And I check out the source,found that ZODB open this file in ""w+b"" mode.I write a very simple test programme(also python),and got the same problem.Here is the source:
{{{
#Test programme
f = open(""Data.fs"",mode=""w+b"")
f.read(10)#got error here
}}}
Data.fs is the file in shared folder.I also test in mode ""r+b"",it's ok for both write and read.",Yao
4804,creating directories with umlauts in a shared folder fail with error 0x80070057 on Windows Host,VirtualBox 3.0.2,other,2009-08-18T15:42:26Z,2009-08-18T15:42:26Z,2009-08-18T15:42:26Z,"A) cannot create folders with umlauts in a shared folder within a Windows Server 2008 guest.
(probably windows guest in general...)

If I try to create an ""umlaut folder"" within Gentoo guests, which have access to this folder via NFS , there are no problems and the folder is properly created. Also on the host (Gentoo) the folder-name is correctly written in umlauts. (all systems UTF-8)

B) this linux-host-created umlaut-folder is not listed when I refresh the shared folder view in the windows host....

log says nothing related, just:
00:00:01.461 SharedFolders host service: adding host mapping.
00:00:01.461     Host path /mnt/VIRTUAL/EXCHANGE, map name EXCHANGE, writable 1
00:00:01.461 SharedFolders host service: add mapping result VINF_SUCCESS
00:00:01.461 SharedFolders host service: adding host mapping.

I'm using virtualbox-bin 3.0.2 

HOST:
srv1 ~ # eix virtualbox
[U] app-emulation/virtualbox-bin
     Available versions:  1.6.6!f (~)3.0.4+i!m {additions chm headless sdk vboxwebsrv}
     Installed versions:  3.0.2!s(19:32:09 24.07.2009)(additions chm -headless -sdk -vboxwebsrv)
     Homepage:            http://www.virtualbox.org/
     Description:         Family of powerful x86 virtualization products for enterprise as well as home use

[U] app-emulation/virtualbox-modules
     Available versions:  1.6.6 1.6.6-r1 (~)3.0.4 {kernel_linux}
     Installed versions:  3.0.2(19:30:22 24.07.2009)(kernel_linux)
     Homepage:            http://www.virtualbox.org/
     Description:         Kernel Modules for Virtualbox


GUESTS:

web1 EXCHANGE # eix virtualbox
[I] app-emulation/virtualbox-guest-additions
     Available versions:  1.6.6 (~)1.6.6-r1 (~)2.1.4 (~)2.2.0 (~)2.2.2 (~)2.2.4 (~)3.0.2 {X}
     Installed versions:  3.0.2(03:03:35 23.07.2009)(kernel_linux -X)
     Homepage:            http://www.virtualbox.org/
     Description:         VirtualBox kernel modules and user-space tools for Linux guests

Is this a known problem , since in virtualbox's change-logs I could not find any fixes ?!
Also when searching internet and your bug-reports I could'nt find a similar issue ?!

",rottex
4728,using host share for my documents in windows is slow but mapped drive isn't,VirtualBox 3.0.4,Windows,2009-08-09T02:53:10Z,2009-08-23T21:24:11Z,2009-08-23T21:24:11Z,"Weird issue found.

If you change my documents location to your mapped virtual share and use the my documents link to get there it is very slow upwards of 10 seconds to open sometimes longer.

If you create a link to the mapped drive on the desktop it is much faster. Here is where it gets weird. If you change the icon for the shortcut to the mapped drive to the standard folder icon it becomes slow again!

told you it was weird!",Richard
4381,windows guest - linux host file permissions changed on shared folders -> Fixed in SVN,VirtualBox 3.0.6,Windows,2009-07-03T15:34:45Z,2016-03-05T01:44:13Z,2016-03-05T01:44:13Z,"I recently upgraded to 3.0.0. 

I have a number of EXT3 and EXT4 share folders which I access from a windows host via VirtualBox's shared folder handler.  When I access a file in one of the EXT folders it reads and writes to it the first time.  When I modify the file and re-save, or auto save it says it is read-only.  This primarily happens with Microsoft office related products.  [URL=""http://ubuntuforums.org/showthread.php?t=1202151]""]This Thread[/URL] was started by some one having the same problem in 2.2.4  It does not happen on NTFS shared folders.  ",Tvtech
4367,Better folder sharing ideas,VirtualBox 3.0.0,other,2009-07-02T22:30:04Z,2009-07-03T08:16:42Z,2009-07-03T08:16:42Z,"It took me some time to figure out how to do folder sharing with VMs and it seems from my research that I'm not the only one.  Some suggest using a smb share if the host is a linux OS.

A couple of suggestions, though not sure how hard to implement:

 * Ease the mapping, possibly something automatic:
 Currently for windows guests, you have to share the folder as a temporary or fixed share.  Then in addition to that you have to go into windows and create a mapped drive for that share.  That second part I didn't know about because on the mac, from what I recall it maps the share automatically in parallels and vmware fusion.

 It would be nice if something default could be done, like a share automatically created and a shortcut created on the desktop of the windows guest.

 If not that, at least give information in the window that creates a share that additional steps are necessary to see the share on the guest, maybe a link to help or some verbiage in the window itself.

 * Be able to drag and drop files - in addition it would be nice to have a way to drag and drop files between guest and host transparently.  Again, not sure how hard this is, but I recall that vmware fusion did that on the mac.  It's extremely nice :).",Jeremy
4184,Allow network drive mapping too all shared folders,VirtualBox 2.2.4,Windows,2009-06-04T23:41:14Z,2013-09-18T16:57:43Z,2013-09-18T16:57:43Z,"When I used VMware I could map a network drive (under Windows XP guest) to all shared folders within the host (Windows Vista). This was easy because when I went to:
My Network Places » Entire Network » VMware Shared Folders

There was a ""folder"" holding all shared folders and I could just map that folder to a network drive.

This doesn't seem to be possible with VirtualBox. When I go to ""VirtualBox Shared Folders"" in the network, I see one entry by shared folder and I have to map each folder to a network drive, which sucks if I have a bunch of shared folders.

Is it possible to do the same as VMware does in a future release?
",Nazgulled
3645,files in guest shared folders seems not to reflect changes done in host,VirtualBox 2.1.4,Linux,2009-04-06T20:34:53Z,2009-04-15T08:44:17Z,2009-04-15T08:44:17Z,"I have a guest OS (Ubuntu Hardy Heron) with shares a folder (in read/write) with the host OS (Ubuntu Hardy Heron). I use a web editor to edit the files in this folder in the host OS so the modifications should be seen in the guest OS (the shared folder, mounted in the guest, is the root directory of an apache web server installed just in the guest).
The problem is that, when I modify a file in the host side, these changes seem not reflected correctly in guest side. Via a simple cat or less or vi the modified files seem correct but with apache the modifications aren't reflected (I can test this via ""telnet server 80""). In fact often the modifications are seen as strange characters or other times other strange behaviours happen.
I can solve this either:
- umount and then re-mount the shared folder (but I have to do this after every file change)
or
- simply edit the file via vi (guest side) and, with no modifications, save the file",Marco 
3484,"Using shared folders, if the underlying shared resource becomes unavailable, you cannot remove it from its previously assigned VBOXSVR mapping.",VirtualBox 2.1.4,Windows,2009-03-03T12:33:36Z,2009-03-03T12:33:36Z,2009-03-03T12:33:36Z,"Share a resource permanently, read-only, say E:\mp3 -> mp3.  This will show up in the guest OS as \VBOXSVR\mp3.  Then change the drive letter or make the resource generally unavailable (e.g. no E: drive).  Then try to go in to shared folders and remove it - this will appear to work successfully.  But if you go into the guest OS and browse, \VBOXSVR\mp3 will still be there!  Nothing you do within Vbox will make that change - rebooting, logging out as different user, etc.

I've attached virtual machine config files as well.

WORKAROUND:
* Shut down the guest OS
* Go to MachineDisks and find the guest OS's .xml file.
* Find section SharedFolders/SharedFolder which corresponds to share you're trying to remove.
* Change or remove the entry to be correct.
* Restart guest OS virtual machine.
* Vbox appears to just remove the entry you modified in the .xml file regardless of whether you set it to a valid value or not.
* Re-add the changed resource path (if you want to change it).

",cboyd
3458,Shared Folders failing on access,VirtualBox 2.1.4,Windows,2009-03-01T09:08:51Z,2011-05-28T16:46:15Z,2011-05-28T16:46:15Z,"Ubuntu 8.10 64-Bit host, Windows XP SP3 32-Bit guest.

When accessing shared files on the shared folder, often the shared folders file access fails. This includes directory browsing, file access, file deletion, or other operations. Other times, the access works fine. The issue appears random - but generally occurs after inactivity. Shared folders have been shared as a Mapped Drive under XP.

I have disabled the Mapped Drive timeout (http://support.microsoft.com/kb/297684 = ""net config server /autodisconnect:-1""), and have also added 'vboxsvr' to the hosts file as 127.0.0.1 to try to solve the problem - no success.

Accessing files returns ""unknown error occurred while accessing [file]"".
Refreshing the directory after this failure results in ""E:\ is not accessible. The request is not supported.""
Refreshing the directory after a 'timeout', then the directory is displayed, and files are accessible again.

Logfile attached immediately after this issue occurred. VM was still running and active.

",Robert
3451,files with national characters not shown via \vboxsvr,VirtualBox 2.1.4,Windows,2009-02-27T10:13:55Z,2009-02-27T10:13:55Z,2009-02-27T10:13:55Z,"I am running VB 2.1.4_OSE with GA 2.1.4r42893. Guest is WinXPSP2, host is Debian 5.0 (smbd 3.2.5). When accesing host shares via standard \10.0.2.2\ I get full list of all files on that share (files with national characters have them converted to '_'s). When accessing shares via GA - Shared Folders, only files without national characters are shown.
",wolcano
3340,"Shared folder file creation/deletion not permitted on sub-folders, WinXP SP3 Guest",VirtualBox 2.1.2,Windows,2009-02-14T19:13:20Z,2010-09-07T04:11:34Z,2010-09-07T04:11:34Z,"Shared folder issues with Virtualbox 2.1.2 running in a ubuntu 8.10 box, with a WinXP SP3 guest.

The guest can access the shared folder: it shows up in ""My Network Neighbourhood"" and it shows as \VBOXSVR\MYFOLDER

Using the File Explorer in the guest, I can select files, and do Copy/Paste to obtain a copy of the file. I can delete files with no issue.

However, when attempting to do the same in a sub-folder (e.g.: in \VBOXSVR\MYFOLDER\MISC), then I get an error message:

""Cannot copy file: cannot read from the source file or disk""

or if I attempt to delete a file I get:

""Cannot delete file: cannot read from the source file or disk""

I can edit files in sub-folders with no problems. I just can not do file operations on them.

In Linux, the folder I am sharing is in an EXT3 partition. I double checked Permissions and they look all right and they look the same for the root of the folder and its sub-folders:

/media/sda6/MYFOLDER: drwxrwx---

/media/sda6/MYFOLDER/MISC: drwxrwx--- 

Note: if I map the shared folder to a Drive (say X:), the same problem occurs (but the error messages are slighly different).

I believe this started happening with VBox 2.0",Ari
2389,mount.vboxfs does not allow context= option,VirtualBox 2.0.2,Linux,2008-10-07T16:36:55Z,2009-01-21T09:07:47Z,2009-01-21T09:07:47Z,"Mounting a shared folder in a Fedora 9 linux guest, I receive SELinux denials when I try to copy files into the shared folder.  I received advice to attempt the mount using a ''context= option''.

According to the mount manpage, the ''context='' option should be supported on all filesystems...  So I guess this ticket is an RFE.

Cheers,
 Christian",Christian Iseli
