VirtualBox

Ticket #8798 (closed defect: obsolete)

Opened 3 years ago

Last modified 2 months ago

Async I/O thread probably stuck in operation

Reported by: aeickho Owned by:
Priority: major Component: other
Version: VirtualBox 4.0.4 Keywords:
Cc: Guest type: Windows
Host type: Linux

Description (last modified by frank) (diff)

One of the VDI files is located at an external iSCSI disk, which is mounted at the host, because of historical reasons. At high IO-load at the iSCSI disk an IO_ERR_TIMEOUT event occurs at Win2003r2 Guest and the drive located at that disk will be removed.

The Windows Eventlog is: "The device, \Device\Ide\IdePort0, did not respond within the timeout period."

at VBox Log: 03:46:39.867 PIIX3 ATA: Ctl#0: RESET, DevSel=0 AIOIf=1 CmdIf0=0xca (-1 usec ago) CmdIf1=0x39 (9777309 usec ago) 03:46:39.889 PIIX3 ATA: Async I/O thread probably stuck in operation, interrupting . . . 03:50:08.051 PIIX3 ATA: Async I/O thread probably stuck in operation, interrupting 03:50:08.061 PIIX3 ATA: Async I/O thread probably stuck in operation, interrupting 03:50:08.065 PIIX3 ATA: Ctl#0: RESET, DevSel=1 AIOIf=1 CmdIf0=0xca (-1 usec ago) CmdIf1=0x39 (57922482 usec ago) 03:50:08.075 PIIX3 ATA: Async I/O thread probably stuck in operation, interrupting

Attachments

VBox.log Download (91.6 KB) - added by aeickho 3 years ago.

Change History

Changed 3 years ago by aeickho

comment:2 Changed 3 years ago by udippel

I think I'm hitting the same thing here (see discussion thread as above). At least, the hard disk is thrashing, the LED is almost continuously on, and blocks the host processes to a grinding halt, while the guest 'LED' (virtual) is not too busy.

comment:3 Changed 3 years ago by pablo

Howdy,

I'm seeing a similar issue with my Guest VM Windows 2003 Server, VBox 4.1.2. The Host O/S is an `openSUSE 11.1'

This particular VM is used for SQL Server development and when under a lot of I/O pressure, I get data errors. I've tried configuring my devices as SATA and it's worst as I end up with my database getting corrupted. With IDE, I see errors in the `Event Viewer > System' but it appears I'm not getting data corruption.

Using the `Windows Event Viewer > System', I get two types of messages depending on the controller.

Controller  Message
==========  ============================================================================
IDE         The device, `Device\Ide\IdePort1, did not respond within the timeout period.
SATA        The device, `Device\Ide\iaStor0, did not respond within the timeout period.

When configured to use IDE, I also see the following messages in the VM's `VBox.log':

02:24:20.327 PIIX3 ATA: Async I/O thread probably stuck in operation, interrupting
02:24:20.338 PIIX3 ATA: Async I/O thread probably stuck in operation, interrupting
02:24:20.348 PIIX3 ATA: Async I/O thread probably stuck in operation, interrupting
02:24:20.358 PIIX3 ATA: Async I/O thread probably stuck in operation, interrupting
02:24:20.368 PIIX3 ATA: Async I/O thread probably stuck in operation, interrupting

I didn't check `VBox.log' for messages when using SATA. If it's useful, I can post those as well.

comment:4 Changed 2 months ago by frank

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

www.oracle.com
ContactPrivacy policyTerms of Use