I/O cache encountered error while updating data

[sferrell615]

Hi
I have VirtualBox installed on my laptop. I created a Windows 7 VM (25GBs, 2 CPUs), removed it from VirtualBox (I didn’t delete the VM), moved the VM to the company network, added the VM to VirtualBox, and left the VM on overnight for a couple of days. I found the Windows 7 VM paused with the message below. All that I could do was power it off. I pasted some of the info from the VBox.log file that stuck out to me and attached the VBox.log file; however, I don’t know what to look for. Can someone please help me figure this out? The Puppet VM that I have installed has had no issues.
Thanks!
Scott

An error has occurred during virtual machine execution! The error details are shown below. You may try to correct the error and resume the virtual machine execution. The I/O cache encountered an error while updating data in medium "ahci-0-0" (rc=VERR_INVALID_HANDLE). Make sure there is enough free space on the disk and that the disk is working properly. Operation can be resumed afterwards. Error ID: BLKCACHE_IOERR Severity: Non-Fatal Error

Info from the VBox.log that stuck out to me:
Chipset cannot do MSI: VERR_NOT_IMPLEMENTED
PIIX3 ATA: LUN#0: no unit
PIIX3 ATA: LUN#1: no unit
PIIX3 ATA: LUN#3: no unit
Chipset cannot do MSI: VERR_NOT_IMPLEMENTED
HdaCodec: can't open in fmt(freq: 44100)
HdaCodec: can't open out fmt(freq: 44100)
VMM: Thread-context hooks unavailable.
ERROR [COM]: aRC=VBOX_E_IPRT_ERROR (0x80bb0005) aIID={480b372c-c0b5-4c23-9bd7-dcbb85b1594c} aComponent={Display} aText={Could not take a screenshot (VERR_NOT_SUPPORTED)}, preserve=false
AIOMgr: Preparing flush failed with VERR_NOT_SUPPORTED, disabling async flushes

[rpmurray]

You're trying to run a virtual machine that is stored on a network share? That's not ... optimal.

[sferrell615]

yes, that is what i said. i am not trying to be optimum... this is a test box. if you tell me that the errors will go away if i move them to my C drive then i'll do it.
now, any idea what the logs are referring to? turns out the puppet (CentOS) server wasn't happy afterall. it was complaining about not enough memory (not storage), i believe. i have 8GB of ram and these 2 VMs equate to about a third of that, so not sure what the deal is there.
thanks
scott

[noteirak]

if you tell me that the errors will go away if i move them to my C drive then i'll do it.

Let's put it this way : You're lucky that's the only errors you got while running the VM on a network share. I never saw this kind of errror on a local drive, so yes, they should go away.
Not trying to be optimum is one thing, this is simply asking for troubles. Run the VM properly locally first, don't overcommit your RAM or cores, and then see how it goes.

[sferrell615]

alright, well i'm not going to argue but the previous SA had them out there and never reported any issues so i figured something went hay wire.
i moved them to my local drive... i'll report back in about a week!

[sferrell615]

ok, i'll admit it... YOU WERE RIGHT. moving it to my local drive seems to have resolved the issues.
THANKS
scott

[noteirak]

Always a pleasure to put a lost lamb on the right path