7 messages in com.xensource.lists.xen-bugs[Xen-bugs] [Bug 1247] Cascade failure...
FromSent OnAttachments
bugz...@lists.xensource.com08 May 2008 13:34 
bugz...@lists.xensource.com08 May 2008 14:02 
bugz...@lists.xensource.com08 May 2008 14:04 
bugz...@lists.xensource.com09 May 2008 07:15 
bugz...@lists.xensource.com09 May 2008 10:03 
bugz...@lists.xensource.com09 May 2008 10:06 
bugz...@lists.xensource.com12 May 2008 09:12 
Subject:[Xen-bugs] [Bug 1247] Cascade failure when creating multiple domU's requires dom0 reboot
From:bugz...@lists.xensource.com (bugz@lists.xensource.com)
Date:05/12/2008 09:12:36 AM
List:com.xensource.lists.xen-bugs

http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1247

jpea@messagesystems.com changed:

What |Removed |Added

---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |WONTFIX

------- Comment #6 from jpea@messagesystems.com 2008-05-12 09:12 ------- I've gone back through all of my recent system changes and I have found the problem: quagga/zebra! We were having some internal routing problems and I wound up enabling quagga (we use OSPF internally due to the complexity of our networking with VMWare). This is apparently throwing off the timing of Xen's networking, which in turn was causing the xenstore to get corrupted.

In practice, Xen needs to support this kind of dynamic network reconfiguration (in addition to the many other ways it supports networking), but I think for now, I can mark this ticket as WONTFIX...