High CPU usage and Kernel Panics

Discussion in 'Parallels Desktop for Mac' started by pixelpusher, Feb 8, 2007.

  1. pixelpusher

    pixelpusher

    Messages:
    3
    Lately everytime I use Parallels, my Macbook Pro will have a kernel panic after a short time. I have tried uninstalling and re-installing. I am using the RC2 version right now, but it has occurred with the last official build as well.

    I am seeing some errors in the console that I haven't been able to make any sense of, but maybe the Parallels team will know what is up with them. Here is the content the last entry in my panic.log file as well as the output I am seeing in system.log. The system.log errors seem of importance as the same ones just repeat and repeat as Parallels is trying to run.

    At this point, I can't even setup and install a new VM image as I get a kernel panic when windows is trying to install. Any help will be greatly appreciated so I can continue to use this great software.

    panic.log:
    *********

    Thu Feb 8 11:20:20 2007
    panic(cpu 0 caller 0x001414FE): zalloc: "kalloc.4096" (114954 elements) retry fail 3
    Backtrace, Format - Frame : Return Address (4 potential args on stack)
    0x25b13988 : 0x128d1f (0x3c9540 0x25b139ac 0x131df4 0x0)
    0x25b139c8 : 0x1414fe (0x3ca24c 0x3c9818 0x1c10a 0x3)
    0x25b13a28 : 0x12d994 (0x1f6da30 0x1 0x25b13a98 0x10)
    0x25b13a58 : 0x12d9b3 (0x1000 0x1 0x25b13a98 0x3d62a0ca)
    0x25b13a78 : 0x37dff8 (0x1000 0x1 0x25b13aa8 0x23f9ba00)
    0x25b13a98 : 0x3d62a572 (0x1000 0x400000 0x20438080 0x0)
    0x25b13ad8 : 0x3d62d49f (0x3802e000 0x400 0x0 0x46)
    0x25b13b28 : 0x3d62c476 (0x5206f04 0x18 0x200000 0x198cc3)
    0x25b13be8 : 0x3d62c862 (0x5206f04 0x25b13ec8 0x18 0x1a91da)
    0x25b13d48 : 0x3d6298c7 (0x5206f04 0xc0185401 0x25b13ec8 0x4f0d8b0)
    0x25b13d78 : 0x1ef2fd (0xf000000 0xc0185401 0x25b13ec8 0x81)
    0x25b13db8 : 0x1e624b (0x25b13de0 0x297 0x25b13e18 0x1cfbe5)
    0x25b13e18 : 0x1de0ef (0x51ef5ac 0xc0185401 0x25b13ec8 0x81)
    0x25b13e68 : 0x330295 (0x4f391a0 0xc0185401 0x25b13ec8 0x4cf99c4)
    0x25b13e98 : 0x34e562 (0x4f391a0 0xc0185401 0x25b13ec8 0x4cf99c4)
    0x25b13f68 : 0x378337 (0x4cf99c4 0x4f8b970 0x4f8b9b4 0x0) Backtrace continues...
    Kernel loadable modules in backtrace (with dependencies):
    com.parallels.kext.vmmain(2.2)@0x3d628000

    Kernel version:
    Darwin Kernel Version 8.8.1: Mon Sep 25 19:42:00 PDT 2006; root:xnu-792.13.8.obj~1/RELEASE_I386


    *********

    system.log:
    Feb 8 11:18:32 Simons-MacBook-Pro kernel[0]: [err in mmIoWirePages ] : Failed to lock memory region -> ../host.Darwin/mm/io_memory.cpp:531
    Feb 8 11:18:32 Simons-MacBook-Pro kernel[0]: [err in hostLockPages ] : Failed to wire guest memory pages down -> ../host.Darwin/mm/generic.c:259
    Feb 8 11:18:32 Simons-MacBook-Pro kernel[0]: [err in pmmLockRegion ] : Can't Lock memory in PMM region -> pmm.c:206
    Feb 8 11:18:32 Simons-MacBook-Pro kernel[0]: [err in pmmLockRegion ] : Err2 -> pmm.c:237
    Feb 8 11:18:32 Simons-MacBook-Pro kernel[0]: [err in pmmLockRegion ] : Err3 -> pmm.c:241
    Feb 8 11:18:33 Simons-MacBook-Pro kernel[0]: 31
    Feb 8 11:18:33 Simons-MacBook-Pro kernel[0]: [err in hostLockPages ] : Failed to wire guest memory pages down -> ../host.Darwin/mm/generic.c:259
    Feb 8 11:18:33 Simons-MacBook-Pro kernel[0]: [err in pmmLockRegion ] : Can't Lock memory in PMM region -> pmm.c:206
    Feb 8 11:18:33 Simons-MacBook-Pro kernel[0]: [err in pmmLockRegion ] : Err2 -> pmm.c:237
    Feb 8 11:18:33 Simons-MacBook-Pro kernel[0]: [err in pmmLockRegion ] : Err3 -> pmm.c:241
    Feb 8 11:18:33 Simons-MacBook-Pro kernel[0]: [err in mmIoWirePages ] : Failed to lock memory region -> ../host.Darwin/mm/io_memory.cpp:531
    Feb 8 11:18:33 Simons-MacBook-Pro kernel[0]: [err in hostLockPages ] : Failed to wire guest memory pages down -> ../host.Darwin/mm/generic.c:259
    Feb 8 11:18:33 Simons-MacBook-Pro kernel[0]: [err in pmmLockRegion ] : Can't Lock memory in PMM region -> pmm.c:206
    Feb 8 11:18:33 Simons-MacBook-Pro kernel[0]: [err in pmmLockRegion ] : Err2 -> pmm.c:237
    Feb 8 11:18:33 Simons-MacBook-Pro kernel[0]: [err in pmmLockRegion ] : Err3 -> pmm.c:241
    Feb 8 11:18:33 Simons-MacBook-Pro kernel[0]: [err in mmIoWirePages ] : Failed to lock memory region -> ../host.Darwin/mm/io_memory.cpp:531
    Feb 8 11:18:33 Simons-MacBook-Pro kernel[0]: [err in hostLockPages ] : Failed to wire guest memory pages down -> ../host.Darwin/mm/generic.c:259
    Feb 8 11:18:33 Simons-MacBook-Pro kernel[0]: [err in pmmLockRegion ] : Can't Lock memory in PMM region -> pmm.c:206
    Feb 8 11:18:33 Simons-MacBook-Pro kernel[0]: [err in pmmLockRegion ] : Err2 -> pmm.c:237
    Feb 8 11:18:33 Simons-MacBook-Pro kernel[0]: [err in pmmLockRegion ] : Err3 -> pmm.c:241
     
  2. VTMac

    VTMac

    Messages:
    340
    The best advice I could give you is to go back to 1970 if stability is you aim. It runs great on MBP, unless of course you are reliant on USB, and just doesn't have some of the nicer eye candy. I know they are calling this RC2, but honestly it's less stable than beta 3.
     
  3. pixelpusher

    pixelpusher

    Messages:
    3
    Thanks for the input. However, as I said, this issue is happening for me with the official release build as well. There seems to be some issue with Parallels locking the memory it needs.
     
  4. wgdixon

    wgdixon

    Messages:
    29
    I am getting this with 1970 as well.
     
  5. drval

    drval

    Messages:
    490
    Have you tried RC3 build 3170?
     
  6. pixelpusher

    pixelpusher

    Messages:
    3
    Actually, it turned out that one of my fans had died and this seems to be the reason I was getting the kernel panics when trying to use parallels....
     
  7. wgdixon

    wgdixon

    Messages:
    29
    How did you know one of your fans had died? FWIW, I have the *exact* same symptoms and syslog messages as pixelpusher. Pixelpusher, are there any third party extensions or other funky things installed on your MBP? Trying to rule out things, but so far nothing seems to help. For me this happens about the third time I either resume a VM or completely restart Parallels...doesn't seem to matter if I've shut down or just parked the VM, quit Parallels, or whatever...seems like something Parallels is doing is leaving some nasties that kick in down the road. I'm using 1970.
     
  8. svaillant

    svaillant

    Messages:
    1
    Same symptom on a MacPro 8Gb with 2 Linux RedHat VM when they begin to used all the memory assign to them.


    OsX 10.4.9, Parallels Build 3188
     
  9. dbrashear

    dbrashear

    Messages:
    6
    I get it with the new release build.
    panic(cpu 0 caller 0x00143144): /SourceCache/xnu/xnu-1051.1/osfmk/kern/zalloc.c:
    745 "zalloc: \"kalloc.4096\" (119367 elements) retry fail 3"

    I don't have xnu source for this but it looks like it's trying to get 119367 4096 byte elements. So then the question is why is it trying to allocate 119367 elements, anyway?

    If I were out of memory I'd expect other problems, and I have 11gb of free disk, so I should be able to swap.
     
  10. barefootguru

    barefootguru

    Messages:
    16
    I'm getting this under // 3188, OS X 10.4.9, and guest OS Windows XP. The system log messages start whenever lots of paging is needed, and if left, trigger a panic.

    Both my fans are fine, I used Hardware Monitor to test.
     

Share This Page