Below is the issue as per logs for the systemVM's 2025-08-06 00:06:39,656 ERROR [c.c.u.FileUtil] (DirectAgent-452:[ctx-f3c410e8, 10.79.0.225, job-45/job-110, cmd: StartCommand]) (logid:557d5e35) Failed to scp files to system VM due to, No route to host 2025-08-06 00:06:39,657 ERROR [c.c.h.v.r.VmwareResource] (DirectAgent-452:[ctx-f3c410e8, 10.79.0.225, job-45/job-110, cmd: StartCommand]) (logid:557d5e35) Failed to scp files to system VM. Patching of systemVM failed com.cloud.utils.exception.CloudRuntimeException: Failed to scp files to system VM due to, No route to host at com.cloud.utils.FileUtil.scpPatchFiles(FileUtil.java:88) at com.cloud.hypervisor.vmware.resource.VmwareResource.execute(VmwareResource.java:2624)
1. Can you check if the management servers can reach the system VM IP's? As this is vmware the IP's will be the pod range defined. 2. If 1. is fine, From one of the screenshots uploaded I see that the systemVM console shows it as Loading ramdisk file.. Can you please confirm if they are booting fine and you can see login screen for the system VM's through the vmware console? If the VM's are stuck on the loading ramdisk file it could be issue with systemVm template or the OS type defined ( I see this set to other linux 64bit). Thanks Prashanth ________________________________ From: Kayo Henrique <kayo.henri...@onexdatacenter.com.br> Sent: Wednesday, August 6, 2025 6:44 PM To: users@cloudstack.apache.org <users@cloudstack.apache.org> Subject: Re: SYSTEM VMS DOES NOT BOOT - SYSTEM VMS NÃO BOOTAM *IN ENGLISH* Hello, Sorry. I added the entire management server log file this time. https://drive.onexdatacenter.com.br/s/gRreLjZ4bg5KPHM // *EM PORTUGUÊS* Olá, Me desculpe. Adicionei o arquivo de logs inteiro do management server dessa vez. https://drive.onexdatacenter.com.br/s/gRreLjZ4bg5KPHM Em 2025-08-06 12:10, Prashanth Reddy escreveu: > Hi, > > The logs uploaded covers only 3 minutes of timeframe. I has logs > related to SSVM (s-28-VM) being in starting state but has no logs > related to what is causing the failure. > > Can you provide access to complete management-server.log from all your > management servers? > > > > ________________________________ > From: Kayo Henrique <kayo.henri...@onexdatacenter.com.br> > Sent: Wednesday, August 6, 2025 2:44 PM > To: users@cloudstack.apache.org <users@cloudstack.apache.org> > Subject: Re: SYSTEM VMS DOES NOT BOOT - SYSTEM VMS NÃO BOOTAM > > *IN ENGLISH* > > Hello, > > Below is the link with image evidence of our environment's status. > > https://drive.onexdatacenter.com.br/s/gRreLjZ4bg5KPHM > > In addition to the images, I've also included a file with the logs from > /var/log/cloudstack/management/management-server.log. > > The System VM template appears to be "ok," unlike another CentOS > template in the same location. > > The allocation state in the zone, pod, and cluster is active! > > // > > *EM PORTUGUÊS* > > Olá, > > Segue abaixo o link com as evidências em imagem dos status de nosso > ambiente. > > https://drive.onexdatacenter.com.br/s/gRreLjZ4bg5KPHM > > Além das imagens, incluí também um arquivo com os logs de > /var/log/cloudstack/management/management-server.log. > > O template da System VM parece estar "ok", diferente de um outro > template do CentOS presente no mesmo local. > > O allocation state na zona, pod e cluster está ativo! > > > > > > Em 2025-08-06 05:56, Prashanth Reddy escreveu: >> Hello Kayo, >> >>>> I noticed that my Primary Storage is being read and its size is >>>> recognized by CloudStack (as well as the amount in use), but the >>>> Secondary Storage is not... (I don't know if this is normal). >> >> This is expected if the SSVM is not up >> >> Unfortunately attachments doesn't make through mailing list. Can you >> post a link to the screenshots shared. >> >> As your SystemVM's are not running , please check the following >> >> >> 1. >> >> >> 1. >> Please check the status of the "SystemVM Template" status under Images >> --> Templates in GUI. The state of the template should be Ready, if >> not this needs to be fixed. >> 2. >> If the state of the template is ready, Check the state of the host >> itself to make sure its UP. Also check if zone, pod and cluster has >> allocation state Enabled >> >> If you cannot find any issue with the above , please share a link to >> the management server logs from the affected environment >> >> Thanks >> Prashanth >> >> >> >> >> >> >> ________________________________ >> From: Kayo Henrique <kayo.henri...@onexdatacenter.com.br> >> Sent: Tuesday, August 5, 2025 7:08 PM >> To: users@cloudstack.apache.org <users@cloudstack.apache.org> >> Subject: SYSTEM VMS DOES NOT BOOT - SYSTEM VMS NÃO BOOTAM >> >> *IN ENGLISH* >> >> Hello, >> >> I recently installed CloudStack on bare metal and am using it with >> vSphere. >> >> I configured the first zone, pod, cluster, networks, primary storage, >> and secondary storage. >> >> I used a TrueNAS server to provide the Secondary Storage NFS pool. >> >> Everything seemed to go well. My cluster hosts are being read >> normally, >> and their VMs are being recognized (but not yet managed) by >> CloudStack. >> >> I noticed that my Primary Storage is being read and its size is >> recognized by CloudStack (as well as the amount in use), but the >> Secondary Storage is not... (I don't know if this is normal). >> >> Anyway, my problem is that when I start the zone, CloudStack generates >> the two System VMs (CPVM and SSVM), but they don't start (they don't >> boot). >> >> I seeded the System VM template normally, and so far the template >> appears in the NFS pool (looking directly at vCenter). >> >> Attached are the images! >> >> // >> >> *EM PORTUGUÊS* >> >> Olá, >> >> Instalei recentemente o CloudStack em um baremetal, e estou utilizando >> ele com vSphere. >> >> Configurei a primeira zona, pod, cluster, redes, primary storage e >> secondary storage. >> >> Utilizei um servidor TrueNAS para fornecer o pool NFS da Secondary >> Storage. >> >> Aparentemente correu tudo bem no processo. Meus hosts do cluster estão >> sendo lidos normalmente, assim como as VMs deles estão sendo >> reconhecidas (mas ainda não gerenciadas) pelo CloudStack. >> >> Notei que meu Primary Storage está sendo lido e o tamanho é >> reconhecido >> pelo CloudStack (assim como quantidade em uso), mas o Secondary >> Storage >> não... (não sei se é normal). >> >> Enfim, meu problema é que quando inicio a zona, o CloudStack gera as 2 >> System VMs (CPVM e SSVM), mas elas não iniciam (não dão boot). >> >> Eu fiz o seed do template das System VMs normalmente e até então o >> template consta dentro do pool NFS (olhando diretamente pelo vCenter). >> >> Seguem imagens em anexo! >> >> -- >> Atenciosamente, >> Kayo Henrique >> Analista de Infraestrutura e Redes >> OneX Data Centers > > -- > Kayo Henrique > Analista de Infraestrutura e Redes > OneX Data Centers -- Kayo Henrique Analista de Infraestrutura e Redes OneX Data Centers
