When migrating an LPAR utilizing Live Partition Mobility (LPM), which statement is correct?

LPM is explicitly designed to move LPARs between systems managed by the same HMC, so requiring different HMC devices contradicts the standard LPM architecture.

LPM does not require that virtual adapter slot numbers on the destination VIO Server match those of the source - virtual adapters are remapped during the mobility operation.

IBM requires that the reservation_policy attribute on physical disk backing devices be the same on both the source and destination VIO Servers before LPM can proceed. A mismatch - for example, no_reserve on one side and single_path on the other - can cause I/O errors or data integrity issues once the LPAR resumes on the destination system. This requirement is validated during the LPM pre-migration check and will block the operation if inconsistencies are found.

LPARs with dedicated physical I/O adapters cannot be migrated using LPM because dedicated hardware is bound to a specific physical system and cannot be transparently moved.