Re: [libvirt PATCH] conf: properly clear out autogenerated macvtap names when formatting/parsing

2020-08-24 Thread Daniel Henrique Barboza
On 8/24/20 8:01 PM, Laine Stump wrote: On 8/24/20 6:28 PM, Daniel Henrique Barboza wrote: On 8/23/20 1:52 AM, Laine Stump wrote: Back when macvtap support was added in commit 315baab9443 in Feb. 2010 (libvirt-0.7.7), it was setup to autogenerate a name for the device if one wasn't

Re: [libvirt PATCH] conf: properly clear out autogenerated macvtap names when formatting/parsing

2020-08-24 Thread Laine Stump
On 8/24/20 6:28 PM, Daniel Henrique Barboza wrote: On 8/23/20 1:52 AM, Laine Stump wrote: Back when macvtap support was added in commit 315baab9443 in Feb. 2010 (libvirt-0.7.7), it was setup to autogenerate a name for the device if one wasn't supplied, in the pattern "macvtap%d" (or

Re: [libvirt PATCH] conf: properly clear out autogenerated macvtap names when formatting/parsing

2020-08-24 Thread Daniel Henrique Barboza
On 8/23/20 1:52 AM, Laine Stump wrote: Back when macvtap support was added in commit 315baab9443 in Feb. 2010 (libvirt-0.7.7), it was setup to autogenerate a name for the device if one wasn't supplied, in the pattern "macvtap%d" (or "macvlan%d"), similar to the way an unspecified standard tap

[libvirt PATCH] conf: properly clear out autogenerated macvtap names when formatting/parsing

2020-08-22 Thread Laine Stump
Back when macvtap support was added in commit 315baab9443 in Feb. 2010 (libvirt-0.7.7), it was setup to autogenerate a name for the device if one wasn't supplied, in the pattern "macvtap%d" (or "macvlan%d"), similar to the way an unspecified standard tap device name will lead to an autogenerated