Re: [libvirt] [PATCH 12/28] conf/openvz: eliminate incorrect/undocumented use of

2016-06-24 Thread Laine Stump
On 06/24/2016 03:35 PM, Laine Stump wrote: On 06/23/2016 06:14 PM, John Ferlan wrote: On 06/22/2016 01:37 PM, Laine Stump wrote: When support for was added in commit 9a4b705f back in 2010, it erroneously looked at for a user-specified guest-side interface name. This was never documented thou

Re: [libvirt] [PATCH 12/28] conf/openvz: eliminate incorrect/undocumented use of

2016-06-24 Thread Laine Stump
On 06/23/2016 06:14 PM, John Ferlan wrote: On 06/22/2016 01:37 PM, Laine Stump wrote: When support for was added in commit 9a4b705f back in 2010, it erroneously looked at for a user-specified guest-side interface name. This was never documented though. (that attribute already existed at the t

Re: [libvirt] [PATCH 12/28] conf/openvz: eliminate incorrect/undocumented use of

2016-06-23 Thread John Ferlan
On 06/22/2016 01:37 PM, Laine Stump wrote: > When support for was added in commit > 9a4b705f back in 2010, it erroneously looked at > for a user-specified guest-side interface name. This was never > documented though. (that attribute already existed at the time in the > data.ethernet union memb

[libvirt] [PATCH 12/28] conf/openvz: eliminate incorrect/undocumented use of

2016-06-22 Thread Laine Stump
When support for was added in commit 9a4b705f back in 2010, it erroneously looked at for a user-specified guest-side interface name. This was never documented though. (that attribute already existed at the time in the data.ethernet union member of virDomainNetDef, but apparently had no practical