ARM64 ubuntu20.04 system, failed to auto create system vms.

[JimmyXC]

the error logs is:

management：
2025-07-14 10:25:12,700 DEBUG [c.c.d.DeploymentPlanningManagerImpl] (Work-Job-Executor-104:[ctx-3bf785c1, job-32830/job-32934, ctx-9561ed64]) (logid:0f1b8fc3) Trying to deploy VM [error decoding VM instance {"id":10968,"instanceName":"v-10968-VM","type":"ConsoleProxy","uuid":"658eb9a2-9dcf-47be-93e2-0ed40e15f057"}] and details: Plan [error decoding {"_clusterId":null,"_dcId":1,"_physicalNetworkId":null,"_podId":null,"_poolId":null,"migrationPlan":false}]; avoid list [{}] and planner: [].

agent：
2025-07-14 10:07:15,001 ERROR [utils.linux.KVMHostInfo] (Agent-Handler-1:[]) (logid:) Unable to retrieve the CPU speed from lscpu. java.lang.NullPointerException
2025-07-14 10:07:15,002 ERROR [utils.linux.KVMHostInfo] (Agent-Handler-1:[]) (logid:) Unable to retrieve the CPU speed from file [/sys/devices/system/cpu/cpu0/cpufreq/base_frequency] java.io.FileNotFoundException: /sys/devices/system/cpu/cpu0/cpufreq/base_frequency (no such files or dirs)
2025-07-14 10:07:17,196 ERROR [cloud.agent.Agent] (agentRequest-Handler-4:[]) (logid:b884d36c) Unexpected arch null, expected aarch64

[boring-cyborg]

Thanks for opening your first issue here! Be sure to follow the issue template!

[shwstppr]

@JimmyXC what version are you using?
Also, can you share details about your host and output of the following on it,

/usr/bin/arch

[JimmyXC]

@JimmyXC what version are you using? Also, can you share details about your host and output of the following on it,

/usr/bin/arch

@shwstppr
cloudstack version is :4.20.0.0

/usr/bin/arch output is
arrch64

the host info:
system: arm64 ubuntu20.04，kernel is 5.10 or 5.4.0
cpu: phytium s5000-c or

the error info is the same as both of the two envs

[DaanHoogland]

@JimmyXC , can you try with ubuntu 22.04 or 24.04?

[JimmyXC]

@JimmyXC , can you try with ubuntu 22.04 or 24.04?

@DaanHoogland
Does Cloudstack 4.20.0.0 not support Ubuntu 20.04？

[DaanHoogland]

It should but I hear ubuntu 20.04 on arm is not as well functioning as hypervisor.

[JimmyXC]

It should but I hear ubuntu 20.04 on arm is not as well functioning as hypervisor.

@DaanHoogland
Thank you, and i will try it.

[shwstppr]

@JimmyXC it is weird that when running manually you're getting correct result for /usr/bin/arch but it fails from the agent,

2025-07-14 10:07:17,196 ERROR [cloud.agent.Agent] (agentRequest-Handler-4:[]) (logid:b884d36c) Unexpected arch null, expected aarch64

Do try a newer Ubuntu version as Daan suggested, otherwise it would be good if you could share the agent logs with DEBUG enabled.

[JimmyXC]

@JimmyXC it is weird that when running manually you're getting correct result for /usr/bin/arch but it fails from the agent,

2025-07-14 10:07:17,196 ERROR [cloud.agent.Agent] (agentRequest-Handler-4:[]) (logid:b884d36c) Unexpected arch null, expected aarch64

Do try a newer Ubuntu version as Daan suggested, otherwise it would be good if you could share the agent logs with DEBUG enabled.

@shwstppr
Thanks, and i will accept Daan sugggested to try on ubuntu 24.04.2. If it's still reporting errors, i wiil upload the agent and management logs to you.

[shwstppr]

@JimmyXC you can replace jars on agent ormanagement server after maven build.
I don't remember any specific documentation for this but you can check,
https://github.com/shapeblue/hackerbook/blob/main/2-dev.md
https://github.com/shapeblue/mbx
https://github.com/shapeblue/mbx/blob/main/files/aliasrc#L43

[JimmyXC]

It should but I hear ubuntu 20.04 on arm is not as well functioning as hypervisor.

@shwstppr
@DaanHoogland
I updated the system to 24.04.2, but the errors still existed.

the agent error images:

the is the error logs file:

error_log.zip

[DaanHoogland]

@JimmyXC ,
You have a DB initialisation error. There are Spring and SQL exceptions from the start of your log, which usually means a DB configuration error.
Next, it looks like your systemvm template is the x86 version. I think an arm64 version is needed. It might be that x86 is just the default as nothing is loaded in the first place due to the errors above.

[JimmyXC]

@JimmyXC , You have a DB initialisation error. There are Spring and SQL exceptions from the start of your log, which usually means a DB configuration error. Next, it looks like your systemvm template is the x86 version. I think an arm64 version is needed. It might be that x86 is just the default as nothing is loaded in the first place due to the errors above.

@DaanHoogland
Yes, the problem lies in the architecture recognition issue. We confirmed that the uploaded template file is for arm64, but it seems that the code fails to recognize the current system's architecture and thus defaults to x86.

[DaanHoogland]

@JimmyXC , can you try #11254 it seems to be addressing a similar issue.

[shwstppr]

@JimmyXC also, can you please check and share what is the value of arch shown in the UI for the host or by listHosts API?