From mboxrd@z Thu Jan 1 00:00:00 1970 Date: Fri, 21 Aug 2015 04:27:42 -0700 (PDT) From: Antonio Malcolm To: voidlinux Message-Id: <7ad3c3a9-495e-4b6e-ab18-4cc8bf3bd6cc@googlegroups.com> Subject: After Kernel Update to 4.1.6_1, Can't Boot Virtualbox Guests if Host I/O Cache Disabled MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_Part_9212_1065995497.1440156462549" ------=_Part_9212_1065995497.1440156462549 Content-Type: multipart/alternative; boundary="----=_Part_9213_1440148915.1440156462550" ------=_Part_9213_1440148915.1440156462550 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit After updating to kernel 4.1.6_1, I can no longer boot Virtualbox guests if "Use Host I/O Cache" is disabled. It doesn't appear to matter what the guest is. I have several Void guests for development, and one Windows 7 guest for testing. All of them are using SATA with AHCI mode as the storage interface. The specific error Virtualbox throws is: 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 (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 The Void host is using the XFS file system. Not sure if that makes a difference (I read about a bug a few years back in the Linux kernel which results in EXT4 users also needing Host I/O Cache enabled, and wonder if it's related). Anyone else encountered this issue? Enabling Host I/O Cache is an acceptable workaround (certainly not a deal-breaker), but I would prefer to determine the cause of the issue, and solve it there. I had disabled it to save on some resources. I'm runnning everything from an SSD, so things are fast enough that I'd rather avoid some of the performance and reliability pitfalls which might occur from using the I/O cahce with multiple VMs running simultaneously. I'm not certain, just yet, if it's a kernel issue, or if the virtualbox-ose/virtualbox-ose-dkms XBPS package needs an update. I already tried a force-reinstall of the dkms package. The only thing which corrects the issue is enabling Host I/O Cache. ------=_Part_9213_1440148915.1440156462550 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable
After updating to kernel 4.1.6_1, I can no longer boot Vir= tualbox guests if "Use Host I/O Cache" is disabled.
It doesn&#= 39;t appear to matter what the guest is. I have several Void guests for dev= elopment, and one Windows 7 guest for testing.
All of them are using SAT= A with AHCI mode as the storage interface.

The specific error Virtu= albox throws is:

An error has occurred during virtual machine execut= ion! The error=20 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 upd= ating data in medium (rc=3DVERR_INVALID_HANDLE). Make sure there is enough = free space on the=20 disk and that the disk is working properly. Operation can be resumed=20 afterwards.

Error ID: BLKCACHE_IOERR
Severity: Non-Fatal Error<= br>
The Void host is using the XFS file system. Not sure if that makes a= difference (I read about a bug a few years back in the Linux kernel which = results in EXT4 users also needing Host I/O Cache enabled, and wonder if it= 's related).

Anyone else encountered this issue?

Enabling= Host I/O Cache is an acceptable workaround (certainly not a deal-breaker),= but I would prefer to determine the cause of the issue, and solve it there= .
I had disabled it to save on some resources. I'm runnning everythi= ng from an SSD, so things are fast enough that I'd rather avoid some of= the performance and reliability pitfalls which might occur from using the = I/O cahce with multiple VMs running simultaneously.

I'm not cert= ain, just yet, if it's a kernel issue, or if the virtualbox-ose/virtual= box-ose-dkms XBPS package needs an update. I already tried a force-reinstal= l of the dkms package.
The only thing which corrects the issue is enabli= ng Host I/O Cache.
------=_Part_9213_1440148915.1440156462550-- ------=_Part_9212_1065995497.1440156462549--