Date: Fri, 13 Nov 2015 18:29:15 +0100 From: Matthieu CERDA <matthieu.cerda@gmail.com> To: freebsd-virtualization@freebsd.org Subject: Issue with Virtualbox OSE 4.3.32 SATA/AHCI on 11-CURRENT Message-ID: <CAFm1F4ia1CcJX-sXsGei8QmqvtxJ8n86PNg-QcZT%2BuVgQ4YC9g@mail.gmail.com>
next in thread | raw e-mail | index | archive | help
Hello folks!
I'm having a little bit of trouble here trying to run Virtualbox 4.3.32 on
a 11-CURRENT installation (r290644)
Everytime I try to install a GNU/Linux OS (the test case was installing a
Ubuntu VM from the Live CD, but it also occurs with a Debian netinstall)
with the default SATA disk emulation, the VM stalls as soon as disk I/O are
needed on the virtualized disk (the virtual CD from an ISO runs all right).
The VM VBox.log gives:
---8<---
(...)
00:02:41.496257 AioMgr0-N: Request 0x0000081025e280 failed with
rc=VERR_TRY_AGAIN, migrating endpoint /home/user/VirtualBox
VMs/Ubuntu/Ubuntu.vdi to failsafe manager.
00:02:41.692796 AIOMgr: I/O manager 0x000008180623a0 encountered a critical
error (rc=VERR_FILE_AIO_NO_REQUEST) during operation. Falling back to
failsafe mode. Expect reduced performance
00:02:41.692813 AIOMgr: Error happened in
/wrkdirs/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.32/src/VBox/VMM/VMMR3/PDMAsyncCompletionFileNormal.cpp:(1664){int
pdmacFileAioMgrNormal(RTTHREAD, void *)}
00:02:41.692819 AIOMgr: Please contact the product vendor
00:03:12.298528 AHCI#0: Port 0 reset
00:03:12.306370 AHCI#0P0: Cancelled task 0
00:03:12.306383 AHCI#0P0: Cancelled task 1
00:03:12.306388 AHCI#0P0: Cancelled task 2
00:03:12.306391 AHCI#0P0: Cancelled task 3
00:03:12.306406 AHCI#0P0: Cancelled task 4
00:03:12.306409 AHCI#0P0: Cancelled task 5
00:03:12.306413 AHCI#0P0: Cancelled task 6
00:03:12.306416 AHCI#0P0: Cancelled task 7
00:03:12.306419 AHCI#0P0: Cancelled task 8
00:03:12.306422 AHCI#0P0: Cancelled task 9
00:03:12.306426 AHCI#0P0: Cancelled task 10
00:03:12.306429 AHCI#0P0: Cancelled task 11
00:03:12.306432 AHCI#0P0: Cancelled task 12
00:03:12.306434 AHCI#0P0: Cancelled task 13
00:03:12.306437 AHCI#0P0: Cancelled task 14
00:03:12.306439 AHCI#0P0: Cancelled task 15
00:03:12.306441 AHCI#0P0: Cancelled task 16
00:03:12.306444 AHCI#0P0: Cancelled task 17
00:03:12.306446 AHCI#0P0: Cancelled task 18
00:03:12.306448 AHCI#0P0: Cancelled task 19
00:03:12.306451 AHCI#0P0: Cancelled task 20
00:03:12.306453 AHCI#0P0: Cancelled task 21
00:03:12.306455 AHCI#0P0: Cancelled task 22
00:03:12.306458 AHCI#0P0: Cancelled task 24
00:03:12.306460 AHCI#0P0: Cancelled task 25
00:03:12.306462 AHCI#0P0: Cancelled task 26
00:03:12.306465 AHCI#0P0: Cancelled task 27
00:03:12.306467 AHCI#0P0: Cancelled task 28
00:03:12.306470 AHCI#0P0: Cancelled task 29
00:03:12.306472 AHCI#0P0: Cancelled task 30
00:03:43.322453 AHCI#0: Port 0 reset
00:03:43.330286 AHCI#0P0: Cancelled task 0
00:03:43.330298 AHCI#0P0: Cancelled task 1
00:03:43.330323 AHCI#0P0: Cancelled task 2
(...)
The resets go on and on until I shoot the VM down...
Using the IDE backend seems to work (at least the VM did boot and began to
install properly, I'm waiting for it to complete)
I'm not blocked since a workaround exists, but I feel that the default
backend storage that Virtualbox selected for me should normally misbehave
like this.
Is there a know way to debug this kind of issues?
Thanks in advance, and have a nice week end!
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAFm1F4ia1CcJX-sXsGei8QmqvtxJ8n86PNg-QcZT%2BuVgQ4YC9g>