Re: [zones-discuss] sysidcfg requires zlogin
If you want to configure the ip addresss within the zone with sysidcfg/hostname.* files, then you need to use exclusive ip stack zones: I am using exclusive ip stacks: # zonecfg -z zweb1 export | grep ip-type set ip-type=exclusive # This is definitely a problem with multiple VNICs assigned to a zone. There is no problem when only one VNIC is assigned. -- This message posted from opensolaris.org ___ zones-discuss mailing list zones-discuss@opensolaris.org
Re: [zones-discuss] sysidcfg requires zlogin
If you want to configure the ip addresss within the zone with sysidcfg/hostname.* files, then you need to use exclusive ip stack zones: zonecfg -z zweb$Z set iptype=exclusive -Steve L. On Wed, Jul 15, 2009 at 03:55:27PM -0700, Patrick J. McEvoy wrote: the only thing that comes to mind for me right now is a possible mis-match of the installation repository used and the repository when the zone was created. I could re-create the master -- i.e. that which I am cloning -- if you think that would make a difference. BTW, the master has never been booted -- I assume this makes no difference. This is the script I run to test cloning: Z=1 zoneadm -z zweb$Z halt zoneadm -z zweb$Z uninstall -F zonecfg -z zweb$Z delete -F zonecfg -z zclone export | zonecfg -z zweb$Z -f - zonecfg -z zweb$Z set zonepath=/zonefs/zweb$Z zonecfg -z zweb$Z add net; set physical=vphys1; end zonecfg -z zweb$Z add net; set physical=vweb$Z; end zoneadm -z zweb$Z clone zclone zoneadm -z zweb$Z ready cp ./sysidcfg /zonefs/zweb$Z/root/etc/sysidcfg touch /zonefs/zweb$Z/root/etc/hostname.vphys1 touch /zonefs/zweb$Z/root/etc/hostname.vweb1 #zoneadm -z zweb$Z halt zoneadm -z zweb$Z boot #zlogin -C zweb$Z -- This message posted from opensolaris.org ___ zones-discuss mailing list zones-discuss@opensolaris.org ___ zones-discuss mailing list zones-discuss@opensolaris.org
[zones-discuss] sysidcfg requires zlogin
I am trying to pre-configure zones with sysidcfg as described in: http://docs.sun.com/app/docs/doc/817-1592/z.login.task-38?l=ena=viewq=sysidcfg+and+containers Basically: clone a zone zoneadm -z zone ready edit zonepath/root/etc/sysidcfg zoneadm -z zone boot The problem is that after the zone boots I still have to do an initial zlogin -C to the zone to get the system to look at /etc/sysidcfg. How can I kick the zone so that it configures and comes up on the net without my having to do an interactive login (and without having to write an expect script...)? Thanks! -- This message posted from opensolaris.org ___ zones-discuss mailing list zones-discuss@opensolaris.org
Re: [zones-discuss] sysidcfg requires zlogin
On Wed, Jul 15, 2009 at 3:32 PM, Patrick J.
McEvoyno-re...@opensolaris.org wrote:
I am trying to pre-configure zones with sysidcfg as described in:
http://docs.sun.com/app/docs/doc/817-1592/z.login.task-38?l=ena=viewq=sysidcfg+and+containers
Basically:
clone a zone
zoneadm -z zone ready
edit zonepath/root/etc/sysidcfg
zoneadm -z zone boot
The problem is that after the zone boots I still have to do an initial
zlogin -C
to the zone to get the system to look at /etc/sysidcfg. How can I kick the
zone
so that it configures and comes up on the net without my having to do an
interactive
login (and without having to write an expect script...)?
If you have a correct sysidcfg, you will never need to go thru the
system identification prompt at zlogin -C. Please post your sysidcfg.
Here's a barebone one that works for me:
name_service=NONE
root_password=xyzmno
system_locale=C
timeserver=localhost
timezone=GMT
terminal=vt100
security_policy=NONE
nfs4_domain=dynamic
network_interface=primary {
hostname=${ZONENAME}
protocol_ipv6=no}
YMMV. If you have an exclusive-ip zone you will have to touch
/etc/hostname.NIC in the zone as well.
CT
___
zones-discuss mailing list
zones-discuss@opensolaris.org
Re: [zones-discuss] sysidcfg requires zlogin
On 07/15/09 17:27, Christine Tran wrote:
On Wed, Jul 15, 2009 at 3:32 PM, Patrick J.
McEvoyno-re...@opensolaris.org wrote:
I am trying to pre-configure zones with sysidcfg as described in:
http://docs.sun.com/app/docs/doc/817-1592/z.login.task-38?l=ena=viewq=sysidcfg+and+containers
Basically:
clone a zone
zoneadm -z zone ready
edit zonepath/root/etc/sysidcfg
zoneadm -z zone boot
The problem is that after the zone boots I still have to do an initial zlogin
-C
to the zone to get the system to look at /etc/sysidcfg. How can I kick the zone
so that it configures and comes up on the net without my having to do an
interactive
login (and without having to write an expect script...)?
Patrick and I have been discussing this off-line, it works for me, and
the only thing that comes to mind for me right now is a possible
mis-match of the installation repository used and the repository when
the zone was created.
If you have a correct sysidcfg, you will never need to go thru the
system identification prompt at zlogin -C. Please post your sysidcfg.
Here's a barebone one that works for me:
name_service=NONE
root_password=xyzmno
system_locale=C
timeserver=localhost
timezone=GMT
terminal=vt100
security_policy=NONE
nfs4_domain=dynamic
network_interface=primary {
hostname=${ZONENAME}
protocol_ipv6=no}
YMMV. If you have an exclusive-ip zone you will have to touch
/etc/hostname.NIC in the zone as well.
This should not be required, as the sysid process will create the
file(s) based on the network_interface information.
CT
___
zones-discuss mailing list
zones-discuss@opensolaris.org
___
zones-discuss mailing list
zones-discuss@opensolaris.org
Re: [zones-discuss] sysidcfg requires zlogin
If you have a correct sysidcfg, you will never need
to go thru the
system identification prompt at zlogin -C. Please
post your sysidcfg.
network_interface=vphys1 {
primary
hostname=zweb1
ip_address=192.168.17.1
netmask=255.255.255.0
protocol_ipv6=no
default_route=none
}
network_interface=vweb1 {
hostname=zweb1-vweb
ip_address=172.16.17.1
netmask=255.255.255.0
protocol_ipv6=no
default_route=none
}
terminal=xterm
system_locale=C
security_policy=NONE
name_service=NONE
timezone=US/Pacific
nfs4_domain=dynamic
root_password=zVUhpaPP5oiFo
--
This message posted from opensolaris.org
___
zones-discuss mailing list
zones-discuss@opensolaris.org
Re: [zones-discuss] sysidcfg requires zlogin
YMMV. If you have an exclusive-ip zone you will have to touch /etc/hostname.NIC in the zone as well. I am using exclusive-ip, but touching the hostname.NIC files did not make a difference. Another oddity I did not mention in the original post is that I get different behavior on zlogin depending whether I have terminal= before or after network_interface=. If the network comes first I get prompted for a terminal type; if terminal comes first, I don't get prompted for a terminal type, but I get an error that vphys1 is not valid. -- This message posted from opensolaris.org ___ zones-discuss mailing list zones-discuss@opensolaris.org
Re: [zones-discuss] sysidcfg requires zlogin
If you have a correct sysidcfg, you will never need to go thru the system identification prompt at zlogin -C. Just to be clear: I don't have to go through system identification at zlogin -C, but I have to do a zlogin -C to get sysconfig to happen. That is, once I do zlogin -C and get to the actual login prompt, the system is configured. I am not prompted for anythin -- it all comes from sysidcfg -- but none of it takes effect until zlogin. -- This message posted from opensolaris.org ___ zones-discuss mailing list zones-discuss@opensolaris.org
Re: [zones-discuss] sysidcfg requires zlogin
If I get rid of the second interface and use network_interface=PRIMARY then things work. When I use two interfaces and the primary keyword I get two copies of sysidnet that seem to hang around forever (or until zlogin): swag...@sol:~# ps -fz zweb1 UID PID PPID CSTIME TTY TIME CMD root 24285 1 0 20:47:53 ? 0:00 /usr/sbin/nscd root 24183 1 0 20:47:47 ? 0:00 zsched root 24351 24350 0 20:47:56 ? 0:00 /usr/sbin/sysidnet -l root 24220 24183 0 20:47:47 ? 0:00 /sbin/init root 24346 1 0 20:47:56 ? 0:00 /usr/sbin/cron root 24224 1 0 20:47:47 ? 0:02 /lib/svc/bin/svc.startd root 24349 24224 0 20:47:56 ? 0:00 /sbin/sh /lib/svc/method/sysidtool-net daemon 24257 1 0 20:47:49 ? 0:00 /lib/crypto/kcfd root 24226 1 0 20:47:47 ? 0:04 /lib/svc/bin/svc.configd root 24255 1 0 20:47:49 ? 0:00 /sbin/sh /lib/svc/method/svc-dlmgmtd root 24350 24349 0 20:47:56 ? 0:00 /usr/sbin/sysidnet -l swag...@sol:~# date Wed Jul 15 20:51:22 PDT 2009 swag...@sol:~# So...I expect multiple network interfaces in sysidcfg are broken in OpenSolaris 2009.06. -- This message posted from opensolaris.org ___ zones-discuss mailing list zones-discuss@opensolaris.org
Re: [zones-discuss] sysidcfg requires zlogin
The sysidtool-net script does this: /sbin/ifconfig -a plumb /dev/null 21 Then fires off sysidnet. I embedded these two lines in sysidtool-net /sbin/dladm show-link /etc/dladm-show-link /sbin/ifconfig -a /etc/ifconfig-a and the results show that the VNICs do not appear: swag...@sol:~# cat /zonefs/zweb1/root/etc/dladm-show-link swag...@sol:~# cat /zonefs/zweb1/root/etc/ifconfig-a lo0: flags=2001000849UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL mtu 8232 index 1 inet 127.0.0.1 netmask ff00 lo0: flags=2002000849UP,LOOPBACK,RUNNING,MULTICAST,IPv6,VIRTUAL mtu 8252 index 1 inet6 ::1/128 swag...@sol:~# Something must bring them up later. -- This message posted from opensolaris.org ___ zones-discuss mailing list zones-discuss@opensolaris.org
