solaris 11, p2v in 3 steps
p2v is not a new feature. but i just tried it.
p2v is physical to virtual. which means you can migrate solaris from real HW to solaris zone.
- create zone on solaris11.
root@bnsol11a:~# zonecfg -z liuedy-z10
Use ‘create’ to begin configuring a new zone.
zonecfg:liuedy-z10> create -b
zonecfg:liuedy-z10> set brand=solaris10
zonecfg:liuedy-z10> set zonepath=/zone/liuedy-z10
zonecfg:liuedy-z10> set autoboot=true
zonecfg:liuedy-z10> add net
zonecfg:liuedy-z10:net> set address=10.240.3.180
zonecfg:liuedy-z10:net> set physical=net0
zonecfg:liuedy-z10:net> end
zonecfg:liuedy-z10> info
zonename: liuedy-z10
zonepath: /zone/liuedy-z10
brand: solaris10
autoboot: true
bootargs:
pool:
limitpriv:
scheduling-class:
ip-type: exclusive
hostid:
fs-allowed:
net:
address: 10.240.3.180
allowed-address not specified
configure-allowed-address: true
physical: net0
defrouter not specified
zonecfg:liuedy-z10> verify
net: address cannot be specified if ip-type = exclusive
ip-type is set to ‘exclusive’ by default.
liuedy-z10: Invalid argument
zonecfg:liuedy-z10> set ip-type=shared
zonecfg:liuedy-z10> verify
zonecfg:liuedy-z10> commit
zonecfg:liuedy-z10> exit
root@bnsol11a:~# zoneadm list -civ
ID NAME STATUS PATH BRAND IP
0 global running / solaris shared
– liuedy-z10 configured /zone/liuedy-z10 solaris10 shared
- create flash archive of old solaris.
// -S don’t cacluate the archive size. -L method cpio
[root@beisoltest02 ~]# flarcreate -S -n sol10_new -L cpio /net/10.240.3.210/export/zone/flash_store/sol10_new.flar
Archive format requested is cpio
Full Flash
Checking integrity…
Integrity OK.
Running precreation scripts…
Precreation scripts done.
Creating the archive…
2464714 blocks
Archive creation complete.
Running postcreation scripts…
Postcreation scripts done.
Running pre-exit scripts…
Pre-exit scripts done.
[root@beisoltest02 ~]#
- install the zone
root@bnsol11a:~# zoneadm -z liuedy-z10 install -p -a /export/zone/flash_store/sol10_new.flar
Progress being logged to /var/log/zones/zoneadm.20121120T061159Z.liuedy-z10.install
Installing: This may take several minutes…
Postprocessing: This may take a while…
Postprocess: Updating the image to run within a zone
Postprocess: Migrating data
from: rpool/export/zone/liuedy-z10/rpool/ROOT/zbe-0
to: rpool/export/zone/liuedy-z10/rpool/export
Postprocess: A backup copy of /export is stored at /export.backup.20121120T061735Z.
It can be deleted after verifying it was migrated correctly.
Result: Installation completed successfully.
Log saved in non-global zone as /export/zone/liuedy-z10/root/var/log/zones/zoneadm.20121120T061159Z.liuedy-z10.install
root@bnsol11a:~# zoneadm list -civ
ID NAME STATUS PATH BRAND IP
0 global running / solaris shared
– liuedy-z10 installed /export/zone/liuedy-z10 solaris10 shared
root@bnsol11a:~# zoneadm -z liuedy-z10 boot
root@bnsol11a:~# zoneadm list -civ
ID NAME STATUS PATH BRAND IP
0 global running / solaris shared
5 liuedy-z10 running /export/zone/liuedy-z10 solaris10 shared
root@bnsol11a:~# zlogin -C liuedy-z10
[Connected to zone ‘liuedy-z10’ console]
beisoltest02 console login:
Issue met before.
Postprocessing: This may take a while…
Postprocess: Updating the image to run within a zone
Postprocess: ERROR: SMF repository unavailable.
Postprocess: ERROR: Failed to boot zone to single user mode.
Postprocess: ERROR: Postprocessing failed.
Result: Postprocessing failed.
this is caused by the patch level doesn’t match the necessary for migration. so it’s a good idea to keep the system up to date.
upgrade from SunOS 5.10/Generic_137138-09 to Generic_147441-25 fixed the issue.