Hello Eric, Yes what I am seeing is somewhat different. If the configuration is changed and the controller LDOM is rebooted the reboot fails. I have to access the machine through LOM, set the bootmode to normal and reset the machine. This causes the configuration to be lost.
On a running system with 2 guest domains I wanted to try to reboot the control domain to see the affects on the running guest domains. The control domain shutdown to the boot prom but did not reboot. I had to reboot the machine as in the previous paragraph with the two step in LOM. This defeated the purpose of having the guest domains remaining active. Howard On Wed, 2007-10-31 at 10:43 -0400, Eric Sharakan wrote: > Hi Howard. Without knowing the details of your actual problem, let me > explain how control domain reconfiguration works in LDoms 1.0.1 vs. > 1.0. When reconfiguring the control domain under LDoms 1.0.1, the > LDom Manager enters "delayed reconfiguration" mode. Once in this > mode, all subsequent operations are pended until the control domain > reboots. One important point to understand for folks coming from 1.0 > is that this delayed reconfig behavior is completely distinct from > saving/restoring configurations to/from the SP. Let me elaborate: > Under 1.0, one had to start from the factory-default config, perform > the control domain reconfiguration in "config mode", save the new > configuration to the SP, and initiate a full powercycle of the box to > instantiate that new config. > > > > Under 1.0.1, there is no "config mode" as part of the factory-default > config anymore; in fact the control domain can be reconfigured > regardless of the currently active config. Nor does one need to save > the new config to the SP & powercycle; a simple reboot of the control > domain is all that's needed to have the pended delayed reconfig > operations take effect. Unlike in LDoms 1.0, this reboot will _not_ > initiate a powercycle of the box; this ability to soft reboot the > control domain (or any I/O domain) is the key feature in 1.0.1 that > enables all this. > > > Now, just because you no longer _need_ to save the current > configuration to the SP before rebooting the control domain, doesn't > mean you _shouldn't_ save your new config; you absolutely should! We > _strongly_ recommend you always save any new configuration you create > to the SP. You can safely save your configuration even if there are > delayed reconfig operations pending; in this case, the configuration > that gets saved is the pending one. If you do this, then it doesn't > matter whether you subsequently reboot the control domain or > powercycle the box (assuming no other domains are active of course!); > the new config will be instantiated when the control domain boots back > up. > > > If you neglected to save your configuration to the SP, the system will > revert to the last saved configuration (or factory-default if no other > configs have been saved) if & when the box powercycles. One other > point to understand in all this is that if you reboot the control > domain when there are no other domains bound or active, and there is > _not_ a delayed reconfiguration in progress, the hypervisor will > instruct the SP to powercycle the box (and if you hadn't previously > saved your config... well you get the idea). > > > Howard, I'm hoping this helps explain the behavior you're seeing when > you attempt to reconfigure your control domain. If not, and/or > anything I said above doesn't match what you're seeing, please let me > know. > > > Thanks. > > > -Eric > > > P.S. I think I'm going to post this info to my blog; I suspect it'll > be useful to many folks. > > > On Oct 31, 2007, at 8:07 AM, Howard Selover III wrote: > > > > > Hello Eric, > > > > I am using LDOM 1.0.1. I am NOT able to reconfigure without > > deleting the existing configuration and rebooting back to the > > factory-default. If the latest software is suppose to allow > > reconfiguration why does it not work on my machine? > > > > Howard > > > > On Tue, 2007-10-30 at 14:17 -0700, Eric Sharakan wrote: > > > > > Yes, in LDoms 1.0, you can only reconfigure the control domain when in > > > factory-default mode. This restriction is removed in LDoms 1.0.1, which > > > was just released. > > > > > > Also, you can enable networking between guest & control domain while at > > > the same time communicate off the server. There is some trick with > > > setting the MAC address of the vsw to match the MAC address of the actual > > > NIC to make it work. I don't know the exact details, but I suspect > > > someone who does will post them soon enough. :-) > > > -- > > > This message was posted from opensolaris.org > > > _______________________________________________ > > > ldoms-discuss mailing list > > > ldoms-discuss at opensolaris.org > > > http://mail.opensolaris.org/mailman/listinfo/ldoms-discuss > > > > -- > > Howard Selover III > > Principal Engineer > > Chief Architect's Office > > Ulticom, Inc. > > 1020 Briggs Road > > Mount Laurel, NJ 08054 > > > > Direct: +1-856-787-2739 > > Mobile: +1-856-495-4181 > > Fax: +1-856-866-2033 > > Email: selover at ulticom.com > > Web: www.ulticom.com > > > -- Howard Selover III Principal Engineer Chief Architect's Office Ulticom, Inc. 1020 Briggs Road Mount Laurel, NJ 08054 Direct: +1-856-787-2739 Mobile: +1-856-495-4181 Fax: +1-856-866-2033 Email: selover at ulticom.com Web: www.ulticom.com -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.opensolaris.org/pipermail/ldoms-discuss/attachments/20071031/16ac1768/attachment.html>
