[SOLVED] 2.2.4 / i386 on Centos 5.3: "Segmentation Fault"

[hoover]

Hi folks,

this is my first post in this forum, but I couldn't find anything on this problem so I hope someone will be able to help me here.

I installed version 2.2.4 on CentOS 5.3 (i386, all patches applied), setting the KERN_DIR variable to point to the kernel sources and apparently vboxdrv starts up fine from /etc/init.d.

However when I try to run the "VirtualBox" executable, it segfaults. I've tried both running it as root and as a regular user who is a member of the vboxusers group, but the error persists.

Here are the final messages from strace:

Code: Select all

statfs("/usr/share/doc/VirtualBox-2.2.4_47978_rhel5", {f_type="EXT2_SUPER_MAGIC", f_bsize=4096, f_blocks=29409988, f_bfree=29017760, f_bavail=27523816, f_files=14942208, f_ffree=14892605, f_fsid={0, 0}, f_namelen=255, f_frsize=4096}) = 0
getdents(19, /* 6 entries */, 4096)     = 136
stat64("/usr/share/doc/VirtualBox-2.2.4_47978_rhel5/License-7.html", {st_mode=S_IFREG|0644, st_size=15324, ...}) = 0
stat64("/usr/share/doc/VirtualBox-2.2.4_47978_rhel5/License-7.html", {st_mode=S_IFREG|0644, st_size=15324, ...}) = 0
getdents(19, /* 0 entries */, 4096)     = 0
close(19)                               = 0
write(16, "8", 1)                       = 1
futex(0x99c2668, FUTEX_WAKE, 1)         = 1
gettimeofday({1245155700, 239410}, NULL) = 0
gettimeofday({1245155700, 239504}, NULL) = 0
gettimeofday({1245155700, 239577}, NULL) = 0
clock_gettime(CLOCK_REALTIME, {1245155700, 239644917}) = 0
futex(0x99c73f8, FUTEX_WAIT, 89, {29, 999932083}) = 0
futex(0x99c296c, FUTEX_WAKE, 1)         = 0
gettimeofday({1245155700, 240789}, NULL) = 0
gettimeofday({1245155700, 241061}, NULL) = 0
gettimeofday({1245155700, 241148}, NULL) = 0
clock_gettime(CLOCK_REALTIME, {1245155700, 241221810}) = 0
futex(0x99c2b38, FUTEX_WAIT, 115, {384815, 597926190}) = 0
futex(0x99c2b74, FUTEX_WAKE, 1)         = 0
stat64("/root/.config/Trolltech.conf", 0x99f7cbc) = -1 ENOENT (No such file or directory)
lstat64("/root/.config/Trolltech.conf", 0xbfd5e4c0) = -1 ENOENT (No such file or directory)
stat64("/root/.config/Trolltech.conf", 0xbfd5e330) = -1 ENOENT (No such file or directory)
stat64("/root/.config/Trolltech.conf", 0x99f7cbc) = -1 ENOENT (No such file or directory)
stat64("/etc/xdg/Trolltech.conf", 0xbfd5e330) = -1 ENOENT (No such file or directory)
stat64("/etc/xdg/Trolltech.conf", 0x99f7cbc) = -1 ENOENT (No such file or directory)
stat64("/usr/lib/virtualbox/iconengines/.", 0x99f8104) = -1 ENOENT (No such file or directory)
lstat64("/usr/lib/virtualbox/iconengines/.", 0xbfd5e5e0) = -1 ENOENT (No such file or directory)
stat64("/root/.config/Trolltech.conf", 0x99f827c) = -1 ENOENT (No such file or directory)
lstat64("/root/.config/Trolltech.conf", 0xbfd5e510) = -1 ENOENT (No such file or directory)
stat64("/root/.config/Trolltech.conf", 0xbfd5e380) = -1 ENOENT (No such file or directory)
stat64("/root/.config/Trolltech.conf", 0x99f827c) = -1 ENOENT (No such file or directory)
stat64("/etc/xdg/Trolltech.conf", 0xbfd5e380) = -1 ENOENT (No such file or directory)
stat64("/etc/xdg/Trolltech.conf", 0x99f827c) = -1 ENOENT (No such file or directory)
stat64("/usr/lib/virtualbox/iconengines/.", 0x99f8674) = -1 ENOENT (No such file or directory)
lstat64("/usr/lib/virtualbox/iconengines/.", 0xbfd5e630) = -1 ENOENT (No such file or directory)
--- SIGSEGV (Segmentation fault) @ 0 (0) ---

Thanks in advance for any ideas in this matter & I'll be happy to provide more info if needed.

:edit: SELinux and firewalls are disabled.

All the best,

Uwe

[Perryg]

It looks like you have installed the RHEL version of VirtualBox.
I am not that familiar with CentOS but isn't it more like Ubuntu or Fedora?
Maybe you have installed the wrong version of VirtualBox. Anyway that is where I would start looking.

[hoover]

Thanks for your reply. CentOS claims binary compatibility with RHEL (it's built from the source packages Red Hat thankfully makes available to the community, so I'd guess it's much more similar (in fact, identical) to RHEL than Fedora.

Ubuntu is Debian based which is an entirely different cup of tea

Still, I'll give the fedora packages a try, but I don't harbour much hope as I get the exact same error with the .run file VB that's available.

Reading through the older posts I've seen at least one instance where somebody got VB to run on CentOS 5.3, but I'm really stymied as to where to start looking for the problem.

Cheers,

Uwe

[fixedwheel]

Hi,

setting the KERN_DIR variable to point to the kernel sources

why did you do that, you normally should not need to ...

i dont run Centos/RHEL as host, but the same as for building vbox kernel module applies to installing guest additions ...

[hoover]

I had to set the KERN_DIR variable because the vboxdrv setup told me to

Compilation worked ok after that, so I guess that isn't the problem (for CentOS, I used /usr/src/kernels/2.6.18-128.1.10.el5-i686

after installing the kernel-devel package using yum.

Regards, Uwe

[fixedwheel]

after installing the kernel-devel package using yum.

matching version numbers of the running kernel and kernel-devel? rpm -qa|grep kernel

[hoover]

Hm, looks good as far as I can tell:

uname -a: h5462 2.6.18-128.1.10.el5 #1 SMP Thu May 7 10:39:21 EDT 2009 i686 i686 i386 GNU/Linux

rpm -qa |grep kernel-devel
kernel-devel-2.6.18-128.1.10.el5

All the best, Uwe

[hoover]

Upgraded to VirtualBox 3.0 today, problem remains the same. Any help on this issue?

All the best, Uwe

[jmaltais]

This fixed it for me (basically, install xauth, xfs and fonts including liberation-fonts)

http://www.mail-archive.com/centos@cent ... 20214.html

[hoover]

Hi folks,

thanks for the help in this matter, installing liberation-fonts indeed fixed the problem (although I'm not quite certain because in tne meantime, I've moved up to VB 3.0.6 or thereabouts).

With 3.0.6, I also no longer have to use the KERN_DIR variable as soon as kernel-devel is installed.

all the best & happy vboxing,

Uwe