Changes between Initial Version and Version 1 of Ticket #11219, comment 6
- Timestamp:
- Sep 5, 2013 5:26:20 AM (11 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #11219, comment 6
initial v1 1 The following configurations all eventually fail:1 The following configurations all eventually result in unresponsive VMs: 2 2 3 3 * 10.7.4 with a single windows 7 VM … … 5 5 * 10.7.5 with one windows 7 VM and one Windows XP VM 6 6 7 The same configurations under 10.6 do not encounter any errors.8 9 7 The failures are all as follows: 10 8 11 9 * "aio_queue_async_request(): too many in flight for proc: 16" 12 * after several hundred of these warnings/errors disk IO errors are reported. Later filesystem diagnostics indicate that aio errors might result in filesystem corruption.10 * after several hundred of these warnings/errors disk IO errors are reported. Later filesystem diagnostics do not always find filesystem errors. 13 11 * The windows VMs are mostly unresponsive. They will respond to pings and initial RDP connection negotiation. However, anything involving IO freezes. 14 12 * VBoxManage controlvm commands never complete. … … 25 23 26 24 I replaced Mac 10.7.5 with Ubuntu 12.0.4 on one of the systems. 3 windows 7 VMs were placed on this system and subjected to the same testing load. No errors have occurred. 25 26 The following configurations all encountered aio errors but did not have unresponsive VMs: 27 28 * 10.6.5 with single Windows 7 VM. 29 * 10.6.5 with three windows XP VMs. 30 31 These have been operating fine with 32 33 {{{ 34 kern.aiomax=2048 35 kern.aioprocmax=512 36 kern.aiothreads=128 37 }}} 38 39 (previous post corrected for updated data.)
