For a running VM in VMware, if we enable CBT flags on the fly (while VM is running) by adding both `ctkEnabled=TRUE` and `scsi0:0.ctkEnabled=TRUE` parameters.

While running MTV 2.6.3, and try to create a migration plan, we get a warning that CBT is not enabled for this particular VM (shown in the screenshot)

But! If we ignore this "warning" and move on and create it, it will be in a Ready state and work (can WARM migrate this VM) <-- and seems that CBT is working with the incremental disk migration as per the customer's tests.
 
If we use MTV 2.7.1, we get the same warning as in the screenshot as expected, But! The difference here is that after creating the migration plan, we get the following error message that prevents the migration plan from working (stays in Error state):

Danger alert:The plan is not ready - VMMissingChangedBlockTracking
Changed Block Tracking (CBT) has not been enabled on some VM. This feature is a prerequisite for VM warm migration.. To troubleshoot, check the Forklift controller pod logs.