Opened 13 years ago
Closed 12 years ago
#7929 closed defect (fixed)
Save State fails with VERR_MAP_FAILED => Fixed in SVN
| Reported by: | Mark Cranness | 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 (3)
Change History (13)
by , 13 years ago
| Attachment: | Copy of VBox.log added |
|---|
comment:1 by , 13 years ago
comment:2 by , 13 years ago
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}
by , 13 years ago
| Attachment: | logs and screenshot.zip added |
|---|
comment:4 by , 13 years ago
I just had the same problem in 4.0.8 again.. I attached the logs and a screenshot.
comment:5 by , 12 years ago
Hopefully fixed in the next maintenance release. I've prepared a Windows test build for brave testers.
comment:8 by , 12 years ago
| Summary: | Save State fails with VERR_MAP_FAILED → Save State fails with VERR_MAP_FAILED => Fixed in SVN |
|---|
comment:9 by , 12 years ago
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.
comment:10 by , 12 years ago
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
Fix included in VBox 4.1.8. Please open a separate ticket for unrelated problems.
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).