Dave,
Xen guest domain configuration files are fragments of Python[1] code. Certain variable names are "well known" to the configuration infrastructure and can be set to control the creation of the guest domain.
So is the intent that these Xen configuration files are used to control the IP configuration of the Solaris domUs at each domU boot? If this is the case, what happens during the Solaris installation (or following a sys-unconfig) when the domU boots up and "ifconfig -a plumb" returns one or more of the interfaces specified in the "vif" property? Will the sysidtool(1M) framework prompt the user to configure the xnf* interface(s)? I can see the advantage of having this be a property under Xen configuration (particularly in the migration case) although as Erik pointed out in his reply, it would really be nice if we could be using DHCP for this as it's my hope that we can use that to provide a (locked down) configuration for zones with an exclusive IP stack as well.
3 Accessing the Configuration Data in a Guest Domain ####################################################
A new utility is provided to allow the examination of system properties from within shell scripts (/sbin/devprop).
Given the network centric aspect of these properties, did you consider extending the existing /sbin/netstrategy for this purpose? Or are there other Xen supplied properties (not related to networking) which a guest domain may wish to retrieve from a shell script? dsc _______________________________________________ networking-discuss mailing list [email protected]
