Guest Additions won't run after Fedora update

[dbhinz]

I installed Fedora that had Linux 3.2.6, installed the Guest Additions and the mouse worked better and the display worked better. I ran the Fedora Software Update to get all of the latest patches and Linux was updated to 3.2.7. The mouse was then jerky and the display doesn't work as well. I figured that the Guest Additions needed to be run again. I selected "Install Guest Additions...", and the dialog about running autorun software is displayed, I selected "Run" and nothing happens. Earlier, the first time I ran Guest Additions, a window was displayed with some info about installing the additions. This time it doesn't seem to be installing the Additions. I have tried restarting Fedora and the Virtual Box.

Any suggestions?

Thanks,
David.

[stefan.becker]

In the tutorial section/linux guests there is a howoto to install the additions manually from command line.

[Perryg]

Sounds like you already have the guest additions mounted. You can either unmount them and then click install guest additions or manually install them from a terminal.

[dbhinz]

How can I determine if they are already installed?

I tried unmounting the guest additions and running again from the menu option, the "autorun" warning pops up, when I click OK, a window pops-up and closes real quick.

I'll try running from the command line, but it would be good to know first if they are already installed.

David.

[Perryg]

That really does not tell me anything. If you open the file manager do you see the Guest Additions in the CD?
If they were already installed you should be able to just compile them against the new kernel.
As su/sudo in a terminal rune the following:

Code: Select all

/etc/init.d/vboxadd setup

[dbhinz]

I ran the command you suggested and it looks like the Guest Additions were rebuilt and installed.

Fedora seems to be behaving better now.

Thanks,
David.

[jmdonovan]

One should always run the vboxadd setup command after the kernel is updated. On RHEL/Fedora/other Red Hat based operating systems, you can run "sudo service vboxadd setup", instead.

Hope this helps,
--jmdonovan