From owner-freebsd-bugs@freebsd.org  Tue Mar 28 12:44:05 2017
Return-Path: <owner-freebsd-bugs@freebsd.org>
Delivered-To: freebsd-bugs@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id 013E3D20D3C
 for <freebsd-bugs@mailman.ysv.freebsd.org>;
 Tue, 28 Mar 2017 12:44:05 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from kenobi.freebsd.org (kenobi.freebsd.org
 [IPv6:2001:1900:2254:206a::16:76])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id E504BF93
 for <freebsd-bugs@FreeBSD.org>; Tue, 28 Mar 2017 12:44:04 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from bugs.freebsd.org ([127.0.1.118])
 by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v2SCi4qS032364
 for <freebsd-bugs@FreeBSD.org>; Tue, 28 Mar 2017 12:44:04 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-bugs@FreeBSD.org
Subject: [Bug 203874] MSI/MSI-X interrupts don't work in VMware virtual
 machines
Date: Tue, 28 Mar 2017 12:44:05 +0000
X-Bugzilla-Reason: AssignedTo
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: Base System
X-Bugzilla-Component: kern
X-Bugzilla-Version: CURRENT
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: Affects Many People
X-Bugzilla-Who: igor@hybrid-lab.co.uk
X-Bugzilla-Status: New
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-203874-8-yTxbxs5pKD@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-203874-8@https.bugs.freebsd.org/bugzilla/>
References: <bug-203874-8@https.bugs.freebsd.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-BeenThere: freebsd-bugs@freebsd.org
X-Mailman-Version: 2.1.23
Precedence: list
List-Id: Bug reports <freebsd-bugs.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-bugs>,
 <mailto:freebsd-bugs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-bugs/>
List-Post: <mailto:freebsd-bugs@freebsd.org>
List-Help: <mailto:freebsd-bugs-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-bugs>,
 <mailto:freebsd-bugs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 28 Mar 2017 12:44:05 -0000

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D203874

igor@hybrid-lab.co.uk changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |igor@hybrid-lab.co.uk

--- Comment #6 from igor@hybrid-lab.co.uk ---
(In reply to bhavesh from comment #5)


Is there still a good idea on to keep this blacklisting for ESXi, other than
exposing bugs in fall-back code in drivers
(https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D218113)?

It's been nearly a year and a half since the last comment?

I've removed the blacklisting for 11-RELEASE on my box inside ESXi 6.5 and
there doesn't seem to be any previously reported signs of "badness" with LSI
SAS emulation and igb(4) passthrough so far.

--=20
You are receiving this mail because:
You are the assignee for the bug.=