Jerry Jelinek wrote: > Darren J Moffat wrote: >> Jerry Jelinek wrote: >>> Darren J Moffat wrote: >>>> What happens with the hostid on x86 ? when a p2v is done ? Does the >>>> hostid of the created zone match the hostid of the original host ? >>> >>> Darren, >>> >>> No, by default a zone's hostid is the same as the global zones >>> hostid, unless the zone is configured to use a different hostid >>> as per: >>> >>> PSARC/2008/647 Configurable Hostids for Non-Global Zones >>> >>> The hostid is more of a zone configuration issue so it is >>> very possible that as part of the process of consolidating >>> a physical system into a zone, you would want to configure >>> the original hostid onto the zone. >> >> Given this case is about physical to virtual I fully expected the >> hostid of the zone to match the physical machine in the default case. >> In fact I think I'd almost insist on that being the case unless you >> can explain why it is bad to do this (I can only see good from it as >> it eases the migration from apps running on the physical machine >> dependent on its hostid to running in the zone). I think requiring an >> explicit step to enable to hostid to machine when doing a p2v is >> unnecessary and will lead to confusion. > > Darren, > > The sysadmin manages the zone configuration independently of > the zone installation. While we could change the zone configuration > to match what is being installed into the zone, that might mean > that we would be changing something that the sysadmin had explicitly > intended, so we never change the zonecfg. Instead, what we do is try > to adapt the data inside the zone to match the configuration. For > example, we don't change the zonecfg to match the IP address of the > original system, instead we change the config files inside the zone > to match the IP address that the sysadmin put on the zonecfg. We > take a similar approach for the hostid. While changing the zonecfg > for the hostid is obviously less drastic than changing some of the > other properties, it seems clearer to tell the sysadmin that the > zonecfg they explicitly set up is what is used. This is consistent > with the way the S8 and S9 brands work. We don't change those zonecfgs > to add the hostid of the original system, that is left to the sysadmin > if that is what they really want. I think making a change so that > the zonecfg is modified based on a zone install operation would be > setting a bad precedent. I guess I'm curious if other ARC members > feel differently.
I'm happy with that explanation. I think what is "wrong" here is the split between zonecfg and installation is a little at odds with a p2v conversion. However I don't think this case should attempt to address any of that. The case can go forward as specified as far as I'm concerned. -- Darren J Moffat
