Encountered issues when attempting to bootstrap CloudStack with Proxmox
- Langage dominant
- Java
- Étoiles
- 3.1k
- Forks
- 1.4k
- Merge moyen
- 6 j 19 h
- PR mergées (30 j)
- 32
Description
### 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.
Guide de contribution
Ouvrir le guide de contribution
Piste de recherche
Commencez par l’assistant de création de zone et le comportement de sélection de l’hyperviseur décrit dans l’issue, puis retracez l’erreur d’orchestration de la VM système pour OVM dans les logs fournis. Consultez la documentation de CloudStack couvrant les hyperviseurs externes et les VM système. Le travail est considéré comme terminé lorsque l’assistant ne propose plus le choix d’hyperviseur primaire invalide et que la documentation explique clairement la configuration prise en charge.
Rédigé par le modèle d'indexation à partir du texte de l'issue.
Évaluation
- Stack technique
- java
- Domaine
- cloud, infrastructure
- Type d'issue
- Bug
- Difficulté
- 3/5
- Temps estimé
- 1-2 jours
- Activité
- À l'abandon
- Clarté
- Plutôt claire
- Accessibilité débutants
- 38/100