Re: Domains not being destroyed properly

[Anthony Wright <anthony@overnetdata.com>]

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 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.