How To: Install VirtualBox on Fedora 10

[nishka]

Thanks!!!!
after installing kernel-PAE-devel everything is working....

[neat]

thanks for the howto.

btw...
would be nice if you can tell us or add a point to use the virtualbox with a bridge interface.

[yottie]

Derek et All,

As a relatively new user of Linux may I first say how refreshing it is to find such good quality help. I have spent time testing various Ditros and settled on Fedora. I have also spent time learning how to make use of WINE. As much as I wish to rid myself of a dependency on MSW for some of my hardware, I will need access to it for the present.

I have, therefore, decided to convert my dual boot option to a virtual one.

I am currently running Fedora 10 with XP on my dektop, and Fedora 11 Beta with XP on my notebook (a Macbook Pro - another story).

Will your set up tutorial work, or do I need to make modifications?

Thanks, in anticipation

Mike

[mps2006]

This worked fine for me for F11 Preview - thanks.

Does anyone have any idea how to get a microphone working in a windows guest in virtualbox? The mic is a simple one (not usb) and works fine in the F10/F11 host, but is not detected in the XP guest. Sound output works fine in the guest.

thanks
M.

[Query]

What's wrong ? Can someone point me to the right direction?

[root@localhost ~]# /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)

[root@localhost ~]# cat /var/log/vbox-install.log
Attempting to install using DKMS
removing old DKMS module vboxdrv version 2.2.2

------------------------------
Deleting module version: 2.2.2
completely from the DKMS tree.
------------------------------
Done.

Creating symlink /var/lib/dkms/vboxdrv/2.2.2/source ->
/usr/src/vboxdrv-2.2.2

DKMS: add Completed.

Error! Your kernel source for kernel 2.6.27.21-170.2.56.fc10.i686 cannot be found at
/lib/modules/2.6.27.21-170.2.56.fc10.i686/build or /lib/modules/2.6.27.21-170.2.56.fc10.i686/source.
You can use the --kernelsourcedir option to tell DKMS where it's located.
Failed to install using DKMS, attempting to install without
Makefile:140: *** Error: unable to find the sources of your current Linux kernel. Specify KERN_DIR=<directory> and run Make again. Stop.

[Dangermouse]

Looks like you havent kernel devel installed for your kernel
yum install kernel-devel-$(uname -r)
if it cant find the devel for your kernel, you may need to update your kernel frst

[Query]

It seems that the kernel source files are in /usr/src/kernels/2.6.27.24-170.2.68.fc10.i686/

How to tell dkms or something to find the source?

Package kernel-devel-2.6.27.24-170.2.68.fc10.i686 already installed and latest version

[root@localhost ~]# /etc/init.d/dkms_autoinstaller start
Running DKMS auto installation service for kernel 2.6.27.21-170.2.56.fc10.i686
/etc/init.d/dkms_autoinstaller: line 143: log_action_end_msg: command not found
[root@localhost ~]# /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)

[root@localhost ~]# ls /usr/src/kernels/2.6.27.24-170.2.68.fc10.i686/
arch/ drivers/ init/ Makefile net/ sound/
block/ firmware/ ipc/ mm/ samples/ System.map
.config fs/ kernel/ Module.markers scripts/ usr/
crypto/ include/ lib/ Module.symvers security/

[stunter]

Ok, I was able to get VBox working pretty well. But I can't manage to set up a shared folder. I want to transfer some files from my Fedora 10 install to Windows in VBox. But I can't for the life of me figure this out. I tried the instructions-from a file manager type:

X:\\vboxsvr\share (where the name of your shared folder is "share"), but it says it can't get there.

Everything else is working pretty well.

Any ideas or can someone point me to some instructions on this?

thanks

Edit:

OK, I've tried using the Map Drives thing in windows, but it says it can't reach vboxsvr. I've tried a number of differnt configs trying to come up with something, but not much luck. I may try to set up samba at some point, though I've never messed with that before so it will take a bit of research. Seems a lot of work just to get from the virtual box to the linux box, but hey, if that what it takes...

But I would like to get the shared setup working as VBox says it should work.

Further investigation seems to indicate that something called Virtual Box Guest Additions for Windows has to be installed in order for access to a shared drive to work. Is this part of the OSE package or something that has to be tracked down elsewhere?

Edit2:

Well, as sometimes happens, I answered my own question. I got the VirtualBox Guest Additions installed and I can now get to the shared folder. It all seems to work pretty well.

I should say that this is version 2.1.4 OSE downloaded and installed from yum, so nothing special.

[mercurio0]

Hello there

I am running Fedora 10 64bit. I followed these steps to install VirtualBox on my machine:

donwloaded the rpm from

http://download.virtualbox.org/virtu...ra9-1.i386.rpm

did yum localinstall --nogpgcheck for that rpm

also ran

yum install make automake autoconf gcc kernel-devel dkms

then

/etc/init.d/vboxdrv setup

with no errors and added myself as a user

and made the SeLinux fix.

then started VB as a normal user and created the first virtual machine for win XP.

When I try to start it, it says:

RTR3Init failed with rc=-1912 (rc=-1912)

It may help to reinstall VirtualBox.

I don't think that re-installing would help. What can I do?

Thanks

mario

[marko]

You did confirm that the "vboxdrv" modules did in fact load?

lsmod | grep vbox

should have two modules showing -- vboxnetflt vboxdrv

2) some computers have the VT-x/AMD-V extensions in their cpu but the
stupid computer manufacturer has a bios that purposefully doesn't turn it on
(most Sony Vaios do this). So the virt flag will show to Vbox (or show when you look in /proc/cpuinfo )
but the Win XP VMs can't run. My Vaio has this problem but I didn't see this 1912 error.

[mercurio0]

Hi Marko

yes the vboxdrv module loaded, this is the lsmod ouput

$ lsmod | grep vbox
vboxnetflt 93804 0
vboxdrv 1691756 1 vboxnetflt

also these are the flags for cat /proc/cpuinfo (if you need the whole list, please tell me)

fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx lm constant_tsc arch_perfmon pebs bts rep_good nopl pni monitor ds_cpl est tm2 ssse3 cx16 xtpr sse4_1 lahf_lm

I don't know if this may help but I am running this kernel

2.6.27.24-170.2.68.fc10.x86_64

the error I get when attempting to launch is "Error in SupR3HardenedMain" (I can read it in the title, while the error reported is RTR3Init failed with rc=-1912 (rc=-1912).

Googling for this error didn't help a lot.

thanks

[mercurio0]

I found out this page:

http://www.virtualbox.org/ticket/4069

there it says that this kind of error is given by a type mismatch between 64bit and 32bit


In this related article it reads:

In summary (for the benefit of anyone else who comes across these issues), if you get the VERR_VM_DRIVER_VERSION_MISMATCH error yet your kernel driver and VirtualBox userland version are the same, but you're running a 64-bit kernel with 32-bit userspace, create a 64-bit chroot environment:

Am I running a 32-bit userspace? And what does it mean ? Does it make sense to create a 64bit chroot environment on my fedora? And how I do it? The instructions were for Debian.

Thank you.

[mercurio0]

mhhh, I am sorry

after reading carefully the download page in virtualbox.org:

Note: The package architecture has to match the Linux kernel architecture, that is, if you are running a 64-bit kernel, install the appropriate AMD64 package (it does not matter if you have an Intel or an AMD CPU). Mixed installations (e.g. Debian/Lenny ships an AMD64 kernel with 32-bit packages) are not supported. To install VirtualBox anyway you need to setup a 64-bit chroot environment.

So sorry. When I took a look at the download list I instinctively disregarded the AMD64 version since I have an Intel Processor. Maybe the guys at VirtualBox.org may write (AMD64 or INTEL64)

[SpuriousQ]

Originally Posted by SendDerek

Updated November 25th, 2008



6.) To Get USB Support:

1 - create a new group called “usb”;
2 - locate file usbfs: in my case is /sys/bus/usb/drivers (I suggest to find the file with a usb device inserted;
3 - modify file /etc/fstab inserting a line containing the right path and the number corresponding the “usb” group :
none /sys/bus/usb/drivers usbfs devgid=503,devmode=664 0 0
4 - command mount -a;
5 - start VB and try…;

Source: Fedora Forums

One quick question: where does the "4.- command mount -a" goes? In the fstab file after the new script in 3.-?

[tuxthejedi]

thank you buddy for the howto

Debian