From ArchWiki
Jump to: navigation, search


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)


At the time of writing this, installing virtualbox and virtualbox-host-modules from the official repositories will not work as the modules are outdated, however, following the description for the dkms package works, so it might be worth mentioning that "if the virtualbox-host-modules package is out of date, the dkms solution below can be used." —This unsigned comment is by DusteD (talk) 13:30, 18 September 2014 (UTC). Please sign your posts with ~~~~!

See FS#40495, linked from VirtualBox#Load_the_Virtualbox_kernel_modules_2 along with some accompanying threads. As this issue is the same for both hosts and guests, searching for problems with the other module could provide more information for your issue.
AFAIK, all it takes is to run depmod $(uname -r) after each update of virtualbox-host-modules/virtualbox-guest-modules (depmod should be run from the packages' .install files, see the bug), or use DKMS to (re)compile the virtualbox-guest-dkms/virtualbox-host-dkms module and have a whole bunch of files untracked by pacman in the filesystem...
-- Lahwaacz (talk) 14:22, 18 September 2014 (UTC)

NS_ERROR_FAILURE (0x80004005)

I found out ~/.config/VirtualBox/VirtualBox.xml was empty (size 0 Bytes) while ~/.config/VirtualBox/VirtualBox.xml-prev was not. A simple copy of the "-prev" to the original fixed this issue for me: cp ~/.config/VirtualBox/VirtualBox.xml-prev ~/.config/VirtualBox/VirtualBox.xml —This unsigned comment is by Costis (talk) 11 January 2015 20:44. Please sign your posts with ~~~~!

Cannot find the cause of the problem. Anyway, if ~/.config/VirtualBox/VirtualBox.xml has a 0 byte size, VirtualBox will complain at startup and will say it cannot find proper XML tags. -- wget (talk) 21:26, 12 January 2015 (UTC)

Binding to a physical drive

In the near future, I'm gonna make some changes to this section VirtualBox#Create a raw disk .vmdk image. The latter advertises the use of the disk group while it is clearly unavailable anymore since Arch migrated to systemd. And the command VBoxManage internalcommands createrawvmdk -filename /path/to/file.vmdk -rawdisk /dev/sdb -register does not recognize the -register argument --> replacing each occurrences in the article where this statement appears is needed. Comments on these 2 topics are welcomed and even needed for me to ensure I'm right. -- wget (talk) 08:13, 5 February 2015 (UTC)

modprobe: ERROR: could not insert 'vboxguest': No such device

My system is dual boot for windows 7 & Arch Linux. Is it possible to remove the error message? In windows 7, I use virtualbox to run the same file system of Archlinux. So, my /etc/modules-load.d/virtualbox.conf is like

 # for host
 # for guest

It works well when I boot archlinux inside virtualbox. It shows systemd-modules-load.service failed when I boot directly.

 # systemctl status systemd-modules-load.service
 ● systemd-modules-load.service - Load Kernel Modules
    Loaded: loaded (/usr/lib/systemd/system/systemd-modules-load.service; static; vendor preset: disabled)
    Active: failed (Result: exit-code) since Wed 2015-05-20 09:58:59 CST; 6min ago
      Docs: man:systemd-modules-load.service(8)
   Process: 25784 ExecStart=/usr/lib/systemd/systemd-modules-load (code=exited, status=1/FAILURE)
  Main PID: 25784 (code=exited, status=1/FAILURE)
 May 20 09:58:58 t64 systemd[1]: Starting Load Kernel Modules...
 May 20 09:58:59 t64 systemd-modules-load[25784]: Failed to insert 'vboxguest': No such device
 May 20 09:58:59 t64 systemd-modules-load[25784]: Failed to insert 'vboxsf': No such device
 May 20 09:58:59 t64 systemd[1]: systemd-modules-load.service: main process exited, code=exited, status=1/FAILURE
 May 20 09:58:59 t64 systemd[1]: Failed to start Load Kernel Modules.
 May 20 09:58:59 t64 systemd[1]: Unit systemd-modules-load.service entered failed state.
 May 20 09:58:59 t64 systemd[1]: systemd-modules-load.service failed.

Automounting Shared Folders also requires VBoxService to be enabled

On the wiki page section Load the Virtualbox kernel modules 2 the VBoxService is barely mentioned. It is written

"Alternatively, enable the vboxservice service which loads the modules and synchronizes the guest's system time with the host."

In my humble opinion it should state that this service is also required when you want to automount your shared folders. I would change it myself, but since I just joined the wiki, I feel I should discuss it before changing.

My suggested change would be something like

"Alternatively, enable the vboxservice service which loads the modules and synchronizes the guest's system time with the host. This service is also required if you wish to enable automounting of shared folders."

It should probably also be mentioned in the Automounting section.

Does anyone have any input or feedback on my somewhat limit suggestion?

This was mentioned in the article previously, but I removed it after testing that I was able to automount shared folders without the service running. Can you double check that the service is actually required? Silverhammermba (talk) 16:45, 1 July 2015 (UTC)
When looking through the source code for vboxsf module I cannot find any trace of any code that would automount the devices. This is expected as the module is only responsible for registering the filesystem type and performing the mount when requested to do so. Then again, calling it required is not actually true since you could technically get around this by adding an entry to fstab. Or setting up a script that calls "mount -t vboxsf SHARED_FOLDER_NAME MOUNT_POINT". But without an action like enable the service, adding a fstab entry or any other automation techniques the automating should not happen. So maybe in the Automounting section we should mention this. Soderstrom (talk) 18:14, 1 July 2015 (UTC)

Mount at boot - A better way?

I've just found my way here after trying to 'mount at boot' a vbox share. The "comment=systemd.automount" method seems like a bit of a hack, and leaves the 'mount' output looking a bit strange until the mount is triggered. Isn't there a cleaner way to make this work actually at boot? Maybe using a systemd service 'After=' specification? I tried to get it working but failed (systemd noob). There must be a way I think because the /media/sf_ mount happens magically around boot time. Anyway, not whinging, just trying to improve the world. Thought an expert might be able to see a neater solution. Cheers. Peterg4000 (talk) 11:51, 12 August 2015 (UTC)

Solving smbus module load failure

A VirtualBox Guest apparently doesn't have an smbus, resulting in the appearance of the following message at the console at startup of the VM and in the journal:

 piix4_smbus 0000:00:07.0: SMBus base address uninitialized - upgrade BIOS or use force_addr=0xaddr

With the help of [1] I solved this by doing:

 echo 'blacklist i2c_piix4' > /etc/modprobe.d/modprobe.conf

Guest modules reload

I was about to revert [2] because virtualbox-guest-modules comes already recompiled like virtualbox-host-modules, however /usr/bin/rcvboxdrv also properly removes and reloads the modules; in virtualbox-host-modules.install there is a message reminding to reload the modules, but in virtualbox-guest-modules.install there's nothing, does anyone know why? — Kynikos (talk) 13:47, 3 November 2015 (UTC) (last edit: 14:00, 4 November 2015 (UTC))

Granting user rw access to all disks?

In Section VirtualBox#Create_a_VM_configuration_to_boot_from_the_physical_drive, we have, quote: "[putting user in disk group] way is the more elegant, let us proceed that way..."

Doesn't that mean any process running as the user now has complete write access to ALL raw disk devices?

Isn't that a rather bad idea? Kind of like a permanent su for the user, able to change any disk data at will.

A mechanism that (at the very least) only modified access to the disk in question seems preferable. -- Peterg4000 (talk) 14:22, 7 May 2016 (UTC)

Recent changes to VirtualBox article

Moved from User_talk:Alad. -- Alad (talk) 12:35, 19 May 2016 (UTC)

Hi Alad. I see you have been doing some changes recently (a few minutes ago actually :p) to the VirtualBox article which I have rewritten a year ago and have been maintaining since. I see you are currently moving subsections to dedicated pages, which is basically what has been undone a year ago :-/. After discussions with User:Kynikos, merging everything on a same page has been the right choice for this page, because the structure was has been made quite clear. I'm willing to discuss this issue further on IRC. I'm known on wget there too. -- wget (talk) 10:34, 19 May 2016 (UTC)

To recap from IRC: the old discussion: [3], i.e.
The main VirtualBox article will be clearer when I will have finished the rewrite and a dedicated subpage might be unneeded
Pretty much the only change I've done is moving the big titles ("Advanced configuration", "Virtual disk management") to a subpage, keeping their structure. This simplifies maintenance and gives a quicker overview on the "essentials", in the line of GRUB and GRUB/Tips and tricks.
If you disagree and want to further discuss this, I don't mind undoing the change until we've reached an agreement. -- Alad (talk) 11:17, 19 May 2016 (UTC)
I've moved VirtualBox#Virtual disk management back to the main article as it arguably fits as basic content. import/export isn't though, so I've moved it to the Tips page, crosslinking it from the main article. -- Alad (talk) 12:37, 19 May 2016 (UTC)
No follow-up, closing. -- Alad (talk) 19:46, 9 August 2016 (UTC)
OK. No problem. -- wget (talk) 19:50, 9 August 2016 (UTC)