Date: Mon, 13 Feb 2017 02:33:38 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-virtualization@FreeBSD.org Subject: [Bug 216493] [Hyper-V] Mellanox ConnectX-3 VF driver can't work when FreeBSD runs on Hyper-V 2016 Message-ID: <bug-216493-27103-OHNP4nU2Zr@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-216493-27103@https.bugs.freebsd.org/bugzilla/> References: <bug-216493-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=3D216493 Dexuan Cui <decui@microsoft.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |decui@microsoft.com --- Comment #2 from Dexuan Cui <decui@microsoft.com> --- Updates: hselasky committed the 2 patches (D8867, D8868) into the HEAD last Friday. Issue 1: No update. Issue 2:=20 Actually Linux version of the driver has the same (similar?) issue and I reported it here: https://www.spinics.net/lists/netdev/msg420136.html Some people suspected that it failed to allocate a UAR, but after we increa= sed LOG_BAR_SIZE with mlxconfig from 3 (8MB) to 5 (32MB), the issue was still there. We'll continue to work on this. Issue 3: No update. Issue 4:=20 It looks this may be a host side issue. on Live Migration, the host just removes the VF from the guest by force suddenly. Working on this.=20 But meanwhile, the VF driver should be improved to be more robust to cope w= ith this scenario. --=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-216493-27103-OHNP4nU2Zr>