[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-devel] Pre-domain released event?


  • To: "xen-devel@xxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxx>
  • From: Razvan Cojocaru <rcojocaru@xxxxxxxxxxxxxxx>
  • Date: Mon, 14 Dec 2015 18:23:38 +0200
  • Comment: DomainKeys? See http://domainkeys.sourceforge.net/
  • Delivery-date: Mon, 14 Dec 2015 16:23:05 +0000
  • Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=default; d=bitdefender.com; b=WIXKWAa69dtDzvxV4rbTU724wh5RLYwF+VD4xscBmMdQ/cBWrDxKis29Q4dsvGJQHbUKI4f79N9o+GEwUMhwTsvjZ8EkBFtcUoEqulbVt5lWnJQgioV8Fc7meBpD27fziKuVJaF8PhCk/Tesj1H8vtdVSAHSyJdBNs9o1+OeqPQhvGcE/6SPD3K+pzu2af0N2Lzaflpd8eTsFv/NeTpldUOl9s98/2Dt3nhitHrMvYKtBEjT03ZtwEwgbQ3c4a+OZ5q5T/CihemFeNh2Hx5SgkGtNS3LUV/A0XGIqiYYUy9FkWnK+EyAZPR32BQecKz7KJoJVHcEaB9+iXY0FNpedg==; h=Received:Received:Received:Received:Received:To:From:Subject:X-Enigmail-Draft-Status:Message-ID:Date:User-Agent:MIME-Version:Content-Type:Content-Transfer-Encoding:X-BitDefender-Scanner:X-BitDefender-Spam:X-BitDefender-SpamStamp:X-BitDefender-CF-Stamp;
  • List-id: Xen developer discussion <xen-devel.lists.xen.org>

Hello,

Currently, all the in-tree examples that figure out that a domain has
been shut down subscribe to xenstore's @releaseDomain combined with an
xs_is_domain_introduced() check. That works fine if you're only
interested that the domain no longer exists. However, I'd like to be
able to do some cleanup before a domain is suspended (on taking a
snapshot, for example).

There are various degrees of tolerability doing this if I subscribe to
various xenstore paths that disappear before @releaseDomain gets fired,
and before the guest disappears, but it looks like it's not always
foolproof.

I've previously asked the question in a somewhat more convoluted manner
here: http://lists.xen.org/archives/html/xen-devel/2015-08/msg00735.html

I'm still interested in what the best solution would be here. A new,
blocking vm_event, that fires from the hypervisor immediately after it's
decided that the guest will be shutdown is what comes to mind, but I'm
not sure where the best place to put it would be. Or indeed if there
another / better way to do this.


Thanks,
Razvan

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.