From owner-freebsd-virtualization@freebsd.org Sun Nov 10 01:05:53 2019 Return-Path: <owner-freebsd-virtualization@freebsd.org> Delivered-To: freebsd-virtualization@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id E474B1A35B8 for <freebsd-virtualization@mailman.nyi.freebsd.org>; Sun, 10 Nov 2019 01:05:53 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.nyi.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 479bRP5mzkz4Lw2 for <freebsd-virtualization@freebsd.org>; Sun, 10 Nov 2019 01:05:53 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.nyi.freebsd.org (Postfix) id C44041A35B7; Sun, 10 Nov 2019 01:05:53 +0000 (UTC) Delivered-To: virtualization@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id C2F361A35B6 for <virtualization@mailman.nyi.freebsd.org>; Sun, 10 Nov 2019 01:05:53 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 479bRP4gq3z4Lw0 for <virtualization@FreeBSD.org>; Sun, 10 Nov 2019 01:05:53 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2610:1c1:1:606c::50:1d]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 8313B1F388 for <virtualization@FreeBSD.org>; Sun, 10 Nov 2019 01:05:53 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.5]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id xAA15r6H039578 for <virtualization@FreeBSD.org>; Sun, 10 Nov 2019 01:05:53 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id xAA15rur039577 for virtualization@FreeBSD.org; Sun, 10 Nov 2019 01:05:53 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: virtualization@FreeBSD.org Subject: [Bug 203874] [patch] MSI/MSI-X interrupts don't work in VMware virtual machines Date: Sun, 10 Nov 2019 01:05:51 +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: chrysalis@chrysalisnet.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: virtualization@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: <bug-203874-27103-BBHpjZPnWI@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.29 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: Sun, 10 Nov 2019 01:05:54 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D203874 --- Comment #24 from Chris Collins <chrysalis@chrysalisnet.org> --- 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" hardware, if its on a blacklist, add something to DMESG that tells the end user something like "MSIX disabled due to blacklist, can disa= ble via this bootloader" As I think silently blocking a function is the wrong way to go about things. 2 - The default behaviour should be to suit the current supported builds of vmware so default to no blacklist, but keep an option so those using unsupported versions can still use the OS. But if a way could be found to differentiate between new and old vmware then yeah keep a blacklist for old vmware. Also another point of concern, so we know at this point the kernel developer that replied here has vanished. The vmware developers have written a pvscsi driver for FreeBSD, that driver= is suffering the same issues as this bug report. It has sat in review status for nearly a year. Initially the vmware develo= per who submitted it was available for responses but I expect has now given up = so this issue of things been left in limbo status is holding back FreeBSD virtualization capability. This bug report was submitted 4 years ago, there does seem to be some kind = of issue with approach to this kind of thing. --=20 You are receiving this mail because: You are the assignee for the bug.=