|
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-devel] FW: Cancelling asynchronous operations in libxl
On 26 Oct 2013, at 09:33, Ian Campbell <ian.campbell@xxxxxxxxxx> wrote: > On Wed, 2013-10-23 at 13:23 -0400, Konrad Rzeszutek Wilk wrote: >> On Tue, Oct 15, 2013 at 04:08:31PM +0000, Simon Beaumont wrote: >> Are there specific operations that you are focusing on to cancel? > > Yes, this would be good to know. Ian J would know better than I but AIUI > there is currently no generic support for cancelling an asynchronous op > in libxl. I'm sure we could find a way to add this, for example as an > abort after the current "step" succeeds/times out/fails. I think this generic support is what we’re looking for. Ideally, we’d like to be able to cancel any potentially long-running function (i.e. those that can be called asynchronously). More specifically, we’d like to be able to cancel at least the following: * device_*_[add|remove|destroy] * device_pci_assignable_[add|remove] * libxl_domain_create_new * libxl_domain_create_resume * libxl_domain_shutdown * libxl_domain_wait_shutdown * libxl_domain_reboot * libxl_domain_destroy * libxl_domain_suspend * libxl_domain_pause * libxl_domain_unpause >> Or is this mostly of 'the guest is doing something and does not seem >> to have a vnc/console, lets kill it' ? > > For killing libxl_domain_destroy should be fine to call even if there is > an async op pending on that domain, the async op will naturally fail, > it'll probably log a lot but should do so gracefully. If there are cases > which do not we should fix them, since they would represent a bug > irrespective of any killing of the domain from under the op's feet. Not so much interested in this use case. Si _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxx http://lists.xen.org/xen-devel
|
 |
Lists.xenproject.org is hosted with RackSpace, monitoring our |