VirtualBox

Ticket #16959 (closed defect: fixed)

Opened 4 months ago

Last modified 28 hours ago

fatal error since 5.26: instruction 0x3f526d32 uses memory that can not be read

Reported by: gggeek Owned by: pentagonik
Priority: major Component: other
Version: VirtualBox 5.1.26 Keywords:
Cc: Guest type: Linux
Host type: Windows

Description

Host: win 8.1 64 bit; guest: Debian 8

The VM in question used to work until yesterday, with VBox up to 5.24.

Today I updated to 5.26 and at VM boot I get the error as per the attached image. On the same host, another Debian 8 VM works fine.

Attachments

vbox_bug.jpg Download (143.2 KB) - added by gggeek 4 months ago.
vagrant-devbox-test_default_1469703895183_25836-2017-07-29-22-00-39.zip Download (17.3 KB) - added by gggeek 4 months ago.
VBox.log Download (123.7 KB) - added by lfaatsnat 3 months ago.
VBox.log sound problem on test build

Change History

Changed 4 months ago by gggeek

comment:1 Changed 4 months ago by atrn

Although I don't have screen shots I hit this with a Centos 6.9 guest (hosted on Win7). The VM worked with 5.1.24. Upgraded to 5.1.26 and the VM fails during guest boot/startup (address offset 0x18 is the same, I'm assuming its some NULL deference). I downgraded to 5.1.24 and haven't had time to repeat the test but can do so if more data is desired.

comment:2 Changed 4 months ago by frank

I would like to have an application dump for the crashed VM. If you can provide one (could you upload it to a server?), please contact me via private email at frank _dot_ mehnert _at_ oracle _dot_ com.

comment:3 Changed 4 months ago by gggeek

PS: tried to start the same vm today, and it started without a hitch...

comment:4 Changed 4 months ago by pentagonik

Please give the just uploaded 5.1 test build 117314 a try, which can be found here: https://www.virtualbox.org/wiki/Testbuilds

comment:5 Changed 4 months ago by atrn

I'm unable to provide memory dumps (sensitive work). Some further details:

  • 32-bit Centos 6.9 guest
  • 64-bit Win7 host

VM works fine in 5.1.24. In 5.1.26 the VM fails at startup. Disabling audio (ICH AC97 via DirectSound) makes the VM startup. With 5.1.27 test build 117314 the VM starts with audio enabled.

comment:6 Changed 3 months ago by frank

Thank you. So 5.1.27 test builds > 117314 should definitely fix these problems and everybody experiencing these crashes with 5.1.26 please let us know if these test builds do NOT fix your crashes!

comment:7 Changed 3 months ago by lfaatsnat

Having the same problem with 5.1.26 on a Windows 7 host and Windows XP guest with a different memory location, but otherwise the same message. Works fine with 5.1.24 and earlier. Changing the host audio driver to the null driver, but otherwise leaving sound enabled boots the VM (with no sound). The test build 5.1.27 117332 boots with the host audio driver set to Windows DirectSound, but sound doesn't work properly, the audio is choppy, or sometimes buzzes after a sound until the next sound input, then stops. Otherwise the VM works correctly.

comment:8 Changed 3 months ago by pentagonik

@lfaatsnat Can you please provide a VBox.log of the XP guest running?

Changed 3 months ago by lfaatsnat

VBox.log sound problem on test build

comment:9 Changed 2 months ago by pentagonik

Does the problem still persist in the latest 5.1.28 version?

comment:10 Changed 2 months ago by pentagonik

  • Owner set to pentagonik
  • Status changed from new to assigned

comment:11 Changed 28 hours ago by pentagonik

Should be fixed with 5.1.28. Please re-open if necessary.

comment:12 Changed 28 hours ago by pentagonik

  • Status changed from assigned to closed
  • Resolution set to fixed
Note: See TracTickets for help on using tickets.

www.oracle.com
ContactPrivacy policyTerms of Use