Opened 16 years ago
Last modified 14 years ago
#2255 closed defect
Error VERR_INVALID_HANDLE when saving a snapshot. — at Version 5
Reported by: | Christian Elberfeld | Owned by: | |
---|---|---|---|
Component: | other | Version: | VirtualBox 2.0.2 |
Keywords: | Cc: | ||
Guest type: | Windows | Host type: | Linux |
Description (last modified by )
When I save the virtual machine state very I get the following error very often. After the error Message the virtual machine keeps running.
Mostly I get this error when more than one virtual machine is running.
I also had this Problem with Virtualbox 2.00 and 1.6.4.
Failed to save the machine state to '/home/chris/.VirtualBox/Machines/ CON-NBCE-VIRTUAL/Snapshots/{aff381cd-be96-4314-2eac-01def83676ec}.sav' (VERR_INVALID_HANDLE). Fehlercode: NS_ERROR_FAILURE (0x80004005) Komponente: Console Interface: IConsole {d5a1cbda-f5d7-4824-9afe-d640c94c7dcf}
Change History (7)
comment:1 by , 16 years ago
comment:2 by , 16 years ago
Summary: | Error VERR_INVALID_HANDLE → Error VERR_INVALID_HANDLE when saving a snapshot. |
---|
comment:3 by , 16 years ago
During this week it seems that the error occures every time I try to save an VM if i hat VMs running for al long time (approx 8 hours).
The Error occures at exactly 79% for both VMs and on each try. Shutting down Windows on the machine causes the VirtualBox processes to hang an block the CPU un the host so I had to kill them.
Disk space is no problem, my home partition has > 30 GB free space.
I'll pick up the logfiles on the next crash.
by , 16 years ago
Attachment: | Logs-1.zip added |
---|
by , 16 years ago
Attachment: | Logs-2.zip added |
---|
comment:4 by , 16 years ago
I attached the logs from both VMs. Both had the same error while Itried to save the state and both hang aftrer I tried ti shutdown the guest OS.
I tried to start and stop the VMs several times without problems. It seems that the problem only occures if the VMs are running several hours.
comment:5 by , 16 years ago
Description: | modified (diff) |
---|
Please attach the VBox.log of the failed session. Not sure what could cause the error. Are you running out of disk space by any chance?