[libvirt-users] [Libvir] libvirt & vde_switch
Hi, I would like to ask about status of VDE and libvirt. I found a thread from http://www.redhat.com/archives/libvir-list/2008-February/msg00030.html. I am not interested in connecting the VDE to the outside world. I have created a FW machine using macvtap. To this machine I would like to attach machines from different zones (dmz, prod, cust). I was thinking on using VDE and vlans (FW would have 1 interface in each vlan - machines also), but I am not aware how to configure this in libvirt. I now assume I can do the same setup with regular bridges for the moment (benefit of VDE would be only 1 switch for many vlans). Regards, Robert -- stereoIT - Open Source Technology Partners http://www.stereoit.com mobile: +420 776 762378
The 05/04/11, Robert Šmol wrote:
I would like to ask about status of VDE and libvirt. I found a thread from http://www.redhat.com/archives/libvir-list/2008-February/msg00030.html.
AFAIK, vde_switch is still unsupported by libvirt and nobody seems to work on it these days. Most people wanting vde_switch (or open vswitch) enough leave libvirt.
I am not interested in connecting the VDE to the outside world. I have created a FW machine using macvtap. To this machine I would like to attach machines from different zones (dmz, prod, cust). I was thinking on using VDE and vlans (FW would have 1 interface in each vlan - machines also), but I am not aware how to configure this in libvirt.
I now assume I can do the same setup with regular bridges for the moment
Yes, this is what I do for now.
(benefit of VDE would be only 1 switch for many vlans).
Plus more features (i.e.: easy virtual switch link between hosts), maintenance facilities, etc. -- Nicolas Sebrecht
On 04/06/2011 10:34 AM, Nicolas Sebrecht wrote:
The 05/04/11, Robert Šmol wrote:
I would like to ask about status of VDE and libvirt. I found a thread from http://www.redhat.com/archives/libvir-list/2008-February/msg00030.html. AFAIK, vde_switch is still unsupported by libvirt and nobody seems to work on it these days.
Most people wanting vde_switch (or open vswitch) enough leave libvirt.
On #IRC I got point to message: http://www.mail-archive.com/libvir-list@redhat.com/msg32081.html It seems there is a patch ready. I will test it against 0.9.0. What is the procedure to get the patch reviewed and eventually get into libvirt? I mean VMware has vSwitch and it is very powerful. I'll checkout the vswitch as well.
I am not interested in connecting the VDE to the outside world. I have created a FW machine using macvtap. To this machine I would like to attach machines from different zones (dmz, prod, cust). I was thinking on using VDE and vlans (FW would have 1 interface in each vlan - machines also), but I am not aware how to configure this in libvirt.
I now assume I can do the same setup with regular bridges for the moment Yes, this is what I do for now.
(benefit of VDE would be only 1 switch for many vlans).
Plus more features (i.e.: easy virtual switch link between hosts), maintenance facilities, etc.
-- stereoIT - Open Source Technology Partners http://www.stereoit.com mobile: +420 776 762378
The 06/04/11, Robert Šmol wrote:
On 04/06/2011 10:34 AM, Nicolas Sebrecht wrote:
The 05/04/11, Robert Šmol wrote:
I would like to ask about status of VDE and libvirt. I found a thread from http://www.redhat.com/archives/libvir-list/2008-February/msg00030.html. AFAIK, vde_switch is still unsupported by libvirt and nobody seems to work on it these days.
Most people wanting vde_switch (or open vswitch) enough leave libvirt.
On #IRC I got point to message:
http://www.mail-archive.com/libvir-list@redhat.com/msg32081.html
It seems there is a patch ready. I will test it against 0.9.0. What is the procedure to get the patch reviewed and eventually get into libvirt?
The patch wasn't merged but the why is a question to the maintainers. I guess the way it was implemented did not convinced. This is what I understand from the whole thread, at least. -- Nicolas Sebrecht
On 04/06/2011 04:00 PM, Nicolas Sebrecht wrote:
The 06/04/11, Robert Šmol wrote:
On 04/06/2011 10:34 AM, Nicolas Sebrecht wrote:
The 05/04/11, Robert Šmol wrote:
I would like to ask about status of VDE and libvirt. I found a thread from http://www.redhat.com/archives/libvir-list/2008-February/msg00030.html. AFAIK, vde_switch is still unsupported by libvirt and nobody seems to work on it these days.
Most people wanting vde_switch (or open vswitch) enough leave libvirt.
On #IRC I got point to message:
http://www.mail-archive.com/libvir-list@redhat.com/msg32081.html
It seems there is a patch ready. I will test it against 0.9.0. What is the procedure to get the patch reviewed and eventually get into libvirt? The patch wasn't merged but the why is a question to the maintainers. I guess the way it was implemented did not convinced. This is what I understand from the whole thread, at least.
From the thread it seems the maintainers would like to have a network based on VDE. To me it also looks like better idea (create vde network and then just attach the domain to a network. -- stereoIT - Open Source Technology Partners http://www.stereoit.com mobile: +420 776 762378
For my needs I would like to see either vdeswitch or openvswitch integrated in the project. Is there any preference from the users/developers on which one of those I should start looking into? Also I would like to know how this should be integrated, from the mails I can see devs prefers to have virtual switch present as a network. Can someone describe how the integration should be done? Support for additional features like vlan, QoS? Robert On 04/06/2011 04:13 PM, Robert Šmol wrote:
On 04/06/2011 04:00 PM, Nicolas Sebrecht wrote:
The 06/04/11, Robert Šmol wrote:
On 04/06/2011 10:34 AM, Nicolas Sebrecht wrote:
The 05/04/11, Robert Šmol wrote:
I would like to ask about status of VDE and libvirt. I found a thread from http://www.redhat.com/archives/libvir-list/2008-February/msg00030.html.
AFAIK, vde_switch is still unsupported by libvirt and nobody seems to work on it these days.
Most people wanting vde_switch (or open vswitch) enough leave libvirt.
On #IRC I got point to message:
http://www.mail-archive.com/libvir-list@redhat.com/msg32081.html
It seems there is a patch ready. I will test it against 0.9.0. What is the procedure to get the patch reviewed and eventually get into libvirt? The patch wasn't merged but the why is a question to the maintainers. I guess the way it was implemented did not convinced. This is what I understand from the whole thread, at least.
From the thread it seems the maintainers would like to have a network based on VDE. To me it also looks like better idea (create vde network and then just attach the domain to a network.
-- stereoIT - Open Source Technology Partners http://www.stereoit.com mobile: +420 776 762378
On 04/28/2011 09:56 AM, Robert Šmol wrote:
For my needs I would like to see either vdeswitch or openvswitch integrated in the project. Is there any preference from the users/developers on which one of those I should start looking into?
Are you volunteering to write some code? :-) There have been requests for both, and both should eventually be done, so I guess pick whichever one you like better :-) (since there's already a patch for VDE, albeit with different XML than we'd like, that may be quicker to finish.) You may want to follow development of the work I'll point out below, though, otherwise you could waste a lot of time.
Also I would like to know how this should be integrated, from the mails I can see devs prefers to have virtual switch present as a network. Can someone describe how the integration should be done? Support for additional features like vlan, QoS?
Once we get into these kinds of questions, it's probably best to switch to the developers' list (libvir-list@redhat.com) to get better exposure to people writing the code. I'm Cc'ing this message there (and switching the Reply-To: as well). In particular, I recently send an RFC to libvir-list proposing an expansion of the <network> XML to remove the hard-coded connection between guest interface and host interface for macvtap (type='direct') interfaces: https://www.redhat.com/archives/libvir-list/2011-April/msg00591.html and in a followup message showed how we could expand on this work to provide support for openvswitch (or vde): https://www.redhat.com/archives/libvir-list/2011-April/msg00640.html I'm planning to have this code finished and tested within the next two months at most (hopefully considerably earlier). If you're interested in implementing a <network type='openvswitch'> or <network type='vde'> you should subscribe to libvir-list (if you aren't already) so that you can follow along.
Robert
On 04/06/2011 04:13 PM, Robert Šmol wrote:
On 04/06/2011 04:00 PM, Nicolas Sebrecht wrote:
The 06/04/11, Robert Šmol wrote:
On 04/06/2011 10:34 AM, Nicolas Sebrecht wrote:
The 05/04/11, Robert Šmol wrote:
I would like to ask about status of VDE and libvirt. I found a thread from http://www.redhat.com/archives/libvir-list/2008-February/msg00030.html.
AFAIK, vde_switch is still unsupported by libvirt and nobody seems to work on it these days.
Most people wanting vde_switch (or open vswitch) enough leave libvirt.
On #IRC I got point to message:
http://www.mail-archive.com/libvir-list@redhat.com/msg32081.html
It seems there is a patch ready. I will test it against 0.9.0. What is the procedure to get the patch reviewed and eventually get into libvirt? The patch wasn't merged but the why is a question to the maintainers. I guess the way it was implemented did not convinced. This is what I understand from the whole thread, at least.
From the thread it seems the maintainers would like to have a network based on VDE. To me it also looks like better idea (create vde network and then just attach the domain to a network.
On 04/28/2011 04:35 PM, Laine Stump wrote:
On 04/28/2011 09:56 AM, Robert Šmol wrote:
For my needs I would like to see either vdeswitch or openvswitch integrated in the project. Is there any preference from the users/developers on which one of those I should start looking into?
Are you volunteering to write some code? :-)
There have been requests for both, and both should eventually be done, so I guess pick whichever one you like better :-) (since there's already a patch for VDE, albeit with different XML than we'd like, that may be quicker to finish.)
You may want to follow development of the work I'll point out below, though, otherwise you could waste a lot of time.
OK, I'll try to start with vde. I've subscribed now to libvirt-list as well.
Also I would like to know how this should be integrated, from the mails I can see devs prefers to have virtual switch present as a network. Can someone describe how the integration should be done? Support for additional features like vlan, QoS?
Once we get into these kinds of questions, it's probably best to switch to the developers' list (libvir-list@redhat.com) to get better exposure to people writing the code. I'm Cc'ing this message there (and switching the Reply-To: as well).
In particular, I recently send an RFC to libvir-list proposing an expansion of the <network> XML to remove the hard-coded connection between guest interface and host interface for macvtap (type='direct') interfaces:
https://www.redhat.com/archives/libvir-list/2011-April/msg00591.html
and in a followup message showed how we could expand on this work to provide support for openvswitch (or vde):
https://www.redhat.com/archives/libvir-list/2011-April/msg00640.html
I'm planning to have this code finished and tested within the next two months at most (hopefully considerably earlier). If you're interested in implementing a <network type='openvswitch'> or <network type='vde'> you should subscribe to libvir-list (if you aren't already) so that you can follow along.
I am now trying to compile the stuff, but I get: ... CCLD libvirt_driver_nwfilter.la libtool: link: require no space between `-L' and `/usr/lib' make[3]: *** [libvirt_driver_nwfilter.la] Error 1 make[3]: Leaving directory `/home/rsmol/Code/libvirt/src' make[2]: *** [all] Error 2 make[2]: Leaving directory `/home/rsmol/Code/libvirt/src' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/home/rsmol/Code/libvirt' make: *** [all] Error 2 ... But I'll figure out eventually.
Robert
On 04/06/2011 04:13 PM, Robert Šmol wrote:
On 04/06/2011 04:00 PM, Nicolas Sebrecht wrote:
On 04/06/2011 10:34 AM, Nicolas Sebrecht wrote:
The 05/04/11, Robert Šmol wrote:
> I would like to ask about status of VDE and libvirt. I found a > thread from > http://www.redhat.com/archives/libvir-list/2008-February/msg00030.html. > AFAIK, vde_switch is still unsupported by libvirt and nobody seems to work on it these days.
Most people wanting vde_switch (or open vswitch) enough leave libvirt.
On #IRC I got point to message:
http://www.mail-archive.com/libvir-list@redhat.com/msg32081.html
It seems there is a patch ready. I will test it against 0.9.0. What is the procedure to get the patch reviewed and eventually get into libvirt? The patch wasn't merged but the why is a question to the
The 06/04/11, Robert Šmol wrote: maintainers. I guess the way it was implemented did not convinced. This is what I understand from the whole thread, at least.
From the thread it seems the maintainers would like to have a network based on VDE. To me it also looks like better idea (create vde network and then just attach the domain to a network.
-- stereoIT - Open Source Technology Partners http://www.stereoit.com mobile: +420 776 762378
2011/5/1 Robert Šmol <robert.smol@stereoit.com>:
I am now trying to compile the stuff, but I get: ... CCLD libvirt_driver_nwfilter.la libtool: link: require no space between `-L' and `/usr/lib' make[3]: *** [libvirt_driver_nwfilter.la] Error 1 make[3]: Leaving directory `/home/rsmol/Code/libvirt/src' make[2]: *** [all] Error 2 make[2]: Leaving directory `/home/rsmol/Code/libvirt/src' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/home/rsmol/Code/libvirt' make: *** [all] Error 2 ...
But I'll figure out eventually.
libtool tells you that if found '-L /usr/lib' in the commandline, but it would like to see '-L/usr/lib' (without the space). Typically this comes from a "broken" pkg-config file from one of the libraries libvirt depends on. Run 'make V=1' to make it print the complete commandlines, this might help figuring out from which library the problem comes. Matthias
On 05/02/2011 08:28 AM, Matthias Bolte wrote:
I am now trying to compile the stuff, but I get: ... CCLD libvirt_driver_nwfilter.la libtool: link: require no space between `-L' and `/usr/lib' make[3]: *** [libvirt_driver_nwfilter.la] Error 1 make[3]: Leaving directory `/home/rsmol/Code/libvirt/src' make[2]: *** [all] Error 2 make[2]: Leaving directory `/home/rsmol/Code/libvirt/src' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/home/rsmol/Code/libvirt' make: *** [all] Error 2 ...
But I'll figure out eventually.
2011/5/1 Robert Šmol<robert.smol@stereoit.com>: libtool tells you that if found '-L /usr/lib' in the commandline, but it would like to see '-L/usr/lib' (without the space). Typically this comes from a "broken" pkg-config file from one of the libraries libvirt depends on.
Run 'make V=1' to make it print the complete commandlines, this might help figuring out from which library the problem comes.
Matthias
rsmol@laptop:~/Code/libvirt (git:master)$ pcap-config --libs -L /usr/lib -lpcap I filled #775433 on ubuntu for pcap-config. modified pcap-config and now I can compile the libvirt just fine. Moving on. Robert -- stereoIT - Open Source Technology Partners http://www.stereoit.com mobile: +420 776 762378
participants (4)
-
Laine Stump -
Matthias Bolte -
Nicolas Sebrecht -
Robert Šmol