- 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?
Windows: "The specified path does not exist"
- 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.
Windows: "The specified path does not exist"
Alad, can you explain why you removed info about how to workaround this bug (with this change)? What do you mean under "broken workarounds"? It is working solution and I think it could be very usefull to somebody, including me in the future. -- Ashark (talk) 12:46, 29 June 2017 (UTC)
- In case it will be back in article, I want to add that according to this page, turning slider to "never notify" actually did not disabled UAC from Windows 8. -- Ashark (talk) 18:51, 29 June 2017 (UTC)
- UAC is by no means perfect, but considering privileged users are the default on Windows installations, plain disabling it means you're catapulting yourself back to "admin-only" Windows XP security levels. Here it was suggested without the implications and only for some convenience with virtualization software.
- Users willing to take that route (which is mentioned in the linked bug report anyway) can type "How to disable UAC" in google. -- Alad (talk) 12:13, 2 July 2017 (UTC)
- This article is about VirtualBox, not about best practies of using Windows os. In virtualbox I dont care about which user is default. I just want to use software unavailable in Linux. This "hack" is usefull for me.
- People at least should know that such way (Completely disabling UAC via registry in win8 and win10) exists. Otherwise, they may not even know where to dig. We could leave at least mentioning about this.
- I do not understand why do you delete some usefull information just because you think it is "catapulting yourself back". Lets then remove all info about dual booting... because somebody say it will catapult you back. It is wrong way I think.
- Also I want to note, that this info was in the article. I just decided to reformat it a bit and add a bit more. After that you decided to remove it.
- Let's be more rational. And maybe somebody else will endorse me. -- Ashark (talk) 13:57, 2 July 2017 (UTC)
- Hello, Lahwaacz. In that bug report page there is no info about win8 and win10 changes. I got it from another resource. I mean starting from win8 uac is not turned off by just sliding notifications to never notify. Do you think it would be better if I register in virtualbox.org forum and say it there? -- Ashark (talk) 14:46, 2 July 2017 (UTC)
- I placed a link in my second note of this discussion. From here:
- Changes in Windows 8 UAC. The most significant change to UAC in Windows 8 is that setting UAC to “Never Notify” in User Account Control Settings doesn’t actually turn off UAC completely, as it did in Windows 7.
- Setting UAC to never notify in win10 did not worked for me, but "completely disabling" registry hack worked for me. This is why I edited the article. I have found a solution and thought it may be usefull for somebody using win8 or win10 in virtualbox.
- We could warn users that it could cause problems with ie browser and security, but use it if you know what you are doing.
- -- Ashark (talk) 16:00, 2 July 2017 (UTC)
- The analogy with dual boot is completely nonsensical. The dual boot article lists some common cases in which modifications are required on the Windows side to allow for coexistence with an Arch installation. Here you want to disable one of the most basic security mechanisms in Windows because an error message in a virtual machine annoys you or because you don't want to copy a file.
- On a related note you add "workarounds" for "crackling sound" by disabling driver verification and suggesting users to use arbitrary installers from the internet. Considering that section doesn't even have a meaningful bug report, I've also removed it. 
- If "you know what you are doing" and felt the information you were looking for was hard to find, post it on your user page. It has no place in this article in any case. -- Alad (talk) 17:40, 2 July 2017 (UTC)
- Ok, I have created a comment in virtualbox.org forum. Now I think people could find this information if they want. Should we also remove about non-working solution with VBOXSRV trusted site?
- Now about crackling sound. You can reenable driver verification after installation. I think that setup.exe was made in winxp epoch (in 2009), so it has no microsoft signature. Temporaly disabling verification is a solution.
- As you can see, installer is from official realtek site, not from arbitrary internet page. So please be sure to know, before blaming.
- Nope, there is a forum thread and a bug report about this.
- -- Ashark (talk) 20:46, 2 July 2017 (UTC)
- Good job ignoring the one workaround that's actually sensible, i.e. UNC paths. Added it to the article with .
- As to that report, you didn't include it in your edit. Don't bother adding it back until you find some better solution than installing random 8-year old drivers (and according to said report, it's already fixed anyway ). -- Alad (talk) 21:12, 2 July 2017 (UTC)