← Back to team overview

kernel-packages team mailing list archive

[Bug 1496942] [NEW] Infiniband (mellanox) SR-IOV and libvirt + libnl problems

 

Public bug reported:

When trying to start an IB SR-IOV guest by using the following XML:

    <interface type='hostdev' managed='yes'>
      <mac address='52:54:00:70:ba:16'/>
      <source>
        <address type='pci' domain='0x0000' bus='0x08' slot='0x00' function='0x1'/>
      </source>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x08' function='0x0'/>
    </interface>

following the Mellanox SR-IOV guide, we are able to start guests using
kernel 3.16 (Utopic).

We are NOT able to start guests using 3.13 OR 3.19. The following error
occurs:

2015-09-17 02:25:07.208+0000: 52157: info : libvirt version: 1.2.12, package: 1.2.12-0ubuntu14.1~cloud0
2015-09-17 02:25:07.208+0000: 52157: error : virSecurityDriverLookup:80 : unsupported configuration: Security driver apparmor not enabled
2015-09-17 02:25:42.308+0000: 52281: info : libvirt version: 1.2.12, package: 1.2.12-0ubuntu14.1~cloud0
2015-09-17 02:25:42.308+0000: 52281: error : virSecurityDriverLookup:80 : unsupported configuration: Security driver apparmor not enabled
2015-09-17 02:25:48.996+0000: 52274: error : virNetDevParseVfConfig:1905 : internal error: missing IFLA_VF_INFO in netlink response
2015-09-17 02:25:49.006+0000: 52274: error : virFileReadAll:1347 : Failed to open file '/var/run/libvirt/hostdevmgr/ib0_vf0': No such file or directory
2015-09-17 02:25:49.006+0000: 52274: error : virFileReadAll:1347 : Failed to open file '/var/run/libvirt/qemu/ib0_vf0': No such file or directory

So probably there is some regression in between 3.16 and 3.19 for the
IFLA_VF_INFO feature from netlink AND this has to be backported to
kernel 3.13 for Trusty to have IB SR-IOV working.

** Affects: linux (Ubuntu)
     Importance: Undecided
     Assignee: Rafael David Tinoco (inaddy)
         Status: In Progress

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

** Changed in: linux (Ubuntu)
     Assignee: (unassigned) => Rafael David Tinoco (inaddy)

-- 
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/1496942

Title:
  Infiniband (mellanox) SR-IOV and libvirt + libnl problems

Status in linux package in Ubuntu:
  In Progress

Bug description:
  When trying to start an IB SR-IOV guest by using the following XML:

      <interface type='hostdev' managed='yes'>
        <mac address='52:54:00:70:ba:16'/>
        <source>
          <address type='pci' domain='0x0000' bus='0x08' slot='0x00' function='0x1'/>
        </source>
        <address type='pci' domain='0x0000' bus='0x00' slot='0x08' function='0x0'/>
      </interface>

  following the Mellanox SR-IOV guide, we are able to start guests using
  kernel 3.16 (Utopic).

  We are NOT able to start guests using 3.13 OR 3.19. The following
  error occurs:

  2015-09-17 02:25:07.208+0000: 52157: info : libvirt version: 1.2.12, package: 1.2.12-0ubuntu14.1~cloud0
  2015-09-17 02:25:07.208+0000: 52157: error : virSecurityDriverLookup:80 : unsupported configuration: Security driver apparmor not enabled
  2015-09-17 02:25:42.308+0000: 52281: info : libvirt version: 1.2.12, package: 1.2.12-0ubuntu14.1~cloud0
  2015-09-17 02:25:42.308+0000: 52281: error : virSecurityDriverLookup:80 : unsupported configuration: Security driver apparmor not enabled
  2015-09-17 02:25:48.996+0000: 52274: error : virNetDevParseVfConfig:1905 : internal error: missing IFLA_VF_INFO in netlink response
  2015-09-17 02:25:49.006+0000: 52274: error : virFileReadAll:1347 : Failed to open file '/var/run/libvirt/hostdevmgr/ib0_vf0': No such file or directory
  2015-09-17 02:25:49.006+0000: 52274: error : virFileReadAll:1347 : Failed to open file '/var/run/libvirt/qemu/ib0_vf0': No such file or directory

  So probably there is some regression in between 3.16 and 3.19 for the
  IFLA_VF_INFO feature from netlink AND this has to be backported to
  kernel 3.13 for Trusty to have IB SR-IOV working.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1496942/+subscriptions


Follow ups