On Tue, Feb 19, 2013 at 09:16:56PM +0100, Laszlo Ersek wrote: > On 02/19/13 18:50, Markus Armbruster wrote: > > > Your example uses -net to connect additional backends to the hubport. > > If I understand you correctly, you can't use -netdev to do that. > > Ignorant question: fundamental reason or just not implemented? > In order to take a stab at your question at last: > - the two (parallel, opposing) links created in (3) connect two backends, > - "-netdev" does not set the peer link in the backend, so you cannot use > that, > - "-device" *would* set the links in both directions, but it's for > creating frontends. > > IOW (3) is unique because it links backend to backend.
Right. -netdev doesn't allow you to specify a peer, only NICs (-device) do that. This means there is no way to hook up -netdev dump with -netdev hubport, they are both -netdevs :(. This is why I said it's just playing games with syntax. I don't think it buys us anything in the end. Stefan
