This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


[Xen-devel] domains flapping

To: "xen-devel@xxxxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxxxx>
Subject: [Xen-devel] domains flapping
From: James Harper <JamesH@xxxxxxxxxxxxxxxx>
Date: Wed, 14 Jul 2004 22:30:57 +1000
Delivery-date: Wed, 14 Jul 2004 13:40:10 +0100
Envelope-to: steven.hand@xxxxxxxxxxxx
List-archive: <http://sourceforge.net/mailarchive/forum.php?forum=xen-devel>
List-help: <mailto:xen-devel-request@lists.sourceforge.net?subject=help>
List-id: List for Xen developers <xen-devel.lists.sourceforge.net>
List-post: <mailto:xen-devel@lists.sourceforge.net>
List-subscribe: <https://lists.sourceforge.net/lists/listinfo/xen-devel>, <mailto:xen-devel-request@lists.sourceforge.net?subject=subscribe>
List-unsubscribe: <https://lists.sourceforge.net/lists/listinfo/xen-devel>, <mailto:xen-devel-request@lists.sourceforge.net?subject=unsubscribe>
Sender: xen-devel-admin@xxxxxxxxxxxxxxxxxxxxx
Thread-index: AcRpnmmYQg0QtJChRT67Yc9Lm+UOiw==
Thread-topic: domains flapping
Whilst tinkering with lvm (which now works great - thanks!), I made a typo which caused the domain to stop booting. I think it was just that I got the config file wrong in terms of which device mapped to which.
Anyway, I had specified 'restart=True' and so the domain was starting to boot, failing, then restarting again. This was the expected behaviour, but it was a pain to kill. Had I thought of it I would have just killed xend but I was doing an 'xm list' to find the domain number, then 'xm destroy', but by then it had moved on. doh!
How easy would it be to put in some logic to detect a domain restarting rapidly in quick succession and either stop restarting it, or introduce an increasing delay between restarts?
<Prev in Thread] Current Thread [Next in Thread>