VirtualBox

Changes between Initial Version and Version 1 of Ticket #16660, comment 5


Ignore:
Timestamp:
Jun 6, 2017 12:20:20 PM (7 years ago)
Author:
Philip Seeger

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #16660, comment 5

    initial v1  
    1 Yes, this vm got stuck and I took a snapshot (using the VirtualBox Manager gui) before I killed the vm process. While the vm window was stuck, the vm state was shown as "Running" (gui); after killing the vm process, the state was "Aborted" (btw. I've had many crashes where the state did not switch to "Aborted" indicating a crash so that status seems rare, but that's off topic).
     1Yes, this vm got stuck and I took a snapshot (successfully; using the VirtualBox Manager gui) before I killed the vm process. While the vm window was stuck, the vm state was shown as "Running" (gui). After killing the vm process, the state was "Aborted" (btw. I've had many crashes where the state did not switch to "Aborted" indicating a crash so that status seems rare, but that's off topic).
    22
    33The next "vm window freeze" should happen in just a few weeks. I'll kill that vm without taking a snapshot and provide the core dump.

© 2023 Oracle
ContactPrivacy policyTerms of Use