Custom Query (16363 matches)
Results (982 - 984 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #8798 | obsolete | Async I/O thread probably stuck in operation | ||
| Description |
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 |
|||
| #11138 | obsolete | At least on VirtualBox Win32 4.0.12, on when hibernating and the disk is full, V.B. actually crashes | ||
| Description |
(I would believe this bug is around also now.) Here's how it works:
From here, you *cannot* resume the hibernation process, nor take any action with the VirtualBox window! All that is to be done is to kill it using the task manager from ctrl+alt+delete . All info in that Virtualbox session has been lost. Lots of people must have this error. |
|||
| #1817 | fixed | At least one key not working => fixed in the upcoming version | ||
| Description |
Running VB 1.5.6_OSE as downloaded from the available repositories in ubuntu Hardy Heron. Have installed a windows 2000 server guest. The three key on the top row of my keyboard seems to be ignored by the guest operating system. Using the key on the number pad of my keyboard does work however. Have also tried with a Windows Vista guest, and the same problem is present in that. |
|||

