QCOW2: This does not look like a tar archive:

Please, describe the problem here and provide additional information below (if applicable) …

I have a qcow image that I am trying to spin up but keep getting this error: see logs below

Tue Nov 25 10:40:13 2025 [Z0][VM][I]: New state is CLONING
Tue Nov 25 10:44:40 2025 [Z0][VM][I]: New state is PENDING
Tue Nov 25 10:45:41 2025 [Z0][VM][I]: New state is ACTIVE
Tue Nov 25 10:45:41 2025 [Z0][VM][I]: New LCM state is PROLOG
oneadmin@opennebula-fe-oci:~/datastores/1$ tail -100 /var/log/one/91.log
Tue Nov 25 10:35:45 2025 [Z0][SCM][E]: Cannot dispatch VM: No host meets SCHED_REQUIREMENTS
Tue Nov 25 10:36:24 2025 [Z0][VM][I]: New state is ACTIVE
Tue Nov 25 10:36:24 2025 [Z0][VM][I]: New LCM state is PROLOG
Tue Nov 25 10:38:41 2025 [Z0][TrM][I]: Command execution failed (exit code: 2): /var/lib/one/remotes/tm/local/clone opennebula-fe-oci:/var/lib/one//datastores/1/1bc0e933b6ea6432433c42291f5c3e71 minipc-amd1:/var/lib/one//datastores/0/91/disk.0 91 1
Tue Nov 25 10:38:41 2025 [Z0][TrM][I]: clone: Cloning /var/lib/one/datastores/1/1bc0e933b6ea6432433c42291f5c3e71 to /var/lib/one/datastores/0/91/disk.0
Tue Nov 25 10:38:41 2025 [Z0][TrM][I]: copying opennebula-fe-oci:/var/lib/one/datastores/1/1bc0e933b6ea6432433c42291f5c3e71 to minipc-amd1:/var/lib/one/datastores/0/91/disk.0 from minipc-amd1 (format: qcow2)
Tue Nov 25 10:38:41 2025 [Z0][TrM][E]: clone: copying opennebula-fe-oci:/var/lib/one/datastores/1/1bc0e933b6ea6432433c42291f5c3e71 to minipc-amd1:/var/lib/one/datastores/0/91/disk.0 from minipc-amd1 (format: qcow2)
Tue Nov 25 10:38:41 2025 [Z0][TrM][E]: clone: [STDOUT] “~/datastores/0/91 ~\n”
\ntar: This does not look like a tar archive\ntar: Exiting with failure status due to previous errors\n": Connection timed out
Tue Nov 25 10:38:41 2025 [Z0][TrM][E]: Error executing image transfer script: copying opennebula-fe-oci:/var/lib/one/datastores/1/1bc0e933b6ea6432433c42291f5c3e71 to minipc-amd1:/var/lib/one/datastores/0/91/disk.0 from minipc-amd1 (format: qcow2)


Versions of the related components and OS (frontend, hypervisors, VMs):

Steps to reproduce:

Current results:

Expected results:

Hello,

This problem may arise when the hostname TEMPLATE.HOSTNAME is not correctly resolved.

If your installation have only a node, check the value for this command and check if in your /etc/hosts (or dns server) the IP is correctly resolved to this name

onehost list -j  | jq '.HOST_POOL.HOST |"\(.NAME) \(.TEMPLATE.HOSTNAME)"'

if your installation has more than a node, host is an array, so you should execute

onehost list -j  | jq '.HOST_POOL.HOST[] |"\(.NAME) \(.TEMPLATE.HOSTNAME)"'

Thanks!

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.