Bug 1372944 - libvirt doesn't set the mac on VF's netdev name
Summary: libvirt doesn't set the mac on VF's netdev name
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: libvirt
Version: 25
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Laine Stump
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-09-04 05:56 UTC by Moshe Levi
Modified: 2017-03-29 01:44 UTC (History)
8 users (show)

Fixed In Version:
Clone Of:
: 1374384 (view as bug list)
Environment:
Last Closed: 2017-03-29 01:44:27 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1415609 0 high CLOSED libvirt fails to remove guest mac from VFs of certain drivers 2021-09-24 05:39:43 UTC

Internal Links: 1415609

Description Moshe Levi 2016-09-04 05:56:23 UTC 
Description of problem:
Due to this commit cb3fe38c  (which supposed to fix this bug https://bugzilla.redhat.com/show_bug.cgi?id=1113474) libvirt is now setting the mac on the VF using netlink RTM_SETLINK but not on the VF's netdev name.
For macvtap-passthrough we need the mac to be set both on VF's netdev name and using the VF using netlink RTM_SETLINK.

Version-Release number of selected component (if applicable):
libvirt-1.2.18.3-1.fc23.x86_64

How reproducible:
create a guest with macvtap-passthrough in openstack
The guest will not get DHCP because the the VF's netdev name is not set.


Actual results:
guest didn't get DHCP

Expected results:
guest should get DHCP

Additional info:
https://www.redhat.com/archives/libvir-list/2016-September/msg00008.html
Comment 1 Fedora End Of Life 2016-11-25 09:33:30 UTC 
This message is a reminder that Fedora 23 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 23. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '23'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 23 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.
Comment 2 Laine Stump 2016-11-27 22:10:46 UTC 
This problem still exists in F25.
Comment 3 Laine Stump 2017-03-27 02:11:12 UTC 
This is nearly fixed upstream. See the details in RHEL Bug 1415609
Comment 4 Laine Stump 2017-03-29 01:44:27 UTC 
All necessary patches are upstream, and will be in the next libvirt release - 3.2.0.
Note You need to log in before you can comment on or make changes to this bug.