VirtualBox 4.2.4 causes dtruss/dtrace to panic Macs??

Discussions related to using VirtualBox on Mac OS X hosts.

VirtualBox 4.2.4 causes dtruss/dtrace to panic Macs??

Postby Riot Nrrrd™ » 20. Nov 2012, 03:34

I really hope I'm wrong about this, but I'm seeing a bad pattern ...

If I try to run 'dtruss' (i.e. the layer over DTrace) while in multi-user mode, it panic crashes my 10.6.8 system (a 2010 Mac Pro).

This only started to happen after I upgraded VirtualBox to version 4.2.4.

In the panic tracebacks I always see VBoxDrv in the backtrace:

Code: Select all   Expand viewCollapse view
Mon Nov 19 17:03:16 2012
panic(cpu 0 caller 0xffffff80002d1208): Kernel trap at 0xffffff8000557de3, type 14=page fault, registers:
CR0: 0x0000000080010033, CR2: 0x00000000000299f4, CR3: 0x00000000336a2000, CR4: 0x0000000000000660
RAX: 0xffffff7f8189f0ab, RBX: 0x00000000000299f4, RCX: 0x0000000000000000, RDX: 0xffffff7f8189f190
RSP: 0xffffff80b3c9b990, RBP: 0xffffff80b3c9b990, RSI: 0x0000000000000028, RDI: 0x00000000000299f4
R8:  0xffffff80b3c9b64c, R9:  0x0000000000000000, R10: 0x0000000000000002, R11: 0x0000000000100000
R12: 0xffffff7f8189f1e0, R13: 0xffffff8018fca430, R14: 0x0000000018000002, R15: 0x0000000000000000
RFL: 0x0000000000010282, RIP: 0xffffff8000557de3, CS:  0x0000000000000008, SS:  0x0000000000000010
Error code: 0x0000000000000000

Backtrace (CPU 0), Frame : Return Address
0xffffff80b3c9b630 : 0xffffff8000204d15
0xffffff80b3c9b730 : 0xffffff80002d1208
0xffffff80b3c9b880 : 0xffffff80002e3f4a
0xffffff80b3c9b890 : 0xffffff8000557de3
0xffffff80b3c9b990 : 0xffffff7f8187446c
0xffffff80b3c9ba20 : 0xffffff80004ce549
0xffffff80b3c9ba40 : 0xffffff80004d6a59
0xffffff80b3c9ba90 : 0xffffff80003182d5
0xffffff80b3c9baf0 : 0xffffff800023eb6a
0xffffff80b3c9bb30 : 0xffffff8000239cb8
0xffffff80b3c9bba0 : 0xffffff8000305a64
0xffffff80b3c9bc70 : 0xffffff8000305ed3
0xffffff80b3c9bf40 : 0xffffff80004e8168
0xffffff80b3c9bfa0 : 0xffffff80002e4874
      Kernel Extensions in backtrace (with dependencies):
         org.virtualbox.kext.VBoxDrv(4.2.4)@0xffffff7f81867000->0xffffff7f8189ffff

BSD process name corresponding to current thread: dtrace

Mac OS version:
10K549

Kernel version:
Darwin Kernel Version 10.8.0: Tue Jun  7 16:32:41 PDT 2011; root:xnu-1504.15.3~1/RELEASE_X86_64
System model name: MacPro5,1 (Mac-F221BEC8)

System uptime in nanoseconds: 1825131547035
unloaded kexts:
com.apple.driver.AppleIntel8254XEthernet   2.1.3b1 (addr 0xffffff7f81204000, size 0x118784) - last unloaded 1596184057595
loaded kexts:
org.virtualbox.kext.VBoxNetAdp   4.2.4 - last loaded 1536141775670
org.virtualbox.kext.VBoxNetFlt   4.2.4
org.virtualbox.kext.VBoxUSB   4.2.4
org.virtualbox.kext.VBoxDrv   4.2.4
[...]


If I boot the system in single-user mode (Apple-S at startup), "dtruss"/DTrace does not panic the system.

While it doesn't rule out some other kext as the problem, I don't make many changes on this system and upgrading VirtualBox is the first thing I've done that's updated a kernel extension in a long time.

If anyone else has a spare 10.6.8 system that they don't mind risking having it panic, I'd be curious to know if it happens to them as well.

To recreate, just do a "dtruss" on anything, e.g. "dtruss ls" or "dtruss pwd".

(If it matters, I'm booted in full 64-bit mode - 64-bit CPU, 64-bit EFI, 64-bit kernel boot mode, 64-bit kernel.)
Riot Nrrrd™
 
Posts: 6
Joined: 1. Apr 2012, 01:15

Re: VirtualBox 4.2.4 causes dtruss/dtrace to panic Macs??

Postby CrB » 8. Dec 2012, 09:07

I can confirm the same behavior here. To verify it, I've disabled the virtual box kexts rebooted and loaded iotop (which uses dtrace).

With the VBox kexts loaded, the Mac immediately kernel panics when iotop is executed. Without the VBox kexts, iotop runs normally.

This needs to get elevated. Where do I open a bug ticket for this, *AND* what debug info would the devs like collected to help diagnose the issue?
CrB
 
Posts: 3
Joined: 8. Dec 2012, 09:02

Re: VirtualBox 4.2.4 causes dtruss/dtrace to panic Macs??

Postby mpack » 8. Dec 2012, 09:28

BugTracker : https://www.virtualbox.org/wiki/Bugtracker
BugTracker is a separate system, although you can use the same OSSO login you use here. On first login you'll be asked to choose a nickname for that site. It would make sense to use the same nickname as here, if it lets you.
mpack
Site Moderator
 
Posts: 13167
Joined: 4. Sep 2008, 17:09
Primary OS: MS Windows XP
VBox Version: PUEL
Guest OSses: Mostly XP

Re: VirtualBox 4.2.4 causes dtruss/dtrace to panic Macs??

Postby CrB » 8. Dec 2012, 09:33

I've opened a tracker ticket against this bug. Ticket #11273

Forums wont let me post the link. :-(

I'll try to reproduce next week on some of our other Macs, and see if I can reproduce under 10.7 or 10.8 as well.

[Mod edit: I fixed the link]
CrB
 
Posts: 3
Joined: 8. Dec 2012, 09:02

Re: VirtualBox 4.2.4 causes dtruss/dtrace to panic Macs??

Postby Riot Nrrrd™ » 11. Dec 2012, 09:08

Thanks CrB! Nice to know I'm not going crazy thinking that it was VBox's fault. :mrgreen:
Riot Nrrrd™
 
Posts: 6
Joined: 1. Apr 2012, 01:15

Re: VirtualBox 4.2.4 causes dtruss/dtrace to panic Macs??

Postby CrB » 12. Dec 2012, 04:20

I've now tested on Mac OS X 10.7 and 10.8 and the panic does not occur. The kernel panic only occurs on 10.6 systems. I have also updated the bug ticket.

Ohh yeah, this is an OBVIOUS Vbox issue. I'm kinda surprised this one made it out the door without anybody noticing. Dtrace is fairly important because of how frequently it's used behind the scenes by various Mac debugging tools. I would have thought somebody doing VBox dev on the Mac would have hit it during dev.

Ok folks, what do I need to round up next to make this as easy as humanly possible for somebody on the dev team who knows about the VBox/OS X kexts?
CrB
 
Posts: 3
Joined: 8. Dec 2012, 09:02

Re: VirtualBox 4.2.4 causes dtruss/dtrace to panic Macs??

Postby Riot Nrrrd™ » 31. Dec 2012, 19:38

CrB wrote:I've now tested on Mac OS X 10.7 and 10.8 and the panic does not occur. The kernel panic only occurs on 10.6 systems. I have also updated the bug ticket.

Ohh yeah, this is an OBVIOUS Vbox issue. I'm kinda surprised this one made it out the door without anybody noticing. Dtrace is fairly important because of how frequently it's used behind the scenes by various Mac debugging tools. I would have thought somebody doing VBox dev on the Mac would have hit it during dev.

Ok folks, what do I need to round up next to make this as easy as humanly possible for somebody on the dev team who knows about the VBox/OS X kexts?


It would be nice to get this fixed as I am not updating my Mac Pro from 10.6.8 anytime soon.

Anybody with an update to this? Anyone? Anyone? Bueller?
Riot Nrrrd™
 
Posts: 6
Joined: 1. Apr 2012, 01:15

Re: VirtualBox 4.2.4 causes dtruss/dtrace to panic Macs??

Postby Riot Nrrrd™ » 16. Jan 2013, 04:27

CrB:

I see that 4.2.6 is out. Have you tried testing against it ( on 10.6.8 ) yet?

I looked at the ChangeLog and didn't see anything indicating that this bug had been fixed in 4.2.6 :(

EDIT: I see in the Bug Report that it's claimed to be "fixed in the next maintenance release" but I don't know if that is 4.2.6 or in whatever comes after 4.2.6 ...
Riot Nrrrd™
 
Posts: 6
Joined: 1. Apr 2012, 01:15

Re: VirtualBox 4.2.4 causes dtruss/dtrace to panic Macs??

Postby PRD » 30. Jan 2013, 17:35

I'm running 4.2.6 and have been getting kernel panics just about every night. I posted a new thread about the issue before I read this one. I've shut down Virtualbox every night, but still get a panic. I'm running Mac OS 10.8.2 on a brand new Mac Pro. I've had five kernel panics in the week and half I've been running the system. All occur while the host system is in sleep mode.
PRD
 
Posts: 2
Joined: 30. Jan 2013, 17:03


Return to VirtualBox on Mac OS X Hosts

Who is online

Users browsing this forum: No registered users and 8 guests