VDE: Virtual Distributed Ethernet / Bugs / #69 Segfault after 3 months working fine

renzo davoli - 2013-12-08

On Thu, Dec 05, 2013 at 03:29:19PM +0000, Mathias Mayrhofer wrote:

** [bugs:#69] Segfault after 3 months working fine**

Status: open
Labels: segfault vde_switch crash
Created: Thu Dec 05, 2013 03:29 PM UTC by Mathias Mayrhofer
Last Updated: Thu Dec 05, 2013 03:29 PM UTC
Owner: nobody

Yesterday I experienced a segfault on my vde_switch after 88 days working fine. VDE connects my qemu VMs together and is heavily in use. I want to report this to help you find problems and to ask if there is a possibility to restart the vde device after this fault and how this will affect my VMs.

I use the debian package (vde2, 2.3.2-4, amd64, Linux 3.2.0-4-amd64 #1 SMP Debian 3.2.46-1 x86_64 GNU/Linux), the log is as follows:
Dec 4 22:59:46 server kernel: [7847125.283822] vde_switch[2338]: segfault at 80 ip 0000000000404b48 sp 00007fffbd1339e8 error 4 in vde_switch[400000+15000]

Thank you and VDE is great!
Thank you for your kind report.

I'll try to see what I can do to fix the bug. Have you any other symptom to report? Hunting for a bug using just the
instruction pointer can be a bit daunting...

It is not currently possible for VM to be automatically reconnected to a new switch.
Automatic reconnection can be a useful feature to study for a future versions of libvdeplug.
Unfortunately, the only current way to have your VMs reconnected is to restart them.

renzo davoli

Related

Bugs: #69
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Mathias Mayrhofer - 2013-12-10

Hi Renzo Davoli!

I cannot report any other symptoms, because it worked fine until the segfault. The network device was still up due ifconfig, but the process vde_switch went away. Below you see the ps aux right before the segfault and ifconfig after the segfault and how it is referred by with qemu. There were no other log entries nearby the fault.

Thanks for explaining, greetings!
mtmayr

F S UID PID PPID C PRI NI ADDR SZ WCHAN STIME TTY TIME CMD 5 S root 2338 1 0 80 0 - 3698 - Sep05 ? 11:11:02 /usr/bin/vde_switch -s /var/run/vde2/vmn.ctl -m 660 -g vde2-net -p /var/run/vde2/vmn.pid -t vmn -M /var/run/vde2/vmn.mgmt --mgmtmode 660 -d -t vmn vmn Link encap:Ethernet HWaddr 12:74:99:ce:14:3f inet addr:192.168.1.1 Bcast:192.168.1.255 Mask:255.255.255.0 UP BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:471448132 errors:0 dropped:0 overruns:0 frame:0 TX packets:354058105 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:500 RX bytes:176797413967 (164.6 GiB) TX bytes:234534002363 (218.4 GiB) qemu -net vde,sock=/var/run/vde2/vmn.ctl [...]

Last edit: Mathias Mayrhofer 2013-12-10
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
- Mathias Mayrhofer - 2017-03-24
  
  Dear Renzo Davoli!
  
  Hi again, 4 years later - I hope you are doing fine :-)
  I am writing you because we once had a conversation about vde
  segfaulting. We still have this problem, that vde device is crashing
  about every 100 days (102 days this time). Since we last wrote (in
  2013). Two times, it was around 300 days, then again the shorter period.
  We are always using latest & updated Debian. And a completely new
  installation since the last time we wrote.
  
  Could you please have a look at the source files? You can find
  log-entries and system data below. Thanks in advance!
  
  Regards,
  Mathias Mayrhofer
  
  syslog:Mar 24 11:46:49 server kernel: [8888964.281747] vde_switch[3247]:
  segfault at d9b1bd8 ip 0000000000404bc8 sp 00007ffce1868820 error 4 in
  vde_switch[400000+15000]
  
  ii libvde0 2.3.2-4
  amd64 Virtual Distributed Ethernet - support libraries
  ii libvdeplug2 2.3.2-4
  amd64 Virtual Distributed Ethernet - Plug library
  ii vde2 2.3.2-4
  amd64 Virtual Distributed Ethernet
  
  Linux server 3.2.0-4-amd64 #1 SMP Debian 3.2.78-1 x86_64 GNU/Linux
  
  About 40mins time before segfault:
  
  SYS 1 1490353141 Fri Mar 24 11:59:01 CET 2017
  SYS 2 11:59:01 up 102 days, 22:48, 1 user, load average:
  0.20, 0.39, 0.36
  
  IFCFG 31 vm Link encap:Ethernet HWaddr 3a:54:59:a5:82:19
  IFCFG 32 inet addr:192.168.0.1 Bcast:192.168.0.255
  Mask:255.255.255.0
  IFCFG 33 inet6 addr: fe80::3854:59ff:fea5:82c9/64
  Scope:Link
  IFCFG 34 inet6 addr: 2a01:4f9:192:80ad:5054:1::/80
  Scope:Global
  IFCFG 35 UP BROADCAST MULTICAST MTU:1500 Metric:1
  IFCFG 36 RX packets:224226697 errors:0 dropped:0
  overruns:0 frame:0
  IFCFG 37 TX packets:177181666 errors:0 dropped:0
  overruns:237 carrier:0
  IFCFG 38 collisions:0 txqueuelen:500
  IFCFG 39 RX bytes:148659599163 (138.4 GiB) TX
  bytes:96514991180 (89.8 GiB)
  
  On 12/10/2013 05:41 AM, Mathias Mayrhofer wrote:
  
  Hi Renzo Davoli!
  
  I cannot report any other symptoms, because it worked fine until the
  segfault. The network device was still up due ifconfig, but the
  process vde_switch went away. Below you see the ps aux right before
  the segfault and ifconfig after the segfault and how it is referred by
  with qemu.
  
  Thanks for explaining, greetings!
  mtmayr
  
  F S UID PID PPID C PRI NI ADDR SZ WCHAN STIME TTY TIME CMD
  5 S root 2338 1 0 80 0 - 3698 - Sep05 ? 11:11:02 /usr/bin/vde_switch -s /var/run/vde2/vmn.ctl -m 660 -g vde2-net -p /var/run/vde2/vmn.pid -t vmn -M /var/run/vde2/vmn.mgmt --mgmtmode 660 -d -t vmn
  
  vmn Link encap:Ethernet HWaddr 12:74:99:ce:14:3f
  inet addr:192.168.0.1 Bcast:192.168.0.255 Mask:255.255.255.0
  UP BROADCAST MULTICAST MTU:1500 Metric:1
  RX packets:471448132 errors:0 dropped:0 overruns:0 frame:0
  TX packets:354058105 errors:0 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:500
  RX bytes:176797413967 (164.6 GiB) TX bytes:234534002363 (218.4 GiB)
  
  qemu -net vde,sock=/var/run/vde2/vmn.ctl [...]
  
  [bugs:#69] http://sourceforge.net/p/vde/bugs/69/ Segfault after 3
  months working fine
  
  Status: open
  Labels: segfault vde_switch crash
  Created: Thu Dec 05, 2013 03:29 PM UTC by Mathias Mayrhofer
  Last Updated: Thu Dec 05, 2013 03:29 PM UTC
  Owner: nobody
  
  Yesterday I experienced a segfault on my vde_switch after 88 days
  working fine. VDE connects my qemu VMs together and is heavily in use.
  I want to report this to help you find problems and to ask if there is
  a possibility to restart the vde device after this fault and how this
  will affect my VMs.
  
  I use the debian package (vde2, 2.3.2-4, amd64, Linux 3.2.0-4-amd64 #1
  SMP Debian 3.2.46-1 x86_64 GNU/Linux), the log is as follows:
  Dec 4 22:59:46 server kernel: [7847125.283822] vde_switch[2338]:
  segfault at 80 ip 0000000000404b48 sp 00007fffbd1339e8 error 4 in
  vde_switch[400000+15000]
  
  Thank you and VDE is great!
  mtmayr
  
  Sent from sourceforge.net because you indicated interest in
  https://sourceforge.net/p/vde/bugs/69/
  
  To unsubscribe from further messages, please visit
  https://sourceforge.net/auth/subscriptions/
  
  If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Segfault after 3 months working fine

Group

Searches

Help

#69 Segfault after 3 months working fine

Related

Discussion

Related