https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231117
Mark Johnston changed:
What|Removed |Added
Status|Open|Closed
CC|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231117
--- Comment #31 from Kristian K. Christensen ---
(In reply to Allan Jude from comment #30)
Hi Allan,
I can confirm, that we are no longer experiencing this issue, neither in
11.3-RELEASE nor in 12.1-RELEASE (though 11.2-RELEASE and 12.0-R
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231117
--- Comment #30 from Allan Jude ---
The bhyve chatroom reports that the memory barrier fix seems to solve this
issue.
Should this PR be closed now?
--
You are receiving this mail because:
You are the assignee for the bug.
___
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231117
--- Comment #29 from commit-h...@freebsd.org ---
A commit references this bug:
Author: rgrimes
Date: Thu May 23 18:58:06 UTC 2019
New revision: 348188
URL: https://svnweb.freebsd.org/changeset/base/348188
Log:
MFC: r347960: bhyve virtio
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231117
--- Comment #28 from commit-h...@freebsd.org ---
A commit references this bug:
Author: rgrimes
Date: Thu May 23 18:48:47 UTC 2019
New revision: 348186
URL: https://svnweb.freebsd.org/changeset/base/348186
Log:
MFC: r347960: bhyve virtio
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231117
--- Comment #27 from commit-h...@freebsd.org ---
A commit references this bug:
Author: rgrimes
Date: Sat May 18 19:32:39 UTC 2019
New revision: 347960
URL: https://svnweb.freebsd.org/changeset/base/347960
Log:
bhyve virtio needs barriers
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231117
--- Comment #26 from Mateusz Kwiatkowski ---
(In reply to Rodney W. Grimes from comment #23)
The VM running patched bhyve is stable since Sunday evening. This is 3 whole
days and it didn't run so long without a crash before. I think we can
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231117
--- Comment #25 from Mateusz Kwiatkowski ---
(In reply to Mateusz Kwiatkowski from comment #24)
I'm afraid I celebrated too soon. I/O in VM locked up - it just took more time.
Memory stats:
Mem: 3846M Active, 4806M Inact, 26G Wired, 27G Fr
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231117
--- Comment #24 from Mateusz Kwiatkowski ---
(In reply to Rodney W. Grimes from comment #23)
Rodney, many thanks for your engagement in this matter. It seems that you were
right suspecting that arc_max is the culprit. After reducing its si
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231117
--- Comment #23 from Rodney W. Grimes ---
(In reply to Mateusz Kwiatkowski from comment #22)
> VMs may use 8GBs of RAM in total. Hypervisor has 64GB in total. So VMs and
> ARC could create OOM condition but the statistics I provided were t
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231117
--- Comment #22 from Mateusz Kwiatkowski ---
(In reply to Rodney W. Grimes from comment #21)
> How much memory are your VM's using? Ie, what is the total of all the VM's
> you have > running at any time? How much total memory does the sy
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231117
Rodney W. Grimes changed:
What|Removed |Added
CC||rgri...@freebsd.org
K
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231117
Kubilay Kocak changed:
What|Removed |Added
Summary|I/O lockups inside bhyve|bhyve: I/O lockups inside
13 matches
Mail list logo
