I'm running Parallels 6, with an XP pro guest OS, on OS X Lion.
Earlier today, I tried to pause or suspend the VM while it was running (I don't remember which of those I clicked). Instead of going into an inactive state, the VM showed that darkened "frosty" image with the spinning busy wheel animation. After several minutes of relatively high CPU usage, I quit the parallels VM process. After that, the VM wouldn't boot.
Skimming around the end of the parallels.log file in the .pvm, I see
Code:
07-05 01:32:52.423 F /HddUtils:32998:3923/ hdd: fops 0
07-05 01:32:52.423 F /AbstractFile:32998:3923/ flock() error: 35
07-05 01:32:52.423 F /vdisk:32998:3923/ Error locking file /Users/c0w/Documents/Parallels/Windows XP.pvm/Windows XP-0.hdd/Windows XP-0.hdd [35]
07-05 01:32:52.423 F /vdisk:32998:3923/ Couldn't lock disk: 0x80021037
07-05 01:32:52.423 F /vdisk:32998:3923/ OpenDisk() returned error 0x80021037
07-05 01:32:52.423 F /LocalDevices:32998:3923/ [AppHDD] Can't open requested image [0x80021037].
07-05 01:32:52.423 F /LocalDevices:32998:3923/ [AppHDD] Disconnect
07-05 01:32:52.423 F /vm:32998:3923/ Sending question = PRL_WARN_UNABLE_OPEN_DEVICE
Also, the Windows XP-0.hdd does mount read-only in Parallels Mounter, after that program complains that it is "Unable to get write access to the virtual hard disk." The files look like they're all intact.
Can anyone suggest some way of getting the .hdd back into an operational state? The host system permissions appear to all be read-write for my user.
