The xendomains init script is unnecesarilly waiting for each domain to exit before asking the next one to begin its shutdown. The attached patch asks all domains to stop and then waits for all of them, thus speeding the whole thing. Example output (which might be a bit confusing as the already-stopped domain is reported as "non-running" in the second pass): joel ~ # /etc/init.d/xendomains stop * Shutting down Xen domains from /etc/xen/auto * Asking domain box1-openldap to shutdown... ... [ ok ] * Asking domain box2-fds to shutdown... ... [ ok ] * Stopping domain box1-openldap ... [ ok ] * Not stopping domain box2-fds - not running * Closing screen session xen ... Feel free to adjust those descriptions...
Created attachment 107473 [details, diff] xendomains-parallel-shutdown.patch
Dear Xen maintainers, can we pleae get this fixed/applied?
Thank you for your bug report. I hope it is fixed with the following commit. Please let me know if it works, or not. On a side node, I made parallel shutdown optional, but enabled by default. So users relying on this to avoid race conditions can disable it. *xen-tools-3.3.0 (01 Sep 2008) 01 Sep 2008; Robert Buchholz <rbu@gentoo.org> +files/xen-tools-3.3.0--as-needed.patch, +files/xen-tools-3.3.0-nostrip.patch, +files/xen-tools-3.3.0-xen-detect-nopie-fix.patch, files/xendomains.confd, files/xendomains.initd, metadata.xml, -xen-tools-3.2.0.ebuild, +xen-tools-3.3.0.ebuild: Version bump to Xen 3.3 (bug #201792). Fixes bugs: * Add USE flags for ACM and FLASK Xen Security Modules * Properly compile and uninstall python bytecode * RDEPEND on pyxml (bug #201255) * Remove libvncserver dependency * Shutdown xendomains in reverse start order (bug #210445) * Allow for parallel shutdown of xendomains (bug #162833) * Check that python is built with threading (bug #236092)
