From ArchWiki
Revision as of 16:31, 1 November 2012 by Sylvite (talk | contribs) (Bridge networking on Windows stopped working: new section)
Jump to navigation Jump to search


Anybody, any experience with how to use existing vmware virtual machine in virtualbox? I tried, but without success. I'll retry using: and post my findings.

Removal of VBoxClient-all

Why is there no mention of /usr/bin/VBoxClient-all script? It is imporant for getting the final touches for an archlinux guest to work correctly.

vboxusers group

It would be nice if someone explained why you might need to add your user to vboxusers group. I did not add my user to this group and everything worked as expected. --Bhobbit 19:11, 12 April 2010 (EDT)


In section "Synchronise guest date with host" it should be noted that starting vbox-service is also required for the auto mounting feature to work. For example, creating a Shared Folder with the options Make Permanent and Auto-Mount selected will NOT auto mount in /media/sf_<SHARE_NAME> if vbox-service has not been started. --sjroe 19:13, 30 December 2011 (EST)

With systemd, running sudo systemd enable vboxservice.service makes VBoxService run on every install. Or, running VBoxService as root at boot works too. --Meatcar (talk) 17:34, 17 October 2012 (UTC)


I had to modprobe vboxnetflt and add it in /etc/modules-load.d to be able to run the virtualbox GUI application. -- erlhel (talk) 12:21, 25 September 2012 (UTC)


The tool vdfuse (if it works with archlinux) could be suggested in the Mounting .vdi Images section instead of telling that it's impossible. -- Heinrich5991 (talk) 11:01, 3 October 2012 (UTC)

Since you use vdfuse and familiar with it, you can add these info yourself. See Help:Editing and Help:Style for a guide. -- Fengchao (talk) 12:17, 5 October 2012 (UTC)

Bridge networking on Windows stopped working

After doing a pacman -Syu today, Nov 1, 2012, bridged networking on a Windows 7 guest has stopped working-- the guest can't access the network. NAT works fine in other virtualboxes. The virtualbox module itself wasn't updated with this pacman update, so I'm thinking it might be the 3.6.4 kernel, but I'm not sure yet.