VirtualBox Additions

I am trying to install the VIrtualBox Additions 4.0.4_70112 with Windows 7 host and an Oracle Linux 5 guest system. When I run the /etc/init.d/vboxadd setup I receive the following error. My current kernel is 2.6.18.238.el5xen. I did a full yum update prior to this.
[root@localhost ~]# /etc/init.d/vboxadd setup
Removing existing VirtualBox DKMS kernel modules/etc/init.d/vboxadd: line 343: uninstall: command not found
[ OK ]
Removing existing VirtualBox non-DKMS kernel modules [ OK ]
Building the VirtualBox Guest Additions kernel modules
The headers for the current running kernel were not found. If the following
module compilation fails then this could be the reason.
The missing package can be probably installed with
yum install kernel-devel-2.6.18-238.el5xen
[FAILED]
Your system does not seem to be set up to build kernel modules.
Look at /var/log/vboxadd-install.log to find out what went wrong.
Once you have corrected it, you can run
/etc/init.d/vboxadd setup
to build them.
Doing non-kernel setup of the Guest Additions [ OK ]

Here is a snap-shot of my grub.conf, what should I change. I am fairly new to Linux. Thanks for your help
# grub.conf generated by anaconda
# Note that you do not have to rerun grub after making changes to this file
# NOTICE: You have a /boot partition. This means that
# all kernel and initrd paths are relative to /boot/, eg.
# root (hd0,0)
# kernel /vmlinuz-version ro root=/dev/VolGroup00/LogVol00
# initrd /initrd-version.img
#boot=/dev/sda
default=0
timeout=5
splashimage=(hd0,0)/grub/splash.xpm.gz
hiddenmenu
title Oracle Linux Server (2.6.18-238.el5xen)
     root (hd0,0)
     kernel /xen.gz-2.6.18-238.el5
     module /vmlinuz-2.6.18-238.el5xen ro root=/dev/VolGroup00/LogVol00 rhgb quiet
     module /initrd-2.6.18-238.el5xen.img
title Oracle Linux Server (2.6.18-238.el5)
     root (hd0,0)
     kernel /vmlinuz-2.6.18-238.el5 ro root=/dev/VolGroup00/LogVol00 rhgb quiet
     initrd /initrd-2.6.18-238.el5.img
title Enterprise Linux (2.6.18-8.el5xen)
     root (hd0,0)
     kernel /xen.gz-2.6.18-8.el5
     module /vmlinuz-2.6.18-8.el5xen ro root=/dev/VolGroup00/LogVol00 rhgb quiet
     module /initrd-2.6.18-8.el5xen.img
title Enterprise Linux-base (2.6.18-8.el5)
     root (hd0,0)
     kernel /vmlinuz-2.6.18-8.el5 ro root=/dev/VolGroup00/LogVol00 rhgb quiet divider=10
     initrd /initrd-2.6.18-8.el5.img

Similar Messages

[SOLVED] VirtualBox Additions Package Missing?

Hi all,
Following the VirtualBox section of the wiki here: https://wiki.archlinux.org/index.php/Vi … nux_guests - it directs me to install the following packages:
pacman -S virtualbox-guest-additions
However, I just get a message saying the package isn't found (I can't find it under "packages" on the arch website either), some googling suggested:
pacman -S virtualbox-archlinux-additions
However, that package is also 'not found'. As far as I know, I have the following repositories enabled:
* Testing
* Core
* Extra
* Community
* Community-Testing
* Testing
The wiki says not to install the default VirtualBox additions from VirtualBox. Any suggestions on where to find the VirtualBox additions package?
Regards,
Ben.
Last edited by BM (2012-09-23 13:33:05)

jdarnold wrote:
Wow, that's a long way to figure out 'virtual' packages, when this works just fine:
$ pacman -Ss virtual
You're wrong, graysky was close, but I prefer to use it with the '-q' switch. Compare the output of
pacman -Ssq | grep virtual
with one from your suggestion.

Module vbox* not found; Virtualbox; additions [RESOLVED]

I'm running arch in virtualbox.
And first, I installed virtualbox-archlinux-additions from repository by pacman and everything worked fine, except a little problem.
So I thought (altough it's not recommended) installing virtualbox guest additions from virtualbox (host).
ERROR:
WARNING: Module vboxguest not found.
WARNING: Module vboxsf not found.
WARNING: Module vboxvideo not found.
I tried pacman -S {linux linux-lts and xorg-*; mesa and virtualbox-archlinux-additions}, then modprobe vboxsf vboxguest vboxvideo, still the Not Found error.
Last edited by lqs (2012-07-27 08:03:18)

It's 1 pm in China
Thanks!Your way works.
ewaller wrote:
It is getting late here, so maybe it is just me... but I cannot figure out what you are trying to do.
Is the Archlinux you are working with in a virtual machine? If so, you want to install virtualbox-archlinux-modules.

[Solved] problem with virtualbox-iso-additions for virtualbox v. 4.2

VirtualBox 4.2 was released recently and one of the features mentioned is support for Mac OSX. However, having installed it (an Arch virtualbox 4.2 host, and an osx guest), I found that I couldn't install guest additions via the devices menu on my osx guest. Whereupon I examined the file corresponding to virtualbox-iso-additions (/usr/lib/virtualbox/additions/VBoxGuestAdditions.iso) and found that in fact there were no scripts or drivers for osx (darwin) like there are for windows and linux. Is it possible that the Arch release of this file has not been updated properly or am I missing anything else?
Update: I downloaded the current iso (VBoxGuestAdditions_4.2.0.iso) from http://download.virtualbox.org/virtualbox/4.2.0/ and found that that too has no files that appear linked to osx or darwin. That rules out an Arch packaging issue and I'll need to pursue things at virtualbox.org itself.
Last edited by kinleyd (2013-07-18 12:03:48)

I think I've figured it out, finally. It seems v. 4.2 introduces virtualbox on a mac osx host. osx guests are apparently not officially supported with guest additions. I had assumed that host support already existed, and that the new stuff in v. 4.2 was for guests.

Errors installing virtualbox guest additions from AUR

After failing to get ose guest additions working in an Arch guest on Ubuntu host by (a) mounting the ISO and (b) installing from pacman, I thought that it would be an idea to use builds from AUR as these would likely to be more customised for Arch guests.
Installing ose-guest-additions-modules (the dependency for ose-guest-additions) worked flawlessly, but whenever I try and makepkg -s for ose-guest-additions I get the following error:
install: cannot stat 'vboxadd-timesync' : no such file or directory
install: cannot stat 'VBoxClient' : no such file or directory
install: cannot stat 'mountvboxsf' : no such file or directory
These directories do exist at /usr/share/virtualbox/additions/ so I am at a loss as to what is causing this to fail.
(It is worth pointing out that I am new to Arch -and relatively new to Linux- & while I am having a lot of fun trying to figure this stuff out, I am aware that I am probably missing something quite obvious...)

bump
Last edited by Mufasaa (2015-06-12 13:04:45)

Cant Find to install VirtualBox-Ose-Additions

Hi All
I have installed virtualbox-ose and virtualbox-ose-additions from packages and configured virtualbox etc ... and it runs just fine. But when i go to configure guest additions, i cant find where its been installed ...
I thought it was supposed to be here /usr/share/virtualbox/additions/VBoxGuestAdditions.iso But its not ...
Any suggestions please ?
Many Thanks

whitetimer wrote:Done that but the iso is still not in /usr/share/virtualbox .......
it doesn't need to be there. just try to load the iso from vbox and you'll see that is working
pacman -Ql virtualbox-additions
Last edited by wonder (2010-12-03 22:43:34)

I can't load VirtualBox OSE additions modules

Hi to everyone:
I have VirtualBox (OSE) installed on my system:
[glsadmin@researchlinux ~]$ pacman -Qs virtualbox
local/virtualbox-modules 3.0.12-1
Kernel modules for VirtualBox
local/virtualbox-ose 3.0.12-1
Powerful x86 virtualization for enterprise as well as home use (Open Source Edition)
local/virtualbox-ose-additions 3.0.12-1
Guest Additions for VirtualBox (Open Source Edition)
local/virtualbox-ose-additions-modules 3.0.12-1
Kernel modules for VirtualBox Guest Additions
I can't load the modules of OSE additions:
[root@researchlinux ~]# modprobe vboxadd
FATAL: Error inserting vboxadd (/lib/modules/2.6.31-ARCH/misc/vboxadd.ko): No such device
[root@researchlinux ~]# modprobe vboxvfs
FATAL: Error inserting vboxvfs (/lib/modules/2.6.31-ARCH/misc/vboxvfs.ko): No such device
[root@researchlinux ~]#
But they're on the system:
[root@researchlinux ~]# pacman -Ql virtualbox-ose-additions-modules
virtualbox-ose-additions-modules /lib/
virtualbox-ose-additions-modules /lib/modules/
virtualbox-ose-additions-modules /lib/modules/2.6.31-ARCH/
virtualbox-ose-additions-modules /lib/modules/2.6.31-ARCH/misc/
virtualbox-ose-additions-modules /lib/modules/2.6.31-ARCH/misc/vboxadd.ko
virtualbox-ose-additions-modules /lib/modules/2.6.31-ARCH/misc/vboxvfs.ko
[root@researchlinux ~]#
Someone else with the same problem ... anyone knows how to fix it?

wonder wrote:
do you have virtualbox-additions installed?
pacman -Qs virtualbox
No, I don't.
[glsadmin@researchlinux ~]$ pacman -Qs virtualbox
local/virtualbox-modules 3.1.0-1
Kernel modules for VirtualBox
local/virtualbox-ose 3.1.0-1
Powerful x86 virtualization for enterprise as well as home use (Open Source Edition)
local/virtualbox-ose-additions 3.1.0-1
Guest Additions for VirtualBox (Open Source Edition)
local/virtualbox-ose-additions-modules 3.1.0-1
Kernel modules for VirtualBox Guest Additions
I remember that program's package (virtualbox-additions) is under PUEL license, but I can't use the package in one enterprise environment; by that reason I thought that the virtualbox-ose-additions package could be useful for my main target: change between the guest system and the host system without to use the CTRL key for to release the mouse pointer.

KDE4 on Arch in VirtualBox not working [SOLVED]

Hi all. I have the latest version of VBox (3.2.12) on my windows installation (I dual-boot Arch and Vista), and I've been using it to toy around with Arch setups.
I decided to try KDE4, yet again (honestly, every time I try it, I get turned off from it within 20 minutes, but I keep coming back to try it. Odd?).
After installing Arch64, xorg, setting up user accounts, etc (standard desktop procedure), I -S'd kdebase. Once it finished installing, I added "exec startkde" to my .xinitrc, and typed "startx."
Consistently, the splash screen appears, loads the first two icons, then freezes upon loading the "world" icon, dumps me back to console. The one notable error was that the vboxmodule was not found. I reinstalled the guest additions to no avail.
At first I thought it was just an error with vbox and the new xorg 1.9, but OpenSUSE's KDE4 works fine (thank God for Arch by the way... I was turned off by SUSE very quickly). I'm going to attempt yet another installation of it, but I reinstalled KDE as kdebase, kde, kde-meta, etc, and none worked. I reinstalled guest additions multiple times, tried as many tweaks as I could find, and nothing seemed to work. The one thing that *did* work was completely impractical: forcing kde to ignore compositing using "openglisunsafe = true" seemed to work, but the desktop was so slow that it was pointless to use.
I ran into this issue about 2 weeks ago, and deleted the Arch vbox since then. I only post this now because I realized that KDE works under SUSE, but not under Arch. I'll try again and dump the xorg logs for someone else to examine. Until then, any thoughts?
Last edited by hwkiller (2010-12-18 03:39:35)

This has me curious why yours suddenly worked?
I have the exact same thing - Virtual box running on win 7 x64 host, Arch 64 bit works fine with gnome, so long as I don't try starting compiz, and KDE doesn't launch unless I change the OpenGLIsUnsafe value.
VirtualBox settings have 3D acceleration set to enabled, with 128 MB of video memory.
The error that x.org throws upon lauching compiz in gnome or KDE with opengl on is the same
from /var/log/Xorg.0.log
http://pastebin.com/ue4A98vQ
VirtualBox additions are direct from the ISO, although I've tried PEUL & OSE from the repo's.
They are working - as resizing the window changes the resolution.
I've looked at https://wiki.archlinux.org/index.php/Vi … as_a_guest
and even edited it because the openGL section for guests was in the wrong place.
Also tried running from gdm or kdm and still no joy
Any differences to what you've tried hwkiller?

Virtualbox(PUEL) 3.1.6 Host-Only Adaptor connectivity problems

Hi there! I'm a new Arch Linux user and i'm LOVING it ... I've hit one problem I can't seem to get Host-Only Adaptor networking working with VirtualBox (PUEL) with any virtual machines e.g. VM's can't communicate to anything Host machine, router etc, I've set static addresses for all my Vitual machines.
(Host machine)
/etc/conf.d/bridges
# Settings for layer-2 bridges
# For each bridge interface declared in INTERFACES (in rc.conf), declare
# a bridge_${IF} variable that contains the real ethernet interfaces that
# should be bridged togeether.
# Then list the bridge interface name in the BRIDGE_INTERFACES array.
# example:
# in /etc/rc.conf:
# eth0="eth0 up"
# eth1="eth1 up"
# br0="br0 192.168.0.2 netmask 255.255.255.0 up"
# INTERFACES=(lo eth0 eth1 br0)
# in /etc/conf.d/bridges
bridge_br0="eth0 vbox0"
BRIDGE_INTERFACES=(br0)
#bridge_br0="eth0 eth1"
#BRIDGE_INTERFACES=(br0)
(Host Machine)
/etc/rc.conf
# /etc/rc.conf - Main Configuration for Arch Linux
# LOCALIZATION
# LOCALE: available languages can be listed with the 'locale -a' command
# HARDWARECLOCK: set to "UTC" or "localtime", any other value will result
# in the hardware clock being left untouched (useful for virtualization)
# TIMEZONE: timezones are found in /usr/share/zoneinfo
# KEYMAP: keymaps are found in /usr/share/kbd/keymaps
# CONSOLEFONT: found in /usr/share/kbd/consolefonts (only needed for non-US)
# CONSOLEMAP: found in /usr/share/kbd/consoletrans
# USECOLOR: use ANSI color sequences in startup messages
LOCALE="en_US.UTF-8"
HARDWARECLOCK="UTC"
TIMEZONE="Australia/Melbourne"
KEYMAP="us"
CONSOLEFONT=
CONSOLEMAP=
USECOLOR="yes"
# HARDWARE
# MOD_AUTOLOAD: Allow autoloading of modules at boot and when needed
# MOD_BLACKLIST: Prevent udev from loading these modules
# MODULES: Modules to load at boot-up. Prefix with a ! to blacklist.
# NOTE: Use of 'MOD_BLACKLIST' is deprecated. Please use ! in the MODULES array.
MOD_AUTOLOAD="yes"
#MOD_BLACKLIST=() #deprecated
MODULES=(!snd-pcm-oss bridge vboxdrv vboxnetflt vboxnetadp)
# Scan for LVM volume groups at startup, required if you use LVM
USELVM="no"
# NETWORKING
# HOSTNAME: Hostname of machine. Should also be put in /etc/hosts
HOSTNAME="myhost"
# Use 'ifconfig -a' or 'ls /sys/class/net/' to see all available interfaces.
# Interfaces to start at boot-up (in this order)
# Declare each interface then list in INTERFACES
# - prefix an entry in INTERFACES with a ! to disable it
# - no hyphens in your interface names - Bash doesn't like it
# DHCP: Set your interface to "dhcp" (eth0="dhcp")
# Wireless: See network profiles below
eth0="eth0 up"
br0="dhcp" # Maybe you have some static configuration; change to fit
INTERFACES=(eth0 br0)
#Static IP example
#eth0="eth0 192.168.1.200 netmask 255.255.255.0 broadcast 192.168.1.255"
# eth0="dhcp"
#INTERFACES=(eth0)
gateway="default gw 192.168.1.254"
# Routes to start at boot-up (in this order)
# Declare each route then list in ROUTES
# - prefix an entry in ROUTES with a ! to disable it
gateway="default gw 192.168.1.254"
ROUTES=(gateway)
# Enable these network profiles at boot-up. These are only useful
# if you happen to need multiple network configurations (ie, laptop users)
# - set to 'menu' to present a menu during boot-up (dialog package required)
# - prefix an entry with a ! to disable it
# Network profiles are found in /etc/network.d
# This now requires the netcfg package
#NETWORKS=(main)
# DAEMONS
# Daemons to start at boot-up (in this order)
# - prefix a daemon with a ! to disable it
# - prefix a daemon with a @ to start it up in the background
DAEMONS=(syslog-ng !network hal networkmanager openntpd dnsmasq netfs crond sshd alsa dbus gdm lp parport parport_pc cups)
Guest Machine Slitaz
/etc/network.conf
Static ip = 192.168.1.180
I need to use VirtualBox on an almost daily basis for work... I would highly appreciate you help so thanks in advance!

Hi, I'm not sure I fully understand your issue.
Are you telling VirtualBox don't allow you to add a Host-Only Adaptor via main menu File -> Net -> Add button? I once hit this problem and was lost some days because I come from the *buntu-land and all this configuration was nearly automatic there. If this is your problem you should first download and install the rigth AUR package, tha one working for me is virtualbox_bin now at latest version 3.1.8-1, you will need to install also virtualbox-additions. After you installed VirtualBox follow the instructions provided by packagers:
IMPORTANT NOTES:
- Run "vbox_build_module" as root every time your kernel is upgraded, to
compile the module for the new kernel version.
- Add your user to the vboxusers group:
gpasswd -a USERNAME vboxusers
- Add "vboxdrv" to the MODULES array in your "/etc/rc.conf"
- Add "vboxnetflt" to MODULES if you want Host Interface networking.
- Add "vboxnetadp" to MODULES if you want Host-Only networking.
- If USB does not work for you out-of-the-box, add the following line
to "/etc/fstab":
none /proc/bus/usb usbfs auto,busgid=108,busmode=0775,devgid=108,devmode=0664 0 0
Once you do that you'll be smoooooth 8-D

Can't start virtualbox windows 7 32 bit image anymore please h[SOLVED]

Hello guys,
Just recently, I upgraded my system by executing "sudo pacman -Syu". It upgraded my kernel and kernel header files and mesa devu etc... including virtualbox-ose 3.2.10-3.
Someoutputs that could be useful:
(Please note I picked up only installed ones from the output)
pacman -Ss virtualbox
community/virtualbox-additions 3.2.10-1 [installed]
Guest additions for VirtualBox
community/virtualbox-ose 3.2.10-3 [installed]
Powerful x86 virtualization for enterprise as well as home use (Open Source Edition)
pacman -Ss kernel26
core/kernel26 2.6.36.1-3 (base) [installed]
The Linux Kernel and modules
core/kernel26-headers 2.6.36.1-3 [installed]
Header files and scripts for building modules for kernel26
core/linux-firmware 20101108-1 [installed]
Firmware files for Linux
extra/nvidia 260.19.21-2 [installed]
NVIDIA drivers for kernel26.
I also recompiled the new virtualbox modules by doing:
sudo /etc/rc.d/vboxdrv setup
Password:
:: Unloading VirtualBox kernel modules [DONE]
:: Removing old VirtualBox netadp kernel module [DONE]
:: Removing old VirtualBox netflt kernel module [DONE]
:: Removing old VirtualBox kernel module [DONE]
:: Recompiling VirtualBox kernel modules [DONE]
:: Reloading VirtualBox kernel modules [DONE]
On my archlinux (64-bit) system, I installed windows 7 (32-bit) using virtualbox-ose. It was working fine before I did the upgrade. Now, whenever I try to start the windows 7 (32-bit), it starts the windows 7 until the windows logo comes (just before the login mask of windows 7 comes), my computer restarts itself without giving any error or something. My pc just restarts itself. I think this is only related to virtualbox. When I do not try to start virtualbox, arch linux itself is working fine so far. Only when I try to start the windows 7, my pc gets restarted. Have you guys had any problem of this kind? First, I will wait for your responses. The options that I could think of right at the moment are:
1. Downgrade the kernel back (I do not know how to and do not see it as a good choice)
2. Downgrade the virtualbox-ose only (I also do not know how to do that.)
3. Uninstall the virtualbox-ose and reinstall it again without removing my windows 7 OS (32-bit) (I hope I can continue using it)
4. Delete the existing windows 7 OS and try to install freshly new Windows 7 OS again
Guys, please help me. I really need to use windows 7 sometimes. I would be really grateful if some of you guys can help me.
And again thanks for reading my long post.
Thanks in advance.
Last edited by Archie_Enthusiasm (2010-12-08 19:25:30)

Hi guys, thanks for your responses.
What is this vboxnetflt for? Which modules are the essential modules for virtualbox? What I mean is: do those nice features like mouse point integration, full screen supportment etc... rely on vboxnetflt and vboxnetadp?
What I have in my configuration file is:
MOD_AUTOLOAD="yes"
#MOD_BLACKLIST=() #deprecated
MODULES=(vboxdrv vboxnetflt vboxnetadp)
I think vboxnetadp is used for networkiing. and vboxnetflt sounds like network filtering stuff. Can someone please confirm me? I think the problem was the sequence of upgrading. Firstly it updated the kernel and then installed the new version of virtualbox. I think if it could install the new version of virtualbox first and then the kernel, it would go without any problem, just my opinion as I said.
Let's keep tracked on this. Maybe someone will find a solution before virtualbox developers :-)

[SOLVED] Virtualbox list usb devices is empty.

I moved from virtualbox_bin(AUR) to virtualbox(community), and remove /proc/bus/usb entry in /etc/fstab, after that the usb doesn't work. I can check 'Enable USB 2.0 (EHCI) Controller' in Virtualbox settings, but can't find any available usb devices.
$ pacman -Qs virtualbox
local/virtualbox 4.1.22-1
Powerful x86 virtualization for enterprise as well as home use
local/virtualbox-additions 4.1.22-1
The official all-in-one VirtualBox Guest Additions ISO/CD image
local/virtualbox-ext-oracle 4.1.22-1
Oracle VM VirtualBox Extension Pack
local/virtualbox-hook 2.1-1
mkinitcpio hook to compile the virtualbox modules
local/virtualbox-modules 4.1.22-1
Kernel modules for VirtualBox
local/virtualbox-source 4.1.22-1
VirtualBox kernel modules source
$ VBoxManage list usbhost
Host USB Devices:
<none>
$ ls /dev/usbbox
ls: cannot access /dev/usbbox: No such file or directory
$ groups
log kvm network video audio optical storage users vboxusers guten input libvirt davfs2 virtftp
$ lsusb
Bus 001 Device 002: ID 0424:2513 Standard Microsystems Corp. 2.0 Hub
Bus 001 Device 003: ID 05ac:8509 Apple, Inc. FaceTime HD Camera
Bus 002 Device 002: ID 0424:2513 Standard Microsystems Corp. 2.0 Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 004: ID 0a5c:4500 Broadcom Corp. BCM2046B1 USB 2.0 Hub (part of BCM2046 Bluetooth)
Bus 001 Device 005: ID 05ac:0252 Apple, Inc. Internal Keyboard/Trackpad (ANSI)
Bus 002 Device 003: ID 05ac:8242 Apple, Inc. IR Receiver [built-in]
Bus 002 Device 004: ID 1a40:0101 Terminus Technology Inc. 4-Port HUB
Bus 001 Device 008: ID 05ac:821a Apple, Inc. Bluetooth Host Controller
Bus 002 Device 005: ID 046d:c05a Logitech, Inc. Optical Mouse M90
Bus 002 Device 008: ID 0951:1624 Kingston Technology DataTraveler G2 4GB Pen Drive
Bus 002 Device 007: ID 413c:2003 Dell Computer Corp. Keyboard
Last edited by GutenYe (2012-09-17 12:38:58)

I am having the same problem and have tried "everything" and still cannot get it to work.
calpoly@arch:~$ cat /etc/group | grep vboxusers
vboxusers:x:108:calpoly,root
calpoly@arch:~$ lsusb
Bus 004 Device 003: ID 045e:0745 Microsoft Corp. Nano Transceiver v1.0 for Bluetooth
Bus 004 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 004 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 006 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 002: ID 05ac:12a0 Apple, Inc. iPhone 4S
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 003: ID 046d:c52f Logitech, Inc. Unifying Receiver
Bus 003 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
calpoly@arch:~$ sudo pacman -Qs virtualbox
local/virtualbox 4.3.6-3
Powerful x86 virtualization for enterprise as well as home use
local/virtualbox-guest-dkms 4.3.6-3
VirtualBox Guest kernel modules sources
local/virtualbox-guest-modules 4.3.6-4
Guest kernel modules for VirtualBox
local/virtualbox-guest-utils 4.3.6-3
VirtualBox Guest userspace utilities
local/virtualbox-host-modules 4.3.6-4
Host kernel modules for VirtualBox
local/virtualbox-host-modules-lts 4.3.6-5
Host kernel modules for VirtualBox
calpoly@arch:~$ sudo VBoxManage controlvm windowSeven usbattach 609c101d-ef6a-401a-ad15-306f3e7bc8ae
VBoxManage: error: The USB device with UUID {00000010-0030-0000-90f9-0560b57f0000} is not currently attached to the host
VBoxManage: error: Details: code NS_ERROR_INVALID_ARG (0x80070057), component USBProxyService, interface IHost, callee nsISupports
VBoxManage: error: --------
VBoxManage: error: Could not load the Host USB Proxy service: VERR_NOT_FOUND
VBoxManage: error: Details: code Unknown Status 0x4005 (0x4005), component Host, interface IHost
VBoxManage: error: Context: "AttachUSBDevice(usbId.raw())" at line 973 of file VBoxManageControlVM.cpp
calpoly@arch:~$ sudo VBoxManage showvminfo windowSeven
Name: windowSeven
Groups: /
Guest OS: Windows 7
UUID: 609c101d-ef6a-401a-ad15-306f3e7bc8ae
Config file: /root/VirtualBox VMs/windowSeven/windowSeven.vbox
Snapshot folder: /root/VirtualBox VMs/windowSeven/Snapshots
Log folder: /root/VirtualBox VMs/windowSeven/Logs
Hardware UUID: 609c101d-ef6a-401a-ad15-306f3e7bc8ae
Memory size: 2048MB
Page Fusion: off
VRAM size: 128MB
CPU exec cap: 100%
HPET: off
Chipset: piix3
Firmware: BIOS
Number of CPUs: 2
PAE: off
Long Mode: off
Synthetic CPU: off
CPUID overrides: None
Boot menu mode: message and menu
Boot Device (1): DVD
Boot Device (2): HardDisk
Boot Device (3): Network
Boot Device (4): Floppy
ACPI: on
IOAPIC: on
Time offset: 0ms
RTC: local time
Hardw. virt.ext: on
Nested Paging: on
Large Pages: off
VT-x VPID: on
VT-x unr. exec.: on
State: powered off (since 2014-02-11T12:16:18.000000000)
Monitor count: 1
3D Acceleration: off
2D Video Acceleration: off
Teleporter Enabled: off
Teleporter Port: 0
Teleporter Address:
Teleporter Password:
Tracing Enabled: off
Allow Tracing to Access VM: off
Tracing Configuration:
Autostart Enabled: off
Autostart Delay: 0
Default Frontend:
Storage Controller Name (0): IDE
Storage Controller Type (0): PIIX4
Storage Controller Instance Number (0): 0
Storage Controller Max Port Count (0): 2
Storage Controller Port Count (0): 2
Storage Controller Bootable (0): on
Storage Controller Name (1): SATA
Storage Controller Type (1): IntelAhci
Storage Controller Instance Number (1): 0
Storage Controller Max Port Count (1): 30
Storage Controller Port Count (1): 1
Storage Controller Bootable (1): on
IDE (1, 0): Empty
SATA (0, 0): /media/disk/VirtualBox OS X HDD/windowSeven.vdi (UUID: 5c44157f-350a-467c-a988-b4cfb8635fd5)
NIC 1: MAC: 0800279A3907, Attachment: NAT, Cable connected: on, Trace: off (file: none), Type: 82540EM, Reported speed: 0 Mbps, Boot priority: 0, Promisc Policy: deny, Bandwidth group: none
NIC 1 Settings: MTU: 0, Socket (send: 64, receive: 64), TCP Window (send:64, receive: 64)
NIC 2: disabled
NIC 3: disabled
NIC 4: disabled
NIC 5: disabled
NIC 6: disabled
NIC 7: disabled
NIC 8: disabled
Pointing Device: PS/2 Mouse
Keyboard Device: PS/2 Keyboard
UART 1: disabled
UART 2: disabled
LPT 1: disabled
LPT 2: disabled
Audio: enabled (Driver: ALSA, Controller: HDA)
Clipboard Mode: Bidirectional
Drag'n'drop Mode: Bidirectional
VRDE: disabled
USB: enabled
EHCI: enabled
USB Device Filters:
<none>
Available remote USB devices:
<none>
Currently Attached USB Devices:
<none>
Bandwidth groups: <none>
Shared folders:
Name: 'music', Host path: '/media/disk/music' (machine mapping), writable
VRDE Connection: not active
Clients so far: 0
Video capturing: active
Capture screens: 0
Capture file: /root/VirtualBox VMs/windowSeven/windowSeven.webm
Capture dimensions: 1024x768
Capture rate: 1024 kbps
Capture FPS: 25
Guest:
Configured memory balloon size: 0 MB
calpoly@arch:~$ sudo modprobe vboxdrv
calpoly@arch:~$ sudo modprobe -a vboxguest vboxsf vboxvideo
modprobe: ERROR: could not insert 'vboxguest': No such device
modprobe: ERROR: could not insert 'vboxsf': No such device
calpoly@arch:~$ sudo modprobe vboxnetflt
calpoly@arch:~$ sudo modprobe vboxsf
modprobe: ERROR: could not insert 'vboxsf': No such device
calpoly@arch:~$ sudo VBoxManage list usbhost
Host USB Devices:
<none>
Have rebooted and reinstalled virtualbox multiple times to no avail.
It is important to note that my iPhone used to sync with iTunes on Windows 7 in Virtualbox, but then I removed the USB filter and did some updates and now it no longer works.
I have spent many more hours than I care to admit on this problem, so please, any help is welcome.
Last edited by Kg4XmtUSyxd8B9M7Ex&&KXZGF (2014-02-11 12:33:00)

Virtualbox no longer detects system theme

Hi. I just upgraded all the virtualbox packages. I replaced virtualbox-additions with virtualbox-iso-additions, and virtualbox-modules with virtualbox-host-modules <-- I think those were the replacements. There were two that pacman asked me about and I chose the default answer, which was Y.
I also re-installed the updated virtualbox-ext-oracle from the aur. So, everything still works ok, but the virtualbox manager is not detecting my system theme properly. By properly, I mean that it detects some stuff - for example, the menus and toolbar look right, but the sections with text are giving me white on white. See below,
>>moderator edit: Removed large image. Please read Forum Etiquette: Pasting Pictures and Code. Thanks. --fsckd<<
I used to have the problem that virtualbox wouldn't detect the system theme AT ALL. After reading some threads, I just installed libgnomeui and that fixed the problem, and virtualbox looked just fine up until this recent update.
Anyone know what's going on here?
Last edited by fsckd (2012-09-20 16:43:29)

https://wiki.archlinux.org/index.php/ABS
# pacman -S abs
# abs
$ mkdir -p ~/.builds/virtualbox
$ cp /var/abs/community/virtualbox/* ~/.builds/virtualbox
$ cd ~/.builds/virtualbox
$ makepkg -do
Then have fun poking around in:
"~/.builds/virtualbox/src/VirtualBox-4.2.0/src/VBox/Frontends/VBoxManage/"
"~/.builds/virtualbox/src/VirtualBox-4.2.0/src/VBox/Frontends/VirtualBox/"
When you're done, build and tell pacman to install it with:
$ makepkg -si
Edit: Then again, you should probably ask on their forum or IRC channel (#vbox on freenode).
Last edited by DSpider (2012-09-22 13:33:19)

Build the main Guest Additions module Failed

Hi all,
I am not very sure if I am in the correct forum here. My problem is I cannot install the VirtualBox Guest Additions 4.2.12_84980 on my Oracle Linux 5 update 6_x86_64 bits system. I followed the instructions in a tutorial :
cd /etc/yum.repos.d/
wget http://public-yum.oracle.com/public-yum-el5.repo
yum update
yum install gcc
yum install kernel-uek-devel-2.6.32-300.32.1.el5uek
These steps above all succeeded; but, when I run the installation as below:
cd /media/VBOXADDITIONS_4.2.12_84980/
sh ./VBoxLinuxAdditions.run
I got the error message:
Build the main Guest Additions module Failed
(Look at /var/log/vboxadd-install.log to find out what went wrong).
I have little experience in installing VirtualBox Additions on Oracle Linux. Can anybody pls give me some suggestions? Thanks a lot in advance.

user571093 wrote:
Hi all,
I am not very sure if I am in the correct forum here.No. This forum is "Oracle Database - General Questions". Your question has nothing to do with Oracle Database.
Your problem is in the cracks between VBox and Oracle Linux. I'd suggest you mark this thread answered, then repost in the Oracle Linux Forum (Oracle Linux
My problem is I cannot install the VirtualBox Guest Additions 4.2.12_84980 on my Oracle Linux 5 update 6_x86_64 bits system. I followed the instructions in a tutorial :
cd /etc/yum.repos.d/
wget http://public-yum.oracle.com/public-yum-el5.repo
yum update
yum install gcc
yum install kernel-uek-devel-2.6.32-300.32.1.el5uek
These steps above all succeeded; but, when I run the installation as below:
cd /media/VBOXADDITIONS_4.2.12_84980/
sh ./VBoxLinuxAdditions.run
I got the error message:
Build the main Guest Additions module Failed
(Look at /var/log/vboxadd-install.log to find out what went wrong).Did you look at that file?
>
I have little experience in installing VirtualBox Additions on Oracle Linux. Can anybody pls give me some suggestions? Thanks a lot in advance.When you post in the Oracle Linux forum, be sure to show them the results of this command:
uname -aThat will be key to which kernel header package to install.

[SOLVED]Nomenclature in virtualbox packages

╔═[20:17]═[inxs @ wolfdale]
╚═══===═══[~]>> pacs virtualbox
community/libvirt 0.8.8-1
API for controlling virtualization engines (openvz,kvm,qemu,virtualbox,xen,etc)
community/virtualbox 4.0.4-2
Powerful x86 virtualization for enterprise as well as home use
community/virtualbox-additions 4.0.4-1
CD image containing guest additions for VirtualBox
community/virtualbox-guest-additions 4.0.4-2
VirtualBox user-space tools for Linux guests
community/virtualbox-guest-modules 4.0.4-2
VirtualBox kernel modules for Linux guests
community/virtualbox-sdk 4.0.4-2
VirtualBox Software Developer Kit (SDK)
why is cd image containing guest additions for Virtualbox named as virtualbox-additions and user space tools for Linux guests named virtualbox-guest-additions. Shouldn't it be the other way round?

I recall Ionut (wonder, ioni etc.) once said (to me) that he will do the renaming as he updates the packages from time to time. He probably forgot or is shying away from the matter since it's (1) just renaming and therefore (2) too much of a hassle for the complicated packaging steps it requires.

Virtualbox - Error

Failed to start the virtual machine WindowsXP
The VirtualBox support driver which is running is from a different version of VirtualBox. You can correct this by stopping all running instances of VirtualBox and reinstalling the software..
VBox status code: -1912 (VERR_VM_DRIVER_VERSION_MISMATCH).
Result Code:
0x80004005
Component:
Console
Interface:
IConsole {d5a1cbda-f5d7-4824-9afe-d640c94c7dcf}
i try to do what it says. offcourse with backing up all the Virtualbox folder before. i did pacman -R virtualbox-ose virtualbox-modules virtualbox-additions
and then i went to /var/cache/pacman/pkg/ and install the previous installation first 1.5.6-1 and then did the same with the newest one. nothing.
what must i do to get this thing work?
thank you in advanced

Zer0 wrote:
I think the issue was that the vboxdrv module that was loaded in ram was from the previous version. Then when you upgraded Virtualbox and tried to run it.. there was a version mismatch because the old kernel module was still loaded. A reboot would have solved this issue, as it did.
to avoid the restart you could have also done
rmmod vboxdrv
modprobe vboxdrv
ok ty for your time and the info.

VirtualBox Additions

Similar Messages

Maybe you are looking for