We did a set of tests to understand how controller domain and guest domain configuration info being stored, and how autosave and add-spconfig really works together. T5220 and LDOM 1.3 software are used in this test. sc> showhost Sun System Firmware 7.2.10 2010/07/19 17:13
Host flash versions: Hypervisor 1.7.9 2010/07/19 15:51 OBP 4.30.9 2010/07/16 09:01 POST 4.30.9 2010/07/16 09:39 It looks to me that any change of resource allocation with LDM command, it will be automatically saved somewhere on SP even though ldm list-spconfig -r shows "No autosave configurations". And looks like during system reboot, the latest NOT explicitly saved spconfig will be used as configurations. And until the "NOT explictitly saved spconfig" is saved manually with add-spconfig, the tag will always be "NEXT POWERON" instead of [CURRENT]. Below is what we get Right after LDOM manager installed: ro...@ldommaster LDoms_Manager-1_3> ldm list NAME STATE FLAGS CONS VCPU MEMORY UTIL UPTIME primary active -n-c-- SP 64 32640M 0.1% 9m ro...@ldommaster LDoms_Manager-1_3> ldm list-spconfig factory-default [current] Perform configuration: add-vds/set-vcpu/set-memory to controller domain ro...@ldommaster /> ldm list NAME STATE FLAGS CONS VCPU MEMORY UTIL UPTIME primary active -ndcv- SP 8 8G 0.5% 43m ro...@ldommaster xml> ldm list-spconfig -r No autosave configurations ro...@ldommaster xml> ldm list-spconfig factory-default [next poweron] Reconfiguration reboot: ro...@ldommaster /> ldm list NAME STATE FLAGS CONS VCPU MEMORY UTIL UPTIME primary active -n-cv- SP 8 8G 13% 6m ro...@ldommaster /> ldm list-spconfig factory-default [next poweron] So even though no spconfig was explicitly saved, when server is up, it picks up latest configuration, but the flag still kept as [next poweron] As that being said, we simulated controller domain OS got corruption scenario, in which case controller domain has to be rebuilt. Before controller domain was rebuilt, one guest domain state is running, the other was inactive. After reinstallation of controller domain completed and LDOM manager 1.3 reinstalled, we are seeing one guest domain state is still showing as running. The other guest domain could not be found any more. So the question here is: what exactly information is being saved on spconfig and what is being saved in /var/opt/SUNWldm. Our understanding is: controller domain and running guest domain information is automatically saved on SP. The other guest domains (inactive) will be saved under /var/opt/SUNWldm/autosave*. Is above correct? -- This message posted from opensolaris.org _______________________________________________ ldoms-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/ldoms-discuss
