You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cloudstack.apache.org by Pradeep Cloudstack <pr...@yahoo.com> on 2014/04/14 11:13:35 UTC

Issue with multiple hypervisor in Cloudstack 4.2 

Hi,

I have a Cloustack 4.2 deployment. I created a Advanced zone and there I chose the Hypervisor type as KVM.

Later I created a cluster for XenServer hypervisor type and added a XenServer to it. Now I want to create a VM on the
XenServer from Cloudstack UI.

I created appropriate Host Tags and Compute Offerings. I now tried to create an Instance by choosing the Compute Offering relevant to XenServer. However the VM creation is failing.

When I look at the logs, I find that:
(1)deployVirtualMachine command is being invoked with hypervisor=KVM

(2)In the logs I see  - "Cluster: 2 has HyperVisorType that does not match the VM, skipping this cluster" meaning it is skipping the Xen cluster because the hypervisorType parameter has value as KVM

Any idea why is the hypervisorType being passed as KVM? How do I over come this?

-Pradeep

Re: Issue with multiple hypervisor in Cloudstack 4.2

Posted by Pradeep Cloudstack <pr...@yahoo.com>.
My bad; I was using wrong template (one that was meant for KVM)

-pradeep




________________________________
 From: Pradeep Cloudstack <pr...@yahoo.com>
To: "dev@cloudstack.apache.org" <de...@cloudstack.apache.org> 
Sent: Monday, April 14, 2014 2:43 PM
Subject: Issue with multiple hypervisor in Cloudstack 4.2 
 


Hi,

I have a Cloustack 4.2 deployment. I created a Advanced zone and there I chose the Hypervisor type as KVM.

Later I created a cluster for XenServer hypervisor type and added a XenServer to it. Now I want to create a VM on the
XenServer from Cloudstack UI.

I created appropriate Host Tags and Compute Offerings. I now tried to create an Instance by choosing the Compute Offering relevant to XenServer. However the VM creation is failing.

When I look at the logs, I find that:
(1)deployVirtualMachine command is being invoked with hypervisor=KVM

(2)In the logs I see  - "Cluster: 2 has HyperVisorType that does not match the VM, skipping this cluster" meaning it is skipping the Xen cluster because the hypervisorType parameter has value as KVM

Any idea why is the hypervisorType being passed as KVM? How do I over come this?

-Pradeep