I can see the Mellanox devices with that 4.17.0-1001-azure kernel. I installed the new kernel:
sudo dpkg -i linux- modules-4.17.0-1001-azure_4.17.0-1001.2~lp1794477_amd64.deb linux- modules-extra-4.17.0-1001-azure_4.17.0-1001.2~lp1794477_amd64.deb linux- image-unsigned-4.17.0-1001-azure_4.17.0-1001.2~lp1794477_amd64.deb Fixed the missing depencies with: sudo apt --fix-broken install Updated grub just in case: sudo update-grub I rebooted and I see the devices: ubuntu@lp1794477:~$ uname -a Linux lp1794477 4.17.0-1001-azure #2~lp1794477 SMP Tue Nov 20 22:40:04 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux ubuntu@lp1794477:~$ dmesg | grep -i mella [ 5.534382] mlx4_core: Mellanox ConnectX core driver v4.0-0 [ 5.564313] <mlx4_ib> mlx4_ib_add: mlx4_ib: Mellanox ConnectX InfiniBand driver v4.0-0 [ 5.588721] mlx4_en: Mellanox ConnectX HCA Ethernet driver v4.0-0 ubuntu@lp1794477:~$ lspci | grep -i mell ae9f:00:02.0 Ethernet controller: Mellanox Technologies MT27500/MT27520 Family [ConnectX-3/ConnectX-3 Pro Virtual Function] ubuntu@lp1794477:~$ lsmod | grep -i mlx mlx4_en 114688 0 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1794477 Title: Accelerated networking (SR-IOV VF) broken in 18.10 daily Status in linux package in Ubuntu: In Progress Status in linux-azure package in Ubuntu: Confirmed Status in linux source package in Cosmic: In Progress Bug description: While testing Ubuntu 18.10 daily from cloud-images repo, on Azure, we discovered that accelerated networking wasn’t working inside the VM. No VF shows up inside the VM and lspci didn’t show any Mellanox drivers in use. We tested the daily build on Hyper-V also, but there the Mellanox VF is functional, with the same mlx4 drivers. To give more details about this: • No mellanox logs are showing up in dmesg or syslog. • Modinfo mlx4_core/mlx4_en finds the module, but lsmod doesn’t show it as loaded, although Accelerated Networking is enabled for the Azure VM, so this should happen transparently. • Modprobe -r mlx4_core && modprobe mlx4_core is giving 0 exit code, but nothing really happens. And no Mellanox messages are logged in dmesg/syslog. - There are no entries in the logs to show anything about the drivers or netvsc/pci-hyperv that might relate to this issue. Kernel: 4.18.0-7-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1794477/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
