https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=168298
Mark Linimon changed:
What|Removed |Added
Assignee|freebsd-bugs@FreeBSD.org|freebsd-virtualization@Free
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=168298
--- Comment #8 from rkober...@gmail.com ---
I have done some experimentation and havebeen able to modify these settings to
less extreme values and still get VB to run without failing.
vfs.aio.max_aio_queue: 8192
vfs.aio.max_aio_queue_per_pro
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=168298
mar...@sugioarto.com changed:
What|Removed |Added
CC||mar...@sugioarto.com
--- Com
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=168298
--- Comment #6 from rkober...@gmail.com ---
The adjustments in comment 3 seem to work, although vfs.aio.aiod_timeout does
not exist in 11.0 and vfs.aio.max_aio_procs defaults to 4, so is a noop.
Some of the others seem a bit extreme and I s
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=168298
rkober...@gmail.com changed:
What|Removed |Added
CC||rkober...@gmail.com
--- Comme
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=168298
--- Comment #4 from Martin Birgmeier ---
(In reply to rozhuk.im from comment #3)
Interesting... thank you.
Before I try this myself: Does this just make the issue more unlikely to
happen, or is this a genuine fix?
And also, does VBox not
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=168298
rozhuk...@gmail.com changed:
What|Removed |Added
CC||rozhuk...@gmail.com
--- Comme
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=168298
p...@twisted.org.uk changed:
What|Removed |Added
CC||p...@twisted.org.uk
--- Comme
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=168298
Martin Birgmeier changed:
What|Removed |Added
CC||la5lb...@aon.at
--- Comment #1
