Custom Query (16363 matches)
Results (448 - 450 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #13677 | fixed | 4.3.20 VMs fail to start after today's Windows update KB3004394 [BUGGY UPDATE; RECALLED BY MICROSOFT] | ||
| Description |
I am using Windows 7 64-bit Ultimate and use VirtualBox 4.3.20 r96997. After today's Windows updates VirtualBox fails to start any VM (I tried Windows, Linux, FreeBSD). The GUI presents the following error: Errorcode: E_FAIL (0x80004005) Component: Machine Interface: IMachine {480cf695-2d8d-4256-9c7c-cce4184fa048} The VM startup logs all show an error with crypt32.dll. I am attaching three logs. Please help resolve this problem, it is the second time (after 4.3.14) that Windows breaks VirtualBox, or the other way around. Thanks. |
|||
| #13813 | fixed | 4.3.20 Windows host: port-forwarded SSH connection closed on sleep/wake | ||
| Description |
Windows 8.1 host, Ubuntu 14.04 64-bit guest NAT networking SSH port-forwarded 2222 -> 22 On a Lenovo laptop, on wake after sleep the network connection is reset. Backtracked to 4.3.2, where the connection is not lost. |
|||
| #13777 | obsolete | 4.3.20 almost hung guest? (host win7 64-bit, guest Debian GNU/Linux 64-bit) | ||
| Description |
I have upgraded to 4.3.20 some time ago. Since then, I have experienced the following problems several times. Host Windows 7 64-bit. Guest Debian GNU/Linux 64-bit. The guest seems to hung almost:
I searched the bugtracker but could not find similar issues. Seen from the windows side when the problems occurred, sometimes VBox seems to be spinning on something and uses two cores assinged to it almost 100 %. Other times, it does not seem to use much CPU time. Very random. I am attaching a log when I had to power-reset the guest because it almost gets hung (again, the mouse cursor seems to be alive) so at least Vbox itself is alive, etc. I tried APCI reset, and then to my surprise, Debian GNU/Linux's panel for logout/shutdown, etc appears, but I cannot push any of the button although the cursor moves. Anyway, I am attaching Vbox.log when this happened. Oh, one more thing, when I tried to continue after [POWER RESET] during booting of Debian GNU/Linux from grub, the VBox itself became unresponsive, and I had to kill it by hitting [x] button on the upper right corner. (To be honest I forgot if I did this, or I killed it from task manager.) Anyway, Vbox.log *may* contain something there. I am afraid that the symptom seems to happen when I invoke heavy I/O, but not sure exactly when this happens. Since my PC has ECC memory I would like to rule out hardware problems, but who knows. The particular Vbox.log was created after I was disconnecting and connecting VBox network adaptor a few times to try to simulate network problems and when I was testing the behavior of the program, the problem struck. But other problems occurred without network adaptor removal, etc. TIA |
|||

