This is a tutorial on how to get VirtualBox up and running on Fedora 8. If you havn’t yet, add yourself as a “sudoer” by visiting the tutorial this page. Also, this tutorial is for the 32-Bit version of VirtualBox, so you’ll have to customize a little more to get the 64-bit version running (as pointed out in the comments). Everything in the “code” sections should be copy/pasted/typed into the terminal. Right, let’s get to it:
MOVED!
You have arrived here using an outdated link or bookmark. If you would like to view the most recent content or comments on this post, please use the following link to be directed to the proper address.
How To: Install VirtualBox on Fedora 8 (Werewolf) on DerekHildreth.com/Blog
Thank You.
[...] http://sendderek.wordpress.com/2007/11/18/how-to-install-virtualbox-on-fedora-8-werewolf/ [...]
not working here:
[root@localhost ~]# sudo /etc/init.d/vboxdrv setup
Stopping VirtualBox kernel module [ OK ]
Recompiling VirtualBox kernel module [FAILED]
(Look at /var/log/vbox-install.log to find out what went wrong) </cite)
and the log:
Makefile:68: *** Error: unable to find the sources of your current Linux kernel. Specify KERN_DIR= and run Make again.. Stop.
how do i specify my kernel folder???
Sorry to hear that… everything I outlined worked for myself. I recognize the first error though. You get that if you don’t install the “kernel-devel” package, but if you’re replying to my tutorial, I understand that you’ve probably already tried to do that. Have you tried a restart? I don’t think it’s necessary, but it’s worth a shot.
It looks like another gentleman was having an issue as well on the virtualbox.org forums. Here’s the link:
http://forums.virtualbox.org/viewtopic.php?t=2236&highlight=&sid=696b7049cdafb9c5dbe7b6f18ccbf6a6
I hope that helps!
-Derek
PS. One person said this about the issue:
“I installed kernel and kernel source again, then it is working.”
Thanks for the tutorial! Took me only a few minutes to get this up and running
Only problem I ran into was that you linked to the 32bit version. Virtualbox displays an error message about a different driver version, so that can be kind of confusing.
Simple fix here:
http://www.virtualbox.org/ticket/825
You’re welcome! I’m glad it worked for you.
Thanks for posting a comment and letting myself and readers know about an issue AND giving a fix for it!
I have updated the tutorial accordingly.
Thanks for the tutorial… I did run into a problem on my Fedora 8 install, I was wondering if you’ve run across this problem anywhere else; Basically my sound doesn’t work in the virtual machine. I’m using pulseaudio with the alsa plugin for pulseaudio and i’ve tried just switching back to alsa but that didn’t work either. on boot of the VM (windows in this case) i hear the startup sound for a brief (less then a sec) moment, same for closing down windows. i have the audio enabled in virtualbox and configured to alsa.. anyways i know your not a support forum or anything, just wondering if you’ve seen this before. otherwise i have a lot of digging around to do
… Might want to ignore that last post… Apparently i should always wait another 30 min after i think i’ve run out of things to test before posting for help, because theres always one last thing to try and that normally fixes it
… well it’s not fixed, but the OSS drivers work fine w/ virtualbox, so maybe my fedora installation’s ALSA driver is messed up.
I am getting the same error as been in his first post
Thank you for this post!
Helped me get my v-box working
You only updated one reference to 1.5.4…
wget http://www.virtualbox.org/download/1.5.4/VirtualBox-1.5.4_27034_fedora8-1.i586.rpm && sudo rpm -ivh VirtualBox-1.5.2_25433_fedora7-1.i586.rpm
should be:
wget http://www.virtualbox.org/download/1.5.4/VirtualBox-1.5.4_27034_fedora8-1.i586.rpm&& sudo rpm -ivh VirtualBox-1.5.4_27034_fedora8-1.i586.rpm
thanks again!
Thanks for pointing that out… I totally forgot about updating that part of the command! It has been fixed.
I also added steps to increase the size of an already created virtual disk.
Enjoy!
not working here:
[root@localhost ~]# sudo /etc/init.d/vboxdrv setup
Stopping VirtualBox kernel module [ OK ]
Recompiling VirtualBox kernel module [FAILED]
(Look at /var/log/vbox-install.log to find out what went wrong) </cite)
and the log:
Makefile:68: *** Error: unable to find the sources of your current Linux kernel. Specify KERN_DIR= and run Make again.. Stop.
how do i specify my kernel folder???
=== please check version boot kernel and kernel-devel====
It looks like *been* had that same problem.
I found two other people having the same problem, and both of their solutions was to uninstall and then re-install the kernel and kernel-devel packages. Take a look for yourself in any one of these links:
http://www.howtoforge.com/forums/showthread.php?t=12660
http://forums.virtualbox.org/viewtopic.php?t=2236&highlight=&sid=696b7049cdafb9c5dbe7b6f18ccbf6a6
http://forums.virtualbox.org/viewtopic.php?t=1505&highlight=makefile
http://forums.virtualbox.org/viewtopic.php?t=1493
I hope this helps.
hi there, followed the howto, but running into a problem, i can run Virtualbox without issues on root, but with my user account i get this :
[Gertjan@localhost ~]$ VirtualBox
Cannot create/open directory ‘/tmp/.vbox-Gertjan-ipc/ipcd’
Abnormal termination.
Gertjan is added in the “vboxusers” Group
what is going wrong here?
What would happen if you tried to chmod that particular file?
sudo -c 'chmod 777 /tmp/.vbox-Gertjan-ipc/ipcd'
777 will completely open the file up to all access, so you may want to use it for testing and then change the permissions to 644 and see what happens.
no effect, same error
Try to open up permissions on the /tmp folder and see what happens. This is what my permissions look like for that tmp folder:
http://img.photobucket.com/albums/v203/send_derek/Screenshot-tmpProperties.png
Also, I noticed that your username has a capital letter in it. I didn’t think usernames were allowed to have capitals. Be sure you’ve added yourself to the vboxusers group with the correct spelling and without capitalization. Maybe that will help?
permissions on /tmp folder are the same as yours, trying to make a new user and c if that helps in lower caps since fedora does look for lower caps difference : [root@localhost ~]# usermod -G vboxusers -a gertjan
usermod: user gertjan does not exist
I’m honestly not sure what to tell you. You may want to check on the VirtualBox forums and see if they can help.
http://forums.virtualbox.org/
found the problem, apparently it makes a difference if the login has a capital in it or not, i created another login with exactly the same info and permission, only in lower caps. all works like a charm now.
guess being an old geezer starting a sentence or a single word with a capital doesn’t pay off in the end. LOL
Btw, thanks for the How-to and help m8.
Hey, you’re welcome! I’m glad it turned out for you!
Great Guide!
On a fresh Fedora 8 install I had to install:
libSDL-1.2.so.0
Another option for users, who don’t want to add themselves as sudoers, is the su -c “command”
Example:
su -c “yum install libSDL-1.2.so.0″
And just type in the “root” password.
i have problem i installed it and work and installed centos as virtual but centos can’t ping fedora and vise verca
fedora ip is 10.0.0.122
centos 10.0.0.123
From 10.0.0.122 icmp_seq=2 Destination Host Unreachable
Sorry to hear that.
All I can really suggest is that you double-check your settings in the VirtualBox settings manager. If you still don’t find any fault, report to the VirtualBox forums for help. I just don’t know much about the subject when dealing with VirtualBox and networking between host and guest. Sorry.
i solved it thanks for ur replay i made bridge and used host interface
what happens if i forgot to set up sudo. and install it as root?
@dubb:
Installing it using “sudo” is the same thing as installing it using “su -”. You have nothing to worry about!
thanks for the tutorial!
however, the virtualbox kernel module was not recompiling…
Then I upgraded my kernel to the latest version, performed your instructions again, and it worked perfectly.
cheers!
Great how to. Unfortunately, I learnt these steps the hard way, but you list everything I figured out myself. Well done.
The only issue I’ve had that few tutorials cover are the networking problems. For some reason, it’s a common problem for the guest OS to not have any internet connection. My current setup’s not perfect, but I finally figured out how to enable the internet connection by giving my guest OS the same MAC address as the host.
Another issue I’ve had is VB does a poor job of capturing certain key presses. For instance, pressing the Windows key won’t activate the start menu in a Windows guest OS.
Thanx!
this tutorial solved my problem!
Andrei