lkml.org 
[lkml]   [2012]   [Jan]   [31]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
SubjectRE: VFs go missing with latest kernel
Date
> -----Original Message-----
> From: David Ahern [mailto:daahern@cisco.com]
> Sent: Tuesday, January 31, 2012 4:31 PM
> To: Rose, Gregory V
> Cc: LKML
> Subject: Re: VFs go missing with latest kernel
>
> On 01/31/2012 03:58 PM, Rose, Gregory V wrote:
> >> I am hitting some other problem trying to use the VF on 3.3.0-rc1 --
> KVM
> >> fails the KVM_CAP_IOMMU check though the server has one (works fine
> with
> >> the older kernel) and it is built into the kernel. Debugging that
> >> problem now.
>
> second problem was due to a CONFIG setting.
>
> Back to the missing VF problem: reverting the patch I mentioned before
> and my VM boots up fine with the even-numbered VFs assigned to it.

OK, thanks... I was staring at the dmesg output you sent me and it is odd because the even numbered VFs that go missing are there when you set their MAC addresses. See output below the dotted line after my reply.

Also, the dmesg output indicates 28 VFs are created but the lspci output you've sent only shows 14, even from the stock FC 14 kernel. So even in that case you seem to be missing 14 VFs from the lspci output.

So they're there at one point but then disappear. Very odd. I'm finishing up a few other things but will try to repro ASAP and get back to you with my results.

- Greg

------------
[ 81.432421] igb 0000:07:00.0: setting MAC 02:12:34:56:79:41 on VF 1
[ 81.432550] igb 0000:07:00.0: Reload the VF driver to make this change effective.
[ 81.432667] igb 0000:07:00.0: The VF MAC address has been set, but the PF device is not up.
[ 81.432942] igb 0000:07:00.0: Bring the PF device up before attempting to use the VF device.
[ 81.434947] igb 0000:07:00.0: setting MAC 02:12:34:56:79:42 on VF 2
[ 81.435060] igb 0000:07:00.0: Reload the VF driver to make this change effective.
[ 81.435174] igb 0000:07:00.0: The VF MAC address has been set, but the PF device is not up.
[ 81.435450] igb 0000:07:00.0: Bring the PF device up before attempting to use the VF device.
[ 81.437429] igb 0000:07:00.0: setting MAC 02:12:34:56:79:43 on VF 3
[ 81.437555] igb 0000:07:00.0: Reload the VF driver to make this change effective.
[ 81.437670] igb 0000:07:00.0: The VF MAC address has been set, but the PF device is not up.
[ 81.437937] igb 0000:07:00.0: Bring the PF device up before attempting to use the VF device.
[ 81.439904] igb 0000:07:00.0: setting MAC 02:12:34:56:79:44 on VF 4
[ 81.440016] igb 0000:07:00.0: Reload the VF driver to make this change effective.
[ 81.440132] igb 0000:07:00.0: The VF MAC address has been set, but the PF device is not up.
[ 81.440400] igb 0000:07:00.0: Bring the PF device up before attempting to use the VF device.
[ 81.442328] igb 0000:07:00.0: setting MAC 02:12:34:56:79:45 on VF 5
[ 81.442453] igb 0000:07:00.0: Reload the VF driver to make this change effective.
[ 81.442567] igb 0000:07:00.0: The VF MAC address has been set, but the PF device is not up.
[ 81.442837] igb 0000:07:00.0: Bring the PF device up before attempting to use the VF device.
[ 81.444921] igb 0000:07:00.0: setting MAC 02:12:34:56:79:46 on VF 6
[ 81.445035] igb 0000:07:00.0: Reload the VF driver to make this change effective.
[ 81.445149] igb 0000:07:00.0: The VF MAC address has been set, but the PF device is not up.
[ 81.445417] igb 0000:07:00.0: Bring the PF device up before attempting to use the VF device.
-------------------

>
> David


\
 
 \ /
  Last update: 2012-02-01 01:45    [W:0.045 / U:0.228 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site