VirtualBox Shared Folders not working after upgrade

lazysunbather · 2013-09-18 08:57:55

Hello,
I'm running Arch Linux as a guest OS in VirtualBox. After yesterday's upgrades of linux to 3.11.1-1 and virtualbox-guest-modules to 4.2.18-3, the shared folder functionality seems to be seriously borked.

The vboxsf module itself loads fine, and produces no kernel messages except the standard hello :

[    3.460662] vboxsf: Successfully loaded version 4.2.18_OSE (interface 0x00010004)

Mounting a shared directory with mount.vboxsf and mount -t vboxsf results in a success. However, accessing the mount ends in the CPU usage spiking to 100% and nothing happening. Furthermore, the following line appears in /etc/mtab :

none /mnt vboxsf rw,nodev,relatime 0 0

Removing and adding the shared folder from the machine settings, sadly, does not work. I'm running VirtualBox 4.2.18 on the host machine.

Has anybody had this issue after the update? Thanks in advance.

chetjan · 2013-09-18 15:48:07

Problem:
ls hangs when run in a shared folder.

Yesterday I updated Arch Linux (through pacman), halted, updated Virtual Box to 4.2.18, and started Arch Linux again. However, after I did so I could not access my shared directories (with my Windows host). I do not think it is a permission problem (root cannot ls either).

I can:
cd /media/sf_VMShared
cd <a folder in VMShared>

However, I can't ls the directories. This is only a problem in Shared Folders. When I run

strace ls

It gets stuck looping on

getdents(3, /* 1 entries */, 32768)     = 24

until I Ctrl-C. Any idea how to fix this? Thanks.

Full strace ouput:

execve("/usr/bin/ls", ["ls"], [/* 27 vars */]) = 0
brk(0)                                  = 0xf6b000
access("/etc/ld.so.preload", R_OK)      = -1 ENOENT (No such file or directory)
open("/etc/ld.so.cache", O_RDONLY|O_CLOEXEC) = 3
fstat(3, {st_mode=S_IFREG|0644, st_size=121790, ...}) = 0
mmap(NULL, 121790, PROT_READ, MAP_PRIVATE, 3, 0) = 0x7fe8a216f000
close(3)                                = 0
open("/usr/lib/libcap.so.2", O_RDONLY|O_CLOEXEC) = 3
read(3, "\177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0000\25\0\0\0\0\0\0"..., 832) = 832
fstat(3, {st_mode=S_IFREG|0644, st_size=16872, ...}) = 0
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x7fe8a216e000
mmap(NULL, 2112096, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 0x7fe8a1d6a000
mprotect(0x7fe8a1d6e000, 2093056, PROT_NONE) = 0
mmap(0x7fe8a1f6d000, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x3000) = 0x7fe8a1f6d000
close(3)                                = 0
open("/usr/lib/libacl.so.1", O_RDONLY|O_CLOEXEC) = 3
read(3, "\177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0\300 \0\0\0\0\0\0"..., 832) = 832
fstat(3, {st_mode=S_IFREG|0644, st_size=35384, ...}) = 0
mmap(NULL, 2130592, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 0x7fe8a1b61000
mprotect(0x7fe8a1b69000, 2093056, PROT_NONE) = 0
mmap(0x7fe8a1d68000, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x7000) = 0x7fe8a1d68000
close(3)                                = 0
open("/usr/lib/libc.so.6", O_RDONLY|O_CLOEXEC) = 3
read(3, "\177ELF\2\1\1\3\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0\320\34\2\0\0\0\0\0"..., 832) = 832
fstat(3, {st_mode=S_IFREG|0755, st_size=2027565, ...}) = 0
mmap(NULL, 3844624, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 0x7fe8a17b6000
mprotect(0x7fe8a1958000, 2093056, PROT_NONE) = 0
mmap(0x7fe8a1b57000, 24576, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x1a1000) = 0x7fe8a1b57000
mmap(0x7fe8a1b5d000, 14864, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x7fe8a1b5d000
close(3)                                = 0
open("/usr/lib/libattr.so.1", O_RDONLY|O_CLOEXEC) = 3
read(3, "\177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0`\24\0\0\0\0\0\0"..., 832) = 832
fstat(3, {st_mode=S_IFREG|0755, st_size=18736, ...}) = 0
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x7fe8a216d000
mmap(NULL, 2113912, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 0x7fe8a15b1000
mprotect(0x7fe8a15b5000, 2093056, PROT_NONE) = 0
mmap(0x7fe8a17b4000, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x3000) = 0x7fe8a17b4000
close(3)                                = 0
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x7fe8a216c000
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x7fe8a216b000
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x7fe8a216a000
arch_prctl(ARCH_SET_FS, 0x7fe8a216b700) = 0
mprotect(0x7fe8a1b57000, 16384, PROT_READ) = 0
mprotect(0x7fe8a17b4000, 4096, PROT_READ) = 0
mprotect(0x7fe8a1d68000, 4096, PROT_READ) = 0
mprotect(0x619000, 4096, PROT_READ)     = 0
mprotect(0x7fe8a218d000, 4096, PROT_READ) = 0
munmap(0x7fe8a216f000, 121790)          = 0
brk(0)                                  = 0xf6b000
brk(0xf8c000)                           = 0xf8c000
open("/usr/lib/locale/locale-archive", O_RDONLY|O_CLOEXEC) = 3
fstat(3, {st_mode=S_IFREG|0644, st_size=1852416, ...}) = 0
mmap(NULL, 1852416, PROT_READ, MAP_PRIVATE, 3, 0) = 0x7fe8a1fa5000
close(3)                                = 0
ioctl(1, SNDCTL_TMR_TIMEBASE or SNDRV_TIMER_IOCTL_NEXT_DEVICE or TCGETS, {B38400 opost isig icanon echo ...}) = 0
ioctl(1, TIOCGWINSZ, {ws_row=48, ws_col=95, ws_xpixel=950, ws_ypixel=912}) = 0
openat(AT_FDCWD, ".", O_RDONLY|O_NONBLOCK|O_DIRECTORY|O_CLOEXEC) = 3
getdents(3, /* 1 entries */, 32768)     = 24
getdents(3, /* 1 entries */, 32768)     = 24
getdents(3, /* 1 entries */, 32768)     = 24
...
getdents(3, /* 1 entries */, 32768)     = 24
--- SIGINT {si_signo=SIGINT, si_code=SI_KERNEL} ---
+++ killed by SIGINT +++

Last edited by chetjan (2013-09-18 20:59:31)

renau · 2013-09-18 16:39:55

I had the same problem. My solution was to downgrade to the previous version

cd /var/cache/pacman/pkg
sudo pacman -U linux-3.10.10-1-x86_64.pkg.tar.xz virtualbox-guest-modules-4.2.18-1-x86_64.pkg.tar.xz virtualbox-guest-utils-4.2.18-1-x86_64.pkg.tar.xz
sudo reboot

karol · 2013-09-18 16:51:07

renau wrote:

sudo reboot

OT, but you don't need sudo: https://wiki.archlinux.org/index.php/Al … o_Shutdown

Maybe you should open a bug report for this?

alexneko · 2013-09-19 00:33:15

I had exactly the same problem with you. Then I switched to linux-lts kernel and it's OK.

rogerdarch · 2013-09-19 00:37:12

The same happened to me after upgrading today to linux 3.11.1-1-ARCH. I'm using VirtualBox version 4.1.2.

juniway · 2013-09-19 01:22:24

exactly happen the same to me when I upgrade to linux 3.11.1 core, I am using VirtualBox version 4.2.18
you can use strace -al>/tmp/lsstrace.txt 2>&1 to save the error message in a file

Last edited by juniway (2013-09-19 02:53:37)

karol · 2013-09-19 01:26:33

rogerdarch wrote:

The same happened to me after upgrading today to linux 3.11.1-1-ARCH. I'm using VirtualBox version 4.1.2.

rogerdarch, why are you using an old version of VB?

ewaller · 2013-09-19 02:10:57

Merging with existing thread in Applications and Desktop Environments

lazysunbather · 2013-09-19 07:32:18

The bug has already been reported. See here : https://bugs.archlinux.org/task/36976

rogerdarch · 2013-09-19 08:54:48

karol wrote:

rogerdarch wrote:
The same happened to me after upgrading today to linux 3.11.1-1-ARCH. I'm using VirtualBox version 4.1.2.
rogerdarch, why are you using an old version of VB?

Hi Karol: Because my interaction with my win7 host environment is minimal and previous archlinux guest environment updates have always worked with VirtualBox 4.1.2. I mentioned my use of VBox version 4.1.2 simply to suggest that the "bug" happens (most likely) regarless of the VBox version.

Last edited by rogerdarch (2013-09-19 09:04:51)

karol · 2013-09-19 13:46:05

I'm asking because partial upgrades are unsupported. Arch Linux supports the package versions which are in the repos.

picmantonic · 2013-09-20 10:03:31

This bug was not apparent after upgrading to 3.11.1, from 3.10.10, but has appeared today after upgrades to systemd and procps-ng.
It also could have occurred when upgrading kernel to 3.11.1-1 a day or so ago.
Shared folder mounts OK (as before), but...
system seems to be unable to enumerate files and folders under the mounted shared folder. I can 'ls -l' individual files if I give full path.

I get same problem with kubuntu saucy beta vm, with kernel 3.11.0.7.

walterjr · 2013-09-20 15:35:47

I am experiencing the same here. Would vboxguest-hook be useful in this case?

oboenerd · 2013-09-20 16:46:31

Related upstream bug:
https://www.virtualbox.org/ticket/12128

Fixed upstream in SVN:
https://www.virtualbox.org/changeset/48529/vbox

Is it possible to include this fix into the guest additions packages as a patch?

walterjr · 2013-09-21 20:54:34

any workarounds??

theherk · 2013-09-22 00:17:53

Well this is frustrating. It is a consolation to somebody that is kind of new to Arch that this is an actual problem and not some bonehead mistake on my part. There must be some other way to get around this. Is the solution to downgrade the kernel?

oboenerd · 2013-09-22 04:35:12

Since this is a kernel problem, I'm switching over to linux-lts (long-term support) kernel on the guest system temporarily. If this isn't an option then one can perhaps compile the modules from svn.

EDIT: I'm actually considering permanently switching over to linux-lts for my guest linux operating systems. Since everything is under a virtual machine I really don't need bleeding-edge kernel features anyways. Also, incidents like this are much less likely to happen in this scenario.

Last edited by oboenerd (2013-09-22 04:39:10)

graysky · 2013-09-23 08:26:44

Watch out for https://bugs.archlinux.org/task/36977 if trying to install the guest-utils package.

starvoid · 2013-09-25 06:34:22

oboenerd wrote:

Fixed upstream in SVN:
https://www.virtualbox.org/changeset/48529/vbox

I replaced my original dirops.c with the fix. It didn't seem to fix this bug unfortunately.

Has anyone else done this, or is this not officially a fix yet?

picmantonic · 2013-09-25 07:47:34

I 'upgraded' to vb 4.3 beta 3 on my iMac and tested kubuntu 13.10 beta 1. The shared folders bug IS fixed in that environment.
However, Archlinux uses it's own vb guest additions packages, which are on vb 4.2.18, so Archlinux doesn't run properly (I locked it up trying to save image). Fortunately it recovered when I went back to vb 4.2.18.
I think we just have to wait for vb 4.3.

olegus8 · 2013-09-27 01:00:07

I was able to patch virtualbox-guest-modules and utils. Everything works fine since then. I couldn't find a way to attach files here, so I put detailed explanation in this bug report: https://bugs.archlinux.org/task/36976

Last edited by olegus8 (2013-09-27 03:15:11)

picmantonic · 2013-10-02 15:46:59

Probably seen it it by now but the latest pacman -Syu delivered virtualbox_guest_modules_4.2.18-4, which fixed my shared folders problem.
Arch package maintainers win (again).

chetjan · 2013-10-05 15:55:38

Unfortunately, this update did not fix it for me. It now prevents the ls from hanging, but ls still returns nothing. Cannot move to a shared folder either, claims "No space left on device".

Last edited by chetjan (2013-10-05 15:56:04)

picmantonic · 2013-10-06 15:09:43

I am still on virtualbox-guest-modules-4.2.18-4 but now the kernel has been upgraded to 3.11.3-1 - and I've lost shared folders. Suspect the virtualbox-guest-modules-4.2.18-6, in testing, is needed to fix it? Hope so. Eventually this should settle...

Arch Linux

#1 2013-09-18 08:57:55

VirtualBox Shared Folders not working after upgrade

#2 2013-09-18 15:48:07

Re: VirtualBox Shared Folders not working after upgrade

#3 2013-09-18 16:39:55

Re: VirtualBox Shared Folders not working after upgrade

#4 2013-09-18 16:51:07

Re: VirtualBox Shared Folders not working after upgrade

#5 2013-09-19 00:33:15

Re: VirtualBox Shared Folders not working after upgrade

#6 2013-09-19 00:37:12

Re: VirtualBox Shared Folders not working after upgrade

#7 2013-09-19 01:22:24

Re: VirtualBox Shared Folders not working after upgrade

#8 2013-09-19 01:26:33

Re: VirtualBox Shared Folders not working after upgrade

#9 2013-09-19 02:10:57

Re: VirtualBox Shared Folders not working after upgrade

#10 2013-09-19 07:32:18

Re: VirtualBox Shared Folders not working after upgrade

#11 2013-09-19 08:54:48

Re: VirtualBox Shared Folders not working after upgrade

#12 2013-09-19 13:46:05

Re: VirtualBox Shared Folders not working after upgrade

#13 2013-09-20 10:03:31

Re: VirtualBox Shared Folders not working after upgrade

#14 2013-09-20 15:35:47

Re: VirtualBox Shared Folders not working after upgrade

#15 2013-09-20 16:46:31

Re: VirtualBox Shared Folders not working after upgrade

#16 2013-09-21 20:54:34

Re: VirtualBox Shared Folders not working after upgrade

#17 2013-09-22 00:17:53

Re: VirtualBox Shared Folders not working after upgrade

#18 2013-09-22 04:35:12

Re: VirtualBox Shared Folders not working after upgrade

#19 2013-09-23 08:26:44

Re: VirtualBox Shared Folders not working after upgrade

#20 2013-09-25 06:34:22

Re: VirtualBox Shared Folders not working after upgrade

#21 2013-09-25 07:47:34

Re: VirtualBox Shared Folders not working after upgrade

#22 2013-09-27 01:00:07

Re: VirtualBox Shared Folders not working after upgrade

#23 2013-10-02 15:46:59

Re: VirtualBox Shared Folders not working after upgrade

#24 2013-10-05 15:55:38

Re: VirtualBox Shared Folders not working after upgrade

#25 2013-10-06 15:09:43

Re: VirtualBox Shared Folders not working after upgrade

Board footer