VirtualBox

Opened 9 years ago

Closed 4 years ago

#14175 closed defect (obsolete)

OSX Hypervisor Kernel panic mp_rendezvous_action()

Reported by: josh.r Owned by:
Component: host support Version: VirtualBox 4.3.28
Keywords: Cc:
Guest type: OSX Server Host type: other

Description

Kernel Panic: https://gist.github.com/anonymous/47239d64b01c7f5a8aef

This is a reproducible kernel panic.

Setup:

Hypervisor: OSX 10.10.3 12GB ECC RAM 2x Quad-Core i7 (16 cores total).

Virtual Box: 4.2.28 & 4.3.28 ( i haven't tried older versions yet ).

Guest: Ubuntu 15.04 RAM: 3078MB CPU: 8 cores VTX/Nested paging enabled

NFS share mounted in a Ubuntu 15.04 VM. Ubuntu 15.04 VM is running crash plan and backing up the NFS share. The Ubuntu 15.04 VM is a local vdi on the OSX Hypervisor. Running the backup causes the hypervisor machine to kernel panic (with the above panic trace) after a seemingly random amount of time (usually less than an hour).

I have several vm's with VDI's on the NFS share: CentOS 6/7, Ubuntu 12/14, Debian 6/7, all of these run without any issues and do not cause kernel panics. I have tried leaving these running and leaving them off to see if there was some conflict between the vms that was causing panics. Both ways still cause panics.

The only 3rd party kext's I have installed are the virtual box ones:

Index Refs Address            Size       Wired      Name (Version) <Linked Against>
  112    3 0xffffff7f826da000 0x54000    0x54000    org.virtualbox.kext.VBoxDrv (4.2.28) <7 5 4 3 1>
  113    0 0xffffff7f8272e000 0x8000     0x8000     org.virtualbox.kext.VBoxUSB (4.2.28) <112 103 38 7 5 4 3 1>
  114    0 0xffffff7f82736000 0x5000     0x5000     org.virtualbox.kext.VBoxNetFlt (4.2.28) <112 7 5 4 3 1>
  115    0 0xffffff7f8273b000 0x6000     0x6000     org.virtualbox.kext.VBoxNetAdp (4.2.28) <112 5 4 1>                                                                                

If there is any other information I can provide let me know.

Change History (2)

comment:1 by Frank Mehnert, 9 years ago

Please provide a VBox.log file of such a VM session.

comment:2 by aeichner, 4 years ago

Resolution: obsolete
Status: newclosed

No response and probably fixed long ago, closing as obsolete.

Note: See TracTickets for help on using tickets.

© 2023 Oracle
ContactPrivacy policyTerms of Use