Custom Query (16363 matches)
Results (454 - 456 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #14002 | fixed | 4.3.27-99265 does not work with Server 2003 / XP64 | ||
| Description |
Title says it all. Virtualbox.exe does not start. No error message no nothing. Installed it twice after removing the previous installation. Nothing in the event log either. 4.3.27-99222 works fine. |
|||
| #14341 | fixed | 4.3.28 & 4.3.30 guest additions prevent logout -> fixed in 4.3 and later as of August 5 2015 | ||
| Description |
I just installed 4.3.30 of VB on my Windows 7 machine. I run a Linux Mint KDE 17.1 64bit VM in that VirtualBox. After I installed 4.3.30, I installed the 4.3.30 guest additions. Then I shutdown the VM. I then restarted the VM, logged in, and after it had completed logging in, I attempted to logout. I got a black screen, where I could not type, it would attempt to capture the mouse when I clicked on it, but nothing else worked and I had to power the VM off to shut it down. So I reinstalled 4.3.28, reinstalled the 4.3.28 guest additions and tried the same exact scenario w/ exactly the same results (obviously I hadn't tried logging off of this VM since I had installed 4.3.28). However I also have an older VM which I started up and logged in on, and it was running 4.3.26 guest additions. That VM had no problems returning to the display manager login screen on logout. And that worked both in VB 4.3.28 and in 4.3.30 (after I had installed it again). So I think it's safe to say the issue is in a change in the Guest Additions from version 4.3.26 to 4.3.28, that was not changed in 4.3.30. I think this may be related to the KDM display manager, as I think I recently created another VM that was otherwise similar (Linux Mint 17.2 64bit KDE) that was using MDM and it returned to the DM login screen when I logged out. |
|||
| #14785 | fixed | 4.3.30 -> 5.0.6: aborted VMs, host lockups | ||
| Description |
Recently migrated from 4.3.30 to 5.0.6. Since that, I occasionally observe "aborted" VMs when saving state of a a virtual machine. Sometimes but not always a <VM>\Snapshots\*.SAV file is created as expected. Host is Win7 x64, guests are Win7 x64, XP x86 and FreeBSD x86. No clear indication to what this might be related. Logfiles don't show anything unusual either. Upgrade to 5.0.8 did not help. In addition, the host has completely locked up several times since the upgrade: Screen remains lit, but no mouse move, no disk indication, etc. Downgraded to 4.3.30 (with a bit of pain due to not downward compatible configuration), and everything is rock solid again. Guest additions always at the host's VBox revision. The host is a 1st gen i5 mobile. Let me know which logs / debugs I should provide. |
|||

