Looks like cancelling the migration leaves an orphaned disk on StarLVM. Since qm disk rescan detects it, the volume still exists but isn't properly referenced in the VM config. Hopefully this can be fixed in a future plugin update.