[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: [libvirt] [PATCH 3/4] virnetdevvportprofile: Changes to support portprofiles for hostdevs

On Fri, 2012-03-02 at 14:27 -0500, Laine Stump wrote:
> So, at the end of this, is there *any* 802.1QbX mode that can work
> using
> PCI passthrough without at least one of the following things:
> 1) a macvtap interface on the host. (what about my idea of attaching a
> macvtap interface to the PF? does that have any hint of practicality?)
> 2) extending the protocol for talking with lldpad to support using a
> raw
> PCI device rather than a macvtap device.

> 3) the guest doing vlan tagging
> 4) the guest doing the full 802.1QbX associate/de-associate protocol
> exchange itself?
> Nobody has said it explicitly yet (I think), but I have the impression
> that this problem unfortunately can't be solved by libvirt alone. If
> that's the case, we should state that as soon as possible so that we
> can
> table the <virtualport> part of these patches for the short term, and
> separate the mac address part to get it pushed upstream (along with
> the
> new low-level PCI utility functions), as that is very useful on its
> own.

I am not sure I can follow the conclusion that this can not be solved in
libvirt alone. 
For the macvtap case, the macvtap device is "attached" to the underlying
physical interface and this is where the association request is sent to,
via lldpad.
For the PCI passthrough case, the same must be possible, assuming the
physical interface can be concluded from the PCI device and the VLAN
information is provided.

Or do I miss something?

Best regards, 

Gerhard Stenzel, Hybrid Technologies, LTC
IBM Deutschland Research & Development GmbH
Vorsitzende des Aufsichtsrats: Martina Koederitz | Geschäftsführung:
Dirk Wittkopp
Sitz der Gesellschaft: Böblingen | Registergericht: Amtsgericht
Stuttgart, HRB 243294

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]