This is quite an interesting issue. If you have confirmed that it works as intended via the web interface then I can only think of these possibilities:
The virt-clone command is stored somewhere that is not indicated on your $PATH variable.
The virt-clone command was saved under a different name.
The VMM uses an entirely different method to clone a VM.
Welp, I myself haven’t bothered trying to use ipfire for virtualization so I guess only the veterans/devs can properly answer this question. D:
EDIT: I thought of a possible solution. Try this: find / | grep clon
This will definitely find that virt-clone hiding somewhere or anything that has “clon” in it. Used “clon” instead of “clone” so that it will also match with “cloning”.
Thanks for the feedback and I have installed the Virt-Manager on a separate VM (Debian) and it works with that.
I was just a bit irritated that it doesn’t work with the command on the router.
Many thanks for the information.
So the virt-manager probably wouldn’t be bad, but then it would only be the commands and not an interface (like the VMM on my Debian VM), which isn’t so bad.