quit expectedly - becoming a major problem

[kbrubin]

Recently, Parallels desktop (winxp) stopped launching on my MAC Leopard , so I uninstalled and cleaned out all parallels files as suggested, including running the disk utility -repair permissions.. Then I reinstalled, but I'm getting the same error message that it quit unexpectedly. PLEASE don't ask me to purchase an anti-virus program for my MAC side because that's the reason I purchased the MAC in the first place. I had an anti virus program on the windows side (ESET). Once you can give me a practical way to make parallels work again, then I have to convince Microsoft and ESET to give me new licensing keys to make their programs work. What a hassle!

 

[John@Parallels]

What can you see in:
* Archive of /Library/Parallels/bugreports/
or ~/Library/Parallels/bugreports/

* /Library/Logs/panic.log
or ~/Library/Logs/CrashReporter/Parallels.crash.log from the Mac side;

 

[kbrubin]

crash report

I uninstalled parallels so there's no crash report.

 

[kbrubin]

oops

Ok, I just found under bugreport. Which log do you want?

 

[John@Parallels]

zip the all, and attach here

 

[kbrubin]

last few reports

Here's a copy of my last few reports.

arallels 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
--------------------------------------------------


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
------------------------------------------------

 

[John@Parallels]

hm is there nothing else?

 

[kbrubin]

I zipped the archive but don't know to send it to you.

 

[John@Parallels]

Click Go Advanced, there you will be able to see options to attach files

 

[kbrubin]

I just sent the zipped archive as an attachment to your email. Is that right?

 

[John@Parallels]

Sorry didn't receive anything, you can try to attach logs to post

 

[kbrubin]

bugreport attachments

Hello,

I just attached the zip file.

Thanks

 

[John@Parallels]

Please download build 5608 following link bellow:
http://download.parallels.com/v3/en/GA/Parallels-Desktop-5608-Mac-en.dmg

and reinstall Parallels Desktop as described in kb
http://kb.parallels.com/en/4790

Note after Mac restart you need to eject CD or unmount old build from Finder

 

[Goodbar50]

VM quitting unexpectedly - me too

John@Parallels

This is the same problem (Same stuff in the bugreports) that I am getting, although my "VM quitting" happens randomly only when I leave the VM running overnight not getting it at starup.

I posted in the Windows forum specifically the other day.

I am wondering if this happens to anyone running the VM pointing to a Boot Camp version of Windows XP?

If they are not, I may reinstall in Boot Camp and create a new VM to use Boot Camp.

I bought Parallels Desktop for Mac 3.0 at a store in January 2008. (not sure what build it is, since I have upgraded to 5608)
My earliest incident was in March 2008. The crash report shows build 5582.

I was just looking at system logs from the latest "unexpected quit" on 9/23 and found these messages:

Sep 23 01:39:56 tag-macbook-pro [0x0-0x379379].com.parallels.desktop[7712]: Parallels Desktop 3.0 critical error! Send log file ( /Library/Parallels/bugreports/parallels-fault-013956.230808.7712.log ) to reports@parallels.com
Sep 23 01:40:02 tag-macbook-pro kernel[0]: [err in VmObserverThread ] : Forced quit VM (!) id=75525056 -> ../host.Darwin/device.c:424
Sep 23 01:40:02 tag-macbook-pro ReportCrash[10711]: Formulating crash report for process Parallels[7712]
Sep 23 01:40:03 tag-macbook-pro com.apple.launchd[140] ([0x0-0x379379].com.parallels.desktop[7712]): Stray process with PGID equal to this dead job: PID 7717 PPID 1 vfstool
Sep 23 01:40:03 tag-macbook-pro com.apple.launchd[140] ([0x0-0x379379].com.parallels.desktop[7712]): Exited abnormally: Bus error
Sep 23 01:40:04 tag-macbook-pro KernelEventAgent[36]: tid 00000000 received VQ_DEAD event (32)
Sep 23 01:40:09 tag-macbook-pro ReportCrash[10711]: Saved crashreport to /Users/thomasagoodhart/Library/Logs/CrashReporter/Parallels_2008-09-23-013957_tag-macbook-pro.crash using uid: 501 gid: 20, euid: 501 egid: 20
Sep 23 01:40:09 tag-macbook-pro fseventsd[40]: log dir: /Volumes/ZIPBACKUP/.fseventsd getting new uuid: 33175367-6192-42BF-BE7A-A9B61B16595F

John, I am going to send the bugreport reports@parallels.com, System Profile and system logs, like it says to in the above system log.

 

[John@Parallels]

Probably it will be better to create ticket in support

 

[tonycarreon]

i have sent bug reports on this and not heard a peep. should i be getting a ticket number back?

very annoying, not the best thing to wake up to - having a vm die and all.

11/18/08 4:31:53 AM [0x0-0x307307].com.parallels.desktop[7776] Parallels Desktop 3.0 critical error! Send log file ( /Library/Parallels/bugreports/parallels-fault-043153.181008.7776.log ) to reports@parallels.com
11/18/08 4:32:00 AM com.apple.launchd[133] ([0x0-0x307307].com.parallels.desktop[7776]) Stray process with PGID equal to this dead job: PID 7781 PPID 1 vfstool
11/18/08 4:32:00 AM com.apple.launchd[133] ([0x0-0x307307].com.parallels.desktop[7776]) Exited abnormally: Bus error

 

[Goodbar50]

Note: I have not had this problem since installing build 5624, so maybe the problem is gone.
Not sure where I found the link, but maybe you can supply it, John.

I have ordered Parallels Desktop for Mac 4.0.

 

[tonycarreon]

today parallels update downloaded 5626... i had the pop up for 5624 but i clicked not now and then it never came back.