cloudstack-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Abhinav Roy <abhinav....@citrix.com>
Subject RE: XenServer + New Guest Network = unable to create vm
Date Fri, 13 Jun 2014 06:21:43 GMT
Hi Andrei,

In your setup you have 2 clusters.

Cluster1 - KVM : a default centos template for KVM also should be downloaded when u added
the host  or you can register a template for XEN
Cluster2 - XEN :  a default centos  template for XEN also should be downloaded when you added
the host or you can register a template for KVM

Now, if you choose the template for XEN, it will always deploy the VM on XEN cluster only
and if doesn't find hosts or primary storages with enough capacity in that cluster it will
fail. Similarly for KVM.
(So, actually there is no need for any custom service or disk offerings)

Now, if you have created a custom service offering and disk offering. There are 2 types of
tags there.

Host tags : If you have some host tag in your service/disk offering then have the same tag
on the host on which you want the deployment to happen.  ( If you use service offering with
host tags for deployment it will only deploy on the host which has tags. If hosts with tags
are not present deployment  will fail)
Storage tags : If you have a storage tag in your service/disk offering then have the same
tag on the primary storage on which you want the deployment to happen (If you use service
offering with storage tags for deployment it will only deploy on the storage which has tags.
If storage with tags are not present deployment  will fail )

This is the actual behavior.

And to your question :  - when I create a new instance on a particular hypervisor with a new
network offering, does ACS automatically attempt to create a virtual router on the same hypervisor
type as the instance, or does it randomly chooses what host to launch the virtual router?

------------------------ It randomly choses any host to deploy the virtual router when you
create a new network. So, if during instance creation , you want to create a new network too,
it need not deploy the VR on the same host you want to deploy the VM.

Thanks and regards,
Abhinav

-----Original Message-----
From: Andrei Mikhailovsky [mailto:andrei@arhont.com] 
Sent: Thursday, June 12, 2014 6:12 PM
To: users@cloudstack.apache.org
Subject: Re: XenServer + New Guest Network = unable to create vm

Tim, 

thanks for your answer. 

Regarding the templates, I did upload both xenserver and kvm system vm templates during the
initial cloud install (version 4.1) and during consequent upgrades to 4.2.0 and 4.2.1. Both
kvm and xenserver templates are visible under the Templates menu and I have also changed the
global settings variable to point the xenserver template to the right systemvm template version.


The reason why i've create separate offering for XenServer and used tagging is I wanted to
have a separate vm offering, so that the end user could choose which hypervisor he/she wishesh
to use. 

Regarding the MidoNet - first time I am hearing about this and I am certainly not using it
on my network. I am not sure where ACS got this and why it is trying to use it for the XenServer
vms. In addition to that I am not sure why I do not experience any problems with creating
vms if I pre-create a network before using the Add Instance wizard. 

A question - when I create a new instance on a particular hypervisor with a new network offering,
does ACS automatically attemp to create a virtual router on the same hypervisor type as the
instance, or does it randomly chooses what host to launch the virtual router? 

Cheers 

Andrei 

----- Original Message -----

From: "Tim Mackey" <tmackey@gmail.com>
To: users@cloudstack.apache.org
Sent: Wednesday, 11 June, 2014 7:25:07 PM
Subject: Re: XenServer + New Guest Network = unable to create vm 

Andrei, 

When I created a cloud with XenServer, vSphere and KVM, I didn't need create any new service
offerings, nor did I need to tag them. Template compatibility should take care of that automatically.
What you haven't said is if you uploaded the XenServer system VM template or not. Since you
already have a KVM installation, your system VMs are currently KVM based, but the router you
need for the XenServer environment needs to be a XenServer system VM. Additionally, in a multi-hypervisor
environment, if a system VM needs to restart it could restart on any host, so you'll again
need to have both KVM and XenServer system VM templates or force the system VM to be on a
specific hypervisor type in the config variables. 

The error in your log which did catch my eye is that you appear to be using MidoNet and that's
KVM only. MidoKura isn't something I've had an opportunity to work with, so I'm not certain
what might be required to connect a MidoNet to a normal network. 

If the XenServer hosts aren't in a separate zone, you might want to look into putting them
there. afaik that should at least remove Mido from the mix. 

-tim 



On Wed, Jun 11, 2014 at 11:40 AM, Andrei Mikhailovsky <andrei@arhont.com>
wrote: 

> Hello guys,
> 
> Was wondering if someone could help me with a strange issue that I am 
> having with XenServer 6.2 and ACS 4.2.1.
> 
> I've recently added a new XenServer 6.2 cluster to my existing ACS + 
> KVM setup.I've created a new system and disk offerings using tag "xenserver".
> I've also added this tag to the xenserver host and the nfs primary storage. 
> I have verified that the setup works by successfully creating and 
> staring several vms which are connected to an existing ACS guest 
> network that I have setup for testing. All test vms are being created 
> and started and I can successfully login to them.
> 
> Having said this, I am, however, unable to create any guest vms on the 
> XenServer if I choose to create a new guest network from the Add 
> Instance wizard. The guest vm is created with status Error and the 
> management server logs show the error that I am pasting at the end of 
> this email. From what I can see, the new network is created with 
> status Allocated and I can see it under the Network section. I do not, 
> however, see a virtual router corresponding to that network.
> 
> From the management server log I can see the following, which looks 
> very odd and completely untrue (as I can successfully create a number 
> of vms using the same system and disk offering using a pre-created guest network.
> I've double checked that the XenServer host has the tag "xenserver"): 
> 
> 2014-06-11 16:16:25,312 DEBUG [allocator.impl.FirstFitAllocator]
> (Job-Executor-76:job-5195 = [ 10d345f9-2fb2-42ef-850f-4919512d63db ]
> FirstFitRoutingAllocator) Looking for hosts having tag specified on 
> SvcOffering:xenserver
> 2014-06-11 16:16:25,314 DEBUG [allocator.impl.FirstFitAllocator]
> (Job-Executor-76:job-5195 = [ 10d345f9-2fb2-42ef-850f-4919512d63db ]
> FirstFitRoutingAllocator) Hosts with tag 'xenserver' are:[]
> 
> 
> Any idea what is going on? 
> 
> Management Server Log: 
> 
> 2014-06-11 16:16:24,962 DEBUG [cloud.api.ApiServlet]
> (catalina-exec-6:null) ===START=== 192.168.169.91 -- GET 
> command=createNetwork&response=json&se
> 
> ssionkey=6q8QippP1uE3Jd%2BWL8FuA9xcTfM%3D&networkOfferingId=87e090cb-a
> 134-4d77-b664-ef3858a52f3c&name=XenServer-Network-Test-3&displayText=X
> enServer-N
> etwork-Test-3&zoneId=b8c25216-4c2d-4d01-87d8-3673c0ba9780&_=1402499785
> 135
> 2014-06-11 16:16:25,015 DEBUG [network.guru.NiciraNvpGuestNetworkGuru]
> (catalina-exec-6:null) Refusing to design this network
> 2014-06-11 16:16:25,015 DEBUG [network.guru.MidoNetGuestNetworkGuru]
> (catalina-exec-6:null) design called
> 2014-06-11 16:16:25,016 DEBUG [network.guru.MidoNetGuestNetworkGuru]
> (catalina-exec-6:null) Refusing to design this network, the physical 
> isolation ty pe is not MIDO
> 2014-06-11 16:16:25,017 DEBUG [network.guru.SspGuestNetworkGuru]
> (catalina-exec-6:null) SSP not configured to be active
> 2014-06-11 16:16:25,017 DEBUG [cloud.network.NetworkManagerImpl]
> (catalina-exec-6:null) Releasing lock for 
> Acct[06eedc2c-65f2-11e3-9bd1-d8d38559b2d0-a
> dmin]
> 2014-06-11 16:16:25,039 DEBUG [cloud.api.ApiServlet]
> (catalina-exec-6:null) ===END=== 192.168.169.91 -- GET 
> command=createNetwork&response=json&sess
> 
> ionkey=6q8QippP1uE3Jd%2BWL8FuA9xcTfM%3D&networkOfferingId=87e090cb-a13
> 4-4d77-b664-ef3858a52f3c&name=XenServer-Network-Test-3&displayText=Xen
> Server-Net
> work-Test-3&zoneId=b8c25216-4c2d-4d01-87d8-3673c0ba9780&_=140249978513
> 5
> 2014-06-11 16:16:25,133 DEBUG [cloud.api.ApiServlet]
> (catalina-exec-7:null) ===START=== 192.168.169.91 -- GET
> command=deployVirtualMachine&zoneId=b8c25216-4c2d-4d01-87d8-3673c0ba97
> 80&templateId=677c5335-7224-4ce7-b5e9-da70e89a6f99&hypervisor=KVM&serv
> iceOfferingId=62f076eb-fbae-485d-aa78-e7e4c9717346&diskOfferingId=cbc5
> 779b-7de3-4f6b-90d0-304029f59364&size=10&networkIds=48c669d0-0e41-40b3
> -be7d-b6078ff98cff&displayname=ubuntu-xen-test-4&name=ubuntu-xen-test-
> 4&response=json&sessionkey=6q8QippP1uE3Jd%2BWL8FuA9xcTfM%3D&_=14024997
> 85306
> 2014-06-11 16:16:25,140 DEBUG [cloud.api.ApiDispatcher]
> (catalina-exec-7:null) InfrastructureEntity name 
> is:com.cloud.offering.ServiceOffering
> 2014-06-11 16:16:25,142 DEBUG [cloud.api.ApiDispatcher]
> (catalina-exec-7:null) ControlledEntity name 
> is:com.cloud.template.VirtualMachineTemplate
> 2014-06-11 16:16:25,144 DEBUG [cloud.api.ApiDispatcher]
> (catalina-exec-7:null) ControlledEntity name 
> is:com.cloud.network.Network
> 2014-06-11 16:16:25,148 DEBUG [cloud.api.ApiDispatcher]
> (catalina-exec-7:null) InfrastructureEntity name 
> is:com.cloud.offering.DiskOffering
> 2014-06-11 16:16:25,157 DEBUG [cloud.network.NetworkModelImpl]
> (catalina-exec-7:null) Service SecurityGroup is not supported in the 
> network id=279
> 2014-06-11 16:16:25,168 DEBUG [cloud.vm.UserVmManagerImpl]
> (catalina-exec-7:null) Allocating in the DB for vm
> 2014-06-11 16:16:25,178 DEBUG [cloud.vm.VirtualMachineManagerImpl]
> (catalina-exec-7:null) Allocating entries for VM: 
> VM[User|ubuntu-xen-test-4]
> 2014-06-11 16:16:25,178 DEBUG [cloud.vm.VirtualMachineManagerImpl]
> (catalina-exec-7:null) Allocating nics for VM[User|ubuntu-xen-test-4]
> 2014-06-11 16:16:25,179 DEBUG [cloud.network.NetworkManagerImpl]
> (catalina-exec-7:null) Allocating nic for vm 
> VM[User|ubuntu-xen-test-4] in network Ntwk[279|Guest|8] with requested 
> profile NicProfile[0-0-null-null-null
> 2014-06-11 16:16:25,190 DEBUG [cloud.network.NetworkModelImpl]
> (catalina-exec-7:null) Service SecurityGroup is not supported in the 
> network id=279
> 2014-06-11 16:16:25,191 DEBUG [cloud.vm.VirtualMachineManagerImpl]
> (catalina-exec-7:null) Allocating disks for VM[User|ubuntu-xen-test-4]
> 2014-06-11 16:16:25,199 DEBUG [cloud.vm.VirtualMachineManagerImpl]
> (catalina-exec-7:null) Allocation completed for VM: 
> VM[User|ubuntu-xen-test-4]
> 2014-06-11 16:16:25,199 DEBUG [cloud.vm.UserVmManagerImpl]
> (catalina-exec-7:null) Successfully allocated DB entry for 
> VM[User|ubuntu-xen-test-4]
> 2014-06-11 16:16:25,217 DEBUG [cloud.network.NetworkModelImpl]
> (catalina-exec-7:null) Service SecurityGroup is not supported in the 
> network id=279
> 2014-06-11 16:16:25,219 DEBUG [cloud.network.NetworkModelImpl]
> (catalina-exec-7:null) Service SecurityGroup is not supported in the 
> network id=279
> 2014-06-11 16:16:25,231 DEBUG [cloud.async.AsyncJobManagerImpl]
> (catalina-exec-7:null) submit async job-5195 = [ 
> 10d345f9-2fb2-42ef-850f-4919512d63db ], details: AsyncJobVO {id:5195,
> userId: 3, accountId: 2, sessionKey: null, instanceType: 
> VirtualMachine,
> instanceId: 838, cmd: 
> org.apache.cloudstack.api.command.user.vm.DeployVMCmd, cmdOriginator: 
> null,
> cmdInfo: 
> {"sessionkey":"6q8QippP1uE3Jd+WL8FuA9xcTfM\u003d","cmdEventType":"VM.C
> REATE","ctxUserId":"3","serviceOfferingId":"62f076eb-fbae-485d-aa78-e7
> e4c9717346","httpmethod":"GET","size":"10","zoneId":"b8c25216-4c2d-4d0
> 1-87d8-3673c0ba9780","id":"838","response":"json","templateId":"677c53
> 35-7224-4ce7-b5e9-da70e89a6f99","networkIds":"48c669d0-0e41-40b3-be7d-
> b6078ff98cff","hypervisor":"KVM","name":"ubuntu-xen-test-4","diskOffer
> ingId":"cbc5779b-7de3-4f6b-90d0-304029f59364","_":"1402499785306","ctx
> AccountId":"2","ctxStartEventId":"16816","displayname":"ubuntu-xen-tes
> t-4"},
> cmdVersion: 0, callbackType: 0, callbackAddress: null, status: 0,
> processStatus: 0, resultCode: 0, result: null, initMsid: 
> 115129173025114,
> completeMsid: null, lastUpdated: null, lastPolled: null, created: 
> null}
> 2014-06-11 16:16:25,239 DEBUG [cloud.async.AsyncJobManagerImpl]
> (Job-Executor-76:job-5195 = [ 10d345f9-2fb2-42ef-850f-4919512d63db ]) 
> Executing org.apache.cloudstack.api.command.user.vm.DeployVMCmd for
> job-5195 = [ 10d345f9-2fb2-42ef-850f-4919512d63db ]
> 2014-06-11 16:16:25,240 DEBUG [cloud.api.ApiServlet]
> (catalina-exec-7:null) ===END=== 192.168.169.91 -- GET
> command=deployVirtualMachine&zoneId=b8c25216-4c2d-4d01-87d8-3673c0ba97
> 80&templateId=677c5335-7224-4ce7-b5e9-da70e89a6f99&hypervisor=KVM&serv
> iceOfferingId=62f076eb-fbae-485d-aa78-e7e4c9717346&diskOfferingId=cbc5
> 779b-7de3-4f6b-90d0-304029f59364&size=10&networkIds=48c669d0-0e41-40b3
> -be7d-b6078ff98cff&displayname=ubuntu-xen-test-4&name=ubuntu-xen-test-
> 4&response=json&sessionkey=6q8QippP1uE3Jd%2BWL8FuA9xcTfM%3D&_=14024997
> 85306
> 2014-06-11 16:16:25,245 DEBUG [cloud.api.ApiDispatcher]
> (Job-Executor-76:job-5195 = [ 10d345f9-2fb2-42ef-850f-4919512d63db ]) 
> InfrastructureEntity name is:com.cloud.offering.ServiceOffering
> 2014-06-11 16:16:25,248 DEBUG [cloud.api.ApiDispatcher]
> (Job-Executor-76:job-5195 = [ 10d345f9-2fb2-42ef-850f-4919512d63db ]) 
> ControlledEntity name is:com.cloud.template.VirtualMachineTemplate
> 2014-06-11 16:16:25,251 DEBUG [cloud.api.ApiDispatcher]
> (Job-Executor-76:job-5195 = [ 10d345f9-2fb2-42ef-850f-4919512d63db ]) 
> ControlledEntity name is:com.cloud.network.Network
> 2014-06-11 16:16:25,254 DEBUG [cloud.api.ApiDispatcher]
> (Job-Executor-76:job-5195 = [ 10d345f9-2fb2-42ef-850f-4919512d63db ]) 
> InfrastructureEntity name is:com.cloud.offering.DiskOffering
> 2014-06-11 16:16:25,285 DEBUG [cloud.network.NetworkModelImpl]
> (Job-Executor-76:job-5195 = [ 10d345f9-2fb2-42ef-850f-4919512d63db ]) 
> Service SecurityGroup is not supported in the network id=279
> 2014-06-11 16:16:25,288 DEBUG [cloud.network.NetworkModelImpl]
> (Job-Executor-76:job-5195 = [ 10d345f9-2fb2-42ef-850f-4919512d63db ]) 
> Service SecurityGroup is not supported in the network id=279
> 2014-06-11 16:16:25,299 DEBUG 
> [cloud.deploy.DeploymentPlanningManagerImpl]
> (Job-Executor-76:job-5195 = [ 10d345f9-2fb2-42ef-850f-4919512d63db ]) 
> Deploy avoids pods: [], clusters: [], hosts: []
> 2014-06-11 16:16:25,301 DEBUG 
> [cloud.deploy.DeploymentPlanningManagerImpl]
> (Job-Executor-76:job-5195 = [ 10d345f9-2fb2-42ef-850f-4919512d63db ]) 
> DeploymentPlanner allocation algorithm:
> com.cloud.deploy.FirstFitPlanner_EnhancerByCloudStack_642d2956@3002f35
> 2
> 2014-06-11 16:16:25,301 DEBUG 
> [cloud.deploy.DeploymentPlanningManagerImpl]
> (Job-Executor-76:job-5195 = [ 10d345f9-2fb2-42ef-850f-4919512d63db ]) 
> Trying to allocate a host and storage pools from dc:1, 
> pod:null,cluster:null, requested cpu: 2000, requested ram: 1073741824
> 2014-06-11 16:16:25,301 DEBUG 
> [cloud.deploy.DeploymentPlanningManagerImpl]
> (Job-Executor-76:job-5195 = [ 10d345f9-2fb2-42ef-850f-4919512d63db ]) 
> Is ROOT volume READY (pool already allocated)?: No
> 2014-06-11 16:16:25,301 DEBUG [cloud.deploy.FirstFitPlanner]
> (Job-Executor-76:job-5195 = [ 10d345f9-2fb2-42ef-850f-4919512d63db ]) 
> Searching all possible resources under this Zone: 1
> 2014-06-11 16:16:25,302 DEBUG [cloud.deploy.FirstFitPlanner]
> (Job-Executor-76:job-5195 = [ 10d345f9-2fb2-42ef-850f-4919512d63db ]) 
> Listing clusters in order of aggregate capacity, that have (atleast 
> one host with) enough CPU and RAM capacity under this Zone: 1
> 2014-06-11 16:16:25,304 DEBUG [cloud.deploy.FirstFitPlanner]
> (Job-Executor-76:job-5195 = [ 10d345f9-2fb2-42ef-850f-4919512d63db ]) 
> Removing from the clusterId list these clusters from avoid set: []
> 2014-06-11 16:16:25,310 DEBUG 
> [cloud.deploy.DeploymentPlanningManagerImpl]
> (Job-Executor-76:job-5195 = [ 10d345f9-2fb2-42ef-850f-4919512d63db ])
> Cluster: 4 has HyperVisorType that does not match the VM, skipping 
> this cluster
> 2014-06-11 16:16:25,311 DEBUG 
> [cloud.deploy.DeploymentPlanningManagerImpl]
> (Job-Executor-76:job-5195 = [ 10d345f9-2fb2-42ef-850f-4919512d63db ]) 
> Checking resources in Cluster: 1 under Pod: 1
> 2014-06-11 16:16:25,312 DEBUG [allocator.impl.FirstFitAllocator]
> (Job-Executor-76:job-5195 = [ 10d345f9-2fb2-42ef-850f-4919512d63db ]
> FirstFitRoutingAllocator) Looking for hosts in dc: 1 pod:1 cluster:1
> 2014-06-11 16:16:25,312 DEBUG [allocator.impl.FirstFitAllocator]
> (Job-Executor-76:job-5195 = [ 10d345f9-2fb2-42ef-850f-4919512d63db ]
> FirstFitRoutingAllocator) Looking for hosts having tag specified on 
> SvcOffering:xenserver
> 2014-06-11 16:16:25,314 DEBUG [allocator.impl.FirstFitAllocator]
> (Job-Executor-76:job-5195 = [ 10d345f9-2fb2-42ef-850f-4919512d63db ]
> FirstFitRoutingAllocator) Hosts with tag 'xenserver' are:[]
> 2014-06-11 16:16:25,315 DEBUG [allocator.impl.FirstFitAllocator]
> (Job-Executor-76:job-5195 = [ 10d345f9-2fb2-42ef-850f-4919512d63db ]
> FirstFitRoutingAllocator) FirstFitAllocator has 0 hosts to check for
> allocation: []
> 2014-06-11 16:16:25,317 DEBUG [allocator.impl.FirstFitAllocator]
> (Job-Executor-76:job-5195 = [ 10d345f9-2fb2-42ef-850f-4919512d63db ]
> FirstFitRoutingAllocator) Found 0 hosts for allocation after
> prioritization: []
> 2014-06-11 16:16:25,317 DEBUG [allocator.impl.FirstFitAllocator]
> (Job-Executor-76:job-5195 = [ 10d345f9-2fb2-42ef-850f-4919512d63db ]
> FirstFitRoutingAllocator) Looking for speed=2000Mhz, Ram=1024
> 2014-06-11 16:16:25,317 DEBUG [allocator.impl.FirstFitAllocator]
> (Job-Executor-76:job-5195 = [ 10d345f9-2fb2-42ef-850f-4919512d63db ]
> FirstFitRoutingAllocator) Host Allocator returning 0 suitable hosts
> 2014-06-11 16:16:25,317 DEBUG 
> [cloud.deploy.DeploymentPlanningManagerImpl]
> (Job-Executor-76:job-5195 = [ 10d345f9-2fb2-42ef-850f-4919512d63db ]) 
> No suitable hosts found
> 2014-06-11 16:16:25,317 DEBUG 
> [cloud.deploy.DeploymentPlanningManagerImpl]
> (Job-Executor-76:job-5195 = [ 10d345f9-2fb2-42ef-850f-4919512d63db ]) 
> No suitable hosts found under this Cluster: 1
> 2014-06-11 16:16:25,318 DEBUG 
> [cloud.deploy.DeploymentPlanningManagerImpl]
> (Job-Executor-76:job-5195 = [ 10d345f9-2fb2-42ef-850f-4919512d63db ]) 
> Could not find suitable Deployment Destination for this VM under any 
> clusters, returning.
> 2014-06-11 16:16:25,319 DEBUG [cloud.deploy.FirstFitPlanner]
> (Job-Executor-76:job-5195 = [ 10d345f9-2fb2-42ef-850f-4919512d63db ]) 
> Searching all possible resources under this Zone: 1
> 2014-06-11 16:16:25,319 DEBUG [cloud.deploy.FirstFitPlanner]
> (Job-Executor-76:job-5195 = [ 10d345f9-2fb2-42ef-850f-4919512d63db ]) 
> Listing clusters in order of aggregate capacity, that have (atleast 
> one host with) enough CPU and RAM capacity under this Zone: 1
> 2014-06-11 16:16:25,321 DEBUG [cloud.deploy.FirstFitPlanner]
> (Job-Executor-76:job-5195 = [ 10d345f9-2fb2-42ef-850f-4919512d63db ]) 
> Removing from the clusterId list these clusters from avoid set: [1, 4]
> 2014-06-11 16:16:25,322 DEBUG [cloud.deploy.FirstFitPlanner]
> (Job-Executor-76:job-5195 = [ 10d345f9-2fb2-42ef-850f-4919512d63db ]) 
> No clusters found after removing disabled clusters and clusters in 
> avoid list, returning.
> 2014-06-11 16:16:25,324 DEBUG [cloud.vm.UserVmManagerImpl]
> (Job-Executor-76:job-5195 = [ 10d345f9-2fb2-42ef-850f-4919512d63db ]) 
> Destroying vm VM[User|ubuntu-xen-test-4] as it failed to create on 
> Host with Id:null
> 2014-06-11 16:16:25,330 DEBUG [cloud.capacity.CapacityManagerImpl]
> (Job-Executor-76:job-5195 = [ 10d345f9-2fb2-42ef-850f-4919512d63db ]) 
> VM state transitted from :Stopped to Error with event:
> OperationFailedToErrorvm's original host id: null new host id: null 
> host id before state transition: null
> 2014-06-11 16:16:25,336 WARN [apache.cloudstack.alerts]
> (Job-Executor-76:job-5195 = [ 10d345f9-2fb2-42ef-850f-4919512d63db ])
> alertType:: 8 // dataCenterId:: 1 // podId:: null // clusterId:: null 
> //
> message:: Failed to deploy Vm with Id: 838, on Host with Id: null
> 2014-06-11 16:16:25,359 INFO [user.vm.DeployVMCmd]
> (Job-Executor-76:job-5195 = [ 10d345f9-2fb2-42ef-850f-4919512d63db ])
> com.cloud.exception.InsufficientServerCapacityException: Unable to 
> create a deployment for VM[User|ubuntu-xen-test-4]Scope=interface
> com.cloud.dc.DataCenter; id=1
> 2014-06-11 16:16:25,359 INFO [user.vm.DeployVMCmd]
> (Job-Executor-76:job-5195 = [ 10d345f9-2fb2-42ef-850f-4919512d63db ]) 
> Unable to create a deployment for VM[User|ubuntu-xen-test-4]
> com.cloud.exception.InsufficientServerCapacityException: Unable to 
> create a deployment for VM[User|ubuntu-xen-test-4]Scope=interface
> com.cloud.dc.DataCenter; id=1
> at
> org.apache.cloudstack.engine.cloud.entity.api.VMEntityManagerImpl.rese
> rveVirtualMachine(VMEntityManagerImpl.java:209)
> at
> org.apache.cloudstack.engine.cloud.entity.api.VirtualMachineEntityImpl
> .reserve(VirtualMachineEntityImpl.java:198)
> at
> com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.j
> ava:3439)
> at
> com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.j
> ava:3000)
> at
> com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.j
> ava:2986)
> at
> com.cloud.utils.component.ComponentInstantiationPostProcessor$Intercep
> torDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
> at
> org.apache.cloudstack.api.command.user.vm.DeployVMCmd.execute(DeployVM
> Cmd.java:420) at 
> com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:158)
> at 
> com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:531
> ) at 
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471
> ) at 
> java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
> at java.util.concurrent.FutureTask.run(FutureTask.java:166)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.j
> ava:1146)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.
> java:615) at java.lang.Thread.run(Thread.java:701)
> 2014-06-11 16:16:25,360 DEBUG [cloud.async.AsyncJobManagerImpl]
> (Job-Executor-76:job-5195 = [ 10d345f9-2fb2-42ef-850f-4919512d63db ]) 
> Complete async job-5195 = [ 10d345f9-2fb2-42ef-850f-4919512d63db ],
> jobStatus: 2, resultCode: 530, result: Error Code: 533 Error text: 
> Unable to create a deployment for VM[User|ubuntu-xen-test-4]
> 
> 
> 
> 
> Cheers
> 
> Andrei
> 
> 

Mime
View raw message