By jbeloro on Jun 04, 2008
The steps to follow to upgrade from LDOM 1.0.1 and LDOM 1.0.2 to LDOM 1.0.3
1. Ensure Firmware is at the appropriate level (minimum of 6.6.x for T1 platform and 7.1.x) for T2 platform. Note that the Admin guide states that 6.5 and 7.0 are the minimum levels but the release notes state that 6.6 and 7.1 are the required level for 1.0.3 functionality.
2. Ensure the Solaris OS is at the appropriate kernel level. The Release notes have Solaris 10 11/06 (update 3) at kernel level 127127-11 as the absolute minimum. For update 4 (08/07) it's still kernel level 127127-11 and update 5 (05/08) starts at kernel level 127127-11.
3. Stop the guest domains. I brought the guest domains down to the OK prompt and then issued the ldm stop-domain ldomname from the control domain before proceeding.
4. For safety sake issue the ldm ls-constraints ldomname > /tmp/ldomname.xml command so that you have a listing of the definitions for the ldom.
5) svcadm disable ldmd
6) pkgrm SUNWldm
7) pkgadd the new SUNWldm (pkgadd -Gd . SUNWldm.v)
8) svcadm refresh ldmd
9) svcadm enable ldmd
10) After ensuring that the ldmd service is "online" - ldm start-domain ldomname
The following caveat should also be noted:
The admin guide states that existing LDOMS 1.0.1 or 1.0.2 configurations are compatible with 1.0.3. This is not entirely the case. The upgrade section needs to be amended to point out the following: If the backend volume is a disk slice or a volume manager volume then the virtual disk backend must be re-exported with options=slice. If this reconfiguration is not done the guest domain will not be able to see the disk service and will get I/O errors. Hope this helps others.
(end of Nick's post)
For more information on LDoms 1.0.3, here's the link to my LDoms 1.0.3 entry.