VirtualBox

Ticket #15708 (closed defect: obsolete)

Opened 4 years ago

Last modified 5 weeks ago

Random I/O Cache Error VERR_INVALID_PARAMETER

Reported by: t.oster Owned by:
Component: VMM Version: VirtualBox 5.1.2
Keywords: I/O Cache VERR_INVALID_PARAMETER Cc:
Guest type: other Host type: other

Description

Hi, since a few Weeks I get those random I/O Cache errors which make my VM go to pause. I can then resume it without any problems and I cannot find out what causes that error. If I enable the "Host I/O Cache" in the SATA Controller, the error does not seem to occur, but this slows down my machine, so I cannot leave this enabled.

The exact error message is:

I/O cache: Error while writing entry at offset 87278690304 (16384 bytes) to medium "ahci-0-0" (rc=VERR_INVALID_PARAMETER)

it is written in file

VBox/VMM/VMMR3/PDMBlkCache.cpp

on line 2603 in function

static void pdmBlkCacheIoXferCompleteEntry(PPDMBLKCACHE pBlkCache, PPDMBLKCACHEIOXFER hIoXfer, int rcIoXfer)

I tried to delete all unnecessary snapshots (there are two left) and updated to 5.1, but the problem persists.

Sometimes it is once in a few days, sometimes multiple times a day.

Following System information:

Host System:

  • Ubuntu 12.04.5 LTS on kernel 3.2.0 64bit (problem was present on older kernels, too)
  • VirtualBox Version 5.1.2r108956
  • VDI File on a dedicated SSD (problem was also on HDD) with ext4 filesystem (49% of capacity used)
  • 4.8 of 31.8 GB RAM free during normal operation

GuestSystem:

  • Windows Server 2012 R2 (64 bit)
  • 16.2 GB RAM
  • IO APIC enabled
  • 2 vCPUs
  • PAE/NX enabled
  • VT-x/AMD-V enabled
  • Nested Paging enabled
  • VPID enabled
  • Audio Intel HDA enabled on PulseAudio driver
  • USB 1.1 enabled (not used)

Attachments

VBox.log Download (74.8 KB) - added by t.oster 4 years ago.
Log file with typical Error->Pause->Unpause sequence at the end

Change History

Changed 4 years ago by t.oster

Log file with typical Error->Pause->Unpause sequence at the end

comment:1 Changed 4 years ago by t.oster

I noticed, that I could not clone my VDI (latest snapshot) anymore, so the underlying problem may be a corrupted VDI. I had to recreate the VM and since then, the error did not occur anymore (yet).

comment:2 Changed 5 weeks ago by aeichner

  • Status changed from new to closed
  • Resolution set to obsolete
Note: See TracTickets for help on using tickets.

www.oracle.com
ContactPrivacy policyTerms of Use