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


Re: [Xen-users] Xen domains will not reboot or destroy as they should be

To: Jarkko Santala <jake@xxxxxxxxxxxxx>
Subject: Re: [Xen-users] Xen domains will not reboot or destroy as they should be
From: Peter Viskup <skupko.sk@xxxxxxxxx>
Date: Wed, 15 Dec 2010 11:46:15 +0100
Cc: xen-users <xen-users@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Wed, 15 Dec 2010 02:48:41 -0800
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type; bh=woXiBcBnapzdsCllBAic2KdgKX2wsoLG/xFhedhChTo=; b=N6y01lAJwqpnVa9Sg4DNdzAP0UrlDZDqWycVSNy2WmWWhyYyspAEA8qyk9yRCKfuQe xnJxdkszOswSTAXoyVc6dxvxg6kHUagKn14dOSkr5vefQWoNFCRE6+3bwiK4x0s26A39 nlYzqE1+9VtTiIyvmRn1nhafUfYXD5bcpsKmc=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=jeFI+xFUb4yEZRkqFSEvzWgYURW3f3qIrKxaKDpgnQ0S9f8F0y5VwtuJiA9So7BgT3 6C76edhJjRY5U4ld/Ap2RqkcsC/itHbEx0jDEekWF8loaNgS3WM5Z7aeiL65WdA0frPb TtOTWcxsgxOCBvhZQlvv9FLT/6iIjSu0AEwbM=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <57A890FE-0241-414C-A45E-1583E8D9D301@xxxxxxxxxxxxx>
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <A65DD0C7-D51A-44F5-B442-F4701D385C80@xxxxxxxxxxxxx> <AEC6C66638C05B468B556EA548C1A77D01BB8A71@trantor> <57A890FE-0241-414C-A45E-1583E8D9D301@xxxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
On Tue, Dec 14, 2010 at 11:50 AM, Jarkko Santala <jake@xxxxxxxxxxxxx> wrote:

I don't know if the same setting is the reason for another bug I ran into - I tried running some other xm commands instead of destroy on one of these domains in "s" limbo and what happened was that it started spawning as many copies of that domU as it could fit into memory - killing them would spawn another one in the freed memory. The situation finally resolved itself after I had ran xm destroy in a loop, but I was unable to start any new domUs after that until I rebooted. Not sure which xm command set it off in the first place.


Jarkko Santala <jake&portalify,com>   http://www.portalify.com
System Administrator

I have been experiencing same issue with spawning processes of domU. The solution for this was stopping xend and then killing of all domU-related processes. Sometimes there were some xenstore entries remaining and I had to remove them with xenstore-rm before starting domU again.
Unfortunately Debian stable forward-porting Xen kernels are not as stable as someone would expect and I am thinking of switching to XenSource 'official' kernel versions.

Peter Viskup
Xen-users mailing list