Jeff Victor wrote On 04/24/07 13:27,: > Erik Nordmark wrote: > >> Steffen Weiberle wrote: >> >>> A point was made that this behavior is not consistent with other >>> resouce issues when booting a zone. If a zone is given some >>> 'dedicated-cpus' and there are not sufficient CPUs available, the >>> zone will not boot. >> >> > >> >>> Is this intended behavior? Is it worth considering having the >>> behavior be that the zone does not boot if a network resource is not >>> available, as is the case for [at least] CPUs? Or consider a variable >>> that indicated the minimun available interfaces? Or maybe something >>> else. >> >> >> The consistency has actually been driven from how network interfaces >> work in the global zone. >> When the global zone boots and tries to use e.g. bgeN and that NIC >> doesn't exist, the boot continues. >> In S10 FCS the behavior for zones was different in that a zone would >> fail to boot if the network interface wasn't present. This was fixed >> in a S10 update so that the zone would boot without the missing >> network interface. (And emit a warning.) >> >> For exclusive-IP zones we are consistent with that; the zone boots >> even if the network interface isn't available (and emit a warning.) > > > Thanks Erik, that consistency makes sense. Is the warning emitted to > the GZ, the NGZ, or both? I think that the GZ admin would want to know, > so that the problem can be fixed. Also, the NGZ admin would want to > know, to avoid discovering a downstream symptom and facing the task of > troubleshooting the symptom.
I can answer that, now. If there is no file to plumb the interface in the zone, there is no indication in the zone. Without an /etc/hostname*, the only error message is in the terminal session if the boot is due to the issuance of 'zoneadm... [re]boot', or to the console if it is due to another action (autoboot, reboot within the zone). With an /etc/hostname, their is a message in the zone console, but none in /var/adm/messages. However, this is also consistent with the global zone. If you have /etc/hostname* in it for an interface that does not exist, the only message goes to the console, but not to /var/adm/messages. Steffen > -------------------------------------------------------------------------- > Jeff VICTOR Sun Microsystems jeff.victor @ sun.com > OS Ambassador Sr. Technical Specialist > Solaris 10 Zones FAQ: http://www.opensolaris.org/os/community/zones/faq > --------------------------------------------------------------------------
