VB locks up in Ubuntu 15.10
Posted: 13. Dec 2015, 19:10
I am in a Windows 10 system.
I have had AMD-V enabled in my BIOS and installed Ubuntu x64 guest (15.10).
System runs correctly and I can install Guest Additions.
And then usually within 10 minutes of actually using the system -- I am in fullscreen mode the two times this has happened now -- my system locks up; the guest doesn't respond anymore but I *also* cannot get back to Windows, so VirtualBox in its entirety locks up.
I am on a Six-core FX 6300 and I had 3 cores available to the VM at 90% max. I am going to try to install a 32-bit Ubuntu with no AMD-V to see if that changes things.
But is this something people recognise? I cannot use the system in this way. I was hoping to do some.... well whatever, but right now it is failing. The first time it happened I was able to get into the Process Manager and kill the VB process. The second time I wasn't so "lucky". The "bar" at the bottom of the screen that usually pops up with options (for the virtual machine) also doesn't pop up anymore. The entire thing just freezes.
It's not that my Windows system is actually frozen (for real) but I cannot get back to it because the VB process apparently still claims the foreground window.
This is the final content of my log file, I don't know what else:
I have had AMD-V enabled in my BIOS and installed Ubuntu x64 guest (15.10).
System runs correctly and I can install Guest Additions.
And then usually within 10 minutes of actually using the system -- I am in fullscreen mode the two times this has happened now -- my system locks up; the guest doesn't respond anymore but I *also* cannot get back to Windows, so VirtualBox in its entirety locks up.
I am on a Six-core FX 6300 and I had 3 cores available to the VM at 90% max. I am going to try to install a 32-bit Ubuntu with no AMD-V to see if that changes things.
But is this something people recognise? I cannot use the system in this way. I was hoping to do some.... well whatever, but right now it is failing. The first time it happened I was able to get into the Process Manager and kill the VB process. The second time I wasn't so "lucky". The "bar" at the bottom of the screen that usually pops up with options (for the virtual machine) also doesn't pop up anymore. The entire thing just freezes.
It's not that my Windows system is actually frozen (for real) but I cannot get back to it because the VB process apparently still claims the foreground window.
This is the final content of my log file, I don't know what else:
Regards, X.00:26:53.350629 VMMDev: SetVideoModeHint: Got a video mode hint (1920x1080x32)@(0x0),(1;0) at 0
00:26:53.356876 VBVA: InfoScreen: [0] @0,0 1920x1080, line 0x1e00, BPP 32, flags 0x1
00:26:53.356982 Display::handleDisplayResize: uScreenId=0 pvVRAM=000000000c2f0000 w=1920 h=1080 bpp=32 cbLine=0x1E00 flags=0x1
00:26:53.357161 GUI: UIFrameBufferPrivate::NotifyChange: Screen=0, Origin=0x0, Size=1920x1080, Sending to async-handler
00:26:53.364201 VBVA: InfoScreen: [0] @0,0 1920x1080, line 0x1e00, BPP 32, flags 0x1
00:26:53.372070 GUI: UIMachineView::sltHandleNotifyChange: Screen=0, Size=800x600
00:26:53.372113 GUI: UIFrameBufferPrivate::handleNotifyChange: Size=800x600
00:26:53.372145 GUI: UIFrameBufferPrivate::performResize: Size=800x600, Directly using source bitmap content
00:26:53.375740 VBVA: InfoScreen: [0] @0,0 1920x1080, line 0x1e00, BPP 32, flags 0x1
00:26:53.618844 GUI: UIMachineView::sltPerformGuestResize: Sending guest size-hint to screen 0 as 1920x1080
00:26:53.619729 GUI: UIMachineView::sltHandleNotifyChange: Screen=0, Size=1920x1080
00:26:53.619743 GUI: UIFrameBufferPrivate::handleNotifyChange: Size=1920x1080
00:34:48.870755 OHCI#0: Lagging too far behind, not trying to catch up anymore. Expect glitches with USB devices
00:34:49.025852 OHCI#0: Lagging too far behind, not trying to catch up anymore. Expect glitches with USB devices