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

Re: [Xen-devel] [PATCH v6 06/13] libxl: convert libxl_device_disk_add to an async op



Roger Pau Monne wrote:
Isn't the effect of this that if the xs transaction gets a conflict,
we'll rerun the hotplug scripts, etc. ?  I think I may be confused
here, but I don't understand how this transaction loop is supposed to
work and how it is supposed to relate to the interaction with other
domains, scripts, etc.

Yes I see your point. We should disconnect the device (execute hotplug
scripts) but since the xenstore entries are already gone (because the
transaction is not committed successfully) I don't see anyway to do it,
we cannot execute those scripts if the backend entries have been lost.

Sorry, I've made a mistake here, since the transaction is not committed, we never reach the desired state (2), so if the transaction fails no scripts are executed, and we can carry on trying to add the device again.

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