Lockup after period of use

Discussion in 'Parallels Desktop for Mac' started by Diryt66, Apr 19, 2006.

  1. Diryt66

    Diryt66 Bit poster

    Messages:
    1
    Host: Mac Mini Core Solo, 2 gigs of ram
    OS: Mac OS 10.4.6
    Guest OS: Solaris 10
    RAM for Guest: 512MB
    PW: Beta 4

    I have noticed on my Core Solo Mini, that the workstation seems to lookup after I've been using it for more than an hour. The guest OS (solaris 10/openbsd) stops responding at the console, but I can sometimes login over SSH to the machine. In each case, load on the guest is .1 or lower. The lockup seems to spread the longer I run PW.

    Case in point: just last night, the guest OS was working fine, so I locked by screen and went to bed. Unlocked my machine, and the guest was hung. Couldn't login over SSH, attempted to force quit PW. The entire login session of the host OS then hung--couldn't use the finder, couldn't use the other application I had open (terminal, safari). Spinning Beachball of Death every where.

    I was able to login to the Mini over SSH. Load was ~.3, memory usage was approximately 1.2 gigs, which seems normal based on OS X's requirements and the 512MB I had allocated to the Solaris VM. Started killing processes owned by the user running Parallels. I was able to kill everything but one Parallels process. kill -9 -ing the process as root did not work either. Finally just rebooted the machine from my remote session.

    Okay, now my questions:

    1) Is anyone else having similar problems?
    2) What can I provide you (the devs) with to help fix this?

    I swear this isn't just a bitching session :) --I love the product and will ordering it after the first of May.
     

Share This Page