Arch Linux

Please read this before reporting a bug:

Do NOT report bugs when a package is just outdated, or it is in Unsupported. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!

FS#36976 - [virtualbox-guest-modules] Guest machine cannot properly mount shared folders

Attached to Project: Arch Linux
Opened by Xinyun Zhou (xinsnake) - Wednesday, 18 September 2013, 17:36 GMT
Last edited by Ionut Biru (wonder) - Monday, 30 December 2013, 08:59 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Ionut Biru (wonder)
Architecture x86_64
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 8
Private No



After installing linux 3.11.1-1 and virtualbox-guest-modules, guest machine cannot properly mount shared file system. The file system can be mounted, however, the file type is "none" and if a program try to read the content of that folder, it will crash and can hear noise from the computer's hard drive.

Additional info:

* package version(s)
community/virtualbox-guest-modules 4.2.18-3
community/virtualbox-guest-utils 4.2.18-1
core/linux 3.11.1-1 (base)
core/linux-headers 3.11.1-1

Steps to reproduce:

1. Do a normal update using pacman.
2. Share a folder in the VirtualBox host machine.
3. Try to open a terminal on the client machine and ls the folder.
This task depends upon

Closed by  Ionut Biru (wonder)
Monday, 30 December 2013, 08:59 GMT
Reason for closing:  Works for me
Comment by Daniel Kamil Kozar (XAVeRY) - Thursday, 19 September 2013, 07:36 GMT
Please see the forum for additional information by some other users : .
Comment by Travis Kendrick (pouar) - Friday, 20 September 2013, 08:09 GMT
think it could be related to this?
I only heard about it effecting wine so I whitelisted wineserver and wine-preloader shortly after using yama, this would be the first time I heard about it VirtualBox as it doesn't appear on google or if it even uses ptrace for this.
Comment by Hugh Young (oboenerd) - Friday, 20 September 2013, 16:44 GMT
This was fixed upstream yesterday in SVN.
Comment by Oleg Plakhotnyuk (olegus8) - Friday, 27 September 2013, 00:58 GMT
I spent half a day trying to rebuild VirtualBox with aforementioned changeset.
It took some effort to compile VB - for some reason it won't build with webservice, so I disabled it.
Here's what I did step-by-step. Hopefully it'll save some time for someone.
I'm not sure how verbose the explanation should be to be useful, so I'll aim for newbies like me.

I performed whole process inside my VB guest system.
My instructions are for 64 bit Arch Linux installation. For 32 bit system I guess you can skip steps 3-5.

Just in case, output of "uname -a" in my VB guest system:
Linux archwebbievm 3.11.1-2-ARCH #1 SMP PREEMPT Sun Sep 22 19:45:00 CEST 2013 x86_64 GNU/Linux

Well, here we go.

1. Setup ABS (
sudo pacman -S abs
sudo abs

2. Setup for building in a clean chroot (
sudo pacman -S devtools
mkdir ~/chroot
export CHROOT=$HOME/chroot
sudo mkarchroot $CHROOT/root base-devel

3. Edit $CHROOT/root/etc/pacman.conf, uncomment multilib repository:
Include = /etc/pacman.d/mirrorlist

4. Update chroot environment:
sudo arch-nspawn $CHROOT/root pacman -Syu

5. Install gcc-multilib to chroot:
sudo arch-nspawn $CHROOT/root pacman -S gcc-multilib

6. Copy virtualbox from ABS to build dir:
mkdir ~/build
export BUILD=$HOME/build
cp -r /var/abs/community/virtualbox $BUILD

7. Patch virtualbox package using files attached to this message:
cp -t $BUILD/virtualbox/ 005-dirops.patch LocalConfig.kmk.patch PKGBUILD.patch
cd $BUILD/virtualbox
patch -i LocalConfig.kmk.patch
patch -i PKGBUILD.patch

8. Build virtualbox in chroot:
sudo makechrootpkg -c -r $CHROOT

9. Install patched guest and host dkms to the chroot environment:
cp -t $CHROOT/root/tmp/ virtualbox-{guest,host}-dkms-4.2.18-1-x86_64.pkg.tar.xz
sudo arch-nspawn $CHROOT/root pacman -U /tmp/virtualbox-{guest,host}-dkms-4.2.18-1-x86_64.pkg.tar.xz

10. Install patched guest utils:
sudo pacman -U virtualbox-guest-utils-4.2.18-1-x86_64.pkg.tar.xz

11. Copy virtualbox-modules from ABS to build dir:
cp -r /var/abs/community/virtualbox-modules $BUILD

12. Build virtualbox-modules in chroot:
cd $BUILD/virtualbox-modules
sudo makechrootpkg -c -r $CHROOT

13. Install patched guest-modules:
sudo pacman -U virtualbox-guest-modules-4.2.18-3-x86_64.pkg.tar.xz

14. Reboot:
sudo reboot

After reboot I was able to do 'ls' in shared folders. Hopefully it'll work for somebody else too.
I can also upload patched binary virtualbox-guest-modules and virtualbox-guest-utils somewhere, but I'm not sure if it's the right way to do it.
Comment by Oleg Plakhotnyuk (olegus8) - Sunday, 13 October 2013, 19:07 GMT
The problem doesn't appear for me after the last "pacman -Syu". Namely:

Host & guest kernels:
Linux archfamily 3.11.4-1-ARCH #1 SMP PREEMPT Sat Oct 5 21:22:51 CEST 2013 x86_64 GNU/Linux

virtualbox 4.2.18-2
virtualbox-host-modules 4.2.18-6
virtualbox-guest-modules 4.2.18-6
virtualbox-guest-utils 4.2.18-2

Thanks for patching the packages!
Comment by Doug Newgard (Scimmia) - Sunday, 29 December 2013, 08:01 GMT
Since VirtualBox in [community] is now at 4.3.x, I assume it's fixed?
Comment by Oleg Plakhotnyuk (olegus8) - Sunday, 29 December 2013, 17:32 GMT
Shared folders work fine for me in 4.3.0