Yes, it is intended behavior, cpu is, en, cpu, physical machines cannot boot if cpu or mainboard or even, memory fail, but why a machine would refuse to boot when one or [even] all of the nic-s are unavailable? :-)
Best, Donghai. ----- Original Message ----- From: Steffen Weiberle <[email protected]> Date: Tuesday, April 24, 2007 8:37 pm Subject: [crossbow-discuss] failure mode when exclusive ip-type interface is not available To: crossbow-discuss at opensolaris.org > I have noticed and was discussing with some folks that when a zone > is > configured with an exclusive ip-type, and an interface assigned to > that > zone is not available, there is a message to that effect when > issuing > zoneadm ... boot in the global zone, but none in the non-global > zone. Or on > a reboot, there is a message to syslog/console. > > The test case had the interface just plumbed in the global zone, > after the > zone was configured. > > 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. > > In my case the interface was occupied by the global zone. But other > failure > modes included failed NICs, interfaces that were mis-configured, or > interfaces that DRed out (administratively or via FMA). > > Thanks > Steffen > _______________________________________________ > crossbow-discuss mailing list > crossbow-discuss at opensolaris.org > http://opensolaris.org/mailman/listinfo/crossbow-discuss >
