VirtualBox

Opened 6 years ago

Last modified 6 years ago

#17712 new defect

ed stat Guest VM with OS/2 does not resume from saved state

Reported by: Ingo Owned by:
Component: other Version: VirtualBox 5.2.10
Keywords: Cc:
Guest type: other Host type: Linux

Description

Since versions 5.1.36 and 5.2.10 VM-guest (OS/2 Warp4.5.2) does no longer resume from saved state. Up to and including VBox 5.1.34 all worked without any problems.

When trying to resume following error message pops up:

Für die virtuelle Maschine OS2 konnte keine neue Sitzung eröffnet werden.
    (translation: "for the VM OS2 no new session could be opened")
The VM session was aborted.

Fehlercode:NS_ERROR_FAILURE (0x80004005)
Komponente:SessionMachine
Interface:ISession {7844aa05-b02e-4cdd-a04f-ade4a762e6b7}

and vbox.log ends before the usual lines

00:00:03.338926 Changing the VM state from 'LOADING' to 'SUSPENDED'
00:00:03.338980 Changing the VM state from 'SUSPENDED' to 'RESUMING'
00:00:03.339245 Changing the VM state from 'RESUMING' to 'RUNNING'
00:00:03.339263 Console: Machine state changed to 'Running'
...

I have prepared a test-VM with OS/2 guest (just fresh installed, no guest-additions yet) called "Warp5". Will upload the complete tar.bz2-packed folder (it's only 293 MB) with which you easily can reproduce the bug. The VM is absolutely virgin, no snapshots and shut down. After importing it into VBox 5.1.24, just do the following steps:

  1. create a snapshot to preserve the vdi for testing
  2. start-up the VM, it will boot automatically to the desktop
  3. click on the desktop to catch the mouse pointer

do whatever you like, or even nothing

  1. release mouse pointer (ctrl right)
  2. close the VM and select "save the VM" reboot host (this is just to simulate normal usage and makes sure the bug shows up if present)
  3. start the VM again - it only takes a few seconds and with VBox 5.1.34 all is fine.

Try the same with VBox 5.1.36 or 5.2.10 and VM will crash for sure without any significant log entries for guest or host.

Remark: to cleanly shut down the OS/2-VM, just right click on the desktop and from the menu popping up select "Systemabschluß".

If additional information is needed, please let me know.

Change History (8)

comment:1 by Ingo, 6 years ago

I am not sure whether the upload (292MB) succeeded, please let me know if all is ok.

comment:2 by Ingo, 6 years ago

The complete VM can be downloaded from here, md5sums available as well:

https://c.gmx.net/.....

Last edited 6 years ago by Ingo (previous) (diff)

comment:3 by Socratis, 6 years ago

A related discussion about this problem took place in the "Discuss the 5.2.10 release" thread in the forums.

comment:4 by sunlover, 6 years ago

Looks like a bug already fixed in testbuilds: https://www.virtualbox.org/wiki/Testbuilds

comment:5 by Socratis, 6 years ago

@sunlover,

Can you be a little bit more specific? What revision of 5.2.11? Was it fixed in the trunk as well? Do you have the changeset revision that addressed it?

EDIT: Because I've been seeing a higher than normal "restore from saved state" reports, I'd like to know if/when this was fixed, so that I can direct users appropriately...

Last edited 6 years ago by Socratis (previous) (diff)

comment:6 by sunlover, 6 years ago

Fix is in 5.2 r122179 and 5.1 r122180. Trunk in r122177. So current 5.2 r122245 builds have the fix.

comment:7 by Socratis, 6 years ago

Excellent, thank you very much sunlover for the info!!!

That's why I couldn't replicate the @#$@ thing no matter how hard I tried; I'm on 5.2.11 r122245!!! :D

comment:8 by Ingo, 6 years ago

I can confirm the fix solves this bug for me, tested 5.1.37 r122402 - Thanks!

Note: See TracTickets for help on using tickets.

© 2023 Oracle
ContactPrivacy policyTerms of Use