virtualbox.org

Hi

I am wondering if you guys have faced a similar problem and how you solved it:

The host is ubuntu 14.04 lts 64 bit. The guest is windows 7 64 bit. VirtualBox Version 5.0.20 r106931.

Here are the steps to the problem: I run VB, open the guest, then close the guest and close VB. I put down the screen so the laptop (acer) goes to hibernation.

When I lift the screen, the laptop refuses to start. I think the light of the power button is on.

I have to disconnect the power, take off the battery and only then it will start. Some times this causes problem to the network-manager which I have to reinstall.

Since VirtualBox isn't running when the host is suspended, what makes you think this is a VirtualBox problem?

And to answer your question: no, I know of no-one else reporting this problem - though saying that is usually an invitation for someone to join up to say "me too" just on the basis of the topic title.

mpack wrote:Since VirtualBox isn't running when the host is suspended, what makes you think this is a VirtualBox problem?

I started having these problems the last two months, the same time I started using VB more often. Yesterday I made a test. I followed the steps I described and indeed the laptop froze. I am not 100% sure, but it is the best scenario I have to recreate the problem.

Maybe VB is only indirectly causing it. Maybe even after closing, VB leaves data in memory or the swap area. Hibernation is trying to write to the swap area, swap becomes full and then it crashes? My swap (/dev/sda2) is 6.05 GB and my RAM is 6 GB.

There is an easy way to test this theory; uninstall VirtualBox.
Do not worry, your VMs will not get deleted or disappear.
• If you see the problem go away, we could investigate it further.
• If the problem persists, you'll know it's not VirtualBox that's causing it.

Oh, one more thing. Before you take your host to hibernation, can you make sure that there is no VBox* or VirtualBox* process running?

Hello socratis

I just made the test again and nothing happened (laptop did not freeze).

Before shutting the screen, the swap ise was just 1%. Did not look at the RAM, but I am sure it was low. When VB is running RAM is at about 85%.

If it was consistent I would be able to troubleshoot better.

I think it's about time we saw a VM log: with the VM fully shut down, right click it in GUI. Select "Show Log" and save "VBox.log" (ONLY) to a zip file. Attach the zip here.

Here is the log.

I don't see any obvious mistakes in the log. E.g. you are not exhausting host RAM, in fact not even close. You are OTOH assigning both cores to the VM (usually not a good idea), but I don't see how that can matter when the VM isn't running. So, I still doubt that VirtualBox has anything to do with this. I suspect some kind of host hardware problem, perhaps indirectly provoked by the resource load of running VM.

mpack wrote:You are OTOH assigning both cores to the VM (usually not a good idea), but I don't see how that can matter when the VM isn't running.

While the guest is on, I do very light stuff (send email) on the host. Is this ok?

Maybe I should be looking at the ubuntu syslog to find the error.

Thank you very much.