Desktop for Mac/Fedora Core Crashing

Discussion in 'Parallels Desktop for Mac' started by marcallen, Apr 11, 2007.

  1. marcallen

    marcallen

    Messages:
    2
    I'm trying to run either Fedora Core 5 or 6 in Parallels on a new Mac Pro, and I get consistent Mac BSOD while running parallels. I tried to dial down the memory to 512MB, I tried running it in full screen and not, I tried running it minimized and not. It consistently happens when either

    1) I am trying to do a massive yum upgrade
    2) I leave it sitting for a long time (overnight)

    I really don't know how else to troubleshoot this, I've wasted hours already and need Parallels to be reliable for me at work. From the stack trace below, it looks like it fails on memory allocation and hoses the kernel somehow. Any help would be appreciated. This is using Parallels build 3188. Thanks in advance,

    Marc

    panic(cpu 2 caller 0x00141505): zalloc: "kalloc.4096" (213416 elements) retry fail 3
    Backtrace, Format - Frame : Return Address (4 potential args on stack)
    0x48433978 : 0x128d08 (0x3cb134 0x4843399c 0x131de5 0x0)
    0x484339b8 : 0x141505 (0x3cbe40 0x3cb40c 0x341a8 0x3)
    0x48433a18 : 0x12d97d (0x1feda30 0x1 0x0 0x10)
    0x48433a48 : 0x12d99c (0x1000 0x1 0x48433a88 0xd3f0ca)
    0x48433a68 : 0x37faf8 (0x1000 0x1 0x0 0x0)
    0x48433a88 : 0xd3f572 (0x1000 0x63216e75 0x0 0x6d616769)
    0x48433ac8 : 0xd4249f (0x39e34000 0x400 0x0 0x6f6f7f)
    0x48433b18 : 0xd41476 (0x71c8084 0x18 0x200000 0x199193)
    0x48433bd8 : 0xd41862 (0x71c8084 0x48433eb8 0x18 0x83)
    0x48433d38 : 0xd3e8c7 (0x71c8084 0xc0185401 0x48433eb8 0x10)
    0x48433d68 : 0x1f05d7 (0xb000000 0xc0185401 0x48433eb8 0x81)
    0x48433da8 : 0x1e7411 (0x48433dd0 0x297 0x48433e08 0x721cbb8)
    0x48433e08 : 0x1df212 (0x83f14a4 0xc0185401 0x48433eb8 0x81)
    0x48433e58 : 0x331c4c (0x7290be0 0xc0185401 0x48433eb8 0x721cbb8)
    0x48433e88 : 0x34ffa8 (0x7290be0 0xc0185401 0x48433eb8 0x721cbb8)
    0x48433f58 : 0x379e23 (0x721cbb8 0x790e280 0x790e2c4 0x0) Backtrace continues...
    Kernel loadable modules in backtrace (with dependencies):
    com.parallels.kext.vmmain(2.2)@0xd3d000

    Kernel version:
    Darwin Kernel Version 8.9.1: Thu Feb 22 20:55:00 PST 2007; root:xnu-792.18.15~1/RELEASE_I386

    Model: MacPro1,1, BootROM MP11.005C.B04, 4 processors, Dual-Core Intel Xeon, 3 GHz, 4 GB
    Graphics: NVIDIA GeForce 7300 GT, NVIDIA GeForce 7300 GT, PCIe, 256 MB
    Memory Module: DIMM Riser A/DIMM 1, 1 GB, DDR2 FB-DIMM, 667 MHz
    Memory Module: DIMM Riser A/DIMM 2, 1 GB, DDR2 FB-DIMM, 667 MHz
    Memory Module: DIMM Riser B/DIMM 1, 1 GB, DDR2 FB-DIMM, 667 MHz
    Memory Module: DIMM Riser B/DIMM 2, 1 GB, DDR2 FB-DIMM, 667 MHz
    Bluetooth: Version 1.7.14f14, 2 service, 1 devices, 1 incoming serial ports
    Network Service: Built-in Ethernet 1, Ethernet, en0
    Network Service: Parallels Host-Guest, Ethernet, en2
    Network Service: Parallels NAT, Ethernet, en3
    PCI Card: NVIDIA GeForce 7300 GT, Display, Slot-1
    Serial ATA Device: ST3500641AS P, 465.76 GB
    Parallel ATA Device: SONY DVD RW DW-D150A
    USB Device: Hub, Up to 480 Mb/sec, 500 mA
    USB Device: Hub, Up to 480 Mb/sec, 500 mA
    USB Device: Flash Card Reader, Generic, Up to 480 Mb/sec, 500 mA
    USB Device: Bluetooth HCI, Up to 12 Mb/sec, 500 mA
    USB Device: Hub in Apple Pro Keyboard, Mitsumi Electric, Up to 12 Mb/sec, 500 mA
    USB Device: Apple Optical USB Mouse, Primax Electronics, Up to 1.5 Mb/sec, 100 mA
    USB Device: Apple Pro Keyboard, Mitsumi Electric, Up to 12 Mb/sec, 250 mA
    FireWire Device: FireLite, SmartDsk, Up to 400 Mb/sec
    FireWire Device: built-in_hub, unknown_value, Unknown
     
  2. ajwans

    ajwans

    Messages:
    24
    Have you run a memory checker on your Mac, perhaps you are hitting bad ram
    which you don't normally access.

    andy
     
  3. marcallen

    marcallen

    Messages:
    2
    A short test using Member showed no problems (in multiuser mode). Here is a sample from the system.log

    system.log.0:Apr 10 10:53:49 localhost kernel[0]: ParallelsConnectUSB(0x6e9f880)::start() Control service not started!
    system.log.0:Apr 10 10:53:49 localhost kernel[0]: ParallelsConnectUSB(0x6e9f200)::start() Control service not started!
    system.log.0:Apr 10 10:53:49 localhost kernel[0]: ParallelsConnectUSB(0x6c61f80)::start() Control service not started!
    system.log.0:Apr 10 10:53:49 localhost kernel[0]: NVDANV40HAL loaded and registered.
    system.log.0:Apr 10 10:53:49 localhost kernel[0]: ParallelsConnectUSB(0x6e99100)::start() Control service not started!
    system.log.0:Apr 10 10:53:49 localhost kernel[0]: ParallelsConnectUSB(0x6e99000)::start() Control service not started!
    system.log.0:Apr 10 10:53:49 localhost kernel[0]: PXS1: family specific matching fails
    system.log.0:Apr 10 10:53:49 localhost kernel[0]: Previous Shutdown Cause: 3

    Also

    system.log.0:Apr 10 11:06:22 mcallen-optimator crashdump[1030]: mds crashed
    system.log.0:Apr 10 11:06:23 mcallen-optimator crashdump[1030]: crash report written to: /Library/Logs/CrashReporter/mds.crash.log
    system.log.0:Apr 10 11:06:23 mcallen-optimator mds[1031]: crash data for /.Spotlight-V100 in volume /Volumes/FireLite 100 GB/.Spotlight-V100?!?\n
    system.log.0:Apr 10 11:13:27 mcallen-optimator kernel[0]: [Parallels] IPI stat: rescheduled 4 cpus out of 4 (Ok)
    system.log.0:Apr 10 11:13:27 mcallen-optimator kernel[0]: [Parallels] IPI stat: rescheduled 4 cpus out of 4 (Ok)
    system.log.0:Apr 10 11:13:43 mcallen-optimator diskarbitrationd[40]: Parallels [1202]:25031 not responding.

    and then I basically get

    system.log.0:Apr 10 11:15:21 mcallen-optimator kernel[0]: [err in mmIoWirePages ] : Failed to lock memory region -> ../host.Darwin/mm/io_memory.cpp:531
    system.log.0:Apr 10 11:15:21 mcallen-optimator kernel[0]: [err in hostLockPages ] : Failed to wire guest memory pages down -> ../host.Darwin/mm/generic.c:259
    system.log.0:Apr 10 11:15:21 mcallen-optimator kernel[0]: [err in pmmLockRegion ] : Can't Lock memory in PMM region -> pmm.c:206
    system.log.0:Apr 10 11:15:21 mcallen-optimator kernel[0]: [err in pmmLockRegion ] : Err2 -> pmm.c:237
    system.log.0:Apr 10 11:15:21 mcallen-optimator kernel[0]: [err in pmmLockRegion ] : Err3 -> pmm.c:241
    system.log.0:Apr 10 11:15:26 mcallen-optimator kernel[0]: [err in mmIoWirePages ] : Failed to lock memory region -> ../host.Darwin/mm/io_memory.cpp:531
    system.log.0:Apr 10 11:15:26 mcallen-optimator kernel[0]: [err in hostLockPages ] : Failed to wire guest memory pages down -> ../host.Darwin/mm/generic.c:259
    system.log.0:Apr 10 11:15:26 mcallen-optimator kernel[0]: [err in pmmLockRegion ] : Can't Lock memory in PMM region -> pmm.c:206
    system.log.0:Apr 10 11:15:26 mcallen-optimator kernel[0]: [err in pmmLockRegion ] : Err2 -> pmm.c:237
    system.log.0:Apr 10 11:15:26 mcallen-optimator kernel[0]: [err in pmmLockRegion ] : Err3 -> pmm.c:241
    system.log.0:Apr 10 11:15:28 mcallen-optimator kernel[0]: [err in mmIoWirePages ] : Failed to lock memory region -> ../host.Darwin/mm/io_memory.cpp:531
    system.log.0:Apr 10 11:15:28 mcallen-optimator kernel[0]: [err in hostLockPages ] : Failed to wire guest memory pages down -> ../host.Darwin/mm/generic.c:259
    system.log.0:Apr 10 11:15:28 mcallen-optimator kernel[0]: [err in pmmLockRegion ] : Can't Lock memory in PMM region -> pmm.c:206
    system.log.0:Apr 10 11:15:28 mcallen-optimator kernel[0]: [err in pmmLockRegion ] : Err2 -> pmm.c:237
    system.log.0:Apr 10 11:15:28 mcallen-optimator kernel[0]: [err in pmmLockRegion ] : Err3 -> pmm.c:241
    system.log.0:Apr 10 11:15:29 mcallen-optimator kernel[0]: [err in mmIoWirePages ] : Failed to lock memory region -> ../host.Darwin/mm/io_memory.cpp:531
    system.log.0:Apr 10 11:15:29 mcallen-optimator kernel[0]: [err in hostLockPages ] : Failed to wire guest memory pages down -> ../host.Darwin/mm/generic.c:259
    system.log.0:Apr 10 11:15:29 mcallen-optimator kernel[0]: [err in pmmLockRegion ] : Can't Lock memory in PMM region -> pmm.c:206
    system.log.0:Apr 10 11:15:29 mcallen-optimator kernel[0]: [err in pmmLockRegion ] : Err2 -> pmm.c:237

    until the kernel panic occurs. Interestingly, when I search for "Failed to wire guest memory pages down" on Google, only Parallels support formum posts come up... any word from the parallels guys if this is a known issue? I can post the whole log if anyone wants it, it is fairly large...

    Thanks

    Marc
     
  4. Eru Ithildur

    Eru Ithildur

    Messages:
    1,954

Share This Page