Parallels Stopped Working After Upgrade Help Please!

Discussion in 'Installation and Configuration of Parallels Desktop' started by Alex77777777777, May 19, 2009.

  1. Alex77777777777

    Alex77777777777 Bit poster

    Messages:
    2
    Parallels was running fine and then after a scheduled upgrade i receive the error -

    "Unable to load Parallels driver. Restart your Mac and try again" and After you click OK you get another message: "Unable to start the virtual machine. An unexpected error occurred while starting the virtual machine. Contact the Parallels support team for assistance." And VM does not start.

    I googled this problem and found this info -

    Check if prl_hypervisor.kext is loaded.

    sudo kextstat |grep prl

    You can either load it or restart your Mac:

    sudo kextload /System/Library/Extensions/prl_hypervisor.kext/

    I am no computer expert but i have typed these into terminal and receive the following info -

    Macintosh:~ Alex$ sudo kextstat |grep prl
    Password:
    Sorry, try again.
    Password:
    94 0 0x7a5000 0x7000 0x6000 com.parallels.kext.prl_netbridge (4.0 3810.351321) <6 5 4 2>
    Macintosh:~ Alex$ sudo kextload /System/Library/Extensions/prl_hypervisor.kext/
    kextload: /System/Library/Extensions/prl_hypervisor.kext: no such bundle file exists
    can`t add kernel extension /System/Library/Extensions/prl_hypervisor.kext/ (file access/permissions) (run kextload on this kext with -t for diagnostic output)
    Macintosh:~ Alex$

    When i restart the computer i just get the same problem.

    Please assist ASAP as I need to use Parallels for my work.

    I dont know if this is relevant but I run Parallels through boot camp.

    Many thanks
     
  2. Elric

    Elric Parallels Team

    Messages:
    1,712
    Hi,
    Could you please clarify - was it an upgrade of Parallels Desktop or upgrade of Mac OS to 10.5.7 ?

    Please try for the first to uninstall the Parallels Desktop and install it again
     
  3. Paul Barnard

    Paul Barnard Member

    Messages:
    42
    Alex. Sounds like a quick repair permissions on your HD might help. Open Disk Utilities, select your HD and click repair permissions.
     

Share This Page