https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=277349
--- Comment #10 from commit-h...@freebsd.org ---
A commit in branch stable/14 references this bug:
URL:
https://cgit.FreeBSD.org/src/commit/?id=d6e1ae659b11a13a9c289424735394173907c1d3
commit d6e1ae659b11a13a9c289424735394173907c1d3
Author
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=277349
Gleb Smirnoff changed:
What|Removed |Added
Status|New |Closed
Resolution|---
> On 28. Mar 2024, at 15:00, Nuno Teixeira wrote:
>
> Hello all!
>
> Running rack @b7b78c1c169 "Optimize HPTS..." very happy on my laptop (amd64)!
>
> Thanks all!
Thanks for the feedback!
Best regards
Michael
>
> Drew Gallatin escreveu (quinta, 21/03/2024 à(s) 12:58):
> The entire point is t
Hello all!
Running rack @b7b78c1c169 "Optimize HPTS..." very happy on my laptop
(amd64)!
Thanks all!
Drew Gallatin escreveu (quinta, 21/03/2024 à(s)
12:58):
> The entire point is to *NOT* go through the overhead of scheduling
> something asynchronously, but to take advantage of the fact that a
---> A very simple and elegant shell management tool to play with bhyve is
vm-bhyve
I never use it. I created my own elegant script that in my opinion works
better than vm-bhyve. And I think that I can improve it
I will...
On Tue, Mar 26, 2024 at 8:30 PM Tomek CEDRO wrote:
> On Tue, Mar 26,
On Tue, Mar 26, 2024, at 18:31, Benoit Chesneau wrote:
> How does work VNET with interfaces? Is this as efficient as using pci
> passtrough in a vm ?
Overhead should be minimal, while the device is logically missing from the
default vnet there isn't any more "in the way" for actual usage. Ma
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=275225
--- Comment #4 from ekoort ---
So today it did not work as expected.
Main went down, secondary took over, main came up and instantly main took over
while it (cluster services) should stay on secondary.
So it's a mixed results for unknown r