Product data

110 PowerVM Migration from Physical to Virtual Storage
below, the PHYS2VIRT_CAPABLE field for both disks show a state of YES.
This tells us that it is safe to use these disks for our physical-to-virtual
migration.
$ chkdev -dev hdisk6 -verbose
NAME: hdisk6
IDENTIFIER: 3E213600A0B8000291B0800009DCB0402FC540F1815
FAStT03IBMfcp
PHYS2VIRT_CAPABLE: YES
VIRT2NPIV_CAPABLE: NA
VIRT2PHYS_CAPABLE: NA
PVID: 000fe4117e88efc00000000000000000
UDID: 3E213600A0B8000291B0800009DCB0402FC540F1815
FAStT03IBMfcp
IEEE:
VTD:
$ chkdev -dev hdisk7 -verbose
NAME: hdisk7
IDENTIFIER: 3E213600A0B8000291B0800009DCC0402FC6C0F1815
FAStT03IBMfcp
PHYS2VIRT_CAPABLE: YES
VIRT2NPIV_CAPABLE: NA
VIRT2PHYS_CAPABLE: NA
PVID: 000fe41181e1734c0000000000000000
UDID: 3E213600A0B8000291B0800009DCC0402FC6C0F1815
FAStT03IBMfcp
IEEE:
VTD:
7. Locate the vhost server adapters and map the disks to the destination client
partition using the mkvdev command, as in the example that follows. To
validate that you have chosen the correct vhost adapters, look at the slot
numbers from the lsmap command. As you can see from the lsmap output
below, the slot number for vhost6 is C17 and the slot number for vhost7 is
C18. These slot numbers match the IDs that were used when creating the
adapters on the HMC.
$ lsmap -vadapter vhost6
SVSA Physloc Client Partition ID
--------------- -------------------------------------------- ------------------
vhost6 U8204.E8A.10FE411-V2-C17 0x00000000
VTD NO VIRTUAL TARGET DEVICE FOUND
$ lsmap -vadapter vhost7
SVSA Physloc Client Partition ID
--------------- -------------------------------------------- ------------------