Encountered issues when attempting to bootstrap CloudStack with Proxmox
- Lenguaje dominante
- Java
- Estrellas
- 3.1k
- Forks
- 1.4k
- Merge medio
- 6 d 19 h
- PR fusionados (30 d)
- 32
Descripción
### problem
### Discussed in https://github.com/apache/cloudstack/discussions/12273
Originally posted by **ShadowJonathan** December 16, 2025
Here are a few things I encountered while attempting to install/add Proxmox to cloudstack;
I then attempted to install a new zone, with the following zone-wide settings:
I could only select "external", not proxmox or the likes.
I realise the zone was disabled, enable it, and recreate the VM, which gets me this error:
Looking at the logs, it gives me this:
```
2025-12-16 18:18:29,159 ERROR [c.c.v.ClusteredVirtualMachineManagerImpl] (Work-Job-Executor-10:[ctx-ca2a9424, job-49/job-51, ctx-8cb0346d]) (logid:ce949871) Unable to orchestrate start VM instance {"id":3,"instanceName":"i-2-3VM","state":"Stopped","type":"User","uuid":"53f4a94c-3124-4368-952e-7da10c9f472f"} due to [Cannot find an available cluster in Pod 2 to start domain router for Ovm.
Ovm won't support any system vm including domain router, please make sure you have a cluster with hypervisor type of any of xenserver/KVM/Vmware in the same pod with Ovm cluster. And there is at least one host in UP status in that cluster.].
```
### versions
The versions of ACS, hypervisors, storage, network etc..
### The steps to reproduce the bug
1.
2.
3.
...
### What to do about it?
'External' as a hypervisor option should not be shown in the Zone creation wizard, as a primary hypervisor (kvm, vmware and xenserver) to run the systemvms.
Also update the documentation if it is not clear enough.
Guía de contribución
Línea de trabajo
Comienza con el asistente de creación de zonas y el comportamiento de selección del hipervisor descrito en el issue; después, rastrea el error de orquestación de la VM del sistema para OVM en los logs proporcionados. Revisa la documentación de CloudStack sobre hipervisores externos y VMs del sistema. Se considera terminado cuando el asistente ya no ofrece la opción de hipervisor primario no válida y la documentación explica claramente la configuración compatible.
Escrito por el modelo de indexación a partir del texto del issue.
Evaluación
- Stack tecnológico
- java
- Área
- cloud, infrastructure
- Tipo de issue
- Error
- Dificultad
- 3/5
- Tiempo estimado
- 1-2 días
- Estado de actividad
- Estancado
- Claridad
- Bastante claro
- Aptitud para principiantes
- 38/100