Opened 9 years ago
Closed 7 years ago
#14278 closed defect (fixed)
VirtualBox 5.0 101573 Crash on RHEL6.4 in libQtCoreVBox.so.4
Reported by: | blentz | Owned by: | |
---|---|---|---|
Component: | GUI | Version: | VirtualBox 5.0.0 |
Keywords: | Cc: | ||
Guest type: | all | Host type: | Linux |
Description
Host: RHEL 6.4 x86_64 Problem: I upgraded from VirtualBox 4.3 to 5.0. Afterward, I couldn't even so much as start the GUI interface let alone attempt to boot any VMs.
Each attempt to run the VirtualBox management GUI was met with:
[blentz@d-blentz-kno-0 ~]$ VirtualBox Segmentation fault
So it's back to 4.3 I go.
I am left with entries in dmesg. If you want the core, I can re-upgrade, fix my ulimit and see if I can get a core file for you.
VirtualBox[7761]: segfault at 0 ip 00007f4765c193ff sp 00007fff06ff8230 error 4 in libQtCoreVBox.so.4[7f4765b88000+377000] VirtualBox[7774]: segfault at 0 ip 00007ff63e7393ff sp 00007fff273822f0 error 4 in libQtCoreVBox.so.4[7ff63e6a8000+377000]
I searched and I couldn't find anyone else with this problem in either the bug tracker or the forum.
The only thing weird about my machine is that I have 3xATI Radeon HD 6450 Dual-link DVI running 6 monitors. I am using the proprietary ATI drivers in order to get it working.
Otherwise, I've got a fairly vanilla host.
Change History (9)
comment:1 by , 9 years ago
comment:2 by , 9 years ago
Ticket #14315 is most likely different because this ticket shows segfaults in libQtCoreVBox.
comment:4 by , 9 years ago
Replying to frank:
It seems no, I'm getting segfault with this trace:
#0 0xb4e8ee75 in ?? () from /opt/VirtualBox/libQtCoreVBox.so.4 #1 0xb4e8b357 in QThread::currentThread() () from /opt/VirtualBox/libQtCoreVBox.so.4 #2 0xb4fbb9e6 in QCoreApplicationPrivate::QCoreApplicationPrivate(int&, char**, unsigned int) () from /opt/VirtualBox/libQtCoreVBox.so.4 #3 0xb4461154 in QApplicationPrivate::QApplicationPrivate(int&, char**, QApplication::Type, int) () from /opt/VirtualBox/libQtGuiVBox.so.4 #4 0xb4468150 in QApplication::QApplication(int&, char**, int) () from /opt/VirtualBox/libQtGuiVBox.so.4 #5 0xb57f147b in TrustedMain () from /opt/VirtualBox/VirtualBox.so #6 0x0804a4a0 in ?? () #7 0x08048e24 in ?? () #8 0xb7516db6 in __libc_start_main () from /lib/libc.so.6 #9 0x08048ca1 in ?? ()
(not on RHEL)
comment:5 by , 9 years ago
Is there any update on this issue? I have implemented a virtual device (.so) based on 5.0.6, but I need to run on RHEL. If not fix for this is found, I will need to port it back to an older version of VBox which I really hope to avoid.
comment:7 by , 9 years ago
Another user reported that upgrading the host fixes the issues for him, see #12923. Would that work for you as well.
comment:8 by , 8 years ago
I still have never been able to run the VirtualBox 5.0.x GUI on Red Hat 6.5, though 4.3.32 does work. I have so far avoided it by just using Ubuntu, but I really need to migrate to a Red Hat machine now, so this is becoming a serious problem for me.
bash-4.1$ VirtualBox Segmentation fault bash-4.1$ VBoxManage -v 5.0.20r106931
Here is what I get from dmesg:
VirtualBox[118165]: segfault at 0 ip 00007ff22aa6d3ff sp 00007fffc35eed00 error 4 in libQtCoreVBox.so.4[7ff22a9dc000+377000]
What can I do to help sort this out?
Here are the libraries being loaded:
bash-4.1$ ldd /usr/lib/virtualbox/VirtualBox.so linux-vdso.so.1 => (0x00007fff37907000) libXinerama.so.1 => /usr/lib64/libXinerama.so.1 (0x00007ff471d34000) libGL.so.1 => /usr/lib64/libGL.so.1 (0x00007ff471ad4000) libdl.so.2 => /lib64/libdl.so.2 (0x00007ff4718d0000) VBoxKeyboard.so => /usr/lib/virtualbox/VBoxKeyboard.so (0x00007ff4716bf000) VBoxRT.so => /usr/lib/virtualbox/VBoxRT.so (0x00007ff471280000) libXcursor.so.1 => /usr/lib64/libXcursor.so.1 (0x00007ff471076000) libXext.so.6 => /usr/lib64/libXext.so.6 (0x00007ff470e63000) libX11.so.6 => /usr/lib64/libX11.so.6 (0x00007ff470b25000) VBoxXPCOM.so => /usr/lib/virtualbox/VBoxXPCOM.so (0x00007ff470814000) libQtCoreVBox.so.4 => /usr/lib/virtualbox/libQtCoreVBox.so.4 (0x00007ff47028b000) libQtGuiVBox.so.4 => /usr/lib/virtualbox/libQtGuiVBox.so.4 (0x00007ff46f541000) libQtOpenGLVBox.so.4 => /usr/lib/virtualbox/libQtOpenGLVBox.so.4 (0x00007ff46f236000) libstdc++.so.6 => /usr/lib64/libstdc++.so.6 (0x00007ff46ef30000) libm.so.6 => /lib64/libm.so.6 (0x00007ff46ecab000) libgcc_s.so.1 => /lib64/libgcc_s.so.1 (0x00007ff46ea95000) libc.so.6 => /lib64/libc.so.6 (0x00007ff46e701000) libglapi.so.0 => /usr/lib64/libglapi.so.0 (0x00007ff46e4db000) libXdamage.so.1 => /usr/lib64/libXdamage.so.1 (0x00007ff46e2d9000) libXfixes.so.3 => /usr/lib64/libXfixes.so.3 (0x00007ff46e0d3000) libX11-xcb.so.1 => /usr/lib64/libX11-xcb.so.1 (0x00007ff46ded1000) libxcb-glx.so.0 => /usr/lib64/libxcb-glx.so.0 (0x00007ff46dcbb000) libxcb-dri2.so.0 => /usr/lib64/libxcb-dri2.so.0 (0x00007ff46dab7000) libxcb.so.1 => /usr/lib64/libxcb.so.1 (0x00007ff46d898000) libXxf86vm.so.1 => /usr/lib64/libXxf86vm.so.1 (0x00007ff46d693000) libdrm.so.2 => /usr/lib64/libdrm.so.2 (0x00007ff46d488000) libpthread.so.0 => /lib64/libpthread.so.0 (0x00007ff46d26a000) libselinux.so.1 => /lib64/libselinux.so.1 (0x00007ff46d04b000) /lib64/ld-linux-x86-64.so.2 (0x0000003f62600000) libcrypt.so.1 => /lib64/libcrypt.so.1 (0x00007ff46ce14000) libz.so.1 => /lib64/libz.so.1 (0x00007ff46cbfd000) librt.so.1 => /lib64/librt.so.1 (0x00007ff46c9f5000) libxml2.so.2 => /usr/lib64/libxml2.so.2 (0x00007ff46c6a3000) libcurl.so.4 => /usr/lib64/libcurl.so.4 (0x00007ff46c44e000) libssl.so.10 => /usr/lib64/libssl.so.10 (0x00007ff46c1e3000) libcrypto.so.10 => /usr/lib64/libcrypto.so.10 (0x00007ff46be04000) libXrender.so.1 => /usr/lib64/libXrender.so.1 (0x00007ff46bbf9000) libfontconfig.so.1 => /usr/lib64/libfontconfig.so.1 (0x00007ff46b9c3000) libgthread-2.0.so.0 => /lib64/libgthread-2.0.so.0 (0x00007ff46b7bf000) libglib-2.0.so.0 => /lib64/libglib-2.0.so.0 (0x00007ff46b4b9000) libfreetype.so.6 => /usr/lib64/libfreetype.so.6 (0x00007ff46b21c000) libSM.so.6 => /usr/lib64/libSM.so.6 (0x00007ff46b014000) libICE.so.6 => /usr/lib64/libICE.so.6 (0x00007ff46adf7000) libXau.so.6 => /usr/lib64/libXau.so.6 (0x00007ff46abf4000) libfreebl3.so => /lib64/libfreebl3.so (0x00007ff46a97c000) libidn.so.11 => /lib64/libidn.so.11 (0x00007ff46a74a000) libldap-2.4.so.2 => /lib64/libldap-2.4.so.2 (0x00007ff46a4fd000) libgssapi_krb5.so.2 => /lib64/libgssapi_krb5.so.2 (0x00007ff46a2b8000) libkrb5.so.3 => /lib64/libkrb5.so.3 (0x00007ff469fd2000) libk5crypto.so.3 => /lib64/libk5crypto.so.3 (0x00007ff469da6000) libcom_err.so.2 => /lib64/libcom_err.so.2 (0x00007ff469ba1000) libssl3.so => /usr/lib64/libssl3.so (0x00007ff469964000) libsmime3.so => /usr/lib64/libsmime3.so (0x00007ff469738000) libnss3.so => /usr/lib64/libnss3.so (0x00007ff4693f9000) libnssutil3.so => /usr/lib64/libnssutil3.so (0x00007ff4691cd000) libplds4.so => /lib64/libplds4.so (0x00007ff468fc9000) libplc4.so => /lib64/libplc4.so (0x00007ff468dc3000) libnspr4.so => /lib64/libnspr4.so (0x00007ff468b86000) libssh2.so.1 => /usr/lib64/libssh2.so.1 (0x00007ff46895e000) libexpat.so.1 => /lib64/libexpat.so.1 (0x00007ff468735000) libuuid.so.1 => /lib64/libuuid.so.1 (0x00007ff468531000) liblber-2.4.so.2 => /lib64/liblber-2.4.so.2 (0x00007ff468321000) libresolv.so.2 => /lib64/libresolv.so.2 (0x00007ff468107000) libsasl2.so.2 => /usr/lib64/libsasl2.so.2 (0x00007ff467eed000) libkrb5support.so.0 => /lib64/libkrb5support.so.0 (0x00007ff467ce1000) libkeyutils.so.1 => /lib64/libkeyutils.so.1 (0x00007ff467ade000) bash-4.1$
comment:9 by , 7 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
Please reopen if still relevant with VBox 5.1.22 (which uses Qt5).
Just FYI, I opened ticket #14315 for the same issue on CentOS 5.11. (CentOS is a clone of RHEL.) My /var/log/messages file did not contain anything after the "error 4" part of the segfault.
I note yours includes "in libQtCoreVBox.so.4" in the segfault output. In my ticket, I noted that I do not meet the required minimal QT version per the user guide. (<https://www.virtualbox.org/manual/ch02.html#install-linux-host>). Since you're on RHEL 6.4, then you are probably using qt-4.6.2... so you don't meet the minimum of 4.8, either.
Maybe I was wrong in my ticket to state that this probably isn't the cause of my problem. Could it be the cause of yours, too?