From owner-freebsd-virtualization@freebsd.org  Wed May 31 19:39:01 2017
Return-Path: <owner-freebsd-virtualization@freebsd.org>
Delivered-To: freebsd-virtualization@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 60625B87E64
 for <freebsd-virtualization@mailman.ysv.freebsd.org>;
 Wed, 31 May 2017 19:39:01 +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 48D8165E1A
 for <freebsd-virtualization@FreeBSD.org>; Wed, 31 May 2017 19:39:01 +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 v4VJd0JI023568
 for <freebsd-virtualization@FreeBSD.org>; Wed, 31 May 2017 19:39:01 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-virtualization@FreeBSD.org
Subject: [Bug 203874] [patch] MSI/MSI-X interrupts don't work in VMware
 virtual machines
Date: Wed, 31 May 2017 19:39:00 +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: patch
X-Bugzilla-Severity: Affects Many People
X-Bugzilla-Who: marius@FreeBSD.org
X-Bugzilla-Status: New
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: freebsd-virtualization@FreeBSD.org
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-203874-27103-M9T7xdfHWH@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-203874-27103@https.bugs.freebsd.org/bugzilla/>
References: <bug-203874-27103@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-virtualization@freebsd.org
X-Mailman-Version: 2.1.23
Precedence: list
List-Id: "Discussion of various virtualization techniques FreeBSD supports."
 <freebsd-virtualization.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-virtualization>, 
 <mailto:freebsd-virtualization-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-virtualization/>
List-Post: <mailto:freebsd-virtualization@freebsd.org>
List-Help: <mailto:freebsd-virtualization-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization>, 
 <mailto:freebsd-virtualization-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 31 May 2017 19:39:01 -0000

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

--- Comment #9 from Marius Strobl <marius@FreeBSD.org> ---
One thing that came to my mind regarding some people apparently not being a=
ble
to reproduce the original problem is that it may also depend on the
virtualization capabilities of the hardware used, e. g. APICv, AVIC, MSI/MS=
I-X
remapping etc., i. e. the bug may be present in the full software emulation=
 of
ESXi (or some versions thereof) but hidden when interrupt handling is assis=
ted
by hardware.

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