John Danielson <jhd at xenbld.sfbay.sun.com> writes: > 2. Domains service > > Solaris zones provides a simple transient service that allows autobooting > of zones when the control plane (global zone) is booted, and graceful > shutdown at shutdown/reboot time. In a similar fashion this amendment is > for the transient service: > > svc:/system/xctl/domains:default > > Behaviour is very similar to that of system/zones:default; guest domains > marked as autoboot are booted at dom0 boot time, and are shut down cleanly > at shutdown. > > This is achieved by having the 'domains' service depend upon xend:default. > When the service is started, we ask xend to autoboot all domains as > needed. > > On shutdown, we ask xend to shutdown all running domains and wait for this > to complete (timing out after 6 minutes if no further progress is being > made).
One thing I've heard a few times from customers using zones is that sometimes they would like to be able to offer ordering and dependency of zone startup, so that zone A has to finish starting before zone B is started. It seems that a similar thing may be of interest with Xen domains. Perhaps an implementation where each domain is an instance of svc:/system/xctl/domains could allow dependencies? e.g.: svc:/system/xctl/domains:domain-a svc:/system/xctl/domains:domain-b On the other hand, I don't know how you determine from dom0 that a domU domain has "started" completely. Boyd
