Cloudstack Issue while creating instance in arm based host

[arpanbht]

I have made a cluster which is arm based and trying to add nvidia jetson orin as a kvm host so its getting added to the management server and up and running.

But while creating a vm inside this host I am facing this kind of error

network/vnet/modifyvlan.sh -v 1460 -p -b br-1460 -o add ] failed. 
2026-03-23 17:07:12,207 WARN [kvm.resource.BridgeVifDriver] (AgentRequest-Handler-2:[]) (logid:3bdbe4c7) Process [18707] for command [/usr/share/cloudstack-common/scripts/vm/network/vnet/modifyvlan.sh -v 1460 -p -b br-1460 -o add ] encountered the error: [Cannot find device "br-1460"/usr/share/cloudstack-common/scripts/vm/network/vnet/modifyvlan.sh: line 37: /proc/sys/net/ipv6/conf/br-1460.1460/disable_ipv6: No such file or directoryCannot find device "br-1460.1460"Failed to create vlan 1460 on pif: br-1460.]. 
2026-03-23 17:07:12,211 WARN [resource.wrapper.LibvirtStartCommandWrapper] (AgentRequest-Handler-2:[]) (logid:3bdbe4c7) InternalErrorException com.cloud.exception.InternalErrorException: Failed to create vnet 1460: Cannot find device "br-1460"/usr/share/cloudstack-common/scripts/vm/network/vnet/modifyvlan.sh: line 37: /proc/sys/net/ipv6/conf/br-1460.1460/disable_ipv6: No such file or directoryCannot find device "br-1460.1460"
Failed to create vlan 1460 on pif: br-1460. at com.cloud.hypervisor.kvm.resource.BridgeVifDriver.createVnet(BridgeVifDriver.java:338) at com.cloud.hypervisor.kvm.resource.BridgeVifDriver.createVnetBr(BridgeVifDriver.java:320)
at com.cloud.hypervisor.kvm.resource.BridgeVifDriver.plug(BridgeVifDriver.java:239)
at com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.createVif(LibvirtComputingResource.java:3861)
at com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.createVifs(LibvirtComputingResource.java:3438)
at com.cloud.hypervisor.kvm.resource.wrapper.LibvirtStartCommandWrapper.execute(LibvirtStartCommandWrapper.java:86)
at com.cloud.hypervisor.kvm.resource.wrapper.LibvirtStartCommandWrapper.execute(LibvirtStartCommandWrapper.java:52)
at com.cloud.hypervisor.kvm.resource.wrapper.LibvirtRequestWrapper.execute(LibvirtRequestWrapper.java:78)
at com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.executeRequest(LibvirtComputingResource.java:2280)
at com.cloud.agent.Agent.processRequest(Agent.java:813)
at com.cloud.agent.Agent$AgentRequestHandler.doTask(Agent.java:1295)
at com.cloud.utils.nio.Task.call(Task.java:83) at com.cloud.utils.nio.Task.call(Task.java:29)
at java.base java.util.concurrent.FutureTask.run(FutureTask.java:264)
at java.base java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
at java.base java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
at java.base java.lang.Thread.run(Thread.java:829) 

what is this error coming while creating an instance in this host give me solution

What is the problem? Cannot understand the error log.

[wido]

I am not sure if this a ARM issue, but it's looking for a bridge with the name : br-1460 and that fails.

Are you sure this Agent is configured properly in the agent.properties?

[TheKunalSen]

yes we have configured the agent with cloudbr0 bridge which we have been doing with the x86 hosts, the normal instance making on the x86 is working peoperly but only for this arm based system we are facing this issue even we have added this host in a different cluster which is set to arm

[arpanbht]

Currently we are trying to access the nvidia jetson agx thor to onboard it on our cloudstack platform but we are still facing same kind of error

026-04-10 06:55:56,595 INFO  [kvm.storage.LibvirtStorageAdaptor] (AgentRequest-Handler-1:[]) (logid:27ed23ec) Trying to fetch storage pool a04d1dfc-8cf5-3db0-a2ef-37a92c1bcb9d from libvirt

2026-04-10 06:55:56,657 INFO  [kvm.resource.LibvirtConnection] (AgentRequest-Handler-3:[]) (logid:27ed23ec) No existing libvirtd connection found. Opening a new one

2026-04-10 06:55:56,659 WARN  [kvm.resource.LibvirtConnection] (AgentRequest-Handler-3:[]) (logid:27ed23ec) Can not find a connection for Instance i-2-2000-VM. Assuming the default connection.

2026-04-10 06:55:56,958 WARN  [kvm.resource.LibvirtKvmAgentHook] (AgentRequest-Handler-3:[]) (logid:27ed23ec) Groovy script '/etc/cloudstack/agent/hooks/libvirt-vm-state-change.groovy' is not available. Transformations will not be applied.

2026-04-10 06:55:56,958 WARN  [kvm.resource.LibvirtKvmAgentHook] (AgentRequest-Handler-3:[]) (logid:27ed23ec) Shell script '/etc/cloudstack/agent/hooks/libvirt-vm-state-change.sh' is not available. Transformations will not be applied.

2026-04-10 06:55:56,958 WARN  [kvm.resource.LibvirtKvmAgentHook] (AgentRequest-Handler-3:[]) (logid:27ed23ec) Groovy scripting engine is not initialized. Data transformation skipped.

2026-04-10 06:55:58,785 INFO  [kvm.storage.LibvirtStorageAdaptor] (AgentRequest-Handler-4:[]) (logid:ddaa535f) Trying to fetch storage pool a04d1dfc-8cf5-3db0-a2ef-37a92c1bcb9d from libvirt

2026-04-10 06:55:58,792 INFO  [kvm.storage.LibvirtStorageAdaptor] (AgentRequest-Handler-4:[]) (logid:ddaa535f) Asking libvirt to refresh storage pool a04d1dfc-8cf5-3db0-a2ef-37a92c1bcb9d

2026-04-10 06:57:19,565 INFO  [kvm.storage.LibvirtStorageAdaptor] (AgentRequest-Handler-1:[]) (logid:0d10c5a1) Trying to fetch storage pool a04d1dfc-8cf5-3db0-a2ef-37a92c1bcb9d from libvirt

2026-04-10 06:57:19,609 INFO  [kvm.storage.LibvirtStorageAdap

Can you guys give us any solution on how can we use these kind of devices like nvidia jetson orin, nvidia agx thor, or nvidia dgx spark to onboard them on cloudstack and use them for ml related works?

[vishesh92]

@arpanbht can you share DEBUG logs from the agent?

You also need to set the below configuration for arm64 hosts in agent.properties if not already done. You also need to use aarch64 systemvm template if there are only arm based hosts in the zone.

guest.cpu.arch=aarch64
guest.cpu.mode=host-passthrough
host.cpu.manual.speed.mhz=1500

[TheKunalSen]

@vishesh92

we do have arm based host and x86 under one zone and the arm one is on a different arm cluster and the systemvms are on a x86 host
sharing the logs

and we did the above changed you told

but still facing this error

2026-04-10 10:41:53,057 WARN  [utils.script.Script] (AgentRequest-Handler-3:[]) (logid:8ff3c5d3) Execution of process [55323] for command [/bin/bash -c ovftool --version ] failed.
2026-04-10 10:41:53,057 WARN  [utils.script.Script] (AgentRequest-Handler-3:[]) (logid:8ff3c5d3) Process [55323] for command [/bin/bash -c ovftool --version ] encountered the error: [127].
2026-04-10 10:41:53,118 INFO  [cloud.agent.Agent] (AgentRequest-Handler-4:[]) (logid:8ff3c5d3) Processing agent ready command, agent id = 10, uuid = fd9a752d-aacf-4de2-949b-3606493a10ae, name = iem10th
2026-04-10 10:41:53,124 INFO  [cloud.agent.Agent] (AgentRequest-Handler-4:[]) (logid:8ff3c5d3) Ready command is processed for agent [id: 10, uuid: fd9a752d-aacf-4de2-949b-3606493a10ae, name: iem10th]
2026-04-10 10:41:53,163 WARN  [utils.script.Script] (AgentRequest-Handler-4:[]) (logid:8ff3c5d3) Execution of process [55346] for command [/usr/bin/dpkg -l ovmf ] failed.
2026-04-10 10:41:53,163 WARN  [utils.script.Script] (AgentRequest-Handler-4:[]) (logid:8ff3c5d3) Process [55346] for command [/usr/bin/dpkg -l ovmf ] encountered the error: [1].
2026-04-10 10:41:53,166 WARN  [utils.script.Script] (AgentRequest-Handler-4:[]) (logid:8ff3c5d3) Execution of process [55347] for command [/bin/bash -c virt-v2v --version ] failed.
2026-04-10 10:41:53,166 WARN  [utils.script.Script] (AgentRequest-Handler-4:[]) (logid:8ff3c5d3) Process [55347] for command [/bin/bash -c virt-v2v --version ] encountered the error: [127].
2026-04-10 10:41:53,185 WARN  [utils.script.Script] (AgentRequest-Handler-4:[]) (logid:8ff3c5d3) Execution of process [55367] for command [/bin/bash -c ovftool --version ] failed.
2026-04-10 10:41:53,185 WARN  [utils.script.Script] (AgentRequest-Handler-4:[]) (logid:8ff3c5d3) Process [55367] for command [/bin/bash -c ovftool --version ] encountered the error: [127].
2026-04-10 10:42:33,682 INFO  [kvm.storage.LibvirtStorageAdaptor] (AgentRequest-Handler-2:[]) (logid:14bb74a2) Trying to fetch storage pool a04d1dfc-8cf5-3db0-a2ef-37a92c1bcb9d from libvirt
2026-04-10 10:42:33,694 INFO  [kvm.storage.LibvirtStorageAdaptor] (AgentRequest-Handler-2:[]) (logid:14bb74a2) Asking libvirt to refresh storage pool a04d1dfc-8cf5-3db0-a2ef-37a92c1bcb9d
2026-04-10 10:43:11,188 INFO  [kvm.storage.LibvirtStorageAdaptor] (AgentRequest-Handler-3:[]) (logid:89af079a) Trying to fetch storage pool a04d1dfc-8cf5-3db0-a2ef-37a92c1bcb9d from libvirt
2026-04-10 10:43:11,197 INFO  [kvm.storage.LibvirtStorageAdaptor] (AgentRequest-Handler-3:[]) (logid:89af079a) Trying to fetch storage pool a04d1dfc-8cf5-3db0-a2ef-37a92c1bcb9d from libvirt
2026-04-10 10:43:11,221 INFO  [kvm.storage.LibvirtStorageAdaptor] (AgentRequest-Handler-3:[]) (logid:89af079a) Creating volume 16f92b1f-2f42-44d1-884b-7125fb7318df from template 90b13352-c149-44be-ae2e-ea2b0d4e159d in pool a04d1dfc-8cf5-3db0-a2ef-37a92c1bcb9d (NetworkFilesystem) with size (2.20 GB) 2361393152
2026-04-10 10:43:11,222 INFO  [kvm.storage.LibvirtStorageAdaptor] (AgentRequest-Handler-3:[]) (logid:89af079a) Attempting to create volume 16f92b1f-2f42-44d1-884b-7125fb7318df (NetworkFilesystem) in pool a04d1dfc-8cf5-3db0-a2ef-37a92c1bcb9d with size (2.20 GB) 2361393152
2026-04-10 10:43:11,260 INFO  [kvm.storage.LibvirtStorageAdaptor] (AgentRequest-Handler-3:[]) (logid:89af079a) Creating volume [/mnt/a04d1dfc-8cf5-3db0-a2ef-37a92c1bcb9d/16f92b1f-2f42-44d1-884b-7125fb7318df] with backing file [/mnt/a04d1dfc-8cf5-3db0-a2ef-37a92c1bcb9d/90b13352-c149-44be-ae2e-ea2b0d4e159d] as the property [create.full.clone] is [false].
2026-04-10 10:43:11,571 INFO  [kvm.storage.LibvirtStorageAdaptor] (AgentRequest-Handler-4:[]) (logid:89af079a) Trying to fetch storage pool a04d1dfc-8cf5-3db0-a2ef-37a92c1bcb9d from libvirt
2026-04-10 10:43:11,626 INFO  [kvm.storage.LibvirtStorageAdaptor] (AgentRequest-Handler-4:[]) (logid:89af079a) Trying to fetch storage pool a04d1dfc-8cf5-3db0-a2ef-37a92c1bcb9d from libvirt
2026-04-10 10:43:11,659 WARN  [kvm.resource.BridgeVifDriver] (AgentRequest-Handler-4:[]) (logid:89af079a) Execution of process [55515] for command [/usr/share/cloudstack-common/scripts/vm/network/vnet/modifyvlan.sh -v 1644 -p  -b br-1644 -o add ] failed.
2026-04-10 10:43:11,659 WARN  [kvm.resource.BridgeVifDriver] (AgentRequest-Handler-4:[]) (logid:89af079a) Process [55515] for command [/usr/share/cloudstack-common/scripts/vm/network/vnet/modifyvlan.sh -v 1644 -p  -b br-1644 -o add ] encountered the error: [Cannot find device "br-1644"/usr/share/cloudstack-common/scripts/vm/network/vnet/modifyvlan.sh: line 37: /proc/sys/net/ipv6/conf/br-1644.1644/disable_ipv6: No such file or directoryCannot find device "br-1644.1644"Failed to create vlan 1644 on pif: br-1644.].
2026-04-10 10:43:11,661 WARN  [resource.wrapper.LibvirtStartCommandWrapper] (AgentRequest-Handler-4:[]) (logid:89af079a) InternalErrorException com.cloud.exception.InternalErrorException: Failed to create vnet 1644: Cannot find device "br-1644"/usr/share/cloudstack-common/scripts/vm/network/vnet/modifyvlan.sh: line 37: /proc/sys/net/ipv6/conf/br-1644.1644/disable_ipv6: No such file or directoryCannot find device "br-1644.1644"Failed to create vlan 1644 on pif: br-1644.
	at com.cloud.hypervisor.kvm.resource.BridgeVifDriver.createVnet(BridgeVifDriver.java:338)
	at com.cloud.hypervisor.kvm.resource.BridgeVifDriver.createVnetBr(BridgeVifDriver.java:320)
	at com.cloud.hypervisor.kvm.resource.BridgeVifDriver.plug(BridgeVifDriver.java:239)
	at com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.createVif(LibvirtComputingResource.java:3861)
	at com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.createVifs(LibvirtComputingResource.java:3438)
	at com.cloud.hypervisor.kvm.resource.wrapper.LibvirtStartCommandWrapper.execute(LibvirtStartCommandWrapper.java:86)
	at com.cloud.hypervisor.kvm.resource.wrapper.LibvirtStartCommandWrapper.execute(LibvirtStartCommandWrapper.java:52)
	at com.cloud.hypervisor.kvm.resource.wrapper.LibvirtRequestWrapper.execute(LibvirtRequestWrapper.java:78)
	at com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.executeRequest(LibvirtComputingResource.java:2280)
	at com.cloud.agent.Agent.processRequest(Agent.java:813)
	at com.cloud.agent.Agent$AgentRequestHandler.doTask(Agent.java:1295)
	at com.cloud.utils.nio.Task.call(Task.java:83)
	at com.cloud.utils.nio.Task.call(Task.java:29)
	at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
	at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
	at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
	at java.base/java.lang.Thread.run(Thread.java:829)

2026-04-10 10:43:11,663 INFO  [kvm.storage.LibvirtStorageAdaptor] (AgentRequest-Handler-4:[]) (logid:89af079a) Trying to fetch storage pool a04d1dfc-8cf5-3db0-a2ef-37a92c1bcb9d from libvirt
2026-04-10 10:43:11,728 INFO  [kvm.resource.LibvirtConnection] (AgentRequest-Handler-5:[]) (logid:89af079a) No existing libvirtd connection found. Opening a new one
2026-04-10 10:43:11,730 WARN  [kvm.resource.LibvirtConnection] (AgentRequest-Handler-5:[]) (logid:89af079a) Can not find a connection for Instance i-2-2002-VM. Assuming the default connection.
2026-04-10 10:43:12,061 WARN  [kvm.resource.LibvirtKvmAgentHook] (AgentRequest-Handler-5:[]) (logid:89af079a) Groovy script '/etc/cloudstack/agent/hooks/libvirt-vm-state-change.groovy' is not available. Transformations will not be applied.
2026-04-10 10:43:12,061 WARN  [kvm.resource.LibvirtKvmAgentHook] (AgentRequest-Handler-5:[]) (logid:89af079a) Shell script '/etc/cloudstack/agent/hooks/libvirt-vm-state-change.sh' is not available. Transformations will not be applied.
2026-04-10 10:43:12,061 WARN  [kvm.resource.LibvirtKvmAgentHook] (AgentRequest-Handler-5:[]) (logid:89af079a) Groovy scripting engine is not initialized. Data transformation skipped.

[vishesh92]

This is still the info logs.
This is most likely a network configuration issue.
You can check similar issues below which had a similar error:
#8810
#10884

[TheKunalSen]

@vishesh92

can you tell me how to check the debug log

[TheKunalSen]

@vishesh92

and also we did the exact same network configuration in our x86 machines