Talk:VirtualBox

From ArchWiki
Jump to: navigation, search

vdfuse

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)

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
 vboxdrv
 # for guest
 vboxvideo
 vboxguest
 vboxsf

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)
            man:modules-load.d(5)
   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.

The solution for this is to decide if you need guest or host. Probably you care only about host so feel free to remove anything related to vbox*guest:

 sudo pacman --remove --recursive virtualbox-guest-utils

(more on: forum:[SOLVED] ERROR: could not insert 'vboxguest': No such device ) Alexz (talk) 07:11, 26 December 2016 (UTC)

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)

Arch installation media not mounting due to insufficient Base memory (30 seconds error)

I've discovered that trying to install Arch on VirtualBox's VM with only 256MB of RAM assigned, results in the following error:

ERROR: '/dev/disk/by-label/ARCH_XXXXXX' device did not show up after 30 seconds...

I've not found a connection between this specific error and this specific cause anywhere on the internet. I believe that a correlation between insufficient RAM and mount problems isn't obvious and, as a result, this specific situation is difficult to debug. Therefore I think it is worth publishing somewhere that low Base memory may cause 30 seconds error.

My question to more experienced wikipedians and Arch-users: is this article a right place to store this info? If so, in which section?

I'd like to point out that this behaviour is VirtualBox-specific, i.e. 30 seconds error does not occur on a physical machine with 256MB of RAM and physical USB flash media.

-- Raczek (talk) 14:18, 11 May 2017 (UTC)

Installation_guide#Pre-installation says that the minimum amount of RAM is 512 MB. -- Lahwaacz (talk) 17:07, 11 May 2017 (UTC)
That is right. However, it's quite easy to overlook this fact. My idea of Arch was that it's so lightweight that 256MB of RAM would be hardly enough, yet: enough. Debugging this error took me quite some time, and I'd like to spare troubles to anyone that'd also overlook minimum RAM requirements. -- Raczek (talk) 18:00, 18 May 2017 (UTC)
The requirements are listed for a reason... there's plenty more errors we could mention if you skip any of them (e.g., locale issues). Closing -- Alad (talk) 20:05, 18 May 2017 (UTC)