core: fix wrong dedicated migration assignments

When invoking a migration the `cpusets` is sent to VDSM as a list. The
index of each list represents the virtual CPU and the value is the
physical CPU we are taking. Sorting the values is wrong, as it results a
wrong mapping, causing split cores and split sockets.

Change-Id: Ib5d2d178557fa3f9e0130325f52e8cf6e8a04970
Bug-Url: https://bugzilla.redhat.com/2075037
Signed-off-by: Liran Rotenberg <lrotenbe@redhat.com>

backend/manager/modules/bll/src/main/java/org/ovirt/engine/core/bll/MigrateVmCommand.java

@@ -430,7 +430,7 @@ private MigrateVDSCommandParameters createMigrateVDSCommandParameters() {
             maxIncomingMigrations = maxOutgoingMigrations = effectiveMigrationPolicy.getMaxMigrations();
         }
         if (getVm().getCpuPinningPolicy() == CpuPinningPolicy.DEDICATED) {
-            cpuSets = CpuPinningHelper.getAllPinnedPCpus(getDedicatedCpuPinning(getDestinationVdsManager())).stream().sorted()
+            cpuSets = CpuPinningHelper.getAllPinnedPCpus(getDedicatedCpuPinning(getDestinationVdsManager())).stream()
                     .map(Object::toString).collect(Collectors.toList());
             String numaPinningString = vmHandler.createNumaPinningForDedicated(getVm(), getDestinationVdsId());
             numaNodeSets = NumaPinningHelper.parseNumaSets(numaPinningString);