https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=283341
--- Comment #2 from DYM ---
It's a shame that the discussion ended in nothing at the time.
I believe that two different behaviors should not be described by one value.
In fact, I recently encountered some strange behavior of the disk subsy
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=283352
Li-Wen Hsu changed:
What|Removed |Added
Status|Open|Closed
Resolution|---
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278058
--- Comment #4 from Mark McBride ---
Some progress (or random luck)! As of 14.2-RELEASE, 1 of my 3 test cases for
SR-IOV in a mixed vnet & passthrough setup works.
WORKING (was failing pre 14.2)
Mellanox ConnectX-4 Lx - I have 3 bhyve vms
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=283352
--- Comment #2 from Michael ---
Based on your question, I installed clean five distributions of different
release times on another hypervisor, with the same parameters and equipment.
1. FreeBSD-13.0-CURRENT-amd64-20200130-r357276-disc1.iso
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=283352
--- Comment #3 from Li-Wen Hsu ---
(In reply to Michael from comment #2)
Thanks for confirming it. Then this sounds highly possible due to an issue in
Mellanox driver on Windows. Although there might be chance that an issue has
been reveale
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=283352
--- Comment #4 from Michael ---
To avoid going far, I installed Windows 2022 guest VM.
And guess what?
The same picture 8) !
Vlans inside VM via Microsoft Network Adapter Multiplexor Driver also do not
work on drivers version 24.x.xxx
-
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203643
Michael Dexter changed:
What|Removed |Added
CC||edi...@callfortesting.org
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=283375
Mark Linimon changed:
What|Removed |Added
Assignee|b...@freebsd.org|virtualization@FreeBSD.org
