The sysidtool-net script does this:
/sbin/ifconfig -a plumb > /dev/null 2>&1
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:
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 TI
> 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 th
Easy is a relative term. I'd rather not have to refactor the code to work
around a deficiency in the virtualisaton method. I've decided to switch to a
full hypervisor and leave zones for less problematic configurations.
--
This message posted from opensolaris.org
__
> 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 n
> 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 de
> 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
On 07/15/09 17:27, Christine Tran wrote:
On Wed, Jul 15, 2009 at 3:32 PM, Patrick J.
McEvoy 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=en&a=view&q=sysidcfg+and+containers
Basically:
clone a zone
On Wed, Jul 15, 2009 at 3:32 PM, Patrick J.
McEvoy 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=en&a=view&q=sysidcfg+and+containers
>
> Basically:
>
>clone a zone
>zoneadm -z ready
>edit
+--
| On 2009-07-15 12:24:43, Alastair Neil wrote:
|
| How then do you create two zpools with the same name one for the test zone
and one for the devel zone?
You don't. But you can easily hack around it.
e.g.,
rpool/zo
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=en&a=view&q=sysidcfg+and+containers
Basically:
clone a zone
zoneadm -z ready
edit /root/etc/sysidcfg
zoneadm -z boot
The problem is that after the
How then do you create two zpools with the same name one for the test zone and
one for the devel zone?
--
This message posted from opensolaris.org
___
zones-discuss mailing list
zones-discuss@opensolaris.org
On Wed, Jul 15, 2009 at 11:28:21AM -0700, Alastair Neil wrote:
> I am trying to set up two zones to exactly duplicate a production server one
> for test and one for development. The production server has a number of
> zpools which are specifically named and the scripts we are testing expect
> t
I am trying to set up two zones to exactly duplicate a production server one
for test and one for development. The production server has a number of zpools
which are specifically named and the scripts we are testing expect this naming.
I have run in to a brick wall, as it seems that it is impos
14 matches
Mail list logo
