Fusion 12 Professional: vmrun clone fails

[MagNJ]

The following command works fine in VMware Fusion 11 Pro but fails in 12 Pro (evaluation copy):

$ vmrun clone /Volumes/Users/user1/Documents/Virtual\ Machines.localized/testvm.vmwarevm/testvm.vmx /Volumes/Users/user1/Documents/Virtual\ Machines.localized/testvm-clone.vmwarevm/testvm.vmx full -snapshot=Snapshot-2020-10-06

Error: One of the parameters was invalid

$ vmrun listSnapshots /Volumes/Users/user1/Documents/Virtual\ Machines.localized/testvm.vmwarevm/testvm.vmx

Total snapshots: 1

Snapshot-2020-10-06

According to vmrun help there seems to be nothing different between 11 Pro and 12 Pro:

clone                    Path to vmx file     Create a copy of the VM

                         Path to destination vmx file

                         full|linked

                         [-snapshot=Snapshot Name]

                         [-cloneName=Name]

[MagNJ]

Any ideas?

[Mikero]

I'm seeing something similar, investigating with engineering...

[MagNJ]

Thanks! Does it seem to happen in the registered version too or just in evaluation mode?

Also tested on a newly installed Mac with Catalina 10.15.7 (19H2) and with same behavior

$ vmrun clone /Users/user1/Virtual\ Machines.localized/testvm.vmwarevm/testvm.vmx /Users/user1/Virtual\ Machines.localized/testvm-clone.vmwarevm/testvm.vmx full -snapshot=Snapshot-2020-10-13

Error: One of the parameters was invalid

$ vmrun listSnapshots /Users/user1/Virtual\ Machines.localized/testvm.vmwarevm/testvm.vmx

Total snapshots: 1

Snapshot-2020-10-13

[MagNJ]

Any updates on this? I am not buying a license until this has been resolved....And seems like I cannot submit a bug report without a license, catch 22 - really clever!!!

[Mikero]

Still investigating. I'm seeing it succeed in Big Sur but fail on Catalina, so we're digging in.

[wila]

FYI, if you had not noticed it, that's the Fusion Product Manager who answered your question and he already took it to the engineers working on this.

Opening a ticket / bugreport won't help, I"m pretty sure he already opened some tickets for this internally.

--

Wil