https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203874
Manuel P. changed:
What|Removed |Added
CC||registrazi...@kiokoman.eu.o
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203874
Mark Peek changed:
What|Removed |Added
Resolution|--- |FIXED
Status|New
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203874
--- Comment #31 from John Baldwin ---
Thanks for the digging Mark. It is amusing that the description of the bug in
VMware matches almost exactly the bug Xen had.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203874
--- Comment #30 from commit-h...@freebsd.org ---
A commit references this bug:
Author: mp
Date: Wed Dec 18 23:00:56 UTC 2019
New revision: 355889
URL: https://svnweb.freebsd.org/changeset/base/355889
Log:
Remove VMware MSI-X from the PCI
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203874
Mark Peek changed:
What|Removed |Added
CC||m...@freebsd.org
--- Comment #29 from
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203874
Mahmoud Al-Qudsi changed:
What|Removed |Added
CC||mqu...@neosmart.net
--- Comment
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203874
--- Comment #27 from Chris Collins ---
I am ok with both proposals.
Certainly I think the current approach is wrong, and should be changed.
It is a bit like deciding to block the use of math co processor on all modern
cpu's just because t
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203874
--- Comment #26 from i...@hybrid-lab.co.uk ---
(In reply to John Baldwin from comment #25)
My suggestion is much simpler: remove support for platform that is deprecated
by vendor! If someone (is there anyone?) still is on ESXi 5.x then prov
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203874
--- Comment #25 from John Baldwin ---
I just said how to check the version in the previous comment. So, no, it is
not true that we can't handle versions because the PCI ID doesn't change. As I
said in the previous comment, the fix is to m
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203874
--- Comment #24 from Chris Collins ---
I would be ok with a 5.x only blacklist, the problem is I think there is no way
to seemingly identify it as apparently the pci id's are the same.
So I think should be two changes.
1 - For "all" hardw
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203874
--- Comment #23 from i...@hybrid-lab.co.uk ---
Seems a much more straight forward option would be to require those who are
using archaic hypervisors to manually set a kernel variable (like
kern.disable_msix_on_legacy_hypervisor=1) via loader
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203874
--- Comment #22 from John Baldwin ---
I think a patch that only disabled MSI for <= 5 seems reasonable given that no
one has reported it breaking on anything newer than that when setting the
tunable. Comment 19 suggests 5.5 is still broken
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203874
Chris Collins changed:
What|Removed |Added
CC||chrysa...@chrysalisnet.org
--- Com
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203874
Arun Pereira changed:
What|Removed |Added
CC||arunpere...@gmail.com
--- Comment #
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203874
Dmitry Wagin changed:
What|Removed |Added
CC||dmitry.wa...@ya.ru
--- Comment #19
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203874
--- Comment #18 from i...@hybrid-lab.co.uk ---
(In reply to John Baldwin from comment #17)
In order to investigate anything that sporadically breaks, you need to know how
to break it. Like I said in comment #6 when I disabled the hack, not
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203874
--- Comment #17 from John Baldwin ---
I don't think the commenter in #3 understood what "broken" might mean in the
context of MSI or MSI-X, so I attempted to give more detail on how a particular
type of breakage might boot Linux ok but not
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203874
--- Comment #16 from i...@hybrid-lab.co.uk ---
(In reply to John Baldwin from comment #15)
The reply from VMWare is in comment #3---their implementation was never broken.
They also asked for specific bug reports to be identified where the b
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203874
--- Comment #15 from John Baldwin ---
(In reply to igor from comment #14)
Comment #12 explains why another hypervisor had issues with FreeBSD due to an
incomplete emulation of MSI-X. However, the questions it raises can only be
answered by
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203874
--- Comment #14 from i...@hybrid-lab.co.uk ---
(In reply to Rodney W. Grimes from comment #13)
Given that (a) there is absolutely no definitive background as to why the hack,
pardon me, "quirk" was inserted in in the first place, (b) utter
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203874
--- Comment #13 from Rodney W. Grimes ---
This is a ping, we need to move forward on this issue.
--
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-virtualizat
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203874
John Baldwin changed:
What|Removed |Added
CC||j...@freebsd.org
--- Comment #12 fr
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203874
Jin Heo changed:
What|Removed |Added
CC||h...@vmware.com
--- Comment #11 from Jin
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203874
--- Comment #10 from i...@hybrid-lab.co.uk ---
(In reply to Marius Strobl from comment #9)
And without any bug reports that lead to the exclusion of MSI-X support under
FreeBSD we'll never know. Linux has MSI-X under ESXi, if I recall corre
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203874
--- Comment #9 from Marius Strobl ---
One thing that came to my mind regarding some people apparently not being able
to reproduce the original problem is that it may also depend on the
virtualization capabilities of the hardware used, e. g.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203874
--- Comment #8 from i...@hybrid-lab.co.uk ---
(In reply to Rodney W. Grimes from comment #7)
ESXi 5.0 and 5.1 had their general support discontinued on 24th August 2016:
https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203874
Rodney W. Grimes changed:
What|Removed |Added
CC||rgri...@freebsd.org
--- Comment
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203874
Mark Linimon changed:
What|Removed |Added
CC|jfvo...@gmail.com |
Assignee|freebsd-b...@fr
28 matches
Mail list logo
