VirtualBox

Changes between Version 2 and Version 3 of Ticket #16660, comment 8


Ignore:
Timestamp:
Jun 19, 2017 5:28:13 PM (7 years ago)
Author:
Philip Seeger

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #16660, comment 8

    v2 v3  
    12123 vms were affected, which indicates that this happens randomly. It's happening a lot recently, which makes working with VirtualBox difficult.
    1313
    14 This time, one of the frozen vms was not running in fullscreen mode. That means that it has a window border and title, but otherwise it behaved just like the other frozen vms (I didn't try Host + Home this time, but I'm sure it would not have worked). I made a screenshot with this frozen vm on the right and another frozen vm in fullscreen mode on the left. Note that it's not black because the guest system turned off the screen, that's not the case. It's black because the host's screen was black (screensaver) before I saw this. Switching workspaces, which are blue in this case, made the window blue. That's what I meant by "transparent".
     14This time, one of the frozen vms was not running in fullscreen mode. That means that it has a window border and title, but otherwise it behaved just like the other frozen vms (I didn't try Host + Home this time, but I'm sure it would not have worked). I made a screenshot with this frozen vm on the right and another frozen vm in fullscreen mode on the left. Note that it's not black because the guest system turned off the screen, that's not the case. It's black because the host's screen was black (screensaver) before I saw this. Switching workspaces, which are blue in this case, made the window blue. That's what I mean by "transparent".
    1515
    1616One of the affected vms has this at the end of the log:

© 2024 Oracle Support Privacy / Do Not Sell My Info Terms of Use Trademark Policy