Custom Query (16363 matches)
Results (958 - 960 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #7322 | duplicate | Guru Meditation when i using the FreeDOS guest system. | ||
| Description |
Guru Meditation in Miscellaneous moments on work. |
|||
| #7323 | duplicate | Guru Meditation in Windows95 guest system. | ||
| #17137 | obsolete | VirtualBox GUI unresponsive following long period of inactivity, yet VM still functioning | ||
| Description |
OK, this is an odd problem. First, my environment: Host: Windows 10 1703 x64 Guest: Ubuntu 17.04 with guest additions VirtualBox Version 5.1.28 r117968 VirtualBox and the VM work properly, with no operational problems. The issue happens when I return to the machine after leaving it unused overnight. In the morning, the VM window (I have it windowed, not full-screen) is white, with the usual "(Not responding)" appended in the title bar. Waiting 30 minutes or more does nothing. The unusual part is that the VM IS still running! If I kill the VM and restart it, I can see internal logs and file activities right up to the moment I killed it. That leads me to believe it is VirtualBox that is losing connection with the guest. Since I know of no way to connect again to the guest, I am forced to kill the VM and pray for minimal data loss. Log files attached. The current log is for the VM that is still running (but not responding) but the VBox.log.1 is for the same problem encountered yesterday when I killed the VM. This happens pretty regularly, whenever I leave the machine operational for extended periods. Two observations: VBoxHardening contains log spam for OpenGL32.DLL to the tune of 142k messages... This is similar to an old unresolved forum post (https://forums.virtualbox.org/viewtopic.php?f=6&t=64118) 29e8.2ce8: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ff839780000 'C:\WINDOWS\System32\OPENGL32.dll' 29e8.2ce8: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ff839780000 'C:\WINDOWS\System32\OPENGL32.dll' 29e8.2ce8: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ff839780000 'C:\WINDOWS\System32\OPENGL32.dll' 29e8.2ce8: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ff839780000 'C:\WINDOWS\System32\OPENGL32.dll' Second, my machine is connected by a KVM to another machine. Since I leave it to display my other physical machine overnight, the machine with the VM effectively has no display connected at all until the next morning. Nothing else seems to care about that fact, however since this is a display problem, I thought I'd mention that fact. Whenever I switch the KVM back and forth, The following message appears in the VBox.Log. The 8:26 messages were my last machine switch of the day yesterday, and the 23:39 are (I believe) when I first switched back to the machine this morning. Switching back and forth now no longer generates log messages, as the VirtualBox GUI is frozen. I can still see network activity on the VM as well as file accesses (in ResourceMonitor), and I have no doubt the machine is functioning in the background still. 08:26:16.367569 GUI: UIDesktopWidgetWatchdog::sltHandleHostScreenResized: Screen 0 is formally resized to: 0x0 x 1600x1200 08:26:16.367705 GUI: UIMachineLogic: Host-screen geometry changed 08:26:16.367734 GUI: UIDesktopWidgetWatchdog::sltHandleHostScreenWorkAreaResized: Screen 0 work area is formally resized to: 0x0 x 1600x1200 08:26:16.367750 GUI: UIMachineLogic: Host-screen available-area changed 23:39:35.144963 GUI: UIDesktopWidgetWatchdog::sltHandleHostScreenResized: Screen 0 is formally resized to: 0x0 x 1920x1200 23:39:35.145139 GUI: UIMachineLogic: Host-screen geometry changed 23:39:35.145316 GUI: UIDesktopWidgetWatchdog::sltHandleHostScreenWorkAreaResized: Screen 0 work area is formally resized to: 0x0 x 1920x1200 23:39:35.145336 GUI: UIMachineLogic: Host-screen available-area changed So, with all that information, is the problem indeed with VirtualBox? |
|||

