Hi,
> 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?
Toying with the vif-route script, I might have found a workaround for this
issue.
If I disable the ifconfig and ip route commands from vif-route script, and bring
up vif interface by hand later on, everything seems to work.
In other works, bringing up the interface in vif-route script causes it to stay
up when I shutdown the domain.
I'm not sure though if the workaround is stable, as I again experienced a crash
like before ("kernel BUG at drivers/xen/core/evtchn.c:481!") when doing a lot
of create/shutdown commands, manually bringing up interfaces, etc. I haven't
found a reliable way to reproduce the crash yet.
I need to do more testing before I can say for sure.
What do you think of this?
> Can you try to insulate it within quagga? Does this happen if you just run
> zebra but not ospfd?
If only zebra is running - still a jammed VIF interface.
If only ospfd is running, it actually fixes the problem. (too bad ospfd is
useless without the zebra daemon)
By the way, if you want I could arrange you an SSH access to the xen1 host.
Best regards,
Mikko Korkalo
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
