GitHub user sptest232 added a comment to the discussion: Failed to create VPC
on KVM ACS 4.22
Thank you for your reply!
Yes, if I change system.vm.default.hypervisor to KVM, the VPC is created in the
KVM cluster, but when I try to create a VCP or anIsolated Network in the Xen
cluster, I get an error.
I think the problem is only with VPC when using clusters with different
hypervisors at the same time, because when the setting
system.vm.default.hypervisor = "" I can create an isolated network in both
clusters, a VCP - only on XEN cluster, but when system.vm.default.hypervisor =
"KVM" I can create a VPC and an isolated network only in the KVM cluster.
Allocating the VR with id=27 in datacenter Zone {"id": "1", "name":
"lab-zone1", "uuid": "c585cadf-a5e4-48e5-9e9a-6ef29dd103b1"} with the
hypervisor type KVM
Adding cluster [Cluster {id: "1", name: "lab-xcp-cluster1", uuid:
"38378f29-ec54-46cf-8978-d48881b764ee"}] to the avoid set because the cluster's
hypervisor [XenServer] does not match the VM [VM instance
{"id":27,"instanceName":"r-27-VM","state":"Starting","type":"DomainRouter","uuid":"23a108a2-84f3-450f-8398-0903df7151c2"}]
hypervisor: [KVM]. Skipping this cluster.
GitHub link:
https://github.com/apache/cloudstack/discussions/12315#discussioncomment-15315256
----
This is an automatically sent email for [email protected].
To unsubscribe, please send an email to: [email protected]
