This change was made by a bot.

** Changed in: linux (Ubuntu)
       Status: New => Confirmed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1821205

Title:
  "couldn't find IFLA_VF_INFO for VF 1 in netlink response" when trying
  to start libvirt VM with Chelsio VF

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  I have a Chelsio T62100-LP-CR and I'm trying to create a libvirt VM
  that gets a VF from the NIC.

  The following XML is used :

      <interface type='hostdev' managed='yes'>
        <mac address='52:54:00:ce:f8:e7'/>
        <source>
          <address type='pci' domain='0x0000' bus='0x21' slot='0x01' 
function='0x4'/>
        </source>
        <address type='pci' domain='0x0000' bus='0x02' slot='0x00' 
function='0x0'/>
      </interface>

  When starting the VM, libvirt fails with the following :
  ubuntu@lubbock:~$ sudo virsh start vmaxino
  error: Failed to start domain vmaxino
  error: internal error: couldn't find IFLA_VF_INFO for VF 1 in netlink response

  This is similar to bug 1496942.

  I can create the VM with the VF if I pass it as a <hostdev> like this :
      <hostdev mode='subsystem' type='pci' managed='yes'>
        <source>
          <address domain='0x0000' bus='0x21' slot='0x01' function='0x4'/>
        </source>
        <address type='pci' domain='0x0000' bus='0x02' slot='0x00' 
function='0x0'/>
      </hostdev>

  More info :
  ubuntu@lubbock:~$ sudo virsh nodedev-dumpxml pci_0000_21_01_4
  <device>
    <name>pci_0000_21_01_4</name>
    <path>/sys/devices/pci0000:20/0000:20:03.1/0000:21:01.4</path>
    <parent>pci_0000_20_03_1</parent>
    <driver>
      <name>vfio-pci</name>
    </driver>
    <capability type='pci'>
      <domain>0</domain>
      <bus>33</bus>
      <slot>1</slot>
      <function>4</function>
      <product id='0x6807'>T62100-LP-CR Unified Wire Ethernet Controller 
[VF]</product>
      <vendor id='0x1425'>Chelsio Communications Inc</vendor>
      <capability type='phys_function'>
        <address domain='0x0000' bus='0x21' slot='0x00' function='0x0'/>
      </capability>
      <iommuGroup number='138'>
        <address domain='0x0000' bus='0x21' slot='0x01' function='0x4'/>
      </iommuGroup>
      <numa node='2'/>
      <pci-express>
        <link validity='cap' port='0' speed='8' width='16'/>
        <link validity='sta' width='0'/>
      </pci-express>
    </capability>
  </device>

  pcap of netlink exchange is attached.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-46-generic 4.15.0-46.49
  ProcVersionSignature: User Name 4.15.0-46.49-generic 4.15.18
  Uname: Linux 4.15.0-46-generic x86_64
  AlsaDevices:
   total 0
   crw-rw---- 1 root audio 116,  1 Mar 21 15:42 seq
   crw-rw---- 1 root audio 116, 33 Mar 21 15:42 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Thu Mar 21 16:16:41 2019
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  MachineType: Supermicro AS -2023US-TR4
  PciMultimedia:
   
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=<set>
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 astdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-46-generic 
root=UUID=7a2aa06e-2ea8-451c-9b77-e0c5cdc445ce ro console=ttyS1,115200 nosplash 
iommu=pt amd_iommu=on processor.max_cstate=0 l1tf=full cpuidle.off=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-46-generic N/A
   linux-backports-modules-4.15.0-46-generic  N/A
   linux-firmware                             1.173.3
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/04/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.1c
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H11DSU-iN
  dmi.board.vendor: Supermicro
  dmi.board.version: 1.02A
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 1
  dmi.chassis.vendor: Supermicro
  dmi.chassis.version: 0123456789
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.1c:bd10/04/2018:svnSupermicro:pnAS-2023US-TR4:pvr0123456789:rvnSupermicro:rnH11DSU-iN:rvr1.02A:cvnSupermicro:ct1:cvr0123456789:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: AS -2023US-TR4
  dmi.product.version: 0123456789
  dmi.sys.vendor: Supermicro

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821205/+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

Reply via email to