When a guest is migrated from one hypervisor to another hypervisor it should be eligible for the temporary guest pool within 24 hours of the migration. 

This will prevent the case where a customer is using VDC subscriptions only and a guest consumers a VDC master sub for itself when it checks in before virt-who has reported on the new host association. 

The flow could be as follows:

Guest is running on Host 1
Guest is consumer a host based entitlement from Host 1
Guest is vmotioned to Host 2
Guest is no longer eligible for entitlement from Host 1 so it is removed
Guest checks in (virt-who has not yet reported new host-guest mapping so Guest has no known hypervisor)
Guest is attached to temporary guest entitlement pool for Host 2
Virt-who checks in and reports on mapping of Guest to Host 2
Guest checks in
Temporary guest entitlement is removed from Guest
Guest follows current logic of auto-attach for host based guest pool.