quit expectedly - becoming a major problem

Discussion in 'Installation and Configuration of Parallels Desktop' started by kbrubin, Sep 24, 2008.

  1. kbrubin

    kbrubin Junior Member

    Messages:
    15
    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!
     
  2. John@Parallels

    John@Parallels Forum Maven

    Messages:
    6,333
    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;
     
  3. kbrubin

    kbrubin Junior Member

    Messages:
    15
    crash report

    I uninstalled parallels so there's no crash report.
     
  4. kbrubin

    kbrubin Junior Member

    Messages:
    15
    oops

    Ok, I just found under bugreport. Which log do you want?
     
  5. John@Parallels

    John@Parallels Forum Maven

    Messages:
    6,333
    zip the all, and attach here
     
  6. kbrubin

    kbrubin Junior Member

    Messages:
    15
    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
    ------------------------------------------------
     
  7. John@Parallels

    John@Parallels Forum Maven

    Messages:
    6,333
    hm is there nothing else?
     
  8. kbrubin

    kbrubin Junior Member

    Messages:
    15
    I zipped the archive but don't know to send it to you.
     
  9. John@Parallels

    John@Parallels Forum Maven

    Messages:
    6,333
    Click Go Advanced, there you will be able to see options to attach files
     
  10. kbrubin

    kbrubin Junior Member

    Messages:
    15
    I just sent the zipped archive as an attachment to your email. Is that right?
     
  11. John@Parallels

    John@Parallels Forum Maven

    Messages:
    6,333
    Sorry didn't receive anything, you can try to attach logs to post
     
  12. kbrubin

    kbrubin Junior Member

    Messages:
    15
    bugreport attachments

    Hello,

    I just attached the zip file.

    Thanks
     

    Attached Files:

  13. John@Parallels

    John@Parallels Forum Maven

    Messages:
    6,333
  14. Goodbar50

    Goodbar50 Bit poster

    Messages:
    9
    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:
    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.
     
  15. John@Parallels

    John@Parallels Forum Maven

    Messages:
    6,333
    Probably it will be better to create ticket in support
     
  16. tonycarreon

    tonycarreon Member

    Messages:
    70
    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
     
  17. Goodbar50

    Goodbar50 Bit poster

    Messages:
    9
    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.
     
  18. tonycarreon

    tonycarreon Member

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

Share This Page