<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<font face="Helvetica, Arial, sans-serif"><br>
ok, thanks for the explainer.</font><br>
<br>
<div class="moz-cite-prefix">On 04.01.21 12:20, Daniel P. Berrangé
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:20210104112041.GC640208@redhat.com">
<pre class="moz-quote-pre" wrap="">On Fri, Jan 01, 2021 at 10:24:41AM +0100, vrms wrote:
</pre>
<blockquote type="cite">
<pre class="moz-quote-pre" wrap="">I am trying to understand KVM networking a little better and have noted
that the "virbr0" network interface (the default KVM bridge) comes with
another device named "virbr0-nic".
The same kind of pair comes with each new bridge you may create via the
"virtual machine manager" (and assumingly other KVM tools alike)
Like "virbr1" comes in a pair with "virbr1-nic" (the *-nic interface is
being created automatically (and I assume will disapear automatically if
you remove the parent interface)
Can anybody kindly explain how these pairs are related to each other
and/or work together?
</pre>
</blockquote>
<pre class="moz-quote-pre" wrap="">
The "$FOO-nic" device is a tap device created as a hack to force a
stable MAC address on the main bridge device due to bad kernel impl
of bridge device MAC address assignment.
We stopped creating the "$FOO-nic" device in libvirt 6.8.0 since the
kernel was long ago fixed.
Regards,
Daniel
</pre>
</blockquote>
<br>
</body>
</html>