https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=168298
--- Comment #54 from Tom Rushworth ---
(In reply to Guido Falsi from comment #52)
Thanks for pointing out the VBox contributor information, and all the related
background stuff :).
It looks, from the licensing info there, that I have to
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=168298
--- Comment #53 from Pete French ---
(In reply to Guido Falsi from comment #51)
I followed the thread, and I must admit that I actually laughed out loud when I
got to the end and saw the patch was a one-liner! Ah, yes, definitely having
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=168298
--- Comment #52 from Guido Falsi ---
(In reply to Guido Falsi from comment #51)
I forgot to mention that their policy to accept patches [1] is very copyright
conscious. It means that it's actually impossible for anyone except the
original
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=168298
Guido Falsi changed:
What|Removed |Added
CC||madpi...@freebsd.org
--- Comment
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=168298
--- Comment #50 from Tom Rushworth ---
(In reply to Pete French from comment #48)
Thanks for the "nice job" :).
Yes this should go upstream, it is not FreeBSD specific. As far as I could see
by grepping through the entire source tree,
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=168298
Kurt Jaeger changed:
What|Removed |Added
Resolution|Works As Intended |---
Status|Closed
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=168298
--- Comment #48 from Pete French ---
(In reply to Tom Rushworth from comment #47)
Ah, this is excellent! Is this in FreeBSd specific code, or should it be
brought to the attention of the VirtualBox people upstream ? I advent looked at
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=168298
--- Comment #47 from Tom Rushworth ---
Created attachment 225299
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=225299=edit
a small ugly patch to make vbox stop trying for more AIO resources than it can
have
--
You are
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=168298
Tom Rushworth changed:
What|Removed |Added
CC||t...@acm.org
--- Comment #46 from
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=168298
--- Comment #45 from m...@netfence.it ---
(In reply to hjf from comment #41)
Notice I'm not using zvols, so it's not "obviously broken" only "for people
using zvols".
--
You are receiving this mail because:
You are the assignee for the
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=168298
--- Comment #44 from Pete French ---
(In reply to hjf from comment #43)
Yes - indeed, I am the original reporter of this bug ;-)
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=168298
--- Comment #43 from hjf ---
(In reply to Pete French from comment #42)
Are you also using a zvol as the backing storage for your VM?
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=168298
--- Comment #42 from Pete French ---
!!! I actually saw this effect when I upgraded. My Windows 10 VM booted fine
after the 12.2 upgrade, but my OpenSUSE install just crashed. I ended up
deleting it and installing Ubuntu instead, using the
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=168298
--- Comment #41 from hjf ---
(In reply to ml from comment #40)
Thank you! This patch worked for me. I can use my VMs again
For more detail:
The Linux VMs were backed on a ZFS ZVOL. Since the upgrade to .44, I got read
errors. The sort of
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=168298
--- Comment #40 from m...@netfence.it ---
(In reply to hjf from comment #39)
Yes, I'm able to build it (using Poudriere), with or without disabling AIO.
However, as I said in comment #38, the latest official version does not work
for me.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=168298
hjf changed:
What|Removed |Added
CC||h...@mailinator.com
--- Comment #39 from
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=168298
m...@netfence.it changed:
What|Removed |Added
CC||m...@netfence.it
--- Comment
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=168298
ykla changed:
What|Removed |Added
CC||ykla...@gmail.com
--- Comment #37 from
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=168298
--- Comment #36 from Gleb Popov ---
Well, I'm out of ideas what's wrong here, sorry.
--
You are receiving this mail because:
You are the assignee for the bug.
___
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=168298
--- Comment #35 from datafl...@toxicnet.eu ---
(In reply to Gleb Popov from comment #34)
As I said, I built it from source (the tree was updated yesterday before
compiling).
There are no special tweaks in the files you indicated, not even
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=168298
--- Comment #34 from Gleb Popov ---
(In reply to datafl4sh from comment #33)
This is strange. This version shouldn't use AIO at all. Did you built
VirtualBox from source or installed from the official binary package?
Also, do you have any
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=168298
--- Comment #33 from datafl...@toxicnet.eu ---
(In reply to Gleb Popov from comment #32)
Sorry, 5.2.44_4
--
You are receiving this mail because:
You are the assignee for the bug.
___
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=168298
--- Comment #32 from Gleb Popov ---
(In reply to datafl4sh from comment #31)
No, run `pkg info virtualbox-ose-nox11` and check the version string there.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=168298
--- Comment #31 from datafl...@toxicnet.eu ---
(In reply to Gleb Popov from comment #30)
According to the distinfo file, version is 5.2.44.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=168298
--- Comment #30 from Gleb Popov ---
(In reply to datafl4sh from comment #29)
What is exact version of virtualbox-ose-nox11 are you running?
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=168298
datafl...@toxicnet.eu changed:
What|Removed |Added
CC||datafl...@toxicnet.eu
---
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=168298
--- Comment #28 from commit-h...@freebsd.org ---
A commit references this bug:
Author: arrowd
Date: Mon Oct 12 15:31:45 UTC 2020
New revision: 552134
URL: https://svnweb.freebsd.org/changeset/ports/552134
Log:
emulators/virtualbox-ose:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=168298
--- Comment #27 from p...@twisted.org.uk ---
Yes, this looks good to me too. My original suggested fix was not to load AIO
if you can avoid it, but actually thats not always practical. So having AIO
disabled for virtual box instead of
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=168298
--- Comment #26 from rkober...@gmail.com ---
Comment on attachment 218039
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=218039
turns off aio completely
This looks completely appropriate to me. I have never been comfortable with
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=168298
Gleb Popov changed:
What|Removed |Added
CC||arr...@freebsd.org
--- Comment #25
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=168298
Sarah changed:
What|Removed |Added
CC||kevintaylor15...@gmail.com
--- Comment
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=168298
--- Comment #23 from Steve Wills ---
r324941
https://svnweb.freebsd.org/base?view=revision=324941
did adjust the default value of vfs.aio.max_aio_queue, but I'm not sure if
that's sufficient. Seems to me what's needed is either:
*
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=168298
--- Comment #22 from Kurt Jaeger ---
It's not even overcome by events. The problem is probably still there, the
sysctl fix only masks it.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=168298
--- Comment #21 from Anton Saietskii ---
(In reply to rozhuk.im from comment #20)
"Overcome By Events" as closure code fits much better, although not perfect
also.
--
You are receiving this mail because:
You are the assignee for the
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=168298
--- Comment #20 from rozhuk...@gmail.com ---
(In reply to Kurt Jaeger from comment #19)
1. It works.
2. No one wants dig in to it in past 2-3 years.
I suspect that there is some internal IO queue, probably with limit, and
default limit in
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=168298
--- Comment #19 from Kurt Jaeger ---
It's a bit strange to close a bug report with "works as intended" with a sysctl
tuning fix, and not trying to find the root cause.
--
You are receiving this mail because:
You are the assignee for the
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=168298
Bernhard Froehlich changed:
What|Removed |Added
Status|In Progress |Closed
CC|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=168298
--- Comment #17 from VVD ---
(In reply to pete from comment #16)
> Yes, I would says so, this has been stable for me now for many years with the
> AIO tunings above. I run several machines on virtuabox on zvols fine.
Same here too. But
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=168298
--- Comment #16 from p...@twisted.org.uk ---
(In reply to rozhuk.im from comment #15)
Yes, I would says so, this has been stable for me now for many years with the
AIO tunings above. I run several machines on virtuabox on zvols fine.
--
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=168298
--- Comment #15 from rozhuk...@gmail.com ---
Time to close this?
--
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-virtualization@freebsd.org mailing list
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=168298
--- Comment #14 from Alan Somers ---
*** Bug 212128 has been marked as a duplicate of this bug. ***
--
You are receiving this mail because:
You are the assignee for the bug.
___
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=168298
--- Comment #13 from rozhuk...@gmail.com ---
Lower bounds depends on host system load, host system speed, guest activity.
IMHO lower bounds does nothink, this is max values, it does not consume
resources at idle.
--
You are receiving this
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=168298
--- Comment #12 from Kurt Jaeger ---
Sorry, I forgot to mention the reviews in the commit message. Now we should
probably keep this PR open until some finds a root cause and some safe lower
bounds for those values ?
--
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=168298
Kurt Jaeger changed:
What|Removed |Added
Version|8.3-STABLE |11.1-RELEASE
--
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=168298
--- Comment #11 from commit-h...@freebsd.org ---
A commit references this bug:
Author: pi
Date: Sat May 12 17:11:34 UTC 2018
New revision: 469742
URL: https://svnweb.freebsd.org/changeset/ports/469742
Log:
emulators/virtualbox-ose: add
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=168298
--- Comment #10 from rozhuk...@gmail.com ---
Created attachment 193335
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=193335=edit
update postinstall message
--
You are receiving this mail because:
You are the assignee for the
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=168298
--- Comment #9 from rozhuk...@gmail.com ---
May be add info about AIO tunings to post install message and close this bug?
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=168298
Mark Linimon changed:
What|Removed |Added
Assignee|freebsd-b...@freebsd.org
48 matches
Mail list logo