Hello, I hadn't had an KP since beta3, and had been running RC for awhile without as well. I made a change last night and got a KP within a half an hour. I'd send the panic log, but this one didn't write a log! What I changed: Fear of losing data on my mac hard drive led me to creating my parallels virtual disk within a sparse disk image stored on a network share on my fileserver. Things ran fine that way. But, last night, feeling confident with the stability since beta6, I moved the .hdd image to my local hard disk and started the VM from it. It was a little faster, and I was happy. For about a half hour... Then, KP! WinXP home was the guest OS, and uTorrent was the only app running within windows, so there was some very heavy networking going on. I'm on a dual core mac mini. I moved the .hdd image back to a sparse disk image on my server and it's been running all night stable. I've also had the strange occasional pegging of one of the cores when parallels is running, regardless of what was running within windows.
Further thoughts... I was pondering what might be different on the local filesystem that would cause instability vs running within another volume. Spotlight. Doesn't spotlights kernel extension watch for filesystem changes and update it's index accordingly? Perhaphs there's some contention between the spotlight kext and the hypervisor that parallels is? I'm sure that the running guest os is causing tremendous filesystem activity as it's accessing the .hdd image. I'm not brave enough to test this by running back under my local filesystem, I don't want to lose anything important. Someone who is running with the .hdd file on your local volume, which is probably most of you, add it's folder to spotlights privacy column in the preference pane. I almost wonder if that would speed things up as well?
