[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [Xen-users] some more tweaking in xendomains script
Hi, I wonder if one of you has changed /etc/init.d/xendomains to run in a different order? My idea is to have it * initiate a xm shutdown, * wait for the --halt --wait until the XENDOMAINS_STOP_MAXWAIT is reached * then (and not as the first step!) * if XENDOMAINS_SYSRQ is set, * fire the specific sysrq's and sleep for the XENDOMAINS_CREATE_USLEEP before finally * doing an xm destroy oh, and while at it, it might be also *about time* to add xm trigger <domid> power in between those steps? This is needed for any HVM domU that doesn't have anything listening on Xenbus. Another bad thing is that the maxwait timer affects any "command" no matter if that acts on all VMs or on a single one, whereas this has a huge impact in practice. imho this could improve a lot and will help all users - so to avoid reinventing wheels, *PLEASE* let me know if you did any modifications/improvments there so we can merge them and commit back one thing. Thanks & greetings, Florian -- the purpose of libvirt is to provide an abstraction layer hiding all xen features added since 2006 until they were finally understood and copied by the kvm devs. _______________________________________________ Xen-users mailing list Xen-users@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-users
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |