All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: kvm@vger.kernel.org
Subject: [Bug 55421] igb VF can't work in KVM guest
Date: Thu, 21 Mar 2013 21:29:09 +0000 (UTC)	[thread overview]
Message-ID: <20130321212909.537AC11F7D1@bugzilla.kernel.org> (raw)
In-Reply-To: <bug-55421-28872@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=55421


Alex Williamson <alex.williamson@redhat.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |alex.williamson@redhat.com,
                   |                            |jeffrey.t.kirsher@intel.com




--- Comment #4 from Alex Williamson <alex.williamson@redhat.com>  2013-03-21 21:29:09 ---
Further bisected to:

commit 5ac6f91d39e0884813dc010e14552143cd1d0d8b
Author: Mitch A Williams <mitch.a.williams@intel.com>
Date:   Fri Jan 18 08:57:20 2013 +0000

    igb: Don't give VFs random MAC addresses

    If the user has not assigned a MAC address to a VM, then don't give it a
    random one. Instead, just give it zeros and let it figure out what to do
    with them.

    Signed-off-by: Mitch Williams <mitch.a.williams@intel.com>
    CC: Andy Gospodarek <andy@greyhouse.net>
    CC: Stefan Assmann <sassmann@kpanic.de>
    Tested-by: Aaron Brown <aaron.f.brown@intel.com>
    Tested-by: Stefan Assmann <sassmann@redhat.com>
    Signed-off-by: Jeff Kirsher <jeffrey.t.kirsher@intel.com>

So, for whatever reason we no longer assign a random MAC address when using the
device in a VM (but we do still use one if attached to igbvf in the host).  I
expect we'll eventually see this on all the Intel SR-IOV NICs.  The solution is
to use the ip command to assign the VF a valid MAC address prior to using it
with KVM.  I'll let those who made the change defend it further if they wish.

-- 
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.

  parent reply	other threads:[~2013-03-21 21:29 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-18 15:05 [Bug 55421] New: igb VF can't work in KVM guest bugzilla-daemon
2013-03-18 15:11 ` [Bug 55421] " bugzilla-daemon
2013-03-18 15:12 ` bugzilla-daemon
2013-03-18 15:12 ` bugzilla-daemon
2013-03-21 21:29 ` bugzilla-daemon [this message]
2013-03-21 21:31   ` Alex Williamson
2013-03-21 22:03     ` Williams, Mitch A
2013-03-21 22:21       ` Alex Williamson
2013-04-22 14:14 ` bugzilla-daemon
2013-04-22 14:14 ` bugzilla-daemon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20130321212909.537AC11F7D1@bugzilla.kernel.org \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --cc=kvm@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.