VBox 3.0.0 causes udev to segfault at boot
Posted: 9. Jul 2009, 23:05
After installing VirtualBox version 3.0.0 from rpm, udev segfaults at boot time. After it has segfaulted, boot continues, but many other components which rely on udev also fail (such as X). It is interesting to note that the VBox kernel module actually loads successfully....
The error message looks like this:
I am using Centos 5.3 on a Dell Precision 380, which is a member of our university network. It uses LDAP for user authentication, and a remote file server for home directories. I doubt that our network configuration has anything to do with it, as the machine worked fine before installing VirtualBox. Just pointing out that this system is a little more complicated than a stand alone desktop....
Output from uname -a follows:
Steps to reproduce:
1. install VirtualBox
2. reboot
The rpm i am using is VirtualBox-4.0.0_49315_rhel5-1.i386.rpm. It is possible that something has changed between enough between 5.1 and 5.3 to break the package.... but the kernel module is being compiled at install time, and should have nothing to do with udev anyways....
I am going to attempt installing a previous version of VirtualBox to see if it is an existing issue. Poking around online and through this forum found nothing, so hopefully someone else has experienced this....
Any ideas what may be causing this?
The error message looks like this:
Code: Select all
Starting udev: /sbin/start_udev: line 201: 455 Segmentation fault /sbin/udevd -dOutput from uname -a follows:
Code: Select all
Linux datum 2.6.18-128.el5 #1 SMP Wed Jan 21 10:44:23 EST 2009 i686 i686 i386 GNU/Linux1. install VirtualBox
2. reboot
The rpm i am using is VirtualBox-4.0.0_49315_rhel5-1.i386.rpm. It is possible that something has changed between enough between 5.1 and 5.3 to break the package.... but the kernel module is being compiled at install time, and should have nothing to do with udev anyways....
I am going to attempt installing a previous version of VirtualBox to see if it is an existing issue. Poking around online and through this forum found nothing, so hopefully someone else has experienced this....
Any ideas what may be causing this?