Opened 5 years ago
Closed 4 years ago
#18663 closed defect (obsolete)
Bug on macos with iscsi
| Reported by: | pacey | Owned by: | |
|---|---|---|---|
| Component: | virtual disk | Version: | VirtualBox 6.0.6 |
| Keywords: | iscsi | Cc: | |
| Guest type: | other | Host type: | other |
Description
I am using a synology nas to provide iscsi service for virtual machine. But we (with synology's iscsi engineer) found that the virtualbox-iscsi-initiator's timeout-setting is unreasonable.
issus1: It makes iscsi connection on virtualbox always timeout under very high io.
issus2: When timeout happend, virtualbox trying create a new connection. But it never disconnect from the last connection. If the iscsi target do not support multi-channel new-connection will be failed.
Change History (2)
comment:1 by , 5 years ago
comment:2 by , 4 years ago
| Resolution: | → obsolete |
|---|---|
| Status: | new → closed |
No response, closing. Please reopen if still an issue and attach the requested VBox.log from an affected VM.
Note:
See TracTickets
for help on using tickets.
Please attach a VBox.log for such a failing run. The default iSCSI read timeout is 10s which should be more than enough for the target to supply the data. When using higher timeouts we risk running into guest timeouts which can lead to a dead guest in the worst case. Thatswhy we pause the VM before that can happen. The read timeout can be adjusted using the medium properties (have a look into the manual, the key is "Timeout"). Not dropping the timed out connection needs further investigation.