The target zones still contain configuration information from the source system (for example, network parameters) and must be adjusted for the new environment.
root@TargetGuestDom# zonecfg -z dbzone zonecfg:dbzone> remove net zonecfg:dbzone> remove device zonecfg:dbzone> commit zonecfg:dbzone> add net zonecfg:dbzone:net> set physical=vnet0 zonecfg:dbzone:net> set address=192.0.2.52/23 zonecfg:dbzone:net> end zonecfg:dbzone> add device zonecfg:dbzone:device> set match=/dev/rdsk/c0d2s0 zonecfg:dbzone:device> end zonecfg:dbzone> add device zonecfg:dbzone:device> set match=/dev/rdsk/c0d3s0 zonecfg:dbzone:device> end zonecfg:dbzone> commit zonecfg:dbzone> verify zonecfg:dbzone> exit
root@TargetGuestDom# zonecfg -z dbzone info
zonename: dbzone
zonepath: /zones/dbzone
brand: native
autoboot: true
bootargs:
pool: dbzone-pool
limitpriv: default,proc_priocntl,proc_clock_highres
scheduling-class:
ip-type: shared
hostid:
fs:
dir: /logs/redologs
special: /dev/md/dsk/d20
raw: /dev/md/rdsk/d20
type: ufs
options: [rw,setuid,devices,intr,forcedirectio,largefiles,logging,noquota,xattr,nodfratime]
fs:
dir: /logs/archivelogs
special: /dev/md/dsk/d30
raw: /dev/md/rdsk/d30
type: ufs
options: [rw,setuid,devices,intr,forcedirectio,largefiles,logging,noquota,xattr,nodfratime]
net:
address: 192.0.2.52/23
physical: vnet0
defrouter not specified
device
match: /dev/rdsk/c0d2s0
device
match: /dev/rdsk/c0d3s0
dataset:
name: dbzone_db_binary
root@TargetGuestDom# zonecfg -z webzone zonecfg:webzone> remove net zonecfg:webzone> add net zonecfg:webzone:net> set address=192.0.2.26/23 zonecfg:webzone:net> set physical=vnet0 zonecfg:webzone:net> end zonecfg:webzone> commit zonecfg:webzone> verify zonecfg:webzone> exit
root@TargetGuestDom# zonecfg -z webzone info
zonename: webzone
zonepath: /rpool/webzone
brand: native
autoboot: true
bootargs:
pool: webzone-pool
limitpriv:
scheduling-class:
ip-type: shared
hostid:
inherit-pkg-dir:
dir: /usr
inherit-pkg-dir:
dir: /sbin
net:
address: 192.0.2.26/23
physical: vnet0
defrouter not specified
root@TargetGuestDom# /opt/SUNWldm/lib/contrib/pigz -dc -f /ovas1/dbzone.gz | zfs receive -F dbzone@first root@TargetGuestDom# /opt/SUNWldm/lib/contrib/pigz -dc -f /ovas1/dbzone_db_binary.gz | zfs receive -F dbzone_db_binary@first
Immediately after the zones are attached, the zones are in an installed state.
root@TargetGuestDom# zoneadm -z dbzone attach -u Getting the list of files to remove Removing 485 files Remove 17 of 17 packages Installing 8273 files Add 87 of 87 packages Updating editable files The file </var/sadm/system/logs/update_log> within the zone contains a log of the zone update. root@TargetGuestDom# zoneadm -z webzone attach -u Getting the list of files to remove Removing 279 files Remove 17 of 17 packages Installing 861 files Add 87 of 87 packages Updating editable files The file </var/sadm/system/logs/update_log> within the zone contains a log of the zone update.
root@TargetGuestDom# zoneadm list -cv ID NAME STATUS PATH BRAND IP 0 global running / native shared - webzone installed /rpool/webzone native shared - dbzone installed /zones/dbzone native shared