VirtualBox

Custom Query (16363 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (484 - 486 of 16363)

Ticket Resolution Summary Owner Reporter
#7035 obsolete CapsLock does not intercepted Danil Ilinykh
Description
  1. Try to type some letters in host system, they are small.
  2. Switch to the guest system. Press CapsLock.
  3. Switch back to the host system, type some letters. They are big!
#12648 obsolete Using multiple virtual disks leads to timeouts and crash in client wonko1953
Description

When using multiple virtual disks, I inevitably get DMA timeouts in the client, eventually followed by the client freezing. The only escape then is to kill the client emulation process.

Environment

Host:

  • FreeBSD 9.2.0 amd64 running VirtualBox OSE 4.3.6 (from FreeBSD ports; however, the same behavior has happened for a very long time also with older VB releases) or alternatively
  • Windows 7 (but only tested a while ago with an older VB release showing the same problem)

Devices:

  • 7 raw devices are exported by the FreeBSD host, either attached directly (if VB runs on the FreeBSD host), or via iscsi (if VB runs on Windows 7)
  • 1 x 20 GB attached as IDE0:0 in the VB client
  • 6 x 896 GB attached as SATA0:1-6 in the VB client (the same happens if a SAS instead of an SATA controller is emulated)

Client:

  • FreeBSD 10.0.0 amd64, UFS on 20 GB device, zfs raidz2 on 6 x 896 GB devices. However, the same behavior has been seen with older FreeBSD releases in the client.

Symptoms

After some disk I/O, a DMA timeout is announced in the client OS. This cannot be recovered from. Using "Machine->Reset" from the Client Menu does not work any more. The client process must ultimately be killed.

No problem at all if only one emulated disk is used.

VBox.log

It seems that the following lines in the logfile hint at the problem:

00:32:14.790849 AIOMgr: I/O manager 0x0000080e8eb920 encountered a critical error (rc=VERR_FILE_AIO_NO_REQUEST) during operation. Falling back to failsafe mode. Expect reduced performance
00:32:14.790990 AIOMgr: Error happened in /usr/tmp/z/SRC/FreeBSD-ports/head/emulators/virtualbox-ose/work/VirtualBox-4.3.6/src/VBox/VMM/VMMR3/PDMAsyncCompletionFileNormal.cpp:(1664){int pdmacFileAioMgrNormal(RTTHREADINT*, void*)}
#17089 obsolete crash with host on Windows 7 and iSCSI to FreeBSD 11.1 wonko1953
Description

Scenario:

  • Windows 7 host, VirtualBox 5.1.28
  • FreeBSD 11.1 client
  • iSCSI disk going to FreeBSD 11.1 fileserver

Result:

  • With enough disk activity, the client crashes. VBox.Log has the following last lines:
00:07:54.184158 PIIX3 IDE: guest issued command 0xca while controller busy
00:07:54.186337 
00:07:54.186338 !!Assertion Failed!!
00:07:54.186338 Expression: ReqType == ATA_AIO_RESET_ASSERTED || ReqType == ATA_AIO_RESET_CLEARED || ReqType == ATA_AIO_ABORT || pCtl->uAsyncIOState == ReqType
00:07:54.186339 Location  : F:\tinderbox\win-5.1\src\VBox\Devices\Storage\DevATA.cpp(5524) int __cdecl ataR3AsyncIOThread(struct RTTHREADINT *,void *)
00:07:54.186373 I/O state inconsistent: state=0 request=1
00:07:54.197491 PIIX3 IDE: guest issued command 0xca while controller busy
00:08:24.192298 PIIX3 ATA: Ctl#0: RESET, DevSel=0 AIOIf=0 CmdIf0=0xca (-1 usec ago) CmdIf1=0x00 (-1 usec ago)
  • This is always reproducible

Note:

  • When running the same client on a FreeBSD 11.1 host these crashes do not occur (VirtualBox compiled using FreeBSD port emulators/virtualbox-ose)
Batch Modify
Note: See TracBatchModify for help on using batch modify.
Note: See TracQuery for help on using queries.

© 2024 Oracle Support Privacy / Do Not Sell My Info Terms of Use Trademark Policy