[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: [libvirt] [PATCH] Basic support for VDE networking

On 12/01/2011, at 11:29 PM, Daniel P. Berrange wrote:
> On Tue, Jan 11, 2011 at 04:12:57PM +0100, Renzo Davoli wrote:
>> I have seen several messages asking for VDE networking support.
>> There is an item also in your todo web page.
>> http://libvirt.org/todo.html
>> I have developed a patch to provide a basic support for VDE.
>> It defines and manages the syntax:
>> <domain ....>
>> <device>
>>  <interface type='vde'>
>>   ...
>>   <switch path='/tmp/vde.ctl'/>
>>  </interface>
>> </device>
>> </domain>
>> the switch tag can be omitted: vde uses the default switch.
>> I have tested the qemu/kvm support.
>> user-mode linux support is included but not tested yet.
>> libvirt vde support for virtualbox has not been coded yet (virtualbox
>> itself supports vde).
> eg, so you'd be able to create/delete/manage VDE daemon instances
> using the 'virsh net-XXX' command set. The guest domains would be
> connected to VDE using the existing  <interface type='network'>
> syntax, and not expose any 'vde' syntax in the guest XML directly.
> I think letting apps manage VDE daemon instances via the libvirt
> APi would make this functionality much more friendly & useful
The patch as it's submitted in this thread is very useful for all
users of qemu/kvm with VDE: it makes it possible for these users to
directly migrated to libvirt to manage VMs without too much hassle.

If it can be managed automatically by libvirt, that would be a plus,
but even then, I think it would be good to still support exposing VDE
directly in the XML so users can manually handle VDE configuration if
they choose to do so.

Is it possible to merge this patch into libvirt so VDE users can
benefit from libvirt?


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]