From owner-freebsd-bugs@freebsd.org  Mon Oct 19 16:32:07 2015
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 030A6A108D9
 for <freebsd-bugs@mailman.ysv.freebsd.org>;
 Mon, 19 Oct 2015 16:32:07 +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 CB86C1BC1
 for <freebsd-bugs@FreeBSD.org>; Mon, 19 Oct 2015 16:32:06 +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 t9JGW6YA061366
 for <freebsd-bugs@FreeBSD.org>; Mon, 19 Oct 2015 16:32:06 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: Mon, 19 Oct 2015 16:32:06 +0000
X-Bugzilla-Reason: AssignedTo
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: Base System
X-Bugzilla-Component: kern
X-Bugzilla-Version: 11.0-CURRENT
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: Affects Many People
X-Bugzilla-Who: bhavesh@vmware.com
X-Bugzilla-Status: New
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform
 op_sys bug_status bug_severity priority component assigned_to reporter
Message-ID: <bug-203874-8@https.bugs.freebsd.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
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.20
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: Mon, 19 Oct 2015 16:32:07 -0000

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

            Bug ID: 203874
           Summary: MSI/MSI-X interrupts don't work in VMware virtual
                    machines
           Product: Base System
           Version: 11.0-CURRENT
          Hardware: amd64
                OS: Any
            Status: New
          Severity: Affects Many People
          Priority: ---
         Component: kern
          Assignee: freebsd-bugs@FreeBSD.org
          Reporter: bhavesh@vmware.com

Any PCI* device/driver that relies on MSI or MSI-X interrupts doesn't work in a
VMware (ESXi hypervisor) virtual machine.

This is because of a quirk workaround that exists in the FreeBSD kernel that
fails requests for MSI or MSI-X interrupt vectors when it detects that the PCIe
Root Port or PCI bridge device is a VMware device (PCI Vendor ID 15adh, Device
ID 0790h or 07a0h)

The comment in the code suggests MSI/MSI-X didn't work in older versions of
ESXi:

sys/dev/pci/pci.c:
        /*
         * MSI-X allocation doesn't work properly for devices passed through
         * by VMware up to at least ESXi 5.1.
         */

I don't think this is true any more. Verified this by booting with:

hw.pci.honor_msi_blacklist=0

in /boot/loader.conf

Everything seems to be working fine with various devices and drivers
(passthrough ixgbe/ixgbevf, vmxnet3, etc.) with this boot workaround in a
FreeBSD 10.2 VM on ESXi 6.0.

I'll propose a trivial patch to remove this quirk workaround.

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