Hi guys !
In general, Solaris 11 is a cool evolution to Solaris 10. But I'm not a
fan of the configs buried in some weird places instead of plain files.
After installing a zone (and before booting it for the first time), I
can modify network settings in the initial profile /etc/svc/profile/ incoming/config. Those are applied during zone init and the profile is apparently moved to /etc/svc/profile/sysconfig. When I edit the latter
file later, the changes are ignored on the next reboot. Where is the
actual config saved and how can I edit it to become active with the next boot?
I liked the /etc/hostname.* (etc.) approach better ;) ...
Any hints?
On 23.08.2026 21:02, YTC1 wrote:
Just use the ipadm commands in the zone, it is (as you can see) all held
in XML. This was to make it easier for machines/software to deal with,
apparently.
It's just held in the XML until the zone is booted for the first time. Afterwards, the config is buried in some database.
At the moment, I'm forced to use "ipadm" but this is only possible while
the zone is running - and that's also the main problem. I'd prefer to do
the config while the zone is still down.
If you are not using anet (ie net) in the config then the IP address canYep - this does not work with exclusive IP zones, which I have.
be set there.
Regards
-a-a-a-aFrank
On 24.08.2026 18:37, YTC1 wrote:
Is this just for a 1st time config, or for each boot?
Only for the initial config on the first boot ...
I tried to place a suitable profile before booting but that is ignored.
As in, why do you want to change it, what is the project end point? IsRelocation of the host to a different DC with different networks. Of
it cloning?
course, I can adjust the IP address of the XSCF in advance so that I'll
be able to access the host and the zones but IMO, it's not nice to be
forced to boot with "foreign" addresses and change them while online.
Who knows what happens when those addresses suddenly appear? And even if
I knew that there'll be dupes, I wouldn't be able to avoid trouble.
I can rename the zone and zpools and everything non-invasively but
that's impossible with IP addresses.
Maybe this was working with earlier Solaris versions? I'm using 11.4.94
here and in the meantime, I have taught my script to do all the "ipadm"
and "route" magic right after booting the zone(s). I don't like it that
way but currently, there doesn't seem to be an option ...
On 25.08.2026 10:40, YTC1 wrote:
Right, so what you want is to create a <yadda>/zones/<zonename>/
sc_profile.xml
The profile for the initial config was created by "sysconfig" and is
in /etc/svc/profile/incoming/config. Placing a modified file there later with a subsequent reboot does nothing - as already described.
I now put the new config to /system/zones/<zone>/sc-profile.xml (so
parallel to the zone's root) and rebooted. Again, nothing happened ;) ..
Once you have a "base" sc_profile, you can probably edit it by script as
and when.
I do :) ...
On 25.08.2026 13:38, YTC1 wrote:
Or, if zone already built and running, then run
sysconfig unconfigureHmm ... indeed, I was wondering what would have to be done that the
place the sc_profile.xml
boot
initial config is done again. And I was also thinking about a
"sysunconfig" but I'm not 100% sure if this doesn't remove more than the profile will repair later.
But does the XML file has to be in /system/zones/<zone> or in .../root/ etc/svc/profile/incoming/config?/system/zones/<znone>
Maybe I'll try all that with my test zone ...--
On 25.08.2026 13:34, YTC1 wrote:
The file needs to be in place before the 1st boot, it will then set the
config.
So, between zoneadm install and zoneadm boot, create the fileThat's the way the zones were built - I'm talking about existing zones
which have to be modified after running for a period of time.
On 25.08.2026 18:31, YTC1 wrote:
sysconfig unconfigureWould that also work for the global zone?
create new sc_profile (or edit the one you saved post creation) in
<yadda>/zones/<zone>
boot zone
So far, I always ended up in a zone with absolutely no network config.
Not even loopback. Maybe the new config hasn't been applied at all.
Do you know what would to be done to fake a "sysconfig unconfigure" so
that the profile is used without resetting the entire config? Is there
any file to be touched/removed or is this also hidden somewhere deep
inside?
Regards
-a-a-a-aFrank
"-g network" is mandatory as otherwise, I would also lose users and so forth. After I started using it with attempt #3 or so, the zone at least
had a loopback interface ;) ...
I don't know what but apparently, I'm still doing something wrong. No
matter to which of the dirs I put the exact same profile which had been
used for installation (just with a different IP address) or the same
file named "sc-profile.xml", the main interface is missing. I'll check
the logs but the good news is that the renaming and the "ipadm" stuff
now works for GZ and NGZ.
| Sysop: | Amessyroom |
|---|---|
| Location: | Fayetteville, NC |
| Users: | 74 |
| Nodes: | 6 (0 / 6) |
| Uptime: | 03:56:34 |
| Calls: | 1,194 |
| Files: | 1,353 |
| D/L today: |
2 files (1,590K bytes) |
| Messages: | 291,365 |