Note - By default, the zonep2vchk utility that is described in this section does not exist in Oracle Solaris 10 Update 8 or earlier. However, you can copy the /usr/sbin/zonep2vchk utility from another Oracle Solaris 10 Update 9 (or later) or any Oracle Solaris 11 system to the source system.
This section describes how to run the zonep2vchk(1M) command. This command evaluates a global zone's suitability for a physical-to-virtual migration into an Oracle Solaris 10 branded zone. The command reports these types of issues that might prevent a successful migration:
Issues that can be addressed with a specific zone configuration or with configuration changes in the global zone
Identification of functions that do not work inside a zone
root@SourceSystem# zonep2vchk --Executing Version: 5.10.1.1 - Source System: SourceSystem Solaris Version: Oracle Solaris 10 1/13 s10s_u11wos_24a SPARC Solaris Kernel: 5.10 Generic_150400-61 Platform: sun4u SUNW,SPARC-Enterprise - Target System: Solaris Version: Solaris 10 Zone Brand: native (default) IP type: shared --Executing basic checks - The following /etc/system tunables exist. These tunables will not function inside a zone. The /etc/system tunable may be transfered to the target global zone, but it will affect the entire system, including all zones and the global zone. If there is an alternate tunable that can be configured from within the zone, this tunable is described: rootdev:/pseudo/md@0:0,10,blk zonep2vchk has no information on tunable set md:mirrored_root_flag = 1 zonep2vchk has no information on tunable - The system is configured with the following ISCSI initiators. A zone cannot access ISCSI targets. ISCSI targets must be discovered and configured from the global zone. See iscsiadm(1M) for details: iqn.1986-03.com.sun:02:3e10566b-4e39-e82f-b866-ec2d56d14278 - The following SMF services will not work in a zone: svc:/network/iscsi/initiator:default svc:/system/iscsitgt:default - The following SMF services require ip-type "exclusive" to work in a zone. If they are needed to support communication after migrating to a shared-IP zone, configure them in the destination system's global zone instead: svc:/network/ipsec/ipsecalgs:default svc:/network/ipsec/policy:default svc:/network/routing-setup:default - The system is configured with SVM metadevices. A zone cannot configure SVM metadevices, but a zone can be configured to use existing metadevices. See metastat(1M) for details - If needed, the following non-standard vfstab entries will impact the zone configuration: Device /dev/md/dsk/d30 /dev/md/rdsk/d30 /u01 ufs 2 yes forcedirectio,logging /dev/md/dsk/d30 /dev/md/dsk/d40 /dev/md/rdsk/d40 /oradata ufs 2 yes forcedirectio,logging /dev/md/dsk/d40 - When migrating to an exclusive-IP zone, the target system must have an available physical interface for each of the following source system interfaces: bge0 bge2 - When migrating to an exclusive-IP zone, interface name changes may impact the following configuration files: /etc/hostname.bge0 /etc/hostname.bge2 - When migrating to a shared-IP zone, the following network features must be configured in the global zone if needed to support communication. They will not be configured automatically during migration. Nothing needs to be done for these features when migrating to an exclusive-IP zone where the configuration inside the migrated system image will be used: IP Multipath group ipmp0 Basic checks complete. Issue(s) detected: 16 --Total issue(s) detected: 16
In this example, there are no critical issues, and the few reported issues are addressed later in Prepare the Target System and Verify the Solaris 10 Branded Zone Configuration.