# zonecfg -z zone1
zone1: No such zone configured
Use 'create' to begin configuring a new zone.
zonecfg:zone1> create
zonecfg:zone1> set zonepath=/localzones/zone1
zonecfg:zone1> add net
zonecfg:zone1:net> set physical=e1000g0
zonecfg:zone1:net> set address=dhcp
zonecfg:zone1:net> end
zonecfg:zone1> verify
zonecfg:zone1> exit
# zoneadm -z zone1 install
could not verify net address=dhcp physical=e1000g0
       Neither an IPv4 nor an IPv6 address nor a host name
zoneadm: zone zone1 failed to verify

zoneadm(1M) has no notion of the "dhcp" keyword.  What you've done
above is request a shared stack zone be created with an IPv4 address of
the *hostname* called "dhcp".  If you don't have such a name in your
"hosts" map, then you'll see the above error.

The resolution of

        5005887 RFE: zoneadmd should support plumbing an interface via

in snv_57 was for exclusive stack zones only.  There had been talk of
providing a similar capability for shared stack zones at one point but
I don't know the current status of that.  The fix that James mentioned

        6386331 dhcpagent should implement RFC 4361 client identifier

should help in this respect but it isn't sufficient by itself.  Both
zoneadmd(1M) and dhcpagent(1M) require further changes in order to
provide shared stack zones a dynamic address capability.

A question for those who would like this - what other sorts of DHCP
information would one want to use in this case?  The DNS domain name?
Time server information?

zones-discuss mailing list

Reply via email to