Hi, And thanks for the quick answer.
First of all I discoved a very similar bug report in CentOS: http://bugs.centos.org/view.php?id=2300 Guido Trotter kirjoitti: > Are you using the standard vif-route scripts or have you customized them? > Yes, I have customized my vif-route script. I just tried with the original vif-route script, and same happened. > Can you show us your quagga configuration too? > I've changed the hostnames and passwords, but here they are: <--------- xen1:~# cat /etc/quagga/ospfd.conf hostname xen1.XXX.XXX password XXX enable password XXX log file /var/log/ospfd.log interface dummy0 interface eth0 interface dummy2 router ospf ospf router-id 172.16.255.16 ospf abr-type standard ospf rfc1583compatibility network 172.16.255.16/32 area 0.0.0.0 network 172.16.255.11/28 area 0.0.0.0 passive-interface dummy0 passive-interface dummy2 redistribute static area 0.0.0.0 authentication xen1:~# cat /etc/quagga/zebra.conf log file /var/log/quagga/zebra.log hostname xen1.XXX.XXX xen1:~# ---------> > Can you manually do on the xen interfaces what the scripts would? How about > doing it on some other interface configured in a similar way? > I'll try this next week, see below :) > Can you try to insulate it within quagga? Does this happen if you just run > zebra > but not ospfd? > Wow... I disabled ospfd, /etc/init.d/quagga restart, and creating a domain crashed xen. Here's what happened. <------------- xen1:~# pico /etc/quagga/daemons xen1:~# /etc/init.d/quagga restart Stopping Quagga daemons (prio:0): (zebra) (bgpd) (ripd) (ripngd) (ospfd) (ospf6d ) (isisd). Removing all routes made by zebra. Nothing to flush. Loading capability module if not yet done. Starting Quagga daemons (prio:10): zebra. xen1:~# xm list Name ID Mem(MiB) VCPUs State Time(s) Domain-0 0 1892 2 r----- 193.1 xen1:~# xm create test7.cfg Using config file "/etc/xen/test7.cfg". Started domain test7 xen1:~# Message from [EMAIL PROTECTED] at Sun Sep 9 16:33:46 2007 ... xen1 kernel: ------------[ cut here ]------------ Message from [EMAIL PROTECTED] at Sun Sep 9 16:33:46 2007 ... xen1 kernel: kernel BUG at drivers/xen/core/evtchn.c:481! Message from [EMAIL PROTECTED] at Sun Sep 9 16:33:46 2007 ... xen1 kernel: invalid opcode: 0000 [#1] Message from [EMAIL PROTECTED] at Sun Sep 9 16:33:46 2007 ... xen1 kernel: SMP Message from [EMAIL PROTECTED] at Sun Sep 9 16:33:46 2007 ... xen1 kernel: CPU: 1 Message from [EMAIL PROTECTED] at Sun Sep 9 16:33:46 2007 ... xen1 kernel: EIP is at retrigger+0x1f/0x35 Message from [EMAIL PROTECTED] at Sun Sep 9 16:33:46 2007 ... xen1 kernel: eax: 00000000 ebx: 02080000 ecx: 00000018 edx: f55f6000 Message from [EMAIL PROTECTED] at Sun Sep 9 16:33:46 2007 ... xen1 kernel: esi: c0324460 edi: 0000010a ebp: 00000000 esp: ed78deb0 Message from [EMAIL PROTECTED] at Sun Sep 9 16:33:46 2007 ... xen1 kernel: ds: 007b es: 007b ss: 0069 Message from [EMAIL PROTECTED] at Sun Sep 9 16:33:46 2007 ... xen1 kernel: Process xenwatch (pid: 11[#0], ti=ed78c000 task=c03a50d0 task.ti=ed 78c000) Message from [EMAIL PROTECTED] at Sun Sep 9 16:33:46 2007 ... xen1 kernel: Stack: c01418b1 c0324460 0000010a c0324488 c0141607 e6b6a2c0 000000 00 00000000 Message from [EMAIL PROTECTED] at Sun Sep 9 16:33:46 2007 ... xen1 kernel: e6b6a2c0 c022077c 00000000 c0220b5c c0219ceb 00000010 000000 00 0000020b Message from [EMAIL PROTECTED] at Sun Sep 9 16:33:46 2007 ... xen1 kernel: 0000020a 00000000 00000000 e74703b6 c02f10e4 ee868000 000000 00 00000002 Message from [EMAIL PROTECTED] at Sun Sep 9 16:33:46 2007 ... xen1 kernel: Call Trace: Message from [EMAIL PROTECTED] at Sun Sep 9 16:33:46 2007 ... xen1 kernel: Code: ee 85 f6 75 96 58 5a 5b 5e 5f 5d c3 0f b7 0c 85 00 89 38 c0 8 b 15 a4 b9 2d c0 85 c9 74 1d 0f a3 8a 80 08 00 00 19 c0 85 c0 75 08 <0f> 0b e1 0 1 ce c2 2b c0 f0 0f ab 8a 00 08 00 00 b8 01 00 00 00 Message from [EMAIL PROTECTED] at Sun Sep 9 16:33:46 2007 ... xen1 kernel: EIP: [<c02157d6>] retrigger+0x1f/0x35 SS:ESP 0069:ed78deb0 xen1:~# -------------> The hex codes got a bit mangled because they didn't fit in my putty window. The computer (which is at work) doesn't respond to ping anymore, and I'm at home currently, so I'll get back to this next week. I appreciate the help. Regards, Mikko -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
