New install "successful" but Parallels 3.0 crashes on launch

D

dwinsemius

Junior Member
I have a MacPro quad core 2 x 2.8 machine under 10.5.4 with 8 GB memory. System Profiler reports no hardware errors.

WinXP hs already been installed via Boot Camp on a 32 GB FAT32 partition the second bay HD.

Installing from the CD image (build 4128) was reported as "successful" but resulted in crash upon launch. Reading this installation forum produced multiple solutions and sometimes conflicting advice. Tried uninstalling and repairing permissions and reinstalling the build 5608 downloaded as Parallels-Desktop-5608-Mac-en.dmg, but this results in same outcome (Installer reports success but Parallels crashes upon launch).

Looked for Parallels log entry in the Library ----
------------------------------------------------------------------------------
Parallels Desktop 3.0 for Mac OS X version 3.0 Build 4128.0 from 2007-06-09
-------------------------------------------------------------------------------
Received SIGBUS: Bus error
Access to fault address: 0x1
unknown signal sender: 2
-------------------------------------------------------------------------------

And ....Why does the error log indicate that it is build 4128??? Is this just the result of a section of your code that was never updated. The last effort at installing from the CD was yesterday and this log was created today.

Hoping for prompt reply... this notion that software that won't even launch the first time cannot get phone support seems very lame.

David Winsemius
---------
Here is the top of error log that the system displays;

Process: Parallels [426]
Path: /Applications/Parallels/Parallels Desktop.app/Contents/MacOS/Parallels
Identifier: com.parallels.desktop
Version: 3.0 (3.0 Build 4128.0)
Code Type: X86 (Native)
Parent Process: launchd [106]

Date/Time: 2008-07-14 10:49:23.630 -0400
OS Version: Mac OS X 10.5.4 (9E17)
Report Version: 6

Exception Type: EXC_CRASH (SIGBUS)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Crashed Thread: 1

Thread 0:
0 com.parallels.desktop 0x0034c890 0x1000 + 3455120
1 com.parallels.desktop 0x0034c938 0x1000 + 3455288
2 com.parallels.desktop 0x0034cac5 0x1000 + 3455685
3 com.parallels.desktop 0x0012e9b3 0x1000 + 1235379
4 com.parallels.desktop 0x000419ec 0x1000 + 264684
5 com.parallels.desktop 0x00006792 0x1000 + 22418
6 com.parallels.desktop 0x000066b9 0x1000 + 22201

Thread 1 Crashed:
0 libSystem.B.dylib 0x9097e68e __semwait_signal + 10
1 libSystem.B.dylib 0x909a936d pthread_cond_wait$UNIX2003 + 73
2 libGLProgrammability.dylib 0x95117432 glvmDoWork + 162
3 libSystem.B.dylib 0x909a86f5 _pthread_start + 321
4 libSystem.B.dylib 0x909a85b2 thread_start + 34

Thread 1 crashed with X86 Thread State (32-bit):
eax: 0x00000004 ebx: 0x909a938d ecx: 0xb00a0e9c edx: 0x9097e68e
edi: 0xa0617e00 esi: 0xb00a1000 ebp: 0xb00a0f18 esp: 0xb00a0e9c
ss: 0x0000001f efl: 0x00000247 eip: 0x9097e68e cs: 0x00000007
ds: 0x0000001f es: 0x0000001f fs: 0x0000001f gs: 0x00000037
cr2: 0xb00a0fec

Binary Images:
0x1000 - 0xc31eeb +com.parallels.desktop 3.0 (3.0 Build 4128.0) /Applications/Parallels/Parallels Desktop.app/Contents/MacOS/Parallels
0xf33000 - 0xf56fed com.apple.audio.OpenAL 1.2 (1.2) <dc38faba8e97c51597580a19740afe65> /System/Library/Frameworks/OpenAL.framework/Versions/A/OpenAL
0x1327000 - 0x1335feb libSimplifiedChineseConverter.dylib ??? (???) <ec9a1c1949952acb83d09a0320ba2df1> /System/Library/CoreServices/Encodings/libSimplifiedChineseConverter.dylib
0x1516000 - 0x1528fff libTraditionalChineseConverter.dylib ??? (???) <086a18ff56a7d80d4446b979a18a4f64> /System/Library/CoreServices/Encodings/libTraditionalChineseConverter.dylib
0x167b2000 - 0x167ceff7 GLRendererFloat ??? (???) <98be9cb44eb018fa6300e9447b214fd7> /System/Library/Frameworks/OpenGL.framework/Versions/A/Resources/GLRendererFloat.bundle/GLRendererFloat
0x16f6f000 - 0x170f1fef GLEngine ??? (???) <e9b3c93e50e3236cae43a2161e331720> /System/Library/Frameworks/OpenGL.framework/Resources/GLEngine.bundle/GLEngine
0x1711f000 - 0x17374fe9 com.apple.ATIRadeonX2000GLDriver 1.5.28 (5.2.8) <fc6b901a0043ea8495eaebf80882939c> /System/Library/Extensions/ATIRadeonX2000GLDriver.bundle/Contents/MacOS/ATIRadeonX2000GLDriver
0x8fe00000 - 0x8fe2da53 dyld 96.2 (???) <5013f43c4d2c33c9619011f103ec3238> /usr/lib/dyld
0x90654000 - 0x90654ff8 com.apple.Cocoa 6.5 (???) <e9318c93615b27231498bbe585b8da98> /System/Library/Frameworks/Cocoa.framework/Versions/A/Cocoa
0x90655000 - 0x90656ffc libffi.dylib ??? (???) <596e0dbf626b211741cecaa9698f271b> /usr/lib/libffi.dylib

--- trimmed report since the size of post was too large...
 
Please read the entire message for meaning. I did exactly what you suggest after the first install failed. The error is what I am getting AFTER downloading and "successfully" intalling using build 5608.

Sincerely;
David Winsemius
 
I can just repeat again, build in crash is old, it means that you did some mistake somewhere,
I even guess where, you left Parallels CD inside, after restart.
Please read article I recommended again.
It mean uninstall from old dmg , etc, restart
in order old dmg (or CD) is not mounted or in there,
Mount new build and do install
 
Last edited:
You did not mention in your initial reply that having the CD in place was a source of problem. The knowledge base entry did not mention that fact, either. It was useful that you gave that as a possible problem, but why wait until I had already failed again??? I now have a launchable copy of Parallels. The problem as I see it is not my "error", but rather your company's incomplete documentation. The further problem is that you, personally, blame the user for not reading minds. Constuctive suggestion #1. Create a cut-and-pastable reply that includes suggestion to remove CD if the version is outdated. Suggestion number 2: Ask your web guys to put that advice in the knowledge base article.

Now ... Having started the creation of a VM for my copy of Windows that resides on a 32 GB FAT32 partition on a second internal drive, Parallels does not seem to be findng it. The documentation indicates that it would find that copy. I am stopping at the point where it asks me to put in the XP CD, since I already have a working, bootable copy.

The only way I can find the option to use the Boot Camp partition is to go down the "Custom" installation tree and when I get to the select virtual hard disk page, the boot camp choice is greyed out. What portion of the manual do you suggest I consult, and are there any other problems about which I should be alerted that are not in the documentation?

--
David Winsemius
 
We have kb article when Boot Camp Partition is located on another drive.

http://kb.parallels.com/en/5063
2 requirements
-Partition should be EFI formatted
-Partition should be located in the first 128 gb

P.S.
Thanks for suggestions.
- No one blames you I just described possible errors cause, this was the first came in mind, and happily it was, but in 99% cases, it is just broken permissions and as a result parallels drivers are still there even users state that they removed drivers
- We are considering to change article
 
Non-Boot Camp partitions act similarly

I installed on a non-Boot Camp disk partition set up and got a similar crash, with a similar machine, a MacPro. In my case the recovery from crash was no problem. I have yet to fix my permissions, something I do try to regularly, when installing software. As mentioned here this seems to be a big cause of problems especially with Parallels. I simply rebooted the machine. In checking Parallels found that it had installed the newest version and ran it OK after the re-boot.

System details (from System Profiler):
Model Name: Mac Pro
Model Identifier: MacPro1,1
Processor Name: Dual-Core Intel Xeon
Processor Speed: 2.66 GHz
Number Of Processors: 2
Total Number Of Cores: 4
L2 Cache (per processor): 4 MB
Memory: 5 GB
Bus Speed: 1.33 GHz
Boot ROM Version: MP11.005C.B08
SMC Version: 1.7f10

My question is why?

Here's my crash log as intercepted by fault recovery:
Fri Jul 18 17:47:14 2008
panic(cpu 0 caller 0x001A8CD4): Kernel trap at 0x6e7c0308, type 14=page fault, registers:
CR0: 0x8001003b, CR2: 0x24148904, CR3: 0x012a0000, CR4: 0x00002660
EAX: 0xffffffff, EBX: 0x00737361, ECX: 0x0b882c80, EDX: 0x24148904
CR2: 0x24148904, EBP: 0x863d7eb8, ESI: 0x00000000, EDI: 0x66f98000
EFL: 0x00010202, EIP: 0x6e7c0308, CS: 0x00000008, DS: 0x10ae0010
Crash Log sent to Apple.

Error code: 0x00000000

Backtrace, Format - Frame : Return Address (4 potential args on stack)
0x863d7cb8 : 0x12b0fa (0x4592a4 0x863d7cec 0x133243 0x0)
0x863d7d08 : 0x1a8cd4 (0x46280c 0x6e7c0308 0xe 0x461fbc)
0x863d7de8 : 0x19ede5 (0x863d7e00 0x27a317ea 0x863d7eb8 0x6e7c0308)
0x863d7df8 : 0x6e7c0308 (0xe 0x6e450048 0x10 0x10)
0x863d7eb8 : 0x6e7bf5d6 (0x737361 0x154cbf20 0x863d7f08 0x136a72)
0x863d7ee8 : 0x6e7c3cc5 (0x16285200 0x202 0x863d7f18 0x6e7bee27)
0x863d7f18 : 0x6e7c0828 (0x965ab04 0x6e7c803c 0x6e7c8058 0x2c)
0x863d7f48 : 0x6e7be57f (0x965ab04 0x6e7c7690 0x6e7c7670 0x28f)
0x863d7f78 : 0x6e7be6f2 (0x11000000 0x0 0x0 0x90f24a0)
0x863d7fc8 : 0x19ebdc (0x0 0x0 0x1a20b5 0x154cbf20)
Backtrace terminated-invalid frame pointer 0
Kernel loadable modules in backtrace (with dependencies):
com.parallels.kext.vmmain(3.0)@0x6e7bd000->0x6e7ccfff

BSD process name corresponding to current thread: kernel_task

Mac OS version:
9E17

Kernel version:
Darwin Kernel Version 9.4.0: Mon Jun 9 19:30:53 PDT 2008; root:xnu-1228.5.20~1/RELEASE_I386
System model name: MacPro1,1 (Mac-F4208DC8)
 
My crashing version of Parallels was caused by not knowing (because it's nowhere documented) that you need to take the distribution CD out of the bay when installing a new down-loaded version. Further problems arose due to having the Boot Camp-installed copy of WinXP on an Fdisk_partition_scheme partitioned disk, which I later learned is refered to as an MBR partition.

The correct partition scheme at least as far as Parallels is concerned is GUID (aka EFI, aka GPT). I cannot find that anywhere documented, either. There seems to be surprise and doubt in the audience that my disk was partitioned with Disk Utility, but I swear that I have never used anything else. My guess is that the drive arrived from the factory with that partition scheme and that Disk Utility somehow "honored" that arrangement.

Fore your problem....What is the output of:

diskutil list

.....issued from the terminal window?

David.
 
dwinsemius said:
Fore your problem....What is the output of:

diskutil list

.....issued from the terminal window?

David.
Click to expand...

I deleted the listing of the other two attached disks as they are used for backup purposes only and have no part of the picture.

MacPro startup disk (which has always worked before and crashed w/ Kenel Panic when installing the latest Parallels):
[BubbaMacPro:/] bubba% diskutil list
/dev/disk0
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *232.9 Gi disk0
1: EFI 200.0 Mi disk0s1
2: Apple_HFS Macintosh HD 232.6 Gi disk0s2
 
David,

Could it be that Boot Camp formatted this 'bad' feature in a partition back whenever you set up Boot Camp? That would seem logical to me as Apple's partitioning scheme kinda works behind their user interface enlarging or shrinking the normal partition suring the installation process. Certainly they've been through several iterations of Boot Camp / OS. I don't know the history.

Not an expert in this GPT/GUID stuff by any means! Simply assuming you're all telling the truth, going by logic, and my 2¢...

Henry
 
Henry Seiden said:
I deleted the listing of the other two attached disks as they are used for backup purposes only and have no part of the picture.

MacPro startup disk (which has always worked before and crashed w/ Kenel Panic when installing the latest Parallels):
[BubbaMacPro:/] bubba% diskutil list
/dev/disk0
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *232.9 Gi disk0
1: EFI 200.0 Mi disk0s1
2: Apple_HFS Macintosh HD 232.6 Gi disk0s2
Click to expand...


But where is Windows Partition?
I suppose you are not using Windows from Boot Camp, but you are using old build, use link in me previous post to install new version
 
You must log in or register to reply here.
Back
Top