Inconsistent right-click clone options

I'm seeing inconsistent behaviour regarding the right-click menu and the option to create new clones/linked-clones

Windows 11
I have snapshots already. The right-click menu does not allow me to create a clone or a linked clone.
I can navigate to my existing snapshots and create a linked clone from there (but not a full clone)

MacOS 13
The right-click menu presents no options to create any kind of clone. This is a known limitation, fine.

Fedora 38 (ARM)
I have no snapshots already. The right-click menu allows me to create a clone or a linked clone. Expected behaviour.

Fedora 39 (ARM)
I have snapshots already. The right-click menu does not allow me to create a clone or a linked clone.
I can navigate to my existing snapshots and create a linked clone from there (but not a full clone)


So it seems that, having no snapshots allows me to create either a clone or a linked clone from the right-click menu.. while having snapshots already means I can only create a linked clone, and only from the manage snapshots view.

This may all be by design, and not preventing me from doing what I need to do, but seems the UI could be improved in this regard.

 

Hmm.. well.. I don't much care for this..
This is the first time I actually tried to create a clone (linked or otherwise).. it's been sitting here for 10 minutes not doing much, but my macbook is certainly warming up with the VM itself running hot.

Given the lack of progress bar, it might be safe to assume this isn't going to finish and the VM is frekaing out.




What's more.. cancelling the operation reveals a rather telling dialog that was not previously visible:


So, that makes sense.. but there are some usability issues here.

1. Any attempt to create a linked clone should inform the user that the guest needs to be shut down first (if not already)
2. The "Creating a linked clone" progress bar should not show up at all in this scenario, and certainly it should not obscure the "Unable to perform the action because ... ..."
3. In this scenario, there's no reason for the guest VM to be burning on all cores while it waits for me to realise what is (not) happening and cancel the operation. (For the record, cancelling this non-operation allowed all cores to go back to normal)


If there is a better place to log bug reports, please advise.

 

Ahh, I discovered the inconsistency in the first post (right-click menu).. It would seem to be context sensitive to wether the VM is actually running or not (while bieng able to create clones from the "snapshot manager" is not sensitive to the current VM state

 

Hello Tim!
Thanks for sharing this.
I was able to replicate the issue by opening the 'Manage snapshots' window and clicking 'New Linked clone' when the VM is running/suspended/paused.
As for the context menu (right-click the VM name in Control Center), the options aren't offered when the VM state is not 'shut down', so the behaviour is correct.

I'll report this issue to our Engineering team. Appreciate you sharing this feedback with us

 

Wonderful, thank you.