Ticket #7929 (closed defect: fixed)
Save State fails with VERR_MAP_FAILED => Fixed in SVN
Reported by: | MarkCranness | Owned by: | |
---|---|---|---|
Component: | VM control | Version: | VirtualBox 4.0.0 |
Keywords: | Cc: | ||
Guest type: | Windows | Host type: | Windows |
Description
Running Windows 2008 R2 VM > Close > Save the machine state ... and state is not saved, error occurs then VM is permanently paused and cannot be restarted. See attached log.
The third time this happened the VM displays as "Inaccessible" in VirtualBox Manager with error something like (sorry): "cannot find disk with UUID . hexhex"
Problem is likely memory related. Save machine state works OK with 1500MB assigned to VM but fails with 2048MB assigned (from 3.25GB on host)
Attachments
Change History
comment:1 Changed 12 years ago by MarkCranness
When VM has 1500MB assigned, host Task Manager reports: Physical Memory Total: 3406252, Available: 963664.
When VM has 2048MB assigned, host Task Manager reports: Physical Memory Total: 3406252, Available: 452848 (in other words, it looks to me that the host still has sufficient memory to work with).
comment:2 Changed 11 years ago by MarkCranness
Also in 4.0.2 r69518. Message is:
Failed to save the state of the virtual machine .
Failed to save the machine state to 'C:\Documents and Settings\Mark\VirtualBox VMs\W2008Test\Snapshots\{GUID}.sav' (VERR_MAP_FAILED).
Details
Result Code: E_FAIL (0x80004005)
Component: SessionMachine
Interface: ISession {12f4dcdb-12b2-4ec1-b7cd-ddd9f6c5bf4d}
comment:4 Changed 11 years ago by a_catalin
I just had the same problem in 4.0.8 again.. I attached the logs and a screenshot.
comment:5 Changed 11 years ago by frank
Hopefully fixed in the next maintenance release. I've prepared a Windows test build for brave testers.
comment:8 Changed 11 years ago by frank
- Summary changed from Save State fails with VERR_MAP_FAILED to Save State fails with VERR_MAP_FAILED => Fixed in SVN
comment:9 Changed 11 years ago by wacher
A small thing to fix: I've resumed a virtual machine, but memory low. Expected result is a Paused VM state, but the VirtualBox simple crashed with guru mediation.
Changed 11 years ago by wacher
-
attachment
VBox.log.1
added
Memory low, not paused state but VM crashed.
comment:10 Changed 11 years ago by frank
- Status changed from new to closed
- Resolution set to fixed
Fix included in VBox 4.1.8. Please open a separate ticket for unrelated problems.