- 1 vdfuse
- 2 NS_ERROR_FAILURE (0x80004005)
- 3 Binding to a physical drive
- 4 modprobe: ERROR: could not insert 'vboxguest': No such device
- 5 Automounting Shared Folders also requires VBoxService to be enabled
- 6 Mount at boot - A better way?
- 7 Solving smbus module load failure
- 8 Guest modules reload
- 9 Granting user rw access to all disks?
- 10 Suggestions for improvements on the installation guide
- 11 Automount should suggest adding user to group vboxsf
- 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)
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.xmlhas 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: Starting Load Kernel Modules... May 20 09:58:59 t64 systemd-modules-load: Failed to insert 'vboxguest': No such device May 20 09:58:59 t64 systemd-modules-load: Failed to insert 'vboxsf': No such device May 20 09:58:59 t64 systemd: systemd-modules-load.service: main process exited, code=exited, status=1/FAILURE May 20 09:58:59 t64 systemd: Failed to start Load Kernel Modules. May 20 09:58:59 t64 systemd: Unit systemd-modules-load.service entered failed state. May 20 09:58:59 t64 systemd: systemd-modules-load.service failed.
The solution for this is to decide if you need
host. Probably you care only about
host so feel free to remove anything related to
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)
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  I solved this by doing:
echo 'blacklist i2c_piix4' > /etc/modprobe.d/modprobe.conf
Guest modules reload
I was about to revert  because comes already recompiled like , 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.
Suggestions for improvements on the installation guide
I have had problems troubleshooting the instalation of VMs after following this page. I am not an expert with VirtualBox so there are several concepts that are shown here without further explanation that I don't understand and that I don't even know if are optional or necessary steps.
I'll post these doubts here so maybe someone could add some explanations for newbies.
1. The Wiki starts explaining how to install host modules and guest modules but does not explain what they are or for what they are used for.
2. It is not clear which steps are necessary to have a working VM running, so I have to guess and that is confusing.
Also, some less important info that would be helpful (maybe a link to an appropriate doc would suffice):
1. What are "VirtualBox kernel modules" and why are they necessary (a link would be great)
2. Why would someone use a custom kernel and how can I be sure I am not using one?
And I think that's the most important stuff.
I should highlight that the most important point for me would be to make explicit which parts of the installation process are optional and when should I follow them. Since when something goes wrong I do not know if I missed some important step or if I did some step I shouldn't have.
Sadly I do not have the knowledge to write this myself =/.
Automount should suggest adding user to group vboxsf
Users do not need to be in group vboxsf to access manually mounted vbox shares, in my experience. But they definitely do need to be in vboxsf to access auto-mounted shares, this should be corrected and made more explicit as following this myself led to confusion, thanks. —This unsigned comment is by Jgr (talk) 10:37, 22 March 2018. Please sign your posts with ~~~~!
Each time I do an ArchLinux UEFI installation on Virtualbox, I have always the same problem: the bootloader display a back screen. Yes, I have the Enable EFI (special OSes only) and all the stuff. So for example on my install that use rEFInd as a bootloader I get a blackscreen until on OS is booted. But this is not a problem with rEFInd or my config, because even when I boot on the ArchLinux live CD I get a blackscreen (while on the CD bootloader that is GRUB currently) and then when the 2sec automatic entry pickup is done (and so quitting the booloader) I begin to see systemd stuff and all is displayed correctly.
So there is only 1) ArchLinux 2) UEFI 3) bootloader 4) on Virtualbox that displays a black screen. Using another distro, using BIOS legacy mode, after the bootloaader, or booting on a physical machine, all that works.
This is coming from the shitty UEFI integration of Virtualbox, clearly. Changing (enabling/disabling) 3D acceleration won't work, putting more video memory either, etc. and of course not weird logs.
BUT I FINNALY found the answer for this mysterious blackscreen: in the VM settings, go to the Display tab and change the graphics controller, the only one that does not display a black screen for me is VBoxVGA. The default VMSVGA doesn't work and neither VBoxSVGA.
- The issue you're experiencing is FS#61184. If you want to document the problem and workaround, crate a new subsection in VirtualBox#Troubleshooting and link to that section from a note in VirtualBox#Installation in EFI mode.
- If you're interested, you can also document FS#61307 in VirtualBox#Automounting and FS#61183 in VirtualBox#Install the Guest Additions. -- nl6720 (talk) 07:59, 15 January 2019 (UTC)
- it's done: VirtualBox#Black_screen_for_Arch_Linux_guest_in_UEFI and VirtualBox#Installation_in_EFI_mode. Noraj (talk) 11:08, 16 January 2019 (UTC)