Hi Kevin Please make sure to use the systemvmtemplate for aarch64 when registering the systemvm template
https://download.cloudstack.org/systemvm/4.22/systemvmtemplate-4.22.0-aarch64-kvm.qcow2.bz2 The template type “SYSTEM” is good enough And the global settings are set correctly router.template.kvm >> systemvm template name system.vm.preferred.architecture >> is set to aarch64 system.vm.default.hypervisor >> is set to KVM Regards Kiran From: Kevin Humphreys <[email protected]> Date: Tuesday, 3 February 2026 at 5:59 PM To: [email protected] <[email protected]> Subject: [4.22.0] issue with launching VR on host that doesn't match management server architecture Hello, This is my first time on the mailing list, I think I have run into a bug with how system VM templates are handled when the management server isn't running the same architecture as the host. A brief overview of my setup: - 2 machines (1 management server, 1 host) - management server is x86_64, host is aarch64 (raspberry pi 5) running KVM I worked through the quickstart guide and got the management server up and the host connected into the zone created by the wizard. I waited for a bit, and saw the SystemVM templates had download for aarch64 as expected. Both secondarystoragevm and consoleproxy started and showed successfully connected. I then attempted to launch a VM in the default isolated guest network created. This errored out, with errors about being unable to contact Data Center 1. But the concerning one was "KVM won't support system vm" I wasn't able to find any mentions of aarch64 not being supported for the VR. After a bunch of failed attempts down rabbit holes about how I had configured my host, I then tried to play around with config settings. First thing I noticed was the preferred architecture for system VMs was x86_64. I tried changing that to aarch64 (even though I saw the other system VMs had started so I didn't think this would do anything and it didn't. What I eventually tried, that worked was downloading the system VM template again from https://docs.cloudstack.apache.org/en/latest/adminguide/systemvm.html and selecting the type of ROUTING. Once this downloaded, I changed the default router template name to the one I downloaded and everything started working. So I suspect somehow, someway, the automatically downloaded SYSTEM VM template is not being allowed to be used for the VR. This is my first time working with/configuring Cloudstack so I don't have a good visualization of how its supposed to look in a fresh working configuration. Is there an expectation to be both a downloaded template of type SYSTEM and type ROUTING or just SYSTEM? I am happy to provide more troubleshooting and reproduction steps if needed. I am not sure if I am just missing something or if this is a bug. Thanks, -- Kevin
