VM worked fine last night. Booted fine this morning. Appears to have crashed during the day. When I got home, Mac was rebooted. Needed to reboot twice to get back to desktop. Weird. Ran Disk Utility and verified the disk and repaired permissions. Tried to start VM. VM BSOD. I can't read the BSOD message because Parallels flips back to the config screen too fast (what idiot programmed that feature???). I followed the re-install Parallels instructions on the sticky thread. For good measure, I booted single-user, did disk check. Still have BSOD. BSOD in Safe Mode as well. I'm pretty stuck at this point. I have another "spare" VM that boots fine (but of course it doesn't have any of my applications set up on it--it's just a toy for playing around with). I might could do some debugging if I could read the BSOD message. Is there anyway to get the BSOD to stay on the screen? Any other ideas?
What a spooky system... I have things booting again. Here is what I did: 1. Got my toy VM to boot. This took a couple of tries because I kept getting an error about parallels being unable to allocate virtual memory. This is unbelievable because I have 8Gb of RAM and over 700Gb free on the system disk (system disk is 1Tb; made up of 2 500Gb disks in a stripe set). spooky... 2. Went to the advanced panel of the HDD configuration pane and added the broken system's HDD file as a disk to my toy system (Toy system is exactly the same OS install just no apps.) 3. Did a disk check on the partitions from my broken system (all are NTFS which is pretty robust). Found and repaired errors. 4. Booted broken system... not broken anymore. My guess is that this approach (mount and disk check on other VM) may be of use to others who find themselves with broken systems. I would still very much like to know how to set things up so that I can read the BSOD message...
