Re: [libvirt] [PATCH v2] RFC Libvirt + Openvswitch

2012-02-15 Thread Laine Stump
On 02/14/2012 09:26 PM, Laine Stump wrote: > On 02/14/2012 05:33 PM, Eric Blake wrote: >> On 02/13/2012 10:56 PM, Laine Stump wrote: >> >>> But because an interfaceid is auto-generated by the parser when one >>> isn't given, and a common parser function for virtualport is used by the >>> domain and

Re: [libvirt] [PATCH v2] RFC Libvirt + Openvswitch

2012-02-14 Thread Laine Stump
On 02/14/2012 05:33 PM, Eric Blake wrote: > On 02/13/2012 10:56 PM, Laine Stump wrote: > >> But because an interfaceid is auto-generated by the parser when one >> isn't given, and a common parser function for virtualport is used by the >> domain and network parsers, this will result in an interface

Re: [libvirt] [PATCH v2] RFC Libvirt + Openvswitch

2012-02-14 Thread Eric Blake
On 02/13/2012 10:56 PM, Laine Stump wrote: > But because an interfaceid is auto-generated by the parser when one > isn't given, and a common parser function for virtualport is used by the > domain and network parsers, this will result in an interfaceid being > filled in when the network is defined

Re: [libvirt] [PATCH v2] RFC Libvirt + Openvswitch

2012-02-13 Thread Laine Stump
On 02/10/2012 04:09 PM, Ansis Atteka wrote: > This patch allows libvirt to add interfaces to already > existing Open vSwitch bridges. The following syntax in > domain XML file can be used: > > > > > > > >function='0x0'/> > > > or if libvirt sho

[libvirt] [PATCH v2] RFC Libvirt + Openvswitch

2012-02-10 Thread Ansis Atteka
This patch allows libvirt to add interfaces to already existing Open vSwitch bridges. The following syntax in domain XML file can be used: or if libvirt should auto-generate the interfaceid use following syntax: