VirtualBox

Ticket #9859 (new defect)

Opened 2 years ago

Last modified 5 months ago

[4.1.X regression] Event ID 9: did not respond within the timeout period

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

Description

It's probably a Virtual Box 4.1.6 regression but it takes up to 2 minutes to initialize SATA HDD (virtual or real - doesn't matter) using Intel iastor driver.

Intel driver says that event ID 9 occured after the OS has finally booted.

Host OS: Linux 3.0.8 x86 vanilla

Guest OS: Windows XP (BartPE bootable CD) SP2 x86, iastor.sys 7.6.1.1002, iastor.inf 7.6.1.1002

Shutdown sequence also takes ages to complete.

Chipset type doesn't matter (PIIX3 and ICH9 both exhibit this behaviour).

Attachments

WindowsXPE.7z Download (19.5 KB) - added by birdie 2 years ago.
he entire virtual machine, excluding a bootable Windows XP SP2 BartPE CD-Rom

Change History

Changed 2 years ago by birdie

he entire virtual machine, excluding a bootable Windows XP SP2 BartPE CD-Rom

comment:1 follow-up: ↓ 2 Changed 2 years ago by frank

Which was the last VirtualBox version where you booted this guest successfully?

comment:2 in reply to: ↑ 1 Changed 2 years ago by birdie

Replying to frank:

Which was the last VirtualBox version where you booted this guest successfully?

I cannot be sure, it could have been 4.1.4 or even 4.0.X.

comment:3 Changed 2 years ago by ColtGTi

I am having the same issue. Same ATAPI error with Id 9. This error is from my guest Windows Server 2003 R2, It’s an Spanish version the exact error is: Origen: atapi Id de suceso: 9 Descripción: "El dispositivo, \Device\Ide\IdePort1, no respondió en el tiempo de espera permitido."

The host server is running on Centos 6.1, and VirtualBox 4.1.8

I get a few errors of ATAPI per day on both .vhi drives that are running on the Guest Windows 2003. Both error of both HDD (.vhi images) at the same time.

VirtualBox is having an atapi issue. With prior version 4.0.x there were no error. This was working fine with 4.0.4

Thanks

Version 0, edited 2 years ago by ColtGTi (next)

comment:4 Changed 5 months ago by birdie

4.3.2 - without any changes.

Note: See TracTickets for help on using tickets.

www.oracle.com
ContactPrivacy policyTerms of Use