[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <032fd940-f0e8-4cd6-e455-8b8855c3105f@gmail.com>
Date: Thu, 9 Feb 2017 18:47:33 +0200
From: Tariq Toukan <ttoukan.linux@...il.com>
To: Dexuan Cui <decui@...rosoft.com>,
Yishai Hadas <yishaih@...lanox.com>,
Tariq Toukan <tariqt@...lanox.com>
Cc: "netdev@...r.kernel.org" <netdev@...r.kernel.org>
Subject: Re: Mellanox ConnectX-3 VF driver can't work with 16 CPUs?
Hi Dexuan,
On 09/02/2017 12:03 PM, Dexuan Cui wrote:
> Hi,
> While trying SR-IOV with a Linux guest running on Hyper-V, I found this issue:
> the VF driver can't work if the guest has 16 virtual CPUs (less vCPUs, e.g. 8, can work fine):
>
> [ 9.927820] mlx4_core: Mellanox ConnectX core driver v2.2-1 (Feb, 2014)
> [ 9.927882] mlx4_core: Initializing b961:00:02.0
> [ 9.970994] mlx4_core b961:00:02.0: Detected virtual function - running in slave mode
> [ 9.976783] mlx4_core b961:00:02.0: Sending reset
> [ 9.985858] mlx4_core b961:00:02.0: Sending vhcr0
> [ 10.004855] mlx4_core b961:00:02.0: HCA minimum page size:512
> [ 10.010465] mlx4_core b961:00:02.0: Timestamping is not supported in slave mode
> [ 10.203065] mlx4_core b961:00:02.0: Failed to initialize event queue table, aborting
> [ 10.226728] mlx4_core: probe of b961:00:02.0 failed with error -12
>
> I'm using the mainline kernel (4.10.0-rc4).
>
> Any idea?
Thanks for your report.
We'll check this internally and get back to you.
Regards,
Tariq
>
> Thanks,
> -- Dexuan
>
Powered by blists - more mailing lists