Date: Sat, 09 Nov 2019 18:26:44 +0000 From: bugzilla-noreply@freebsd.org To: virtualization@FreeBSD.org Subject: [Bug 203874] [patch] MSI/MSI-X interrupts don't work in VMware virtual machines Message-ID: <bug-203874-27103-GKygbvorvl@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/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D203874 --- Comment #22 from John Baldwin <jhb@FreeBSD.org> --- I think a patch that only disabled MSI for <=3D 5 seems reasonable given th= at no one has reported it breaking on anything newer than that when setting the tunable. Comment 19 suggests 5.5 is still broken, so I think disabling it = for all of 5.x by default seems prudent. I think that type of quirk would requ= ire removing the existing device-ID-based entry and instead adding a "manual" q= uirk that checks for VMWare (e.g. VM_GUEST_VMWARE) and then checks the major version. I'm not quite sure how to get the major version of VMWare, perhaps via the hypervisor cpuid leaf or the vmware_hvcall() function. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-203874-27103-GKygbvorvl>