The following kernel functionality is missing
to make macvtap with SRIOV support same functionality
as one supported by tap with bridge.
This is used by qemu-kvm and so is required to make
kvm support macvtap with SRIOV at the same level
as tap with bridge, which was requested from kvm in 6.1.
At the moment the macvtap interface connects to a device
and adds a single new mac to it. The mac can not be changed
and new addresses can not be added through the macvtap fd.
For multicast, the multicast addresses can not be programmed
through the macvtap fd. At least with intel cards, SRIOV functions
themselves only support one mac address so macvtap can not bind to these.
Similar issue for vlans.
Contrast this with tap which when connected to a bridge
can accept packets for any number of addresses.
(In reply to comment #0)
> The following kernel functionality is missing
> to make macvtap with SRIOV support same functionality
Not sure this is relevant to man-pages-es (Spanish man pages).
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated
in the current release, Red Hat is unfortunately unable to
address this request at this time. Red Hat invites you to
ask your support representative to propose this request, if
appropriate and relevant, in the next release of Red Hat
Enterprise Linux. If you would like it considered as an
exception in the current release, please ask your support
This request was erroneously denied for the current release of Red Hat
Enterprise Linux. The error has been fixed and this request has been
re-proposed for the current release.
This request was erroneously denied for the current release of
Red Hat Enterprise Linux. The error has been fixed and this
request has been re-proposed for the current release.
*** Bug 678488 has been marked as a duplicate of this bug. ***
Since RHEL 6.1 External Beta has begun, and this bug remains
unresolved, it has been rejected as it is not proposed as an
exception or blocker. It has been moved to RHEL 6.2 since
it is a FutureFeature request.
Hi Michael, is any one working on this ?.
I saw this
and i also contacted Dragos Tatulea who is listed as a developer on this.
I havent heard from any one.
I am willing to work on this. Let me know if you know any current status regarding this RFE.
And also if this is targeted for inclusion in RHEL 6.2. I don't see this assigned yet..so I am assuming not.
*** Bug 668712 has been marked as a duplicate of this bug. ***