Ticket #13945 (new defect)

Opened 5 years ago

Last modified 5 years ago

Yosemite 10.10.2 and Virtualbox 4.3.X Crash System

Reported by: tekmanforce Owned by:
Component: other Version: VirtualBox 4.3.24
Keywords: Cc:
Guest type: Windows Host type: Mac OS X


After migration from 4.2.28 to any version of 4.3.X the Yosemite OS crash with memory fault error. This event is just with this version and Guest Windows 7.


VirtualBoxVM_2015-03-09-104621.wakeups_resource.diag.txt Download (40.9 KB) - added by tekmanforce 5 years ago.
Kernel_2015-06-10-182831_flexs-MacBook-Pro.panic Download (7.1 KB) - added by flex 5 years ago.

Change History

Changed 5 years ago by tekmanforce

comment:1 Changed 5 years ago by frank

This diagnostics is from VBox 4.2.28 so not useful. We don't have problems on Yosemite hosts. Is there any crash information available, any kernel log?

comment:2 Changed 5 years ago by ruslan_zasukhin

Well, I confirm that this issue exists in VirtualBox 4.3.26 Story is next.

  • on MacMini I did have long time 10.8
  • then I did upgrade to 10.10. installed on existed 10.8
  • also I have upgrade VirtualBox from ... to 4.3.26
  • Aslo we have Jenkins on this machine.

Next day we have start to see that Jenkins lose connections to virtual machines (2 machines, Win and Linux). While other host-computers did work fine ...

Finally we have found in that VirtualBox crashes? and produce many wakes_resource.diag files ...

Also we see in logs another trouble message as

4/20/15 5:27:41.477 PM VirtualBox[78285]: WARNING: The Gestalt selector gestaltSystemVersion is returning 10.9.3 instead of 10.10.3. Use NSProcessInfo's operatingSystemVersion property to get correct system version number.
Call location:
4/20/15 5:27:41.477 PM VirtualBox[78285]: 0   CarbonCore                          0x00007fff93aee2b7 ___Gestalt_SystemVersion_block_invoke + 113
4/20/15 5:27:41.477 PM VirtualBox[78285]: 1   libdispatch.dylib                   0x00007fff962c4c13 _dispatch_client_callout + 8
4/20/15 5:27:41.477 PM VirtualBox[78285]: 2   libdispatch.dylib                   0x00007fff962c4b26 dispatch_once_f + 117
4/20/15 5:27:41.477 PM VirtualBox[78285]: 3   CarbonCore                          0x00007fff93a77456 _Gestalt_SystemVersion + 987
4/20/15 5:27:41.477 PM VirtualBox[78285]: 4   CarbonCore                          0x00007fff93a766e3 Gestalt + 144
4/20/15 5:27:41.477 PM VirtualBox[78285]: 5   QtCoreVBox                          0x000000010289a536 _Z8qWarningPKcz + 214
4/20/15 5:27:41.477 PM VirtualBox[78285]: 6   ???                                 0x00007fff67b44ceb 0x0 + 140734933257451

On Google it is possible to find talks about both this trouble ... and most without clean solution ...

Right now I will try downgrade to 4.2.28, because it seems original author of this issue says it did worked fine for him on Mac OS 10.10

Last edited 5 years ago by frank (previous) (diff)

comment:3 Changed 5 years ago by frank

ruslan_zasukhin, the original report is about a Mac OS X host crash. From your report I understand that you saw a VM process crash, is that correct?

And I still would like to see crash reports.

Changed 5 years ago by flex

comment:4 Changed 5 years ago by flex

Confirm this, my OS is 10.10.3, VBox version is 4.3.28. Seems the kernel panic only occurs on booting win7 vm, sometimes.

Attachment is the panic report

comment:5 Changed 5 years ago by aeichner

Can you please attach the VBox.log for the run which caused the crash? Even if it will be incomplete it can contain useful information like load addresses for our R0 modules wihch makes it easier to get a meaningful stack trace.

comment:6 Changed 5 years ago by flex

@aeichner I searched the Log dir, but not found any log file associated with this crash. The crash occurred immediately after booting the VM

Note: See TracTickets for help on using tickets.
ContactPrivacy policyTerms of Use