hibernation issue

ACPI is a dream not come true.....and now hibernation issue:

1) running windows xp + latest and greatest updates

2) click on start ---> turn off computer ---> hibernate

3) wait a few seconds after this completes

4) start the vm image

5) Local area connection shows an yellow mark that it has a limited connectivity, ie; unable to get an IP from DHCP server / router

6) as well, you have to hold down control+alt (control) to move the mouse out of VM image!

The only solution is shutdown / reboot the vm image.

Please stop adding colorful menu / icons and fix the ACPI and other reported issues by your customers. Thanks!

 

hibernate is greyed out on my VM
and I never used it

Hugh W

 

On XP image, please enable "APM" (Advanced Power Management) support. This can be found ---> Screen Saver tab ---> Power. As well, enable Hibernation mode. After that, you have the option available, ie, you can either set a timer to automate hibernation or manually do this.

This is NOT a show stopper for most people. However, it is an issue for those of us who make $$ doing computer work!!! It's a broken feature under each and every version of Windows out there... win95, 98,......Vista!

I am not sure what is with all these good / positive reviews all over the 'net about this program really. These reviews seem like only installing the program, launch it and off you go... it passed and it's kick a$$ product! hmmm.....

During my research, found an interesting comment about Parallels..... it feels like a hack product! I now agree. Parallels developers seem like looking for "shortcuts" only instead of proper coding... sorry folks. This is my job too and I know how difficult it is....however, I would get fired if I wanted to do things like this

 

Just as I guessed, Vista has problem with Hibernation too. This one as soon as I clicked on Sleep / Hibernation, VM freezes! Very bad, indeed.

Well, I really like this product but maybe those who switched already are smarter than me!

 

I think it is best to remember you are running a Macintosh and to let that system control power saving

Hugh W

 

If you want the VM to hibernate, why not just click the VM's "pause" icon? Or are you coding for Windows under Parallels and need to test the robustness of this feature? The latter seems a bit beyond the scope of Parallels intentions at the moment.

When I have used Parallels with Vista, I don't think I bothered with the sleep/hibernation feature because the VM seemed to automatically "pause" after a given time of inactivity anyway. I remember the icons being darkened, and after clicking on them, getting a message like "Please wait while the VM resumes" or something to that effect.

 

My VM hung too when initiating hibernation from Vista on my bootcamp partition. I hope it will be fixed soon.

 

Why would you want to hibernate anyway? I would do what Hugh says and let your primary OS do the power settings/conservation. I do it and have no issues. Again this is a VM and NOT full machine so don't treat or expect it work exactly like one. I would turn off hibernation in XP and not use it. I've had normal machines in the many networks we support have hibernation issues. It's not a Parallels issue. 99.9% of the time it's another software conflicting with the hibernation state. Read the Microsoft forums and you'll see this issue is rampant. Also, if you have over 2GB of RAM, XP has an issue with hibernation and you need to get a patch from Microsoft. It fixed the issues I was having on about 45 workstations.

Hope this helps!!

 

If I weren't concerned about power consumption (and attached USB equipment) I'd use the sleep feature. The issue I have with Sleep feature is that it responds to any key and mousebutton. That's annoying. Perhaps I could unplug keyboard and mouse
Anyway...
I'm very used to Windows' hibernation feature. It's handy (I even use it at work to quickly return to whatever I was doing to other day). I cannot imagine how Mac (and early Linux) users don't/didn't miss it.
Anyways, Parallels' Suspend feature is greyed out since it's running in bootcamp mode. VMware can handle it so it's either a bug, unimplemented feature, bad documentation or me not reading it.
But I'll try to change some memory settings. Perhaps that'll solve it.