Custom Query (16363 matches)
Results (1891 - 1893 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #9751 | obsolete | E_ACCESSDENIED for 'GUI/UpdateDlgWinID' when starting a VM | ||
| Description |
When starting any VM now from the Oracle VM VirtualBox Manager, I get a dialog with the message below. The VMs start OK. 58720551 is the "Oracle VM VirtualBox Manager" window, which has been running for 3 days. There is no log of this error in the VBox.log, but I've attached one anyway. The error is: Failed to open a session for the virtual machine Ubuntu 10.10 64-bit. Could not set extra data because someone refused the requested change of 'GUI/UpdateDlgWinID' to '58720551'. Details: Result Code: E_ACCESSDENIED (0x80070005) Component: VirtualBox Interface: IVirtualBox {c28be65f-1a8f-43b4-81f1-eb60cb516e66} |
|||
| #9752 | obsolete | Windows 7 XP Mode and Vbox Blue Screens | ||
| Description |
I cannot use VBOX with Microsoft's VM implementation and it keeps causing Blue Screens immediately upon launch of a Microsoft VM. For the time being I only use VBOX for BOINC's Test4Theory project and I already have my XP and Server 2003 VM's which run just fine on their own. But if VBOX is already running and I start XP or 2K3 server VM's it crashes VBOX then results in a blue screen when trying to restart VBOX. They used to run together for the most fairly stable as I can recall. Recently they have been failing to run together. |
|||
| #9760 | obsolete | VirtualBox deadlocks host system while running guest. | ||
| Description |
When I run a Guest OS, such as Ubuntu, Windows 7, Windows 8 and even others, the OS will, at random, freeze. When I go to reset the VM that also fails. If I open up Process Explorer and kill the VirtualBox Process there is one thread left over which sits in a "Wait:WrResource" state. The longer the system is left with this thread in a deadlock the more the other programs on the host OS are affected. Also once VB has deadlocked, the GUI manager can't be opened anymore if it is closed. I tried earlier versions of VirtualBox, all the way back to 3.2.12 and the problem exists in them as well. The best version seems to be 3.2.12 where the Guest will run for quite some time before experiencing this issue. The only way to get rid of the deadlocked thread is to use forcefully reset the Host Machine, Windows cannot kill it.
Steps to Reproduce
Host
Guest Forum post: https://forums.virtualbox.org/viewtopic.php?f=6&t=44944 |
|||

