virtualbox.org

I had an issue when running Virtual Box 4.3.30 on a Windows 8.1 64 bits host running in a laptop computer and Linux 32 bits guests without graphics mode. I was using both Ubuntu Server 14.04 LTS and Debian 8 Jessy without any X Server implementation. Both guests had VBox 4.3.30 extensions installed

Issue appears when the Windows 8.1 Host has the cover closed or that it goes to suspend mode having the Linux guests running under Virtual Box. When resuming the host then the guests resume as well but if we shutdown the guests either via Host Key + H or running shutdown command inside the guest, then the Windows host crashes with a message IRQ something less than ... on VBoxDriver Next ... Apologize for not providing the full text, it was impossible to me to recover the full message before the host completes the reboot after the crash. I removed the Virtual Box extensions in the Debian 8 guest: same behavior.

Notice that when upgrading to Virtual Box 5.0, I don't see the same problem. Neither I noticed before when running Virtual Box 4.3.28 or earlier. I am unable to say if this happens on other systems that the one I described. I always had the issue when running with the laptop battery. I didn't try with sector.

I can confirm this.

I am running VirtualBox 4.3.30 r101610 on a Windows 8.1 host (laptop).

I have 64bit guest Debian-based (Ubuntu and Mint) virtual machine(s). When I shutdown the virtual machine instances (sudo shutdown -h now), the Windows 8.1 host then locks, forcing a hard, FULL restart of the host machine.

There is no error message provided during the event, as they host is fully locked and doesn't accept user input.

When the host completes the restart, Microsoft shows a basic warning message that something "bad" happened, and a Yes/No option to send a basic report to them.

I never experienced this behavior on 4.3.28. I will be rolling-back to the previous version, 4.3.28, as this is unacceptable.

I'm willing to provide logs from the host, if someone wants to help me identify where they are located (if they even exist).

Thanks.

The same problem, all my machines are broken with the new version...thanks a lot VirtualBox