On Sun, May 26, 2013 at 6:35 PM, Renzo Davoli <re...@cs.unibo.it> 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
