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-devel] Domains not being destroyed properly

On Fri, 2011-06-24 at 14:36 +0100, Anthony Wright wrote:
> On 24/06/2011 14:01, Tim Deegan wrote:
> > Hi, 
> >
> > At 13:54 +0100 on 24 Jun (1308923697), Anthony Wright wrote:
> >> The problem is that I don't think there's enough information available
> >> from watching @releaseDomain to implement a reaper well. The
> >> xenstore-watch on @releaseDomain only tells you that a domain has died
> >> (to make things more complicated I actually get two notifications when a
> >> domain get's shutdown), it doesn't tell you which domain has died. A
> >> reaper would have to maintain a list of domains as they were before the
> >> notification to compare against the list after the notification to be
> >> able to issue a notification for the domain that has died.
> > That sounds awfully fragile.  It could get a list of all living domains
> > and reap qemus/xenstore data for any domain not in the list.  (Or, more
> > safely, enumerate all qemus and xenstore entries and check for each
> > whether the domain is alive). 
> Is this information still available after a domain has been destroyed? I
> was expecting that the watcher of @releaseDomain was only notified of a
> domain destruction after the domain had been completely destroyed

@releaseDomain fires after the domain has shutdown but _before_ the
domain is destroyed. This is necessary because @releaseDomain is the
signal to the toolstack that it is time to destroy the domain.

>  so
> there would be no information amount the domain available any more. Are
> you saying the would still be qemus/xenstore information available for
> the domain, and if so how does it get tidied up?
> Anthony.
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-devel

Xen-devel mailing list