No Intel VT after computer going into sleep mode

[Mathias]

Hi,

I face a strange problem on a new computer: when I start the computer, VBox is working fine. However, if the computer is put to sleep (deep sleep mode, when only the RAM is powered) then my VMs will not run when the computer wake up. More precisely, the VMs will crash instantely if they were running or they will not start if they were not ((*) see below).

If I deactivate the use of the Intel VT instructions for a VM then the problem will not occur for that VM. So I figured out that maybe the computer does not start properly that part of the CPU after waking from sleep mode. Does anyone have already seen this problem ? Is it possible that my CPU is faulty ? or could it be a driver problem ?

The computer is running Windows 7 Pro with VBox 4.2.12 on an i7-3770K processor with a Z77X-D3H Gigabyte motherboard. All my drivers are up-to-date and the processor is running at its normal (non overclocked) speed.

Thanks for your help.

(*) to be exact, when I start a VM after waking up the computer from sleep mode (even loong after if I did not reboot it) the VM start to boot, e.g. the GRUB menu appears or the first screen of a linux installation CD is displayed (start the instalation/test the memory/boot normally/...) but then, then next step will just be a black screen doing nothing but echoing the keyboard input (sometime, not for all systems).

[dlharper]

This sounds like a host motherboard issue rather than one directly related to VirtualBox, even if it is in VirtualBox where it is showing up.

Waking-from-sleep issues tend to be rather motherboard specific, so it might be best to enquire on a forum devoted to your particular model. It might be that flashing the most recent BIOS ROM will solve it, or if not then some minor voltage or timing tweaks are likely to work, but I wouldn't like to guess which.

[Mathias]

Thanks for your reply.

I am well aware that the problem is probably not coming from Virtuabox. I am posting here because if others have already encountered this issue, this will be when using a virtualization software. As I found nothing usefull elsewhere I was hoping that someone here might have a solution.

I narrowed down the problem a little: I installed Linux on the same host and there the problem does not happen. So it seems that it is linked to the way windows is using the sleep mode and (maybe) not a motherboard issue.

Any feedback on similar issues will be appreciated (even more with solution).

Thanks!

[Perryg]

VirtualBox uses the guest additions in the guest to sync the time with the host. If the host time stops as in hibernation VirtualBox does not know it until the next sync interval, and if the time drift was not substantial the sync can take hours to recover.

You can however change the threshold to work around the issue.

Code: Select all

VBoxManage guestproperty set "<guest_name>" "/VirtualBox/GuestAdd/VBoxService/--timesync-set-threshold" 1000

You can tweak the value to fit your needs, just remember some programs don't like having the time changed a lot.

Backup the *.vbox control file first.

[glopez686]

Hi,

Did anyone ever find a solution to this? I am having the same issue, I am using:
vbox 4.3.16
windows 7 ultimate (host)
ubuntu 14.04 (guest)
motherboard: P8P67 Deluxe (lastest drivers)