Which statement about creating templates in FusionCompute is incorrect?

Turning a running VM into a template is a valid operation in FusionCompute. This means that it is indeed possible to create a template from a VM that is actively running. The process typically involves capturing the current state of the VM, including its configurations and data, without necessitating the shutdown of the VM. This characteristic allows for flexibility and efficiency in resource management, especially in environments where uptime is crucial.

Selecting a running VM to create a template ensures that the template reflects the most current state and configuration of the VM. Templates created in this way can be used to rapidly deploy new VMs with the same configurations, which is advantageous for scaling applications or services.

The other statements contain implications that involve actions that are either not accurate or misrepresent the effects of those actions in the context of FusionCompute. For instance, converting a VM directly into a template typically does not preserve the original VM, and cloning operations may also need to be correctly understood in terms of whether they affect the original resources.