VirtualBox

Ticket #5042 (closed defect: fixed)

Opened 5 years ago

Last modified 5 years ago

Crashes on save machine state and resume machine state => Fixed in SVN/3.0.8

Reported by: john.doe Owned by:
Priority: critical Component: other
Version: VirtualBox 3.0.6 Keywords: crash same resume machine state aborted
Cc: Guest type: Windows
Host type: Mac OS X

Description

MacOS 10.5.8 host WindowsXP SP3 guest VirtualBox 3.0.6 (guest disk and installation created under VirtualBox 3.0.5)

15 out of all attempts (17 total) to "Save machine state" resulted in a VM crash and a status listed as "Aborted", which must is followed by a cold boot, windows chkdsk, and occasionally guest data loss from files open during the failed state save.

2 out of the 17 attempts successfully saved state, showing status as "Saved", but in both cases were followed by a VM crash on attempting to resume that state, again leaving the status listed as "Aborted" and requiring a cold start up.

Uploading examples of a log from each of the two types of state-related crash...

Attachments

Windows XP (virtual disk)-2009-09-20-12-43-54.log Download (59.4 KB) - added by john.doe 5 years ago.
Save machine state crash
Windows XP (virtual disk)-2009-09-18-10-20-08.log Download (44.2 KB) - added by john.doe 5 years ago.
Resume machine state crash
Windows XP (virtual disk)-2009-09-23-08-23-40.log Download (61.3 KB) - added by john.doe 5 years ago.
Different example of crash on save machine state

Change History

Changed 5 years ago by john.doe

Save machine state crash

Changed 5 years ago by john.doe

Resume machine state crash

Changed 5 years ago by john.doe

Different example of crash on save machine state

comment:1 follow-up: ↓ 3 Changed 5 years ago by frank

In the third log, the VM did not crash AFAICS.

comment:2 Changed 5 years ago by bird

  • Summary changed from Crashes on save machine state and resume machine state to Crashes on save machine state and resume machine state => Fixed in SVN

The assertion is wrong. Removed it. The fix will be included in 3.0.8.

comment:3 in reply to: ↑ 1 Changed 5 years ago by john.doe

Replying to frank:

In the third log, the VM did not crash AFAICS.

I apologize, I should probably use different wording-- the VM failed to save the machine state. It was marked as "Aborted" instead of "Saved", and there appeared to be no attempt to resume on next start. I lumped them together for that fact, but this could indeed be a different bug.

At first I, too, thought I had the wrong log; but they all looked about the same as that: no failed assertion or anything else standing out, except perhaps that the VM transitioned to "DESTROYED" instead of "SAVED", which, correct me if I am wrong, is not what it is supposed to do.

comment:4 Changed 5 years ago by sandervl73

  • Status changed from new to closed
  • Resolution set to fixed
  • Summary changed from Crashes on save machine state and resume machine state => Fixed in SVN to Crashes on save machine state and resume machine state => Fixed in SVN/3.0.8

comment:5 Changed 5 years ago by john.doe

Thank you for working on this.

It now appears to be fixed in 3.0.8. There is, however an exception-- it still exhibits this behavior if a USB device is attached. Aborted also happens if a USB devices is attached and a normal (non-saving state) shutdown is initiated. I opened a new ticket, since the original problem is now fixed, but similar symptoms occur when a USB device is attached. See #5146 .

comment:6 Changed 5 years ago by frank

Thanks for the feedback!

Note: See TracTickets for help on using tickets.

www.oracle.com
ContactPrivacy policyTerms of Use