Vbox crashes with Error ID: BLKCACHE_IOERR

[jlcenter]

My Windows 8.1 Pro guest (Ubuntu 14.04.1 host) locked up with the following message:

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_DEV_IO_ERROR). 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

Even though it said "Non-Fatal Error", it was definitely fatal! I saw several previous bug tickets reported for this, but not for the most recent version. I'm attaching the log file.

[jlcenter]

Last log file

[jlcenter]

This log file was created at time of crash

[jlcenter]

I had another crash, apport reported:

Version: virtualbox-4.3.4.3.16-95972~Ubuntu-raring VirtualBox crashed with SIGABRT in libc_message()

[jlcenter]

I just upgraded to 4.3.18 & dkms complained that:

could not locate dkms.conf file. file does not exist

but, I found the file for virtualbox at /usr/share/virtualbox/src/vboxhost/dkms.conf. Is this the wrong place?

[Don Hughes]

I am haveing the same issue with:

Windows 7 guests SuSE Linux hosts VB 4.3.18

Use Host I/O Cache is not checked

This started happening on multiple different physical machines after upgrading to VM 4.3.18 and Linux 3.17.1.

The error can be triggered by trying to paste from the shared clipboard.

Reverting to the 3.11 kernel seems to resolve the issue, but, unfortunately, I then have issues with the AMD video driver which causes a hard crash, so this recoverable error seems slightly preferable.

Will attach log.

[Don Hughes]

Log file with BLKCACHE_IOERR when doing paste from clipboard.

[Frank Mehnert]

jlcenter, your problem must have to do with btrfs. VBox.log clearly shows that your virtual disk image files are located on a btrfs partition. You should mark all these files as well as the snapshots directory as No_COW, see ​here. Btw, marking existing files as No_COW is not sufficient, you have to copy them once again!

don, on which file system are you virtual disk image files stored (/Data/VMs/Wren3/)?

[Don Hughes]

/Data/VMs/ is a btrfs partition. It was mounted nocow.