Custom Query (16611 matches)
Results (10 - 12 of 16611)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #19039 | duplicate | Windows 10 VirtualBox uninstallation required for 6.0.12, or application within VM crashes. | ||
| Description |
Submitted for third-party in order to document rare issue encountered by a third party. Third-party virtualizes a physical classroom disk image with VirtualBox for portability, deployment, and testing, and has done so for years. A recent upgrade from 6.0.10 to 6.0.12 caused a commercial application within the VM to crash when accessing HTML files. We determined that UNINSTALLING 6.0.10 and then conducting a fresh installation of 6.0.12 solved this application crash, so something is not being uninstalled properly during the upgrade process. I apologize for the lack of log files. Third party encountered this bug on a production machine and deadlines prevented retrieval of additional troubleshooting assistance. 6.0.12 was already uninstalled and 6.0.14 freshly installed, without issue. |
|||
| #10610 | worksforme | rcu-bh detected stall in release 4.1.16 | ||
| Description |
Since upgrading to 4.1.16 I have started seeing stack traces in my log files. A sample is attached. |
|||
| #11300 | fixed | extraneous Creating process for, and Failed to open a session messages | ||
| Description |
Since upgrading to 4.2.4, when starting a VM I get a "Creating Process for Virtual Machine" pop-up that does not close, even after the VM starts. After the VM has been running for a few minutes, I will get a "Failed to open a Session for the Virtual Machine" message. Despite the messages, the VMs seem to run correctly. This happens even after the host machine has been rebooted. It does not seem to happen for all VMs or for every time a particular VM is restarted. The guest additions have been upgraded to 4.2.4. |
|||
