PDA

View Full Version : vbox guest additions after kernel update


chrismurphy
20th April 2012, 01:55 AM
After a yum update that includes a kernel update, Virtual Box Guest Additions no longer appear to work. At least, the 3D acceleration, copy/paste between host and guest, and Shared folders, no longer work. This wasn't the case with F16.

If I re-rerun the script to reinstall (which actually means removing DKMS and non-DKSM modules, and then rebuilding them from source), and reboot, things work again. Is anyone else seeing this? And is it expected? Makes me wonder if it's a bug and then if it's a kernel bug related to DKMS, or if it's a vbox bug related to DKMS, if it I'm just lucky.

JValeck
20th April 2012, 03:30 AM
This is the error I am getting;
Failed to open a session for the virtual machine XP-Pro.

The virtual machine 'XP-Pro' has terminated unexpectedly during startup with exit code 1.

Result Code: NS_ERROR_FAILURE (0x80004005)
Component: Machine
Interface: IMachine {5eaa9319-62fc-4b0a-843c-0cb1940f8a91}

Then it says I should '/etc/init.d/vboxdrv setup', which fails!

-Val

marco765
20th April 2012, 03:50 AM

noticed this dkms bug today https://bugzilla.redhat.com/show_bug.cgi?id=790521

maybe related?

JValeck
20th April 2012, 04:31 AM
This is what happened when ran vboxdrv setup

[r2d2@localhost ~]$ su
Password:
[root@localhost r2d2]# /etc/init.d/vboxdrv setup
Stopping VirtualBox kernel modules [ OK ]
Uninstalling old VirtualBox DKMS kernel modules [ OK ]
Trying to register the VirtualBox kernel modules using DKMSError! Bad return status for module build on kernel: 2.6.42.12-1.fc15.x86_64 (x86_64)
Consult /var/lib/dkms/vboxhost/4.1.6/build/make.log for more information.
[FAILED]
(Failed, trying without DKMS)
Recompiling VirtualBox kernel modules [FAILED]
(Look at /var/log/vbox-install.log to find out what went wrong)
[root@localhost r2d2]#

I am not knowlegeable enough to understand the log file. If someone wants it I will try to post it.


-Val

JValeck
20th April 2012, 04:44 AM
Just figured out how to attach the log file. Hope this works.

-Val

chrismurphy
20th April 2012, 05:58 AM
2.6.42.12-1.fc15.x86_64 (x86_64)

a.) F17 beta is at 3.3.2-1 so I don't see how this kernel is relevant to the convo.

b.) I'm not having any problems running the guest addition install script, it builds just fine. The problem is that the additions stop working after a kernel update, whereas with F16 my recollection is that guest additions continued to function.

pedromadeira
20th April 2012, 11:39 AM
I'm on an yum updated F17 using VirtualBox VirtualBox-4.1-4.1.12_77245_fedora16-1.x86_64 and having no problems here.

It can't use DKMS after a kernel update but compiles well even with this new kernel 3.3.2-1.fc17.x86_64.

JValeck
20th April 2012, 09:41 PM
I found a link that may correct my problem with vbox and F15.

http://blog.andreas-haerter.com/2011/11/19/virtualbox-4.1.6-fedora-15-kernel-2.6.41.1-compilation-error-vboxpci-linux.o

-Val

chrismurphy
29th April 2012, 08:30 PM
Appears to be a known issue.
http://lists.fedoraproject.org/pipermail/test/2012-April/107316.html

fpmurphy
30th April 2012, 04:37 AM
It has always been the case that you generally need to rebuild VirtualBox guest additions whenever the kernal is rev'ed.

chrismurphy
30th April 2012, 04:52 AM
Has not ever been the case for me during the entire F16 life cycle. I've only had to rebuild when guest additions themselves change versions (because vbox has changed versions).

Mister B
30th April 2012, 09:31 AM
I've been having the same issue on F17 and IIRC I had it on F16 as well.

Dutchy
30th April 2012, 10:21 AM
Reinstalled those plenty of times after kernel updates in my F16 guest.

JValeck
1st May 2012, 03:51 AM
I reciently was pointed to this link:

https://bugzilla.redhat.com/show_bug.cgi?id=815103

-Val

solo2101
1st May 2012, 04:01 AM
I saved this (http://download.virtualbox.org/virtualbox/rpm/fedora/virtualbox.repo) file in the /etc/yum.repos.d/ folder... that way everytime I do a "#yum update" I also get the VirtualBox update...
not that it has to do with the issue...but...