No lock files to find but left for 30 min and when I came back the error was gone...

Looks like PowerOffVM_Task is not supported on ESXI Free.
Maybe you could read the ESXI license information and disable warm migration for ESXI Free.
Or ask user to shutdown VM when ready. Right now it just hang waiting for VM to shutdown.

No lock files to find but left for 30 min and when I came back the error was gone...

Hard to restore the VM at VMware as the migration in XO broke the VM.
Updated to Centos 5.11 and halted it manually before migration and this time it can boot fine.

BUT cold migration still broke the VM on VMware.

Cold migration worked without errors

But it cannot boot - any idea?

I'm using NodeJS v18.19.1

How do you shutdown VM remote from XO if I should dig into if ESXI free is the problem?

Have updated XO and deleted failed VM import.

Trying import with cold migration.

I'll update again with the latest commits.

How do I force the import task to stop so I can remove the failed import and start over?

Could the problem be that I am using a VMware free for my test? Not sure if remote shutdown is supported.

XO from sources 2 days old - missing 12 commits.

Tried to shutdown VM at VMware host to see if it would continue after 2 hours.

As nothing happed I aborted import of VM, but task is still hanging in aborting.

Last part of raw log:

        {
          "id": "cytcdexn2q",
          "properties": {
            "name": "powering down source VM"
          },
          "start": 1708600049726,
          "status": "pending",
          "abortionRequestedAt": 1708607922243
        }
      ],
      "abortionRequestedAt": 1708607922242
    }

Hi,

Started an import of an old 9GB Centos 5.8 VM from VMware 6.7.0 update 3.

Not sure if it's doing anything - started it over an hour ago.
Servers are in same 1Gb switch.

Can raw log give any clue on what is going on?