Re: [vde-users] Newbie questions: managing VLANs in VDE
On Sun, May 26, 2013 at 9:13 PM, Renzo Davoli wrote: > The version I have just uploaded on SVN should fix the problem. > Please let me know. > renzo Hello, segfault is gone. I haven't tested anything else though(might do later). Thanks, Z. > On Sun, May 26, 2013 at 07:34:40PM +0200, Zdenek Styblik wrote: >> On Sun, May 26, 2013 at 6:35 PM, Renzo Davoli wrote: >> > I have tried: >> > >> > $ vde_switch -s /var/run/vde2//vde.virswitch0 --mgmt >> > /var/run/vde2//vde.virswitch0.sock --mgmtmode 660 -p >> > /var/run/vde2//vde.virswitch0.pid >> > >> > vde$ port/create 24 >> > 1000 Success >> > >> > vde$ port/setvlan 24 4095 >> > 1000 Success >> > >> > both using trunk code and rd235 experimental and I have not got any >> > sigsegv. >> > >> > If I am not able to replicate the bug here it is hard for me to catch the >> > bug... >> > >> > can you give me some more info about your configuration? >> > >> > renzo davoli >> >> And have you actually attached QEMU to this port? Because SIGSEGV >> happens after you attach QEMU to such port. >> >> ``-netdev vde,id=hostnet0,sock=/var/run/vde2/vde.virswitch0,port=24'' >> >> Please, tell me what information would be useful to you. I'd say I >> have pretty generic setup here. >> >> Thanks, >> Z. -- Try New Relic Now & We'll Send You this Cool Shirt New Relic is the only SaaS-based application performance monitoring service that delivers powerful full stack analytics. Optimize and monitor your browser, app, & servers with just a few lines of code. Try New Relic and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_may ___ vde-users mailing list vde-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/vde-users
Re: [vde-users] Newbie questions: managing VLANs in VDE
The version I have just uploaded on SVN should fix the problem. Please let me know. renzo On Sun, May 26, 2013 at 07:34:40PM +0200, Zdenek Styblik wrote: > On Sun, May 26, 2013 at 6:35 PM, Renzo Davoli wrote: > > I have tried: > > > > $ vde_switch -s /var/run/vde2//vde.virswitch0 --mgmt > > /var/run/vde2//vde.virswitch0.sock --mgmtmode 660 -p > > /var/run/vde2//vde.virswitch0.pid > > > > vde$ port/create 24 > > 1000 Success > > > > vde$ port/setvlan 24 4095 > > 1000 Success > > > > both using trunk code and rd235 experimental and I have not got any sigsegv. > > > > If I am not able to replicate the bug here it is hard for me to catch the > > bug... > > > > can you give me some more info about your configuration? > > > > renzo davoli > > And have you actually attached QEMU to this port? Because SIGSEGV > happens after you attach QEMU to such port. > > ``-netdev vde,id=hostnet0,sock=/var/run/vde2/vde.virswitch0,port=24'' > > Please, tell me what information would be useful to you. I'd say I > have pretty generic setup here. > > Thanks, > Z. -- Try New Relic Now & We'll Send You this Cool Shirt New Relic is the only SaaS-based application performance monitoring service that delivers powerful full stack analytics. Optimize and monitor your browser, app, & servers with just a few lines of code. Try New Relic and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_may ___ vde-users mailing list vde-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/vde-users
Re: [vde-users] Newbie questions: managing VLANs in VDE
On Sun, May 26, 2013 at 6:35 PM, Renzo Davoli wrote: > I have tried: > > $ vde_switch -s /var/run/vde2//vde.virswitch0 --mgmt > /var/run/vde2//vde.virswitch0.sock --mgmtmode 660 -p > /var/run/vde2//vde.virswitch0.pid > > vde$ port/create 24 > 1000 Success > > vde$ port/setvlan 24 4095 > 1000 Success > > both using trunk code and rd235 experimental and I have not got any sigsegv. > > If I am not able to replicate the bug here it is hard for me to catch the > bug... > > can you give me some more info about your configuration? > > renzo davoli And have you actually attached QEMU to this port? Because SIGSEGV happens after you attach QEMU to such port. ``-netdev vde,id=hostnet0,sock=/var/run/vde2/vde.virswitch0,port=24'' Please, tell me what information would be useful to you. I'd say I have pretty generic setup here. Thanks, Z. -- Try New Relic Now & We'll Send You this Cool Shirt New Relic is the only SaaS-based application performance monitoring service that delivers powerful full stack analytics. Optimize and monitor your browser, app, & servers with just a few lines of code. Try New Relic and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_may ___ vde-users mailing list vde-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/vde-users
Re: [vde-users] Newbie questions: managing VLANs in VDE
I have tried: $ vde_switch -s /var/run/vde2//vde.virswitch0 --mgmt /var/run/vde2//vde.virswitch0.sock --mgmtmode 660 -p /var/run/vde2//vde.virswitch0.pid vde$ port/create 24 1000 Success vde$ port/setvlan 24 4095 1000 Success both using trunk code and rd235 experimental and I have not got any sigsegv. If I am not able to replicate the bug here it is hard for me to catch the bug... can you give me some more info about your configuration? renzo davoli -- Try New Relic Now & We'll Send You this Cool Shirt New Relic is the only SaaS-based application performance monitoring service that delivers powerful full stack analytics. Optimize and monitor your browser, app, & servers with just a few lines of code. Try New Relic and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_may ___ vde-users mailing list vde-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/vde-users
Re: [vde-users] Newbie questions: managing VLANs in VDE
On Sat, May 25, 2013 at 8:10 PM, Daniele Lacamera wrote: > The situation might have differed if you would have been able to fill in a > bug with a specific description, including the exact way to reproduce this > (system you are running, full qemu command line, ...). > I'll do it later. There is no problem doing such thing, but given the inactivity on mailing list and the fact vde-switch didn't have release for 2 years, it seemed like a waste of time. And yes, I'm aware of SVN activity, but that doesn't mean anything. > > I am sorry we could not help, but I disagree on that definition of VDE as > "yet-another-dead-project". > In my personal opinion you failed to check about > it before writing. I didn't mean to offend and as I hinted above, I haven't failed to check. I did. But right now, I can't sit down and study how vde-switch code works etc. nor another project to "baby-sit" :) > I am very glad that you have found a valid alternative > for your goal; I wish you that it will "cut it". If by alternative you mean killing an ant with Ion Cannon, then yes, yes I did. :D Thanks and hopefully later, Z. > > > > Kindest regards, > > > > -- > > Daniele -- Try New Relic Now & We'll Send You this Cool Shirt New Relic is the only SaaS-based application performance monitoring service that delivers powerful full stack analytics. Optimize and monitor your browser, app, & servers with just a few lines of code. Try New Relic and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_may ___ vde-users mailing list vde-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/vde-users
Re: [vde-users] Newbie questions: managing VLANs in VDE
W dniu 2013-05-25 10:16, Zdenek Styblik pisze: > >> --- SIGSEGV (Segmentation fault) @ 0 (0) --- +++ killed by SIGSEGV > >> +++ ~~~ strace > >> > >> Any ideas what might be wrong? > > As you've been already told before, it's a cornerstone case. Most of the users reading this, including ourselves, had not experienced such kind of difficulties. The situation might have differed if you would have been able to fill in a bug with a specific description, including the exact way to reproduce this (system you are running, full qemu command line, ...). On Saturday, May 25, 2013 03:14:07 PM Zdenek Styblik wrote: > > I could, would and wanted to in the meantime. However, I'll rather put > time into openvswitch than into yet-another-dead-project(sad to say). > I might come back to this later, but right now, I have to get > something done and VDE doesn't seem it will cut it(I've actually found > another problem regarding VLANs). > I am sorry we could not help, but I disagree on that definition of VDE as "yet- another-dead-project". In my personal opinion you failed to check about it before writing. I am very glad that you have found a valid alternative for your goal; I wish you that it will "cut it". Kindest regards, -- Daniele -- Try New Relic Now & We'll Send You this Cool Shirt New Relic is the only SaaS-based application performance monitoring service that delivers powerful full stack analytics. Optimize and monitor your browser, app, & servers with just a few lines of code. Try New Relic and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_may___ vde-users mailing list vde-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/vde-users
Re: [vde-users] Newbie questions: managing VLANs in VDE
On Sat, May 25, 2013 at 12:49 PM, Marcin Mirosław wrote: > W dniu 2013-05-25 10:16, Zdenek Styblik pisze: >> --- SIGSEGV (Segmentation fault) @ 0 (0) --- +++ killed by SIGSEGV >> +++ ~~~ strace >> >> Any ideas what might be wrong? > > Hi! > Can you try compile vde with debug symbols, catch core and do > backtrace? I don't have skills to analyse trace but devs has such skills:) > Regards > Hello, I could, would and wanted to in the meantime. However, I'll rather put time into openvswitch than into yet-another-dead-project(sad to say). I might come back to this later, but right now, I have to get something done and VDE doesn't seem it will cut it(I've actually found another problem regarding VLANs). Thanks, Z. -- Try New Relic Now & We'll Send You this Cool Shirt New Relic is the only SaaS-based application performance monitoring service that delivers powerful full stack analytics. Optimize and monitor your browser, app, & servers with just a few lines of code. Try New Relic and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_may ___ vde-users mailing list vde-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/vde-users
Re: [vde-users] Newbie questions: managing VLANs in VDE
W dniu 2013-05-25 10:16, Zdenek Styblik pisze: > --- SIGSEGV (Segmentation fault) @ 0 (0) --- +++ killed by SIGSEGV > +++ ~~~ strace > > Any ideas what might be wrong? Hi! Can you try compile vde with debug symbols, catch core and do backtrace? I don't have skills to analyse trace but devs has such skills:) Regards -- Try New Relic Now & We'll Send You this Cool Shirt New Relic is the only SaaS-based application performance monitoring service that delivers powerful full stack analytics. Optimize and monitor your browser, app, & servers with just a few lines of code. Try New Relic and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_may ___ vde-users mailing list vde-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/vde-users
Re: [vde-users] Newbie questions: managing VLANs in VDE
On Thu, May 16, 2013 at 2:56 PM, Zdenek Styblik
wrote:
>>> The switch does not delete ports 1 and 24 from vlan0 because port 1 and 24
>>> are already using vlan 0 for their
>>> untagged traffic.
>>> If you want to define tagged only ports use the following command:
>>> /port/setvlan 1 4095
>>> /port/setvlan 24 4095
>>>
>>> Vlan 4095 does not exist, it is used to say that no untagged traffic should
>>> pass
>>> through the port.
>
>> Great! It works but it wasn't obvious for me. Is it good idea to add
>> this information to yours wiki?
>
>>> I hope these explanations are not arriving too late
>> No, they didn't arrive too late.
>
>> I have worse news. I have more questions!:) If you don't mind I'd like
>> to ask you about such corner case. Let imagine vde_switch process crash,
>> next I start vde_switch again. Is it possible to readd VM to port
>> without restarting qemu? After some reading it looks I have to use
>> vde_plug2tap to do it. Am I right?
>
> Hello,
>
> first of all, thank you both, renzon and Marcin, for this information.
>
> Sadly, my VDE2-2.3.2 crashes after QEMU taps to port with (untagged)
> VLAN 4095, resp. 'port/setvlan 24 4095'.
>
This happens with VDE from trunk as well.
VDE started as: vde_switch -s /var/run/vde2//vde.virswitch0 --mgmt
/var/run/vde2//vde.virswitch0.sock --mgmtmode 660 -p
/var/run/vde2//vde.virswitch0.pid
~~~ strace
--- SIGALRM (Alarm clock) @ 0 (0) ---
rt_sigreturn(0) = -1 EINTR (Interrupted system call)
poll([{fd=5, events=POLLIN|POLLHUP}, {fd=4, events=POLLIN|POLLHUP},
{fd=0, events=POLLIN|POLLHUP}, {fd=3, events=POLLIN|POLLHUP}], 4, -1)
= ? ERESTART_RESTARTBLOCK (To be restarted)
--- SIGALRM (Alarm clock) @ 0 (0) ---
rt_sigreturn(0xe) = -1 EINTR (Interrupted system call)
poll([{fd=5, events=POLLIN|POLLHUP}, {fd=4, events=POLLIN|POLLHUP},
{fd=0, events=POLLIN|POLLHUP}, {fd=3, events=POLLIN|POLLHUP}], 4, -1)
= 1 ([{fd=4, revents=POLLIN}])
accept(4, {sa_family=AF_FILE, NULL}, [2]) = 6
poll([{fd=5, events=POLLIN|POLLHUP}, {fd=4, events=POLLIN|POLLHUP},
{fd=0, events=POLLIN|POLLHUP}, {fd=3, events=POLLIN|POLLHUP}, {fd=6,
events=POLLIN|POLLHUP}], 5, -1) = 1 ([{fd=6, revents=POLLIN}])
read(6, "\316\372\355\376\3\0\0\0\0\36\0\0\1\0/var/run/vde2/vde."..., 256) = 145
access("/var/run/vde2/vde.virswitch0/.03184-0", R_OK|W_OK) = 0
stat("/var/run/vde2/vde.virswitch0/.03184-0",
{st_mode=S_IFSOCK|0700, st_size=0, ...}) = 0
socket(PF_FILE, SOCK_DGRAM, 0) = 7
fcntl(7, F_SETFL, O_RDONLY|O_NONBLOCK) = 0
connect(7, {sa_family=AF_FILE,
path="/var/run/vde2/vde.virswitch0/.03184-0"}, 110) = 0
--- SIGSEGV (Segmentation fault) @ 0 (0) ---
+++ killed by SIGSEGV +++
~~~ strace
Any ideas what might be wrong?
Thanks,
Z.
--
Try New Relic Now & We'll Send You this Cool Shirt
New Relic is the only SaaS-based application performance monitoring service
that delivers powerful full stack analytics. Optimize and monitor your
browser, app, & servers with just a few lines of code. Try New Relic
and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_may
___
vde-users mailing list
vde-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/vde-users
Re: [vde-users] Newbie questions: managing VLANs in VDE
>> The switch does not delete ports 1 and 24 from vlan0 because port 1 and 24 >> are already using vlan 0 for their >> untagged traffic. >> If you want to define tagged only ports use the following command: >> /port/setvlan 1 4095 >> /port/setvlan 24 4095 >> >> Vlan 4095 does not exist, it is used to say that no untagged traffic should >> pass >> through the port. > Great! It works but it wasn't obvious for me. Is it good idea to add > this information to yours wiki? >> I hope these explanations are not arriving too late > No, they didn't arrive too late. > I have worse news. I have more questions!:) If you don't mind I'd like > to ask you about such corner case. Let imagine vde_switch process crash, > next I start vde_switch again. Is it possible to readd VM to port > without restarting qemu? After some reading it looks I have to use > vde_plug2tap to do it. Am I right? Hello, first of all, thank you both, renzon and Marcin, for this information. Sadly, my VDE2-2.3.2 crashes after QEMU taps to port with (untagged) VLAN 4095, resp. 'port/setvlan 24 4095'. I'm also wondering how to re-attach QEMU processes to VDE2 switch after its crash. I haven't seen any follow up reply to original thread. I don't believe vde_plug2tap is proper way how to do it if VM is using ``qemu -netdev vde,id=hostnet0,sock=/var/run/vde2/vde.virswitch0''. Thanks, Z. -- AlienVault Unified Security Management (USM) platform delivers complete security visibility with the essential security capabilities. Easily and efficiently configure, manage, and operate all of your security controls from a single console and one unified framework. Download a free trial. http://p.sf.net/sfu/alienvault_d2d ___ vde-users mailing list vde-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/vde-users
Re: [vde-users] Newbie questions: managing VLANs in VDE
W dniu 04.03.2013 17:20, Renzo Davoli pisze: > I am sorry for the delay. Hi Renzo! > There are two problems in your configuration. > > First: kvm's or qemu's vlan command line definition has nothing to do with > ethernet vlans. > > I complained several times with qemu developers about this misleading > definition. I was expecting qemu/kvm add vlans tags to frames. I was wrong:) >> Now I'm startin qemu-kvm OS: >> ... -net nic,model=virtio,vectors=4,vlan=4,macaddr=52:54:1C:10:12:24 >> -net vde,vlan=4,port=24 ... >> >> Now I would like to have port 1 and 24 only as tagged VLAN 4, so I'm doing: >> vlan/addport 4 1 >> vlan/addport 4 24 >> >> I'm getting: >> vde[/var/run/vde.ctl/vde.mgmt]: vlan/allprint >> >> VLAN >> -- Port 0001 tagged=0 active=1 status=Forwarding >> -- Port 0024 tagged=0 active=1 status=Forwarding >> VLAN 0004 >> -- Port 0001 tagged=1 active=1 status=Forwarding >> -- Port 0024 tagged=1 active=1 status=Forwarding >> Success >> >> How to remove ports 1 and 24 from VLAN 0? I'm trying to do this in such way: >> vde[/var/run/vde.ctl/vde.mgmt]: vlan/delport 0 1 >> >> Address already in use >> vde[/var/run/vde.ctl/vde.mgmt]: vlan/delport 0 24 > > The switch does not delete ports 1 and 24 from vlan0 because port 1 and 24 > are already using vlan 0 for their > untagged traffic. > If you want to define tagged only ports use the following command: > /port/setvlan 1 4095 > /port/setvlan 24 4095 > > Vlan 4095 does not exist, it is used to say that no untagged traffic should > pass > through the port. Great! It works but it wasn't obvious for me. Is it good idea to add this information to yours wiki? > I hope these explanations are not arriving too late No, they didn't arrive too late. I have worse news. I have more questions!:) If you don't mind I'd like to ask you about such corner case. Let imagine vde_switch process crash, next I start vde_switch again. Is it possible to readd VM to port without restarting qemu? After some reading it looks I have to use vde_plug2tap to do it. Am I right? I'd like to also ask about network speed. I did test between two VMs (both are using virtio driver for network adaper) using iperf. I got ~890Mb/s (ping shows latency ~0.4-0.5ms), are such values acceptable for VDE? Thanks again! Marcin P.S. Wiki and program help displays: vlan/addport N PORT add port to the vlan N (tagged) vlan/delport N PORT add port to the vlan N (tagged) shouldn't it be like: vlan/addport N PORT add port to the vlan N (tagged) vlan/delport N PORT delete port from the vlan N (tagged) ? -- Symantec Endpoint Protection 12 positioned as A LEADER in The Forrester Wave(TM): Endpoint Security, Q1 2013 and "remains a good choice" in the endpoint security space. For insight on selecting the right partner to tackle endpoint security challenges, access the full report. http://p.sf.net/sfu/symantec-dev2dev ___ vde-users mailing list vde-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/vde-users
Re: [vde-users] Newbie questions: managing VLANs in VDE
I am sorry for the delay. There are two problems in your configuration. First: kvm's or qemu's vlan command line definition has nothing to do with ethernet vlans. I complained several times with qemu developers about this misleading definition. > ... -net nic,model=virtio,vectors=4,vlan=4,macaddr=52:54:1C:10:12:24 > -net vde,vlan=4,port=24 ... this simply means that the two -net definitions match together. If you have several virtual adapters and you wand to connect two of them to a vde connection and three to a tap: ... -net nic...,vlan=1,... -net nic,...,vlan=1.. -net vde \ -net nic,,vlan=2 -net nic,,vlan=2 -net nic,,vlan=2 -net tap... (newer versions of qemu/kvm accept clearer options: ... -net nic...,vlan=1,... -net nic,...,vlan=1.. -netdev vde \ -net nic,,vlan=2 -net nic,,vlan=2 -net nic,,vlan=2 -netdev tap... These definitions has nothing to do with the vlans on the switch... If you want to connect two machines using vlan 4/untagged there is no need to specify vlan 4 on kvm. start kvm in this way: kvm -net nic,model=virtio,vectors=4,macaddr=52:54:1C:10:12:24 -net vde,port=24 kvm -net nic,model=virtio,vectors=4,macaddr=52:54:1C:10:12:01 -net vde,port=1 and on the switch type the following commands: vlan/create 4 port/setvlan 1 4 port/setvlan 24 4 port/setvlan sets the vlan for untagged traffic. if you want to add other 802.1Q tagged vlan on the same ports (say vlan 5) you can type the following commands: vlan/create 5 vlan/addport 5 4 On the virtual host, using its operating system commands, you can define vlan 5 tagged virtual interface. e.g. if it is a GNU-linux you can add the port in this way: # vconfig add eth0 5 and then you have a new eth0.5 interface. On debian/ubuntu/mint and similar you can add the 802.1Q tagged port using this syntax in your /etc/network/interfaces file: auto eth0.5 iface eth0.5 inet static address 192.168.1.2 netmask 255.255.255.0 network 192.168.1.0 > Now I'm startin qemu-kvm OS: > ... -net nic,model=virtio,vectors=4,vlan=4,macaddr=52:54:1C:10:12:24 > -net vde,vlan=4,port=24 ... > > Now I would like to have port 1 and 24 only as tagged VLAN 4, so I'm doing: > vlan/addport 4 1 > vlan/addport 4 24 > > I'm getting: > vde[/var/run/vde.ctl/vde.mgmt]: vlan/allprint > > VLAN > -- Port 0001 tagged=0 active=1 status=Forwarding > -- Port 0024 tagged=0 active=1 status=Forwarding > VLAN 0004 > -- Port 0001 tagged=1 active=1 status=Forwarding > -- Port 0024 tagged=1 active=1 status=Forwarding > Success > > How to remove ports 1 and 24 from VLAN 0? I'm trying to do this in such way: > vde[/var/run/vde.ctl/vde.mgmt]: vlan/delport 0 1 > > Address already in use > vde[/var/run/vde.ctl/vde.mgmt]: vlan/delport 0 24 The switch does not delete ports 1 and 24 from vlan0 because port 1 and 24 are already using vlan 0 for their untagged traffic. If you want to define tagged only ports use the following command: /port/setvlan 1 4095 /port/setvlan 24 4095 Vlan 4095 does not exist, it is used to say that no untagged traffic should pass through the port. > > Address already in use > > but I don't know what "Address already in use" means in this context. > Another question is how to add again working qemu virt machines to vde? > For example I'm starting vde, next I'm starting qemu OSes, next somthing > happens and vde is restarted. What next? Should I restart virtual > machines to add them to vde? > Thanks for help! > Regards, I hope these explanations are not arriving too late renzo -- Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_feb ___ vde-users mailing list vde-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/vde-users
