hi,
I just tried to install virtual box by downloading the RPM from their website running it with yast. It said install succesful but I checked the install log and this is the result that I got. The program will not start. I want to run opensuse as my host and install Windows XP to run on top of it for my wife. I can provide any information just ask if it helps.
My software is
System
Atom
2GB of ram
ION
Linux 2.6.34.7-0.4-desktop x86_64
openSUSE 11.3 (x86_64)
4.5.2 (KDE 4.5.2) “release 10”
NVIDIA 260.19.12
VirtualBox Version is
VirtualBox-3.2-3.2.10_66523_openSUSE113-1.x86_64.rpm
WARNING: The vboxdrv kernel module is not loaded. Either there is no module
available for the current kernel (2.6.34.7-0.4-desktop) or it failed to
load. Please recompile the kernel module and install it by
sudo /etc/init.d/vboxdrv setup
You will not be able to start VMs until this problem is fixed.
Failed to open the X11 display!
I did try to run sudo /etc/init.d/vboxdrv setup it failed I than ran
vim /var/log/vbox-install.log and this information was in the file
/usr/share/virtualbox/src/vboxhost/vboxdrv/build_in_tmp: line 55: make: command not found
you don’t have to use ‘sudo’ to start VirtualBox. You just have to be member of the vboxusers group.
If you start VirtualBox or any other GUI application with sudo, it will fail because nobody (even root) has access to your X display. So if you wanted to do that, you should first allow others to use your display, which can be done - as user, not root! - with the command: xhost + local:.
But again, it is not needed here.
no I just want to run VirtualBox. I had gone under user group management in yast changed my default group to vboxusers. Here is what I did with your comment. if xhost + office was not a good command to use for my situation how can I change those settings back. the only reason I ask is because I am trying to keep my install as clean as I can, I hate having lose ends and such. After using you command I am getting the same outputs the only reason I tried to sudo was because of the “Permission denied” outputs
office@Office:~> xhost + local
xhost: bad hostname “local”
office@Office:~> xhost + office
office being added to access control list
office@Office:~> VirtualBox
/usr/bin/VirtualBox: line 72: /usr/lib/virtualbox/VirtualBox: Permission denied
/usr/bin/VirtualBox: line 72: exec: /usr/lib/virtualbox/VirtualBox: cannot execute: Permission denied
office@Office:~> sudo VirtualBox
root’s password:
Failed to open the X11 display!
office@Office:~>
This is not xhost + local
but xhost + local:
and nothing else!
I understand that you just want to run VirtualBox, but in order to do that with this version (the Oracle version), you have to compile the kernel module first, i.e. follow the steps I described in my previous post.
Again: one does not start VirtualBox as root, but as a regular user. Also note what please_try_again wrote about ‘xhost + local’:
But again, it is not needed here.
Are you sure you are a member of the group ‘vboxusers’? Please show the output of the command
groups
[also called as regular user!] and do not forget you have to compile the respective VBox kernel module first.
semi-OT: Guys (please_try_again & other members of this forum), please note that ‘sudo’ is not a proper replacement for ‘su -’ to become root. Read the manual of ‘sudo’ to find out why. The only system I know where ‘sudo’ makes sense per default is Ubuntu and its derivates.
Once more: do not use ‘sudo’ to start root processes. Become root with ‘su -’.
Again #2: you have to be a member of the group ‘vboxusers’. Check that with the command ‘groups’ (as user, not as root). If you are not in ‘vboxusers’, start YaST, go to “Security and users” / “User and Group Management”, mark your user, then ‘Edit’, click the tab ‘details’ and check the group ‘vboxusers’, then click ‘ok’. After that, open a terminal, become root (su -) and command ‘/etc/init.d/vboxdrv setup’ (not ‘service xyz’, that is not a valid command).
Again#3: you have to install the mentioned Kernel development packages.
If you don’t see ‘vboxusers’ as part of the ouput of ‘groups’, become root and add yourself (your loging name) to the group vboxusers:
su -l
usermod -A vboxusers mich04
replace ‘mich04’ with your user name on your system
Yes it is a valid command. But that’s right, it’s not in the default user path (/sbin/service). I’ll try to remember that before advising to use sudo. (i promise )
@mich04, OK, use “su -l” before typing such commands and you shouldn’t get “command not found” errors anymore … unless the program you’re trying to run is indeed not installed.
su -l
zypper in -t pattern devel_basis
zypper in kernel-devel kernel-desktop-devel kernel-source kernel-syms
service vboxdrv setup
service vboxdrv setup and /etc/init.d/vboxdrv setup do the same… although the second one is more likely to work because by using that command, you’re calling the script directly.
Well I finally got it to work except I am can only run it while I am root
office@Office:~> VirtualBox
/usr/bin/VirtualBox: line 72: /usr/lib/virtualbox/VirtualBox: Permission denied
/usr/bin/VirtualBox: line 72: exec: /usr/lib/virtualbox/VirtualBox: cannot execute: Permission denied
office@Office:~> su -l
Password:
Office:~ # VirtualBox
so I checked my groups here is what I got (double checked root groups just in case)
Office:~ # groups
root
Office:~ # exit
logout
office@Office:~> groups
users video
here is the command I tried earlier to add that group before I tried the other steps
office@Office:~> su -l
Password:
Office:~ # usermod -A vboxusers office
usermod: `vboxusers’ is primary group name.
That is what I had originally tried at the beginning of this process. I had also tried to change the default group settings my login in yast says I am part of the following groups
video,vboxusers. I did just try again to unselect and reselect the groups just to see if I could shake things up. I have also tried to restart my computer to see if I re-logging in would help
I just got done running the commands you told me to here is the out-put
Office:~ # SuSEconfig
Starting SuSEconfig, the SuSE Configuration Tool…
Running in full featured mode.
Reading /etc/sysconfig and updating the system…
Executing /sbin/conf.d/SuSEconfig.desktop-file-utils…
Error in file “/usr/share/applications/kde4/kfontview.desktop”: “fonts/package” is an invalid MIME type (“fonts” is an unregistered media type)
Executing /sbin/conf.d/SuSEconfig.fonts…
Creating fonts.{scale,dir} files …
/etc/fonts/suse-font-dirs.conf unchanged
/etc/fonts/suse-hinting.conf unchanged
/etc/fonts/suse-bitmaps.conf unchanged
Creating cache files for fontconfig …
Creating 32bit cache files for fontconfig …
generating java font setup
Warning: cannot find a sans serif Japanese font. Japanese in Java might not work.
Warning: cannot find a serif Japanese font. Japanese in Java might not work.
Warning: cannot find a sans serif simplified Chinese font. Simplified Chinese in Java might not work.
Warning: cannot find a serif simplified Chinese font. Simplified Chinese in Java might not work.
Warning: cannot find a sans serif traditional Chinese font. Traditional Chinese in Java might not work.
Warning: cannot find a serif traditional Chinese font. Traditional Chinese in Java might not work.
Warning: cannot find a sans serif Korean font. Korean in Java might not work.
Warning: cannot find a serif Korean font. Korean in Java might not work.
writing /usr/lib64/jvm/jre/lib/fontconfig.SuSE.properties
Executing /sbin/conf.d/SuSEconfig.glib2…
Executing /sbin/conf.d/SuSEconfig.groff…
Executing /sbin/conf.d/SuSEconfig.gtk2…
Executing /sbin/conf.d/SuSEconfig.ispell…
Executing /sbin/conf.d/SuSEconfig.permissions…
Executing /sbin/conf.d/SuSEconfig.postfix…
Setting up postfix local as MDA…
Setting SPAM protection to “off”…
Executing /sbin/conf.d/SuSEconfig.words…
Finished.
Office:~ # zypper ref
Repository ‘KDE45’ is up to date.
Repository ‘KDE Extra’ is up to date.
Repository ‘Mozilla’ is up to date.
Repository ‘Nvidia’ is up to date.
Repository ‘OpenOffice’ is up to date.
Repository ‘Packman’ is up to date.
Repository ‘Updates for openSUSE 11.3 11.3-1.82’ is up to date.
Repository ‘VLC’ is up to date.
Repository ‘VirtualBox’ is up to date.
Repository ‘openSUSE-11.3 11.3-1.82’ is up to date.
Repository ‘openSUSE-11.3-Non-Oss’ is up to date.
All repositories have been refreshed.
Office:~ # zypper up
Loading repository data…
Reading installed packages…
The following package updates will NOT be installed:
gstreamer-0_10-fluendo-mp3 gstreamer-0_10-plugin-gnomevfs kdeartwork4-screensaver
The following packages are going to be upgraded:
MozillaFirefox akregator kaddressbook kdepim4 kdepim4-runtime kdepim4-wizards kmail knotes kontact korganizer libkdepim4 marble
mozilla-js192 mozilla-xulrunner192 mozilla-xulrunner192-gnome python-kde4 python-qt4 python-sip
That’s true. I forgot to mention that if you ran VirtualBox as root, it switched the ownership of some files that normal users won’t be able to access afterwards.
I don’t know were you put your virtual machines. If for example, they were in /srv/vbox (but they are not ! It’s just an example), you could issue these commands as root to regain ownership of the virtual machines and log files/directories (Don’t forget to replace ‘/srv/vbox’ and ‘mich04’ is this example:
)