Consistent wake problems on a MacBookPro

sean.dudley said:
Do you mean to suggest that it's somehow acceptable for a public beta to hose a filesystem? If this was a CVS snapshot then I might accept that as part of the equation (though even then it's pretty extreme).

Is that what the mac community is coming to? We take filesystem corruption from a public beta as just part of the package?
Click to expand...

I don't think Parallels ist the direct reason for the FS corruption - the FS is corrupted because there was no shutdown / umount of the FS. The same problem can happen on any Kernel panic or switchoff without dismounting FS. Normally a journaled HFS should prevent but ...

BTW: my iMac 20" has the same problem - reboot on wakeup if Parallels where running, but FS was not corrupted (my crashed guest - Debian Linux - FS wasn't corrupted too ;-))
 
Last edited:
bripirie said:
Pausing the VM doesn't exactly work for me. That is, if the VM is paused, I don't get the reboot on wake from sleep. But if my MacBook has slept while the VM was paused, as soon as I un-pause, I get the reboot.

Is that the same for you?
Click to expand...

That's the behavior I'm seeing, too.

This is a really exciting product and one of the most useful things I'm going to buy for my Mac. I'm completely impressed by the speed. It makes Windows actually useable when you need it.

But I can't really use it much yet until they get the sleep issue, kernel panic on heavy network use, and lack of host-only networking worked out. After that, this will be a great product.

Kudos to the development team. (Now, when is the next update coming out? ;))
 
Frank Roscher said:
I don't think Parallels ist the direct reason for the FS corruption - the FS is corrupted because there was no shutdown / umount of the FS. The same problem can happen on any Kernel panic or switchoff without dismounting FS. Normally a journaled HFS should prevent but ...
Click to expand...

With a journaled HFS it does take something extra potent to actually damage the filesystem beyond repair. Something happened with the virtualization Parallels was doing I think.

I don't want to downplay this and have the Parallels team disregard it just to have this happen to someone else. I watched this happen again to another Macbook two days ago. So it is a pretty seriousconcern. Both myself and the other person were very much enjoying Parallels until this devastating bug showed up.
 
Some answers for you:

1. Network related kernel-panics are fixed in Beta2
2. Sleep problem will be fixed soon.
3. Kernel panic is main reason of the FS corruption.
 
Yes! By DEFINITION, betas have bugs - in general the purpose of a beta is to find those bugs - there's no rule that says betas aren't allowed to hose a file system, or any particular other class of bug - if that's a concern to you, then don't run a beta program, public or otherwise!

David Jameson


sean.dudley said:
Do you mean to suggest that it's somehow acceptable for a public beta to hose a filesystem? If this was a CVS snapshot then I might accept that as part of the equation (though even then it's pretty extreme).
Click to expand...
 
Now using Beta3

No reboot now in this version,
HOWEVER...

When the osx machine comes out of sleep mode, the parallels VM is in sleep mode itself showing the Windows XP screen saver logo but (a) no move of the mouse or (b) keyboard action will wake up the VM. No alternative but to force out VM and restart VM service. A shame.
Wanted to put this in front of the development team.

2.16 mac book pro / windows xp vm / beta 3
 
You must log in or register to reply here.
Back
Top