The subject file holds the constraints of any currently configured domains. It is used when the LDom Manager restarts to restore the state of _only those_ domains not otherwise bound or active. In short, it's what provides persistence of inactive domains across LDom Manager restarts and/or control domain reboots.
Now, in the scenario where the machine powercycles into a config containing fewer/different domains than what had been previously running, it is possible to see some of the domains from that previously running config show up in the now-booted config. However, any such "phantom" domains will be in inactive state, and will not consume any actual machine resources. -Eric On Oct 15, 2008, at 1:25 PM, Luis wrote: > I have seen problems due to that file been there. > > Assume you do a configuration and you don?t save it to SC. Then > assume you lose electricity (or power cicle whole box), at that time > system will start with the factory config (assigning all memory and > cpus to control domain. Then when the machine starts due to such > file the guest domains on that file will be "created or at least > initialized" and then you will end up with a weird config having > more VCPus used than you really have. > > Thanks > Luis > -- > This message posted from opensolaris.org > _______________________________________________ > ldoms-discuss mailing list > ldoms-discuss at opensolaris.org > http://mail.opensolaris.org/mailman/listinfo/ldoms-discuss
