yum locks up vbox in fedora 14 guest (winxp host)

[rramos]

I'm a newbee with a shiny new vbox installation on my laptop running win XP. In trying to install the vbox linux additions I ran into a failure while installing the guest additions for linux.

My steps were:

• 1)install dkms (all good)
  2)mount media with the vbox linux additions
  3)cd /media/VBOXADDITIONS_4.0.4_70112
  4)sh ./VBoxLinuxAdditions.run

Then while building the VB Guest Additions kernel modules it fails and complains that the headers for the current kernel weren't found.

In digging around for a solution, I ended up running: yum groupinstall 'Development Tools' and it always locks up the VM so that I have to reset it or power it down. I tried deleting RPM lock files, rebuilding the RPM database and cleaning yum but the same thing always happens. I never did see any RPM lock files but I had to look for them after restarting the VM. I ran all of these commands after running su.

Can anyone offer a solution?

[vbox4me2]

Did you have a look at the VBox linux tutorials yet?

[LenPayne]

it fails and complains that the headers for the current kernel weren't found.

Try installing the headers for the current kernel.

As per http://fedoraunity.org/Members/realz/VB_Guest_Addition

Code: Select all

yum install kernel-headers kernel-devel gcc

What this does is that it installs the kernel headers, the kernel development package and gcc, the GNU C Compiler. These are needed in order to compile kernel modules, which is what you're actually trying to do.

The VirtualBox Guest Additions are a group of kernel modules (drivers) that interface between the guest system (your Fedora system) and the host system (your XP system.)

If you ran a Windows guest, this process would be equivalent to installing new mouse and display drivers. The problem is that in Linux, you need to build them from scratch, and thus need these heavy-duty pre-reqs that don't come in the native Fedora install.