Opened 12 years ago
Closed 8 years ago
#11740 closed defect (obsolete)
Windows guest crashing on Linux host
Reported by: | Das | Owned by: | |
---|---|---|---|
Component: | 3D support | Version: | VirtualBox 4.2.12 |
Keywords: | Cc: | ||
Guest type: | Windows | Host type: | Linux |
Description
Hi,
I am running a Windows (Windows 7 x64 SP1 Enterprise) guest on Linux (Ubuntu 13.04 x64) host. I am using version 4.2.12, guest OS has additions (same version) installed. Inside the guest OS I am trying to use the browser (Google Chrome) to navigate some pages, which leads to a crash. The crash is quite consistent, I was able to successfully reproduce it with the same sequence of steps several times. Each crash is generating a message in /var/log/syslog, here are 6 examples:
Apr 21 03:02:53 Das-PC kernel: [41113.852975] ShCrOpenGL[10014]: segfault at 21 ip 00007f82354d58ff sp 00007f823581cb20 error 4 in VBoxSharedCrOpenGL.so[7f82354b9000+d4000] Apr 21 16:24:28 Das-PC kernel: [ 2983.602303] ShCrOpenGL[12745]: segfault at 0 ip 00000000400e698a sp 00007f3e1c5ea868 error 4 in gltVq6O0 (deleted)[400e5000+2000] Apr 21 16:43:59 Das-PC kernel: [ 4152.658161] ShCrOpenGL[13894]: segfault at 21 ip 00007f3fd5dd2f52 sp 00007f3fd610eb00 error 4 in VBoxSharedCrOpenGL.so[7f3fd5dab000+d4000] Apr 21 16:54:36 Das-PC kernel: [ 4788.479250] ShCrOpenGL[14250]: segfault at 21 ip 00007fa6be3d2f52 sp 00007fa6be70eb00 error 4 in VBoxSharedCrOpenGL.so[7fa6be3ab000+d4000] Apr 21 17:00:55 Das-PC kernel: [ 5167.020859] ShCrOpenGL[15385]: segfault at 0 ip 000000004117898a sp 00007feca6b83868 error 4 in glrD3RdA (deleted)[41177000+2000] Apr 21 17:09:50 Das-PC kernel: [ 5700.842882] ShCrOpenGL[15746]: segfault at 0 ip 000000004020298a sp 00007fc902d61868 error 4 in glbn8LQM (deleted)[40201000+2000]
I've attached the log file from the last (17:09:50) crash. The core dump is available on the FTP server, it's an encrypted archive, please let me know where I can send the password.
Attachments (1)
Change History (9)
by , 12 years ago
comment:1 by , 11 years ago
Component: | other → 3D support |
---|
comment:2 by , 11 years ago
We were unable to reproduce the crash you observe with the latest VBox trunk sources, so it's likely that your issue could be fixed on trunk already.
I can give a trunk test build for you to check whether your issue is fixed for you.
Please give it a try and let me know how it goes.
Note that you'd also need to update Guest Additions with those supplied with this test build.
!!! Note that the trunk is under heavy development now, so this build can NOT be used in production environment,
but ONLY for testing purposes. !!!
Linux 64 Host:
http://www.virtualbox.org/download/testcase/VirtualBox-4.2.51-85953-Linux_amd64.run
Extension pack:
http://www.virtualbox.org/download/testcase/Oracle_VM_VirtualBox_Extension_Pack-4.2.51-85953.vbox-extpack
comment:3 by , 11 years ago
Also, in case the issue with the test build is still there, please attach a new VM log file from that test build. Thanks!
comment:4 by , 11 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
No response, closing. Please give a try to VBox 4.3 and 4.3 additions, and re-open if needed.
follow-up: 7 comment:5 by , 11 years ago
I am trying to run Google Chrome v33.01750.154 in VirtualBox 4.3.10 with a Windows 7 32bit host and the browser flickers when you move the mouse over the browser window. If you run the browser with the virtual machine in full screen mode the screen turns black and then Virtual Box crashes.
Host System: Windows 7 64 bit Virtual Machine: Windows 7 32 bit
comment:6 by , 11 years ago
Resolution: | fixed |
---|---|
Status: | closed → reopened |
comment:7 by , 11 years ago
Replying to cmccarron: I think you have two separate issues here: the black screen, and the crash. We are working on solving the black screen issue currently. Once we are done, I will post you a test build with the fix, and we'll see if the crash goes away for you as well. Stay tuned ;)
comment:8 by , 8 years ago
Resolution: | → obsolete |
---|---|
Status: | reopened → closed |
Please reopen if still relevant with a recent VirtualBox release.
log file