Void Linux discussion
 help / color / mirror / Atom feed
From: Antonio Malcolm <antonio...@gmail.com>
To: voidlinux <void...@googlegroups.com>
Subject: After Kernel Update to 4.1.6_1, Can't Boot Virtualbox Guests if Host I/O Cache Disabled
Date: Fri, 21 Aug 2015 04:27:42 -0700 (PDT)	[thread overview]
Message-ID: <7ad3c3a9-495e-4b6e-ab18-4cc8bf3bd6cc@googlegroups.com> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 1746 bytes --]

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.

[-- Attachment #1.2: Type: text/html, Size: 1856 bytes --]

                 reply	other threads:[~2015-08-21 11:27 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=7ad3c3a9-495e-4b6e-ab18-4cc8bf3bd6cc@googlegroups.com \
    --to="antonio..."@gmail.com \
    --cc="void..."@googlegroups.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).