From mboxrd@z Thu Jan  1 00:00:00 1970
From: Kip Macy <kip.macy@gmail.com>
Subject: Re: recent changes to writable page tables on -unstable
	and xend
Date: Thu, 28 Apr 2005 16:17:44 -0700
Message-ID: <b1fa29170504281617332626cd@mail.gmail.com>
References: <b1fa2917050428161243da7414@mail.gmail.com>
Reply-To: Kip Macy <kip.macy@gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Return-path: <xen-devel-bounces@lists.xensource.com>
In-Reply-To: <b1fa2917050428161243da7414@mail.gmail.com>
Content-Disposition: inline
List-Unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xensource.com>
List-Help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-Subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
Sender: xen-devel-bounces@lists.xensource.com
Errors-To: xen-devel-bounces@lists.xensource.com
To: xen-devel <xen-devel@lists.xensource.com>
List-Id: xen-devel@lists.xenproject.org

> On -testing xend always reaps a domain immediately after it has
> crashed. On -unstable up until today it would wait to reap the guest
> until I ran 'xm list'. Now it appears that I have to explicitly run xm
> destroy on a guest even after it has crashed.

Never mind, this is the result of a local change.