Virtualbox Without Fedora 9 Guest Additions

May 27th, 2008

Using Virtualbox 1.6 you cannot install guest additions support when using a Fedora 9 guest. Yet another consequence of using leading edge distributions that have a release candidate of Xorg. Hopefully the next update of Virtualbox will rectify this situation.

Here’s the output when you try to install the guest additions:

# ./VBoxLinuxAdditions.run
Verifying archive integrity... All good.
Uncompressing VirtualBox 1.6.0 Guest Additions for Linux
installation............................................................
........................................................................
.........................................
VirtualBox 1.6.0 Guest Additions installation
which: no dkms in (/usr/bin:/bin:/bin:/sbin:/usr/sbin)
Building the VirtualBox Guest Additions kernel module...
Building the shared folder support kernel module...
Installing the VirtualBox Guest Additions...

Detected Xorg 1.5 RCx, refusing to install the Xorg modules. We will
provide
updated guest additions once Xorg 1.5.0 was released finally. Please
check
the vbox-users mailing list for further announcements.
Successfully installed the VirtualBox Guest Additions.
You must restart your guest system in order to complete the
installation.

3 responses

  1. CRoKaN comments:

    Hello from Spain:

    I have a problem when I try to install de guest additions in a Fedora 9.

    When I type ./VBoxLinuxAdditions.run, the system don´t detect the header and source files of my kernel, and I have then installed.

    I have installed kernel-devel, gcc, make, dkms, but the software don´t run

    ¿How can I do?

    Thanks

  2. Bob Peers comments:

    Hi Crokan,

    what’s the error message you get when trying to install. Plus what’s the output from running:

    $ rpm -qa|grep kernel

    Bob Peers

  3. CRoKaN comments:

    Hello:

    I install kernel-headers and now the guest additions compile, but when I reboot the system, I don´t have the mouse and desktop (monitor) integration.

    I see that in the startup process the virtualbox kernel module start correctly.

    Thanks

Leave a comment