Quick Survey (About this Issue)
All,
It seems to me that this problem is actually 2 different issues combined, though they may be related to each other directly somehow. Please put in the replies to this thread which is your issue, and what your system configuration is. I have 3 Mac's all running Parallels so I have slightly different issues. Also 2 of my Macs have been running Parallels on the same .hdd image (untill 4560) for over 1 yr! They even upgraded to 3.0 (build 4128) just fine.
Problem #1) Kernal Panic with Parallels 3.0 build 4560 (was working on 4128)
My Mac's affected by this issue:
[Mac Mini Intel Core Duo 1.66Ghz, GMA950 graphics, 2Gb RAM]
[iMac Intel Core 2 Duo 1.83Ghz, GMA950 graphics, 3Gb RAM]
Problem #2) winxp.hdd image file corrupted after upgrade. (mine only had this issue after the Build 4560 upgrade, was working fine on 4128)
My Mac's affected by this issue:
[Mac Mini Intel Core Duo 1.66Ghz, GMA950 graphics, 2Gb RAM]
[17" iMac Intel Core 2 Duo 1.83Ghz, GMA950 graphics, 3Gb RAM]
[17" iMac Intel Core 2 Duo 2.0Ghz, ATI 128Mb graphics, 3Gb RAM]
The only Mac I could salvage the install (.hdd image) was the 17" iMac with the 2.0Ghz processor and ATI graphics. The reason is because this system only experienced the corrupt winxp.hdd image file. The .XML descriptor text file swap fixed this with no issues since. This iMac is running fine on 4560.
My other 2 Macs (Mac Mini 1.66Ghz & 17" iMac 1.83Ghz) will crash with Kernal Panic while running Parallels 3.0 build 4560. Once I reinstalled 3.0 build 4128 they both worked fine. My Mac Mini fared the worst because the winxp.hdd image was sooo corrupted that there was no luck getting it to work correctly after I fixed the .XML descriptor file. For the Mac Mini I did a complete remove and reinstall of Parallels and all of it's components. Then I tried 4560 and still got the Kernal Panic. So both Macs with the GMA950 graphics (Mac Mini and iMac 17") are running on 4128 now with no issues. My 3rd Mac (iMac 17" 2.0Ghz Core 2 Duo ATI equipped) runs with no issues on 4560. I don't understand!!!
When I performed the "Fix", I opened the .xml descriptor file with simple text/text edit. I have the "right click" turned ON in my mouse prefs, and you can select which app opens that file with a right click. You have to right click (or command click) on the .hdd image file and select "show package contents" (or something to that effect) to see these files. Make a copy of your existing .hdd/image data before you try to fix your image or you might loose your data.
If someone has a "universal" text string to overwrite the .xml descriptor file please post the exact text to paste in the .xml file. One of the users here helped me out with a copy of their .xml file even thought it wasn't the same exact size. It allowed me to get my .hdd image working (on previous 3.0 build 4128) well enough to get my data off of it. Then I reinstalled the whole mess and it's now working on 4128.
For anyone who gets this fixed, I highly recomend NOT updating to 4560 untill it's been proven NOT to cause the Kernal Panic on certain Macs. Of course this is my opinion as I do not work for Parallels so your mileage will varry.
~Mike R~
All,
It seems to me that this problem is actually 2 different issues combined, though they may be related to each other directly somehow. Please put in the replies to this thread which is your issue, and what your system configuration is. I have 3 Mac's all running Parallels so I have slightly different issues. Also 2 of my Macs have been running Parallels on the same .hdd image (untill 4560) for over 1 yr! They even upgraded to 3.0 (build 4128) just fine.
Problem #1) Kernal Panic with Parallels 3.0 build 4560 (was working on 4128)
My Mac's affected by this issue:
[Mac Mini Intel Core Duo 1.66Ghz, GMA950 graphics, 2Gb RAM]
[iMac Intel Core 2 Duo 1.83Ghz, GMA950 graphics, 3Gb RAM]
Problem #2) winxp.hdd image file corrupted after upgrade. (mine only had this issue after the Build 4560 upgrade, was working fine on 4128)
My Mac's affected by this issue:
[Mac Mini Intel Core Duo 1.66Ghz, GMA950 graphics, 2Gb RAM]
[17" iMac Intel Core 2 Duo 1.83Ghz, GMA950 graphics, 3Gb RAM]
[17" iMac Intel Core 2 Duo 2.0Ghz, ATI 128Mb graphics, 3Gb RAM]
The only Mac I could salvage the install (.hdd image) was the 17" iMac with the 2.0Ghz processor and ATI graphics. The reason is because this system only experienced the corrupt winxp.hdd image file. The .XML descriptor text file swap fixed this with no issues since. This iMac is running fine on 4560.
My other 2 Macs (Mac Mini 1.66Ghz & 17" iMac 1.83Ghz) will crash with Kernal Panic while running Parallels 3.0 build 4560. Once I reinstalled 3.0 build 4128 they both worked fine. My Mac Mini fared the worst because the winxp.hdd image was sooo corrupted that there was no luck getting it to work correctly after I fixed the .XML descriptor file. For the Mac Mini I did a complete remove and reinstall of Parallels and all of it's components. Then I tried 4560 and still got the Kernal Panic. So both Macs with the GMA950 graphics (Mac Mini and iMac 17") are running on 4128 now with no issues. My 3rd Mac (iMac 17" 2.0Ghz Core 2 Duo ATI equipped) runs with no issues on 4560. I don't understand!!!
When I performed the "Fix", I opened the .xml descriptor file with simple text/text edit. I have the "right click" turned ON in my mouse prefs, and you can select which app opens that file with a right click. You have to right click (or command click) on the .hdd image file and select "show package contents" (or something to that effect) to see these files. Make a copy of your existing .hdd/image data before you try to fix your image or you might loose your data.
If someone has a "universal" text string to overwrite the .xml descriptor file please post the exact text to paste in the .xml file. One of the users here helped me out with a copy of their .xml file even thought it wasn't the same exact size. It allowed me to get my .hdd image working (on previous 3.0 build 4128) well enough to get my data off of it. Then I reinstalled the whole mess and it's now working on 4128.
For anyone who gets this fixed, I highly recomend NOT updating to 4560 untill it's been proven NOT to cause the Kernal Panic on certain Macs. Of course this is my opinion as I do not work for Parallels so your mileage will varry.
~Mike R~