On Fri, Jan 08, 2021 at 08:28:28AM +0100, Erik Skultety wrote:
> On Thu, Jan 07, 2021 at 07:33:38PM -0300, Daniel Henrique Barboza wrote:
> >
> >
> > On 1/7/21 5:22 PM, Ján Tomko wrote:
> > > On a Thursday in 2021, Laine Stump wrote:
> > > > On 1/7/21 10:09 AM, Michal Privoznik wrote:
> > > > >
On Thu, Jan 07, 2021 at 07:33:38PM -0300, Daniel Henrique Barboza wrote:
>
>
> On 1/7/21 5:22 PM, Ján Tomko wrote:
> > On a Thursday in 2021, Laine Stump wrote:
> > > On 1/7/21 10:09 AM, Michal Privoznik wrote:
> > > > When defining/creating a network the bridge name may be filled in
> > > > aut
On 1/7/21 5:22 PM, Ján Tomko wrote:
On a Thursday in 2021, Laine Stump wrote:
On 1/7/21 10:09 AM, Michal Privoznik wrote:
When defining/creating a network the bridge name may be filled in
automatically by libvirt (if none provided in the input XML or
the one provided is a pattern, e.g. "virb
On a Thursday in 2021, Laine Stump wrote:
On 1/7/21 10:09 AM, Michal Privoznik wrote:
When defining/creating a network the bridge name may be filled in
automatically by libvirt (if none provided in the input XML or
the one provided is a pattern, e.g. "virbr%d"). During the
bridge name generation
On 1/7/21 10:09 AM, Michal Privoznik wrote:
When defining/creating a network the bridge name may be filled in
automatically by libvirt (if none provided in the input XML or
the one provided is a pattern, e.g. "virbr%d"). During the
bridge name generation process a candidate name is generated
whic
When defining/creating a network the bridge name may be filled in
automatically by libvirt (if none provided in the input XML or
the one provided is a pattern, e.g. "virbr%d"). During the
bridge name generation process a candidate name is generated
which is then checked with the rest of already def
