virtualbox.org

Hi,

I upgraded to Vbox 4.0 and now my W7 guest doesn't autosuspend when the host Ubuntu 10.10 goes to sleep. This used to work flawlessly in V3 of Vbox. I can of course select ACPI Shutdown in the guest and that works but I want this to happen automatically like it used to in V3. I've looked at the power options in both host and guest to see if there is any mention of sending or receiving ACPI notifications and can't see anything.

I've found a post that discusses writing a script to do this http://www.wiki.blue-it.org/VirtualBox# ... tandby_.2F_hibernation
but as it used to just work automatically I'd rather configure that to happen than implement a coded solution.

I have Vbox 4.0.2 PUEL, Ubuntu 10.10 64bit host, Windows 7 Ultimate 32 bit guest. I have installed guest additions and the USB extensions.

Thank you for reading this.

S

Hi

I don't mean to sound needy but can anyone help me with this?

Stewart

Why should the VM suspend when the Host does that? The whole point of VB is that it suspends the VM just a slight second before the Host goes, so you will never see it. If the Host doesn't suspend because of the VM, then there is something between the Host and VB that's causing issues with your system power management (unable to go to suspend mode). I've put my laptop to suspend and even hibernate a few times while a VM was running, no problem whatsoever and the VM ran right after I unlocked the system (when going to suspend, it locks my session using the screensaver).

Thanks for reading my post and responding.

It looks like I haven't made myself clear, sorry.

What I want to happen is that VB suspends the guest before the host gets suspended. Then, when the host is resumed the guest resumes too, at the point it was when it was suspended.

I am assuming that this isn't happening because when the host resumes the W7 guest is turned off and when I start the W7 guest it reports as it starts that Windows wasn't closed properly and asks whether I want to start in safe mode etc. This is what you get if you pull the power on a Windows machine.

So at the moment I cannot leave any applications open in the guest as any data in these applications is lost.

This worked automatically in V3 of VB but doesn't since I moved to V4 of VB.

I have the Guest Additions installed.

I cannnot see anything in Ubuntu's power management settings or in VB preferences or in VB itself or in the GA or in W7 that can be set to make this happen. Like I said, it used to work without any settings (that I remember) that needed to be configured in V3.

The script method I referred to in my original post works but this wasn't necessary in V3.

I hope that this is clearer!

Stewart

Oh, it was already perfectly clear. From your response, it's more obvious that you didn't understand what I said. It should just work, just as it used to. If it doesn't, then there is something that's aborting the VMs and the log will show more.

OK, thanks.

So there aren't any settings etc. I understand now, it should work like it used to but doesn't for me although it does for other people. So far this hasn't been reported by other users so there is no procedure to follow to resolve it.

Can you give me any pointers to what I should be looking for in the logs?

S

Since I haven't had a VM that aborted when I send the Host to hibernate or suspend, I have no idea. If you can provide the log here, I and others can take a look at it. Please attach it, instead of posting the contents.
If the system doesn't go to suspend when you tell it to, you can also provide the last lines of dmesg and syslog, they should also tell what is happening as to why it doesn't go to suspend.

Subscribing - I just updated to 4.1 yesterday and I'm seeing the same behavior (which was not there on VB3).

Sorry about the "me too" reply... I don't have time for much troubleshooting right now.

Woa, Sasquatch... Your responses come across as borderline mean and patronizing.

Stewart - I'm experiencing the same behavior. It seems that there is a bug in VB where before, when a guest would attempt to go to sleep or hibernate, it would pause the machine. Now, it's crashing: http://forums.virtualbox.org/viewtopic.php?f=2&t=38232

The easy fix is to change your Guest OS settings to not suspend/sleep after a certain amount of time.

Be well,

Tomás

Hi,

I'm not sure if this helps diagnose the problem but I changed the host to "never sleep". The guest settings stayed the same i.e. that it would sleep after 30 minutes.

It failed to sleep and resume properly. In other words, when I restarted the guest it said that it reported that it didn't close properly and offered to start in recovery, safe or normally. This seems to imply that the problem is in the W7 guest sleep/resume in Vbox rather than in the communication between host and guest.

I've attached the VBox log for this. I'll get the other logs next and attach to a second post.

Thanks again.

S

OK, I've attached the dmesg output to this post.

I only found a single entry in syslog at 17:51 (the time that the guest shut down. Here it is:

Feb 15 17:51:28 silver-P5Q-E kernel: [ 8712.098764] device eth0 left promiscuous mode

Hope this helps

S

Stewart - This is a known issue (see my post above). When the guest tries to go to sleep VB terminates it. In the previous versions it would pause the VM, and then resume it when activity was detected.

For the time being, change the guest settings to never go to sleep; the host settings have no bearing on this.

Thanks Tomas,

I've done as you suggested and you're right, setting the guest to never sleep solves the problem for me.

Thanks again and warm regards.

Stewart