VBox and Parallels make OSX 10.5 crash

Discussions related to using VirtualBox on Mac OS X hosts.

VBox and Parallels make OSX 10.5 crash

Postby diddek » 24. May 2008, 20:36

Hi,

Just a small note: when I run vbox 1.6 (with an ubuntu guest) on my macbook, the whole thing freezes as soon as I start parallels and kindly asks me to hold the powerbutton until stopped.

It might have something to do with 2 kernel modules trying to do ...

I hope this will be fixed, as I like both programs!

D
diddek
 
Posts: 3
Joined: 24. May 2008, 20:20

Postby Technologov » 25. May 2008, 14:56

I believe this is due to the fact the they try to use raw CPU both.

In order to use them together, try to disable (!) Hardware Virtualization (VT) in both programs.

They should run together fine...

P.S. I'm no Mac expert, but I do understand virtualization...

-Technologov
Technologov
Volunteer
 
Posts: 3342
Joined: 10. May 2007, 16:59
Location: Israel

Postby jeff275 » 2. Jul 2008, 18:14

I am having the same problem and this did not fix it.
jeff275
 
Posts: 1
Joined: 2. Jul 2008, 18:12

Postby ah228 » 3. Jul 2008, 20:52

It's not just 10.5. 10.4 crashes that way too.
ah228
 
Posts: 1
Joined: 3. Jul 2008, 20:50

Re: VBox and Parallels make OSX 10.5 crash

Postby 1ka » 17. Apr 2009, 10:03

Hi Folks,

I have exactly this problem. Running Parallels and Virtual Box works OK until I close Parallels then it hard crashes the Mac.

Is this a known issue? Any idea which product is causing it?

Naturally it is a major pain to crash the Mac with everything running on it, and yes, I could just run one or the other VM environments.

Here are some snippets of the error log, I can post full logs if required.

Wed Apr 15 10:44:06 2009
panic(cpu 0 caller 0x00193CE7): "pmap_flush_tlbs() timeout: " "cpu(s) failing to respond to interrupts, pmap=0x53a600 cpus_to_respond=0x2"@/SourceCache/xnu/xnu-1228.9.59/osfmk/i386/pmap.c:4582
Backtrace (CPU 0), Frame : Return Address (4 potential args on stack)
0x5b4eb8c8 : 0x12b4f3 (0x45b13c 0x5b4eb8fc 0x1335e4 0x0)


Fri Apr 10 08:30:46 2009
panic(cpu 1 caller 0x00193CE7): "pmap_flush_tlbs() timeout: " "cpu(s) failing to respond to interrupts, pmap=0x53a600 cpus_to_respond=0x1"@/SourceCache/xnu/xnu-1228.9.59/osfmk/i386/pmap.c:4582
Backtrace (CPU 1), Frame : Return Address (4 potential args on stack)
0x5c12f4b8 : 0x12b4f3 (0x45b13c 0x5c12f4ec 0x1335e4 0x0)


Tue Mar 31 08:06:07 2009
panic(cpu 0 caller 0x00193CE7): "pmap_flush_tlbs() timeout: " "cpu(s) failing to respond to interrupts, pmap=0x53a600 cpus_to_respond=0x2"@/SourceCache/xnu/xnu-1228.9.59/osfmk/i386/pmap.c:4582
Backtrace (CPU 0), Frame : Return Address (4 potential args on stack)
0x48a3b4b8 : 0x12b4f3 (0x45b13c 0x48a3b4ec 0x1335e4 0x0)
0x48a3b508 : 0x193ce7 (0x46126c 0x53a600 0x2 0x194406)
0x48a3b578 : 0x194e7b (0x53a600 0x3bd12000 0x0 0x0)
0x48a3bab8 : 0x7fb221 (0x673a000 0x48a3bb54 0xd8d5700 0x1)
Backtrace continues...
Kernel loadable modules in backtrace (with dependencies):
com.apple.ATIRadeonX2000(5.3.6)@0x7c4000->0x87bfff


Fri Mar 27 21:48:09 2009
panic(cpu 0 caller 0x00193CE7): "pmap_flush_tlbs() timeout: " "cpu(s) failing to respond to interrupts, pmap=0x53a600 cpus_to_respond=0x2"@/SourceCache/xnu/xnu-1228.9.59/osfmk/i386/pmap.c:4582
Backtrace (CPU 0), Frame : Return Address (4 potential args on stack)
0x4896f828 : 0x12b4f3 (0x45b13c 0x4896f85c 0x1335e4 0x0)
0

Fri Mar 27 09:36:18 2009
panic(cpu 1 caller 0x00193CE7): "pmap_flush_tlbs() timeout: " "cpu(s) failing to respond to interrupts, pmap=0x53a600 cpus_to_respond=0x1"@/SourceCache/xnu/xnu-1228.9.59/osfmk/i386/pmap.c:4582
Backtrace (CPU 1), Frame : Return Address (4 potential args on stack)
0x4826f4b8 : 0x12b4f3 (0x45b13c 0x4826f4ec 0x1335e4 0x0)
0x4826f508 : 0x193ce7 (0x46126c 0x53a600 0x1 0x194406)
0x4826fa48 : 0x7edec1 (0x6578000 0xeff1300 0x740040 0x3a0)
0x4826fab8 : 0x7ef221 (0x6578000 0x4826fb54 0xeff1300 0x1)
Backtrace continues...
Kernel loadable modules in backtrace (with dependencies):
com.apple.ATIRadeonX2000(5.3.6)@0x7b8000->0x86ffff
dependency: com.apple.iokit.IONDRVSupport(1.7.1)@0x7aa000


Mac OS version:
9G55

Kernel version:
Darwin Kernel Version 9.6.0: Mon Nov 24 17:37:00 PST 2008; root:xnu-1228.9.59~1/RELEASE_I386
System model name: iMac7,1 (Mac-F42386C8)


Parallels is Build 4.0.3810
VirtualBox is build 2.2.0 (and some crashes on earlier versions).


I've posted a similar thread on the Parallels forum which can be found here -> http://forum.parallels.com/showthread.php?t=89543
1ka
 
Posts: 4
Joined: 17. Apr 2009, 10:00
Primary OS: Mac OS X Leopard
VBox Version: OSE other
Guest OSses: Windows 98, XP & 7, Linux flavours

Re: VBox and Parallels make OSX 10.5 crash

Postby rpmurray » 17. Apr 2009, 20:18

Call me crazy or old-fashioned but you might try this new-fangled thing called a User Manual.

On page 12 of the one that came with version 2.2.0 it says:

Warning: Do not run other hypervisors (open-source or commercial virtu-
alization products) together with VirtualBox! While several hypervisors can
normally be installed in parallel, do not attempt to run several virtual ma-
chines from competing hypervisors at the same time. VirtualBox cannot track
what another hypervisor is currently attempting to do on the same host, and
especially if several products attempt to use hardware virtualization features
such as VT-x, this can crash the entire host.


This same warning is probably in earlier versions of the User Manual too.
Last edited by rpmurray on 18. Apr 2009, 17:36, edited 1 time in total.
rpmurray
Volunteer
 
Posts: 918
Joined: 3. Mar 2009, 00:29
Location: Between Heaven and Hell
Primary OS: Mac OS X other
VBox Version: PUEL
Guest OSses: Windows 7, Mac OS X (various flavors)

Re: VBox and Parallels make OSX 10.5 crash

Postby 1ka » 18. Apr 2009, 08:49

Thanks for that, rtfm :) At least it's a known issue, if slightly dodgy cop-out.

As noted earlier in the thread - doesn't always work if we switch off Hypervisor/VT-x or whatever it's called.

Also, it only crashes when I shut-down, running the two together is fine. If I shut down parallels first it crashes, shutting VB first is fine. I'd suggest that it's an issue with releasing resources when closing, so, someone is playing nice and someone isn't :)
1ka
 
Posts: 4
Joined: 17. Apr 2009, 10:00
Primary OS: Mac OS X Leopard
VBox Version: OSE other
Guest OSses: Windows 98, XP & 7, Linux flavours


Return to VirtualBox on Mac OS X Hosts

Who is online

Users browsing this forum: No registered users and 15 guests