Re: Unable to create VM through 100 and 200 GB temaplate.
That's most probably NOT the correct solution but just happens to work in your environment... Something else is in the root cause of the problem... using linked clones should work by all means (known to be broken on VMFS6 - ACS is not compatible with it, requires VMFS5 - but with NFS it should work) On Tue, 5 May 2020 at 14:21, pradeep pal wrote: > Hi Sergey, > > The problem is resolved after changing the settings given below. > > vmware.create.full.clone false after change to True issue solved. > > Thanks to everyone. > > Regards > Pradeep > > From: Sergey Levitskiy > Sent: Saturday, May 2, 2020 6:45 PM > To: users@cloudstack.apache.org ; pradeep > pal > Subject: Re: Unable to create VM through 100 and 200 GB temaplate. > > Most likely this timeout is set to 20 min at present > "vmware.vcenter.session.timeout". If you use full clones on vmware set it > to at least 1 hour. Actual cloning time depends on the size of the root > disk and speed of your storage array. > > Thanks, > Sergey > > On 4/28/20, 11:29 AM, "Andrija Panic" wrote: > > Attachments are (afaik) stripped when you send email to ML (but I got > it, > NFS v3, so not relevant/VMFS) > > Increase all limits to "-1" as already suggested by Marc-Andre and if > it > still fails, please paste full management logs on the pastebin or > similar > (or attach the management-server.log on some external service) > > Regards, > Andrija > > On Tue, 28 Apr 2020 at 15:44, pradeep pal wrote: > > > Hi All, > > > > If we do these changes. any impact in production? > > > > @Andrija Panic , Please find the VMFS > version > > screenshot. > > > > One more thing When we create VMs through the template, the template > is > > successfully copied on secondary storage, but when it goes on primary > > storage the VM creation failed. > > > > Regards > > Pradeep > > > > -- > > *From:* Andrija Panic > > *Sent:* Sunday, April 26, 2020 7:32 PM > > *To:* users > > *Subject:* Re: Unable to create VM through 100 and 200 GB temaplate. > > > > A proper log, or perhaps (if this is what you tried to share) a > > screenshot uploaded online would be better. > > > > Which VMFS version? > > > > regards, > > > > On Sat, 25 Apr 2020 at 19:01, pradeep pal > wrote: > > > > > Hi All, > > > > > > We have built a new VMware cluster in existing CloudStack infra. > But > > when > > > we create new machines with 100 and 200 GB template. always we get > this > > > error. > > > > > > > > > Clone virtual machine > > > Status: > > > The task was canceled by a user. > > > Initiator: VSPHERE.LOCAL\Administrator > > > Target: > > > 271152f909563b3f954b87539960261e > > > Server: xx.xx.xx.xx > > > Related events: > > > 04/25/2020, 9:07:42 AM > > > > > > Removed ROOT-5420 > > > on xx.xx.xx.xx > > > from HOSTDC1 > > > 04/25/2020, 9:07:42 AM > > > > > > Cannot clone 271152f909563b3f954b87539960261e > > > : > > > 04/25/2020, 8:46:59 AM > > > > > > Assign a new instance UUID (502dd00e-baf0-9342-0e31-a635e9bacc48) > to > > > ROOT-5420 > > > 04/25/2020, 8:46:59 AM > > > > > > Assigned new BIOS UUID (422d4f0d-fb3d-3ae9-8710-77eac2aa06f5) to > > ROOT-5420 > > > on xx.xx.xx.xx > > > in HOSTDC1 > > > 04/25/2020, 8:46:59 AM > > > > > > Cloning 271152f909563b3f954b87539960261e > > > on host xx.xx.xx.xx > > > in HOSTDC1 > > > to ROOT-5420 on host 10.106.13.103 > > > 04/25/2020, 8:46:59 AM > > > > > > Task: Clone virtual machine > > > > > > kindly help us in this case. > > > > > > Thanks > > > Pradeep > > > > > > > > > -- > > > > Andrija Panić > > > > > -- > > Andrija Panić > > -- Andrija Panić
Re: Unable to create VM through 100 and 200 GB temaplate.
Hi Sergey,
The problem is resolved after changing the settings given below.
vmware.create.full.clone false after change to True issue solved.
Thanks to everyone.
Regards
Pradeep
From: Sergey Levitskiy
Sent: Saturday, May 2, 2020 6:45 PM
To: users@cloudstack.apache.org ; pradeep pal
Subject: Re: Unable to create VM through 100 and 200 GB temaplate.
Most likely this timeout is set to 20 min at present
"vmware.vcenter.session.timeout". If you use full clones on vmware set it to at
least 1 hour. Actual cloning time depends on the size of the root disk and
speed of your storage array.
Thanks,
Sergey
On 4/28/20, 11:29 AM, "Andrija Panic" wrote:
Attachments are (afaik) stripped when you send email to ML (but I got it,
NFS v3, so not relevant/VMFS)
Increase all limits to "-1" as already suggested by Marc-Andre and if it
still fails, please paste full management logs on the pastebin or similar
(or attach the management-server.log on some external service)
Regards,
Andrija
On Tue, 28 Apr 2020 at 15:44, pradeep pal wrote:
> Hi All,
>
> If we do these changes. any impact in production?
>
> @Andrija Panic , Please find the VMFS version
> screenshot.
>
> One more thing When we create VMs through the template, the template is
> successfully copied on secondary storage, but when it goes on primary
> storage the VM creation failed.
>
> Regards
> Pradeep
>
> --
> *From:* Andrija Panic
> *Sent:* Sunday, April 26, 2020 7:32 PM
> *To:* users
> *Subject:* Re: Unable to create VM through 100 and 200 GB temaplate.
>
> A proper log, or perhaps (if this is what you tried to share) a
> screenshot uploaded online would be better.
>
> Which VMFS version?
>
> regards,
>
> On Sat, 25 Apr 2020 at 19:01, pradeep pal wrote:
>
> > Hi All,
> >
> > We have built a new VMware cluster in existing CloudStack infra. But
> when
> > we create new machines with 100 and 200 GB template. always we get this
> > error.
> >
> >
> > Clone virtual machine
> > Status:
> > The task was canceled by a user.
> > Initiator: VSPHERE.LOCAL\Administrator
> > Target:
> > 271152f909563b3f954b87539960261e
> > Server: xx.xx.xx.xx
> > Related events:
> > 04/25/2020, 9:07:42 AM
> >
> > Removed ROOT-5420
> > on xx.xx.xx.xx
> > from HOSTDC1
> > 04/25/2020, 9:07:42 AM
> >
> > Cannot clone 271152f909563b3f954b87539960261e
> > :
> > 04/25/2020, 8:46:59 AM
> >
> > Assign a new instance UUID (502dd00e-baf0-9342-0e31-a635e9bacc48) to
> > ROOT-5420
> > 04/25/2020, 8:46:59 AM
> >
> > Assigned new BIOS UUID (422d4f0d-fb3d-3ae9-8710-77eac2aa06f5) to
> ROOT-5420
> > on xx.xx.xx.xx
> > in HOSTDC1
> > 04/25/2020, 8:46:59 AM
> >
> > Cloning 271152f909563b3f954b87539960261e
> > on host xx.xx.xx.xx
> > in HOSTDC1
> > to ROOT-5420 on host 10.106.13.103
> > 04/25/2020, 8:46:59 AM
> >
> > Task: Clone virtual machine
> >
> > kindly help us in this case.
> >
> > Thanks
> > Pradeep
> >
>
>
> --
>
> Andrija Panić
>
--
Andrija Panić
Re: Unable to create VM through 100 and 200 GB temaplate.
Most likely this timeout is set to 20 min at present
"vmware.vcenter.session.timeout". If you use full clones on vmware set it to at
least 1 hour. Actual cloning time depends on the size of the root disk and
speed of your storage array.
Thanks,
Sergey
On 4/28/20, 11:29 AM, "Andrija Panic" wrote:
Attachments are (afaik) stripped when you send email to ML (but I got it,
NFS v3, so not relevant/VMFS)
Increase all limits to "-1" as already suggested by Marc-Andre and if it
still fails, please paste full management logs on the pastebin or similar
(or attach the management-server.log on some external service)
Regards,
Andrija
On Tue, 28 Apr 2020 at 15:44, pradeep pal wrote:
> Hi All,
>
> If we do these changes. any impact in production?
>
> @Andrija Panic , Please find the VMFS version
> screenshot.
>
> One more thing When we create VMs through the template, the template is
> successfully copied on secondary storage, but when it goes on primary
> storage the VM creation failed.
>
> Regards
> Pradeep
>
> --
> *From:* Andrija Panic
> *Sent:* Sunday, April 26, 2020 7:32 PM
> *To:* users
> *Subject:* Re: Unable to create VM through 100 and 200 GB temaplate.
>
> A proper log, or perhaps (if this is what you tried to share) a
> screenshot uploaded online would be better.
>
> Which VMFS version?
>
> regards,
>
> On Sat, 25 Apr 2020 at 19:01, pradeep pal wrote:
>
> > Hi All,
> >
> > We have built a new VMware cluster in existing CloudStack infra. But
> when
> > we create new machines with 100 and 200 GB template. always we get this
> > error.
> >
> >
> > Clone virtual machine
> > Status:
> > The task was canceled by a user.
> > Initiator: VSPHERE.LOCAL\Administrator
> > Target:
> > 271152f909563b3f954b87539960261e
> > Server: xx.xx.xx.xx
> > Related events:
> > 04/25/2020, 9:07:42 AM
> >
> > Removed ROOT-5420
> > on xx.xx.xx.xx
> > from HOSTDC1
> > 04/25/2020, 9:07:42 AM
> >
> > Cannot clone 271152f909563b3f954b87539960261e
> > :
> > 04/25/2020, 8:46:59 AM
> >
> > Assign a new instance UUID (502dd00e-baf0-9342-0e31-a635e9bacc48) to
> > ROOT-5420
> > 04/25/2020, 8:46:59 AM
> >
> > Assigned new BIOS UUID (422d4f0d-fb3d-3ae9-8710-77eac2aa06f5) to
> ROOT-5420
> > on xx.xx.xx.xx
> > in HOSTDC1
> > 04/25/2020, 8:46:59 AM
> >
> > Cloning 271152f909563b3f954b87539960261e
> > on host xx.xx.xx.xx
> > in HOSTDC1
> > to ROOT-5420 on host 10.106.13.103
> > 04/25/2020, 8:46:59 AM
> >
> > Task: Clone virtual machine
> >
> > kindly help us in this case.
> >
> > Thanks
> > Pradeep
> >
>
>
> --
>
> Andrija Panić
>
--
Andrija Panić
Re: Unable to create VM through 100 and 200 GB temaplate.
Attachments are (afaik) stripped when you send email to ML (but I got it, NFS v3, so not relevant/VMFS) Increase all limits to "-1" as already suggested by Marc-Andre and if it still fails, please paste full management logs on the pastebin or similar (or attach the management-server.log on some external service) Regards, Andrija On Tue, 28 Apr 2020 at 15:44, pradeep pal wrote: > Hi All, > > If we do these changes. any impact in production? > > @Andrija Panic , Please find the VMFS version > screenshot. > > One more thing When we create VMs through the template, the template is > successfully copied on secondary storage, but when it goes on primary > storage the VM creation failed. > > Regards > Pradeep > > -- > *From:* Andrija Panic > *Sent:* Sunday, April 26, 2020 7:32 PM > *To:* users > *Subject:* Re: Unable to create VM through 100 and 200 GB temaplate. > > A proper log, or perhaps (if this is what you tried to share) a > screenshot uploaded online would be better. > > Which VMFS version? > > regards, > > On Sat, 25 Apr 2020 at 19:01, pradeep pal wrote: > > > Hi All, > > > > We have built a new VMware cluster in existing CloudStack infra. But > when > > we create new machines with 100 and 200 GB template. always we get this > > error. > > > > > > Clone virtual machine > > Status: > > The task was canceled by a user. > > Initiator: VSPHERE.LOCAL\Administrator > > Target: > > 271152f909563b3f954b87539960261e > > Server: xx.xx.xx.xx > > Related events: > > 04/25/2020, 9:07:42 AM > > > > Removed ROOT-5420 > > on xx.xx.xx.xx > > from HOSTDC1 > > 04/25/2020, 9:07:42 AM > > > > Cannot clone 271152f909563b3f954b87539960261e > > : > > 04/25/2020, 8:46:59 AM > > > > Assign a new instance UUID (502dd00e-baf0-9342-0e31-a635e9bacc48) to > > ROOT-5420 > > 04/25/2020, 8:46:59 AM > > > > Assigned new BIOS UUID (422d4f0d-fb3d-3ae9-8710-77eac2aa06f5) to > ROOT-5420 > > on xx.xx.xx.xx > > in HOSTDC1 > > 04/25/2020, 8:46:59 AM > > > > Cloning 271152f909563b3f954b87539960261e > > on host xx.xx.xx.xx > > in HOSTDC1 > > to ROOT-5420 on host 10.106.13.103 > > 04/25/2020, 8:46:59 AM > > > > Task: Clone virtual machine > > > > kindly help us in this case. > > > > Thanks > > Pradeep > > > > > -- > > Andrija Panić > -- Andrija Panić
Re: Unable to create VM through 100 and 200 GB temaplate.
Hi All, If we do these changes. any impact in production? @Andrija Panic<mailto:andrija.pa...@gmail.com>, Please find the VMFS version screenshot. One more thing When we create VMs through the template, the template is successfully copied on secondary storage, but when it goes on primary storage the VM creation failed. Regards Pradeep From: Andrija Panic Sent: Sunday, April 26, 2020 7:32 PM To: users Subject: Re: Unable to create VM through 100 and 200 GB temaplate. A proper log, or perhaps (if this is what you tried to share) a screenshot uploaded online would be better. Which VMFS version? regards, On Sat, 25 Apr 2020 at 19:01, pradeep pal wrote: > Hi All, > > We have built a new VMware cluster in existing CloudStack infra. But when > we create new machines with 100 and 200 GB template. always we get this > error. > > > Clone virtual machine > Status: > The task was canceled by a user. > Initiator: VSPHERE.LOCAL\Administrator > Target: > 271152f909563b3f954b87539960261e > Server: xx.xx.xx.xx > Related events: > 04/25/2020, 9:07:42 AM > > Removed ROOT-5420 > on xx.xx.xx.xx > from HOSTDC1 > 04/25/2020, 9:07:42 AM > > Cannot clone 271152f909563b3f954b87539960261e > : > 04/25/2020, 8:46:59 AM > > Assign a new instance UUID (502dd00e-baf0-9342-0e31-a635e9bacc48) to > ROOT-5420 > 04/25/2020, 8:46:59 AM > > Assigned new BIOS UUID (422d4f0d-fb3d-3ae9-8710-77eac2aa06f5) to ROOT-5420 > on xx.xx.xx.xx > in HOSTDC1 > 04/25/2020, 8:46:59 AM > > Cloning 271152f909563b3f954b87539960261e > on host xx.xx.xx.xx > in HOSTDC1 > to ROOT-5420 on host 10.106.13.103 > 04/25/2020, 8:46:59 AM > > Task: Clone virtual machine > > kindly help us in this case. > > Thanks > Pradeep > -- Andrija Panić
Re: Unable to create VM through 100 and 200 GB temaplate.
Sounds like you're reaching a limit somewhere on your cloudstack... ( error from vmware: The task was canceled by a user. ) in your global settings, check for these points and adjust the value: ( set them to -1 for no limit... ) custom.diskoffering.size.max max.project.primary.storage max.account.primary.storage max.domain.primary.storage Also, depending on your SAN // VMFS speed, you may need to adjust some timeout value in cloudstack / global settings... vm.job.timeout... and since you're on vmware, I will highly recommend you to set these global settings too: vmware.root.disk.controller = lsisas1068 vmware.systemvm.nic.device.type = Vmxnet3 Marcus On 2020-04-27 6:13 AM, pradeep pal wrote: Ok will share with you details asap. Thanks Pradeep Get Outlook for iOS<https://aka.ms/o0ukef> From: Andrija Panic Sent: Sunday, April 26, 2020 7:32:22 PM To: users Subject: Re: Unable to create VM through 100 and 200 GB temaplate. A proper log, or perhaps (if this is what you tried to share) a screenshot uploaded online would be better. Which VMFS version? regards, On Sat, 25 Apr 2020 at 19:01, pradeep pal wrote: Hi All, We have built a new VMware cluster in existing CloudStack infra. But when we create new machines with 100 and 200 GB template. always we get this error. Clone virtual machine Status: The task was canceled by a user. Initiator: VSPHERE.LOCAL\Administrator Target: 271152f909563b3f954b87539960261e Server: xx.xx.xx.xx Related events: 04/25/2020, 9:07:42 AM Removed ROOT-5420 on xx.xx.xx.xx from HOSTDC1 04/25/2020, 9:07:42 AM Cannot clone 271152f909563b3f954b87539960261e : 04/25/2020, 8:46:59 AM Assign a new instance UUID (502dd00e-baf0-9342-0e31-a635e9bacc48) to ROOT-5420 04/25/2020, 8:46:59 AM Assigned new BIOS UUID (422d4f0d-fb3d-3ae9-8710-77eac2aa06f5) to ROOT-5420 on xx.xx.xx.xx in HOSTDC1 04/25/2020, 8:46:59 AM Cloning 271152f909563b3f954b87539960261e on host xx.xx.xx.xx in HOSTDC1 to ROOT-5420 on host 10.106.13.103 04/25/2020, 8:46:59 AM Task: Clone virtual machine kindly help us in this case. Thanks Pradeep -- Andrija Panić
Re: Unable to create VM through 100 and 200 GB temaplate.
Ok will share with you details asap. Thanks Pradeep Get Outlook for iOS<https://aka.ms/o0ukef> From: Andrija Panic Sent: Sunday, April 26, 2020 7:32:22 PM To: users Subject: Re: Unable to create VM through 100 and 200 GB temaplate. A proper log, or perhaps (if this is what you tried to share) a screenshot uploaded online would be better. Which VMFS version? regards, On Sat, 25 Apr 2020 at 19:01, pradeep pal wrote: > Hi All, > > We have built a new VMware cluster in existing CloudStack infra. But when > we create new machines with 100 and 200 GB template. always we get this > error. > > > Clone virtual machine > Status: > The task was canceled by a user. > Initiator: VSPHERE.LOCAL\Administrator > Target: > 271152f909563b3f954b87539960261e > Server: xx.xx.xx.xx > Related events: > 04/25/2020, 9:07:42 AM > > Removed ROOT-5420 > on xx.xx.xx.xx > from HOSTDC1 > 04/25/2020, 9:07:42 AM > > Cannot clone 271152f909563b3f954b87539960261e > : > 04/25/2020, 8:46:59 AM > > Assign a new instance UUID (502dd00e-baf0-9342-0e31-a635e9bacc48) to > ROOT-5420 > 04/25/2020, 8:46:59 AM > > Assigned new BIOS UUID (422d4f0d-fb3d-3ae9-8710-77eac2aa06f5) to ROOT-5420 > on xx.xx.xx.xx > in HOSTDC1 > 04/25/2020, 8:46:59 AM > > Cloning 271152f909563b3f954b87539960261e > on host xx.xx.xx.xx > in HOSTDC1 > to ROOT-5420 on host 10.106.13.103 > 04/25/2020, 8:46:59 AM > > Task: Clone virtual machine > > kindly help us in this case. > > Thanks > Pradeep > -- Andrija Panić
Re: Unable to create VM through 100 and 200 GB temaplate.
A proper log, or perhaps (if this is what you tried to share) a screenshot uploaded online would be better. Which VMFS version? regards, On Sat, 25 Apr 2020 at 19:01, pradeep pal wrote: > Hi All, > > We have built a new VMware cluster in existing CloudStack infra. But when > we create new machines with 100 and 200 GB template. always we get this > error. > > > Clone virtual machine > Status: > The task was canceled by a user. > Initiator: VSPHERE.LOCAL\Administrator > Target: > 271152f909563b3f954b87539960261e > Server: xx.xx.xx.xx > Related events: > 04/25/2020, 9:07:42 AM > > Removed ROOT-5420 > on xx.xx.xx.xx > from HOSTDC1 > 04/25/2020, 9:07:42 AM > > Cannot clone 271152f909563b3f954b87539960261e > : > 04/25/2020, 8:46:59 AM > > Assign a new instance UUID (502dd00e-baf0-9342-0e31-a635e9bacc48) to > ROOT-5420 > 04/25/2020, 8:46:59 AM > > Assigned new BIOS UUID (422d4f0d-fb3d-3ae9-8710-77eac2aa06f5) to ROOT-5420 > on xx.xx.xx.xx > in HOSTDC1 > 04/25/2020, 8:46:59 AM > > Cloning 271152f909563b3f954b87539960261e > on host xx.xx.xx.xx > in HOSTDC1 > to ROOT-5420 on host 10.106.13.103 > 04/25/2020, 8:46:59 AM > > Task: Clone virtual machine > > kindly help us in this case. > > Thanks > Pradeep > -- Andrija Panić
RE: unable to create vm deployment insufficient server capacity
The cpu frequency is set to 2.30Ghz in the GUI, both for the 16GB/4 cpu as well as the 32Gb/4 cpu service offerings. Chris Chupela Systems Engineer DSS -Original Message- From: Erik Weber [mailto:terbol...@gmail.com] Sent: Saturday, June 13, 2015 3:42 AM To: users@cloudstack.apache.org; prapul cool Subject: Re: unable to create vm deployment insufficient server capacity Seems to be 2,3GHz (9200MHz requested over 4 cpus). Chris: check that your host(s) CPU speed is registered as 2300MHz or higher in the ACS gui. Erik Den lørdag 13. juni 2015 skrev prapul cool prapul_cool2...@yahoo.com.invalid følgende: Hi Chris, What are the Compute offering frequencies you set for 32gb offering? Thanks,Prapul sriram,Architect,PSI Cloud Solutions. On Saturday, 13 June 2015 7:25 AM, Chris Chupela cchup...@dsscorp.com javascript:; wrote: I'm trying to change the service offering on an existing vm from 4 cpu/16gb ram, to 4 cpu/32gb of ram. In doing so, I receive the 'unable to create deployment for vm' message in the CP web ui. Looking thru the management-server.log file, I see the following repeating for all of my hosts (noting the cpuFreqGood:false) 3-1361-4028-9b48-7e34d8b54770 ] FirstFitRoutingAllocator) STATS: Can alloc CPU from host: 6, used: 115647, reserved: 9196, actual total: 55176, total with overprovisioning: 275880; requested cpu:9200,alloc_from_last_host?:false ,considerReservedCapacity?: true 2015-06-12 20:21:39,151 DEBUG [cloud.capacity.CapacityManagerImpl] (Job-Executor-39:job-65 = [ 24499b73-1361-4028-9b48-7e34d8b54770 ] FirstFitRoutingAllocator) STATS: Can alloc MEM from host: 6, used: 85094039552, reserved: 17179869184, total: 137412255744; requested mem: 34359738368,alloc_from_last_host?:false ,considerReservedCapacity?: true 2015-06-12 20:21:39,151 DEBUG [allocator.impl.FirstFitAllocator] (Job-Executor-39:job-65 = [ 24499b73-1361-4028-9b48-7e34d8b54770 ] FirstFitRoutingAllocator) Not using host 6; numCpusGood: true; cpuFreqGood: false, host has capacity?true. com.cloud.exception.InsufficientServerCapacityException: Unable to create a deployment for VM[User|4cada82f-23a6-4bac-9508-3c4b07f9a2b4]Scope=interface com.cloud.dc.DataCenter; id=1 at com.cloud.vm.VirtualMachineManagerImpl.advanceStart(VirtualMachineManagerImpl.java:846) at com.cloud.vm.VirtualMachineManagerImpl.start(VirtualMachineManagerImpl.java:580) at org.apache.cloudstack.engine.cloud.entity.api.VMEntityManagerImpl.deployVirtualMachine(VMEntityManagerImpl.java:242) at org.apache.cloudstack.engine.cloud.entity.api.VirtualMachineEntityImpl.deploy(VirtualMachineEntityImpl.java:209) at com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:3509) at com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:1996) at com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125) at org.apache.cloudstack.api.command.user.vm.StartVMCmd.execute(StartVMCmd.java:120) at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:158) at com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:530) at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source) at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source) The vm will not start. If I change service offering back to 4cpu/16gb ram, vm will start successfully. This seems odd, since I have not changed number of cpu's but yet cloudstack is complaining that is the issue - CpuFreqGood: false. Additionally, my memory usage and cpu usage (for the zone), sit at 59% and 29% respectively. Chris Chupela Systems Engineer DSS
Re: unable to create vm deployment insufficient server capacity
Hi Chris, What are the Compute offering frequencies you set for 32gb offering? Thanks,Prapul sriram,Architect,PSI Cloud Solutions. On Saturday, 13 June 2015 7:25 AM, Chris Chupela cchup...@dsscorp.com wrote: I'm trying to change the service offering on an existing vm from 4 cpu/16gb ram, to 4 cpu/32gb of ram. In doing so, I receive the 'unable to create deployment for vm' message in the CP web ui. Looking thru the management-server.log file, I see the following repeating for all of my hosts (noting the cpuFreqGood:false) 3-1361-4028-9b48-7e34d8b54770 ] FirstFitRoutingAllocator) STATS: Can alloc CPU from host: 6, used: 115647, reserved: 9196, actual total: 55176, total with overprovisioning: 275880; requested cpu:9200,alloc_from_last_host?:false ,considerReservedCapacity?: true 2015-06-12 20:21:39,151 DEBUG [cloud.capacity.CapacityManagerImpl] (Job-Executor-39:job-65 = [ 24499b73-1361-4028-9b48-7e34d8b54770 ] FirstFitRoutingAllocator) STATS: Can alloc MEM from host: 6, used: 85094039552, reserved: 17179869184, total: 137412255744; requested mem: 34359738368,alloc_from_last_host?:false ,considerReservedCapacity?: true 2015-06-12 20:21:39,151 DEBUG [allocator.impl.FirstFitAllocator] (Job-Executor-39:job-65 = [ 24499b73-1361-4028-9b48-7e34d8b54770 ] FirstFitRoutingAllocator) Not using host 6; numCpusGood: true; cpuFreqGood: false, host has capacity?true. com.cloud.exception.InsufficientServerCapacityException: Unable to create a deployment for VM[User|4cada82f-23a6-4bac-9508-3c4b07f9a2b4]Scope=interface com.cloud.dc.DataCenter; id=1 at com.cloud.vm.VirtualMachineManagerImpl.advanceStart(VirtualMachineManagerImpl.java:846) at com.cloud.vm.VirtualMachineManagerImpl.start(VirtualMachineManagerImpl.java:580) at org.apache.cloudstack.engine.cloud.entity.api.VMEntityManagerImpl.deployVirtualMachine(VMEntityManagerImpl.java:242) at org.apache.cloudstack.engine.cloud.entity.api.VirtualMachineEntityImpl.deploy(VirtualMachineEntityImpl.java:209) at com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:3509) at com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:1996) at com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125) at org.apache.cloudstack.api.command.user.vm.StartVMCmd.execute(StartVMCmd.java:120) at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:158) at com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:530) at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source) at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source) The vm will not start. If I change service offering back to 4cpu/16gb ram, vm will start successfully. This seems odd, since I have not changed number of cpu's but yet cloudstack is complaining that is the issue - CpuFreqGood: false. Additionally, my memory usage and cpu usage (for the zone), sit at 59% and 29% respectively. Chris Chupela Systems Engineer DSS
Re: unable to create vm deployment insufficient server capacity
Seems to be 2,3GHz (9200MHz requested over 4 cpus). Chris: check that your host(s) CPU speed is registered as 2300MHz or higher in the ACS gui. Erik Den lørdag 13. juni 2015 skrev prapul cool prapul_cool2...@yahoo.com.invalid følgende: Hi Chris, What are the Compute offering frequencies you set for 32gb offering? Thanks,Prapul sriram,Architect,PSI Cloud Solutions. On Saturday, 13 June 2015 7:25 AM, Chris Chupela cchup...@dsscorp.com javascript:; wrote: I'm trying to change the service offering on an existing vm from 4 cpu/16gb ram, to 4 cpu/32gb of ram. In doing so, I receive the 'unable to create deployment for vm' message in the CP web ui. Looking thru the management-server.log file, I see the following repeating for all of my hosts (noting the cpuFreqGood:false) 3-1361-4028-9b48-7e34d8b54770 ] FirstFitRoutingAllocator) STATS: Can alloc CPU from host: 6, used: 115647, reserved: 9196, actual total: 55176, total with overprovisioning: 275880; requested cpu:9200,alloc_from_last_host?:false ,considerReservedCapacity?: true 2015-06-12 20:21:39,151 DEBUG [cloud.capacity.CapacityManagerImpl] (Job-Executor-39:job-65 = [ 24499b73-1361-4028-9b48-7e34d8b54770 ] FirstFitRoutingAllocator) STATS: Can alloc MEM from host: 6, used: 85094039552, reserved: 17179869184, total: 137412255744; requested mem: 34359738368,alloc_from_last_host?:false ,considerReservedCapacity?: true 2015-06-12 20:21:39,151 DEBUG [allocator.impl.FirstFitAllocator] (Job-Executor-39:job-65 = [ 24499b73-1361-4028-9b48-7e34d8b54770 ] FirstFitRoutingAllocator) Not using host 6; numCpusGood: true; cpuFreqGood: false, host has capacity?true. com.cloud.exception.InsufficientServerCapacityException: Unable to create a deployment for VM[User|4cada82f-23a6-4bac-9508-3c4b07f9a2b4]Scope=interface com.cloud.dc.DataCenter; id=1 at com.cloud.vm.VirtualMachineManagerImpl.advanceStart(VirtualMachineManagerImpl.java:846) at com.cloud.vm.VirtualMachineManagerImpl.start(VirtualMachineManagerImpl.java:580) at org.apache.cloudstack.engine.cloud.entity.api.VMEntityManagerImpl.deployVirtualMachine(VMEntityManagerImpl.java:242) at org.apache.cloudstack.engine.cloud.entity.api.VirtualMachineEntityImpl.deploy(VirtualMachineEntityImpl.java:209) at com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:3509) at com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:1996) at com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125) at org.apache.cloudstack.api.command.user.vm.StartVMCmd.execute(StartVMCmd.java:120) at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:158) at com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:530) at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source) at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source) The vm will not start. If I change service offering back to 4cpu/16gb ram, vm will start successfully. This seems odd, since I have not changed number of cpu's but yet cloudstack is complaining that is the issue - CpuFreqGood: false. Additionally, my memory usage and cpu usage (for the zone), sit at 59% and 29% respectively. Chris Chupela Systems Engineer DSS
RE: Unable to create VM
It seems the problem was on ESXi 5.5, I updated the hypervisor software to the second update of ESXi 5.5. Then I added again the zone and now I'm able to add VMs, I don't really know if it was an ACS issue or an ESXi issue. Thanks! Regards, José -Mensaje original- De: Somesh Naidu [mailto:somesh.na...@citrix.com] Enviado el: miércoles, 28 de enero de 2015 14:56 Para: users@cloudstack.apache.org Asunto: RE: Unable to create VM It may be the template I don't know. When I said do a grep, I meant something like - grep job-56 management-server.log | less - then read through the operation and find out the first failure. Somesh CloudPlatform Escalations Citrix Systems, Inc. -Original Message- From: José Egas López [mailto:josee...@farmaenlace.com] Sent: Wednesday, January 28, 2015 2:40 PM To: users@cloudstack.apache.org Subject: RE: Unable to create VM It's a fresh deployment, I don't know why it throws that InsufficientServerCapacityException. Somesh, what do you exactly mean with doing a grep? Thanks! Regards, José -Mensaje original- De: Somesh Naidu [mailto:somesh.na...@citrix.com] Enviado el: miércoles, 28 de enero de 2015 13:51 Para: users@cloudstack.apache.org Asunto: RE: Unable to create VM It say's InsufficientServerCapacityException but not sure which resource based on the logs below. You could do a grep on 'job-56 to get more insight. If not, share that output via pastebin. Somesh CloudPlatform Escalations Citrix Systems, Inc. -Original Message- From: José Egas López [mailto:josee...@farmaenlace.com] Sent: Wednesday, January 28, 2015 1:43 PM To: users@cloudstack.apache.org Subject: Unable to create VM Hi all, pleas help, I'm on a new ACS 4.4 deployment, I just created successfully a new zone, and added successfully both ISOs and Templates. When I try to add a new VM from an ISO or a Template, it shows the following error: Failed to deploy a VM. Here is the log: 2015-01-28 13:25:26,383 DEBUG [c.c.d.FirstFitPlanner] (API-Job-Executor-16:ctx-ee81845c job-56 ctx-91e83bb7) No clusters found after removing disabled clusters and clusters in avoid list, returning. 2015-01-28 13:25:26,387 DEBUG [c.c.v.UserVmManagerImpl] (API-Job-Executor-16:ctx-ee81845c job-56 ctx-91e83bb7) Destroying vm VM[User|i-2-10-VM] as it failed to create on Host with Id:null 2015-01-28 13:25:26,395 DEBUG [c.c.c.CapacityManagerImpl] (API-Job-Executor-16:ctx-ee81845c job-56 ctx-91e83bb7) 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 2015-01-28 13:25:26,420 WARN [o.a.c.alerts] (API-Job-Executor-16:ctx-ee81845c job-56 ctx-91e83bb7) alertType:: 8 // dataCenterId:: 1 // podId:: null // clusterId:: null // message:: Failed to deploy Vm with Id: 10, on Host with Id: null 2015-01-28 13:25:26,461 INFO [o.a.c.a.c.a.v.DeployVMCmdByAdmin] (API-Job-Executor-16:ctx-ee81845c job-56 ctx-91e83bb7) com.cloud.exception.InsufficientServerCapacityException: Unable to create a deployment for VM[User|i-2-10-VM]Scope=interface com.cloud.dc.DataCenter; id=1 2015-01-28 13:25:26,464 INFO [o.a.c.a.c.a.v.DeployVMCmdByAdmin] (API-Job-Executor-16:ctx-ee81845c job-56 ctx-91e83bb7) Unable to create a deployment for VM[User|i-2-10-VM] com.cloud.exception.InsufficientServerCapacityException: Unable to create a deployment for VM[User|i-2-10-VM]Scope=interface com.cloud.dc.DataCenter; id=1 at org.apache.cloudstack.engine.cloud.entity.api.VMEntityManagerImpl.reserveVirtualMachine(VMEntityManagerImpl.java:214) at org.apache.cloudstack.engine.cloud.entity.api.VirtualMachineEntityImpl.reserve(VirtualMachineEntityImpl.java:200) at com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:3468) at com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:3123) at com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:3111) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317) at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:183) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150) at org.apache.cloudstack.network.contrail.management.EventUtils$EventInterceptor.invoke(EventUtils.java:106) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:161) at com.cloud.event.ActionEventInterceptor.invoke
RE: Unable to create VM
It say's InsufficientServerCapacityException but not sure which resource
based on the logs below.
You could do a grep on 'job-56 to get more insight. If not, share that output
via pastebin.
Somesh
CloudPlatform Escalations
Citrix Systems, Inc.
-Original Message-
From: José Egas López [mailto:josee...@farmaenlace.com]
Sent: Wednesday, January 28, 2015 1:43 PM
To: users@cloudstack.apache.org
Subject: Unable to create VM
Hi all, pleas help, I'm on a new ACS 4.4 deployment, I just created
successfully a new zone, and added successfully both ISOs and Templates.
When I try to add a new VM from an ISO or a Template, it shows the following
error: Failed to deploy a VM.
Here is the log:
2015-01-28 13:25:26,383 DEBUG [c.c.d.FirstFitPlanner]
(API-Job-Executor-16:ctx-ee81845c job-56 ctx-91e83bb7) No clusters found after
removing disabled clusters and clusters in avoid list, returning.
2015-01-28 13:25:26,387 DEBUG [c.c.v.UserVmManagerImpl]
(API-Job-Executor-16:ctx-ee81845c job-56 ctx-91e83bb7) Destroying vm
VM[User|i-2-10-VM] as it failed to create on Host with Id:null
2015-01-28 13:25:26,395 DEBUG [c.c.c.CapacityManagerImpl]
(API-Job-Executor-16:ctx-ee81845c job-56 ctx-91e83bb7) 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
2015-01-28 13:25:26,420 WARN [o.a.c.alerts] (API-Job-Executor-16:ctx-ee81845c
job-56 ctx-91e83bb7) alertType:: 8 // dataCenterId:: 1 // podId:: null //
clusterId:: null // message:: Failed to deploy Vm with Id: 10, on Host with Id:
null
2015-01-28 13:25:26,461 INFO [o.a.c.a.c.a.v.DeployVMCmdByAdmin]
(API-Job-Executor-16:ctx-ee81845c job-56 ctx-91e83bb7)
com.cloud.exception.InsufficientServerCapacityException: Unable to create a
deployment for VM[User|i-2-10-VM]Scope=interface com.cloud.dc.DataCenter; id=1
2015-01-28 13:25:26,464 INFO [o.a.c.a.c.a.v.DeployVMCmdByAdmin]
(API-Job-Executor-16:ctx-ee81845c job-56 ctx-91e83bb7) Unable to create a
deployment for VM[User|i-2-10-VM]
com.cloud.exception.InsufficientServerCapacityException: Unable to create a
deployment for VM[User|i-2-10-VM]Scope=interface com.cloud.dc.DataCenter; id=1
at
org.apache.cloudstack.engine.cloud.entity.api.VMEntityManagerImpl.reserveVirtualMachine(VMEntityManagerImpl.java:214)
at
org.apache.cloudstack.engine.cloud.entity.api.VirtualMachineEntityImpl.reserve(VirtualMachineEntityImpl.java:200)
at
com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:3468)
at
com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:3123)
at
com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:3111)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at
org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317)
at
org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:183)
at
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150)
at
org.apache.cloudstack.network.contrail.management.EventUtils$EventInterceptor.invoke(EventUtils.java:106)
at
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:161)
at
com.cloud.event.ActionEventInterceptor.invoke(ActionEventInterceptor.java:51)
at
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:161)
at
org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:91)
at
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172)
at
org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204)
at com.sun.proxy.$Proxy207.startVirtualMachine(Unknown Source)
at
org.apache.cloudstack.api.command.admin.vm.DeployVMCmdByAdmin.execute(DeployVMCmdByAdmin.java:48)
at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:141)
at
com.cloud.api.ApiAsyncJobDispatcher.runJob(ApiAsyncJobDispatcher.java:108)
at
org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.runInContext(AsyncJobManagerImpl.java:503)
at
org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:49)
2015-01-28 13:25:42,875 DEBUG [c.c.a.m.AgentManagerImpl]
(AgentManager-Handler-8:null) SeqA 2-12120: Processing Seq 2-12120: { Cmd ,
MgmtId: -1, via: 2, Ver: v1, Flags: 11,
RE: Unable to create VM
It's a fresh deployment, I don't know why it throws that InsufficientServerCapacityException. Somesh, what do you exactly mean with doing a grep? Thanks! Regards, José -Mensaje original- De: Somesh Naidu [mailto:somesh.na...@citrix.com] Enviado el: miércoles, 28 de enero de 2015 13:51 Para: users@cloudstack.apache.org Asunto: RE: Unable to create VM It say's InsufficientServerCapacityException but not sure which resource based on the logs below. You could do a grep on 'job-56 to get more insight. If not, share that output via pastebin. Somesh CloudPlatform Escalations Citrix Systems, Inc. -Original Message- From: José Egas López [mailto:josee...@farmaenlace.com] Sent: Wednesday, January 28, 2015 1:43 PM To: users@cloudstack.apache.org Subject: Unable to create VM Hi all, pleas help, I'm on a new ACS 4.4 deployment, I just created successfully a new zone, and added successfully both ISOs and Templates. When I try to add a new VM from an ISO or a Template, it shows the following error: Failed to deploy a VM. Here is the log: 2015-01-28 13:25:26,383 DEBUG [c.c.d.FirstFitPlanner] (API-Job-Executor-16:ctx-ee81845c job-56 ctx-91e83bb7) No clusters found after removing disabled clusters and clusters in avoid list, returning. 2015-01-28 13:25:26,387 DEBUG [c.c.v.UserVmManagerImpl] (API-Job-Executor-16:ctx-ee81845c job-56 ctx-91e83bb7) Destroying vm VM[User|i-2-10-VM] as it failed to create on Host with Id:null 2015-01-28 13:25:26,395 DEBUG [c.c.c.CapacityManagerImpl] (API-Job-Executor-16:ctx-ee81845c job-56 ctx-91e83bb7) 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 2015-01-28 13:25:26,420 WARN [o.a.c.alerts] (API-Job-Executor-16:ctx-ee81845c job-56 ctx-91e83bb7) alertType:: 8 // dataCenterId:: 1 // podId:: null // clusterId:: null // message:: Failed to deploy Vm with Id: 10, on Host with Id: null 2015-01-28 13:25:26,461 INFO [o.a.c.a.c.a.v.DeployVMCmdByAdmin] (API-Job-Executor-16:ctx-ee81845c job-56 ctx-91e83bb7) com.cloud.exception.InsufficientServerCapacityException: Unable to create a deployment for VM[User|i-2-10-VM]Scope=interface com.cloud.dc.DataCenter; id=1 2015-01-28 13:25:26,464 INFO [o.a.c.a.c.a.v.DeployVMCmdByAdmin] (API-Job-Executor-16:ctx-ee81845c job-56 ctx-91e83bb7) Unable to create a deployment for VM[User|i-2-10-VM] com.cloud.exception.InsufficientServerCapacityException: Unable to create a deployment for VM[User|i-2-10-VM]Scope=interface com.cloud.dc.DataCenter; id=1 at org.apache.cloudstack.engine.cloud.entity.api.VMEntityManagerImpl.reserveVirtualMachine(VMEntityManagerImpl.java:214) at org.apache.cloudstack.engine.cloud.entity.api.VirtualMachineEntityImpl.reserve(VirtualMachineEntityImpl.java:200) at com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:3468) at com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:3123) at com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:3111) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317) at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:183) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150) at org.apache.cloudstack.network.contrail.management.EventUtils$EventInterceptor.invoke(EventUtils.java:106) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:161) at com.cloud.event.ActionEventInterceptor.invoke(ActionEventInterceptor.java:51) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:161) at org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:91) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172) at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204) at com.sun.proxy.$Proxy207.startVirtualMachine(Unknown Source) at org.apache.cloudstack.api.command.admin.vm.DeployVMCmdByAdmin.execute(DeployVMCmdByAdmin.java:48) at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:141) at com.cloud.api.ApiAsyncJobDispatcher.runJob(ApiAsyncJobDispatcher.java:108) at org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5
Re: Unable to create VM
You just need to read carefully the lines above this one : “create a deployment for VM[User|i-2-10-VM] com.cloud.exception.InsufficientServerCapacityException: Unable to create a deployment for VM[User|i-2-10-VM]Scope=interface com.cloud.dc.DataCenter; id=1” You will see in the logs each cluster and host of the cluster that the CS is checking if they receive the VM. It will say the amount of free memory, CPU and storage for each cluster. You will see what the problem is; just read carefully the logs entries. On Wed, Jan 28, 2015 at 5:40 PM, José Egas López josee...@farmaenlace.com wrote: It's a fresh deployment, I don't know why it throws that InsufficientServerCapacityException. Somesh, what do you exactly mean with doing a grep? Thanks! Regards, José -Mensaje original- De: Somesh Naidu [mailto:somesh.na...@citrix.com] Enviado el: miércoles, 28 de enero de 2015 13:51 Para: users@cloudstack.apache.org Asunto: RE: Unable to create VM It say's InsufficientServerCapacityException but not sure which resource based on the logs below. You could do a grep on 'job-56 to get more insight. If not, share that output via pastebin. Somesh CloudPlatform Escalations Citrix Systems, Inc. -Original Message- From: José Egas López [mailto:josee...@farmaenlace.com] Sent: Wednesday, January 28, 2015 1:43 PM To: users@cloudstack.apache.org Subject: Unable to create VM Hi all, pleas help, I'm on a new ACS 4.4 deployment, I just created successfully a new zone, and added successfully both ISOs and Templates. When I try to add a new VM from an ISO or a Template, it shows the following error: Failed to deploy a VM. Here is the log: 2015-01-28 13:25:26,383 DEBUG [c.c.d.FirstFitPlanner] (API-Job-Executor-16:ctx-ee81845c job-56 ctx-91e83bb7) No clusters found after removing disabled clusters and clusters in avoid list, returning. 2015-01-28 13:25:26,387 DEBUG [c.c.v.UserVmManagerImpl] (API-Job-Executor-16:ctx-ee81845c job-56 ctx-91e83bb7) Destroying vm VM[User|i-2-10-VM] as it failed to create on Host with Id:null 2015-01-28 13:25:26,395 DEBUG [c.c.c.CapacityManagerImpl] (API-Job-Executor-16:ctx-ee81845c job-56 ctx-91e83bb7) 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 2015-01-28 13:25:26,420 WARN [o.a.c.alerts] (API-Job-Executor-16:ctx-ee81845c job-56 ctx-91e83bb7) alertType:: 8 // dataCenterId:: 1 // podId:: null // clusterId:: null // message:: Failed to deploy Vm with Id: 10, on Host with Id: null 2015-01-28 13:25:26,461 INFO [o.a.c.a.c.a.v.DeployVMCmdByAdmin] (API-Job-Executor-16:ctx-ee81845c job-56 ctx-91e83bb7) com.cloud.exception.InsufficientServerCapacityException: Unable to create a deployment for VM[User|i-2-10-VM]Scope=interface com.cloud.dc.DataCenter; id=1 2015-01-28 13:25:26,464 INFO [o.a.c.a.c.a.v.DeployVMCmdByAdmin] (API-Job-Executor-16:ctx-ee81845c job-56 ctx-91e83bb7) Unable to create a deployment for VM[User|i-2-10-VM] com.cloud.exception.InsufficientServerCapacityException: Unable to create a deployment for VM[User|i-2-10-VM]Scope=interface com.cloud.dc.DataCenter; id=1 at org.apache.cloudstack.engine.cloud.entity.api.VMEntityManagerImpl.reserveVirtualMachine(VMEntityManagerImpl.java:214) at org.apache.cloudstack.engine.cloud.entity.api.VirtualMachineEntityImpl.reserve(VirtualMachineEntityImpl.java:200) at com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:3468) at com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:3123) at com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:3111) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317) at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:183) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150) at org.apache.cloudstack.network.contrail.management.EventUtils$EventInterceptor.invoke(EventUtils.java:106) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:161) at com.cloud.event.ActionEventInterceptor.invoke(ActionEventInterceptor.java:51) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:161) at org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java
RE: Unable to create VM
It may be the template I don't know. When I said do a grep, I meant something like - grep job-56 management-server.log | less - then read through the operation and find out the first failure. Somesh CloudPlatform Escalations Citrix Systems, Inc. -Original Message- From: José Egas López [mailto:josee...@farmaenlace.com] Sent: Wednesday, January 28, 2015 2:40 PM To: users@cloudstack.apache.org Subject: RE: Unable to create VM It's a fresh deployment, I don't know why it throws that InsufficientServerCapacityException. Somesh, what do you exactly mean with doing a grep? Thanks! Regards, José -Mensaje original- De: Somesh Naidu [mailto:somesh.na...@citrix.com] Enviado el: miércoles, 28 de enero de 2015 13:51 Para: users@cloudstack.apache.org Asunto: RE: Unable to create VM It say's InsufficientServerCapacityException but not sure which resource based on the logs below. You could do a grep on 'job-56 to get more insight. If not, share that output via pastebin. Somesh CloudPlatform Escalations Citrix Systems, Inc. -Original Message- From: José Egas López [mailto:josee...@farmaenlace.com] Sent: Wednesday, January 28, 2015 1:43 PM To: users@cloudstack.apache.org Subject: Unable to create VM Hi all, pleas help, I'm on a new ACS 4.4 deployment, I just created successfully a new zone, and added successfully both ISOs and Templates. When I try to add a new VM from an ISO or a Template, it shows the following error: Failed to deploy a VM. Here is the log: 2015-01-28 13:25:26,383 DEBUG [c.c.d.FirstFitPlanner] (API-Job-Executor-16:ctx-ee81845c job-56 ctx-91e83bb7) No clusters found after removing disabled clusters and clusters in avoid list, returning. 2015-01-28 13:25:26,387 DEBUG [c.c.v.UserVmManagerImpl] (API-Job-Executor-16:ctx-ee81845c job-56 ctx-91e83bb7) Destroying vm VM[User|i-2-10-VM] as it failed to create on Host with Id:null 2015-01-28 13:25:26,395 DEBUG [c.c.c.CapacityManagerImpl] (API-Job-Executor-16:ctx-ee81845c job-56 ctx-91e83bb7) 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 2015-01-28 13:25:26,420 WARN [o.a.c.alerts] (API-Job-Executor-16:ctx-ee81845c job-56 ctx-91e83bb7) alertType:: 8 // dataCenterId:: 1 // podId:: null // clusterId:: null // message:: Failed to deploy Vm with Id: 10, on Host with Id: null 2015-01-28 13:25:26,461 INFO [o.a.c.a.c.a.v.DeployVMCmdByAdmin] (API-Job-Executor-16:ctx-ee81845c job-56 ctx-91e83bb7) com.cloud.exception.InsufficientServerCapacityException: Unable to create a deployment for VM[User|i-2-10-VM]Scope=interface com.cloud.dc.DataCenter; id=1 2015-01-28 13:25:26,464 INFO [o.a.c.a.c.a.v.DeployVMCmdByAdmin] (API-Job-Executor-16:ctx-ee81845c job-56 ctx-91e83bb7) Unable to create a deployment for VM[User|i-2-10-VM] com.cloud.exception.InsufficientServerCapacityException: Unable to create a deployment for VM[User|i-2-10-VM]Scope=interface com.cloud.dc.DataCenter; id=1 at org.apache.cloudstack.engine.cloud.entity.api.VMEntityManagerImpl.reserveVirtualMachine(VMEntityManagerImpl.java:214) at org.apache.cloudstack.engine.cloud.entity.api.VirtualMachineEntityImpl.reserve(VirtualMachineEntityImpl.java:200) at com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:3468) at com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:3123) at com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:3111) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317) at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:183) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150) at org.apache.cloudstack.network.contrail.management.EventUtils$EventInterceptor.invoke(EventUtils.java:106) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:161) at com.cloud.event.ActionEventInterceptor.invoke(ActionEventInterceptor.java:51) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:161) at org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:91) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172) at org.springframework.aop.framework.JdkDynamicAopProxy.invoke
RE: Unable to create VM
You have run out of IP addresses, should be visible on the Dashboard and/or on the Zone's resources page. --- 2015-01-21 00:46:52,595 DEBUG [c.c.u.d.T.Transaction] (Work-Job-Executor-4:ctx-b225fb2e job-222/job-223 ctx-6e4c92f9) Rolling back the transaction: Time = 7 Name = Work-Job-Executor-4; called by -TransactionLegacy.rollback:900-TransactionLegacy.removeUpTo:843-TransactionLegacy.close:667-Transaction.execute:41-IpAddressManagerImpl.fetchNewPublicIp:660-IpAddressManagerImpl.assignPublicIpAddress:647-DirectPodBasedNetworkGuru$2.doInTransactionWithoutResult:194-TransactionCallbackWithExceptionNoReturn.doInTransaction:25-TransactionCallbackWithExceptionNoReturn.doInTransaction:21-Transaction.execute:37-DirectPodBasedNetworkGuru.getIp:173-DirectPodBasedNetworkGuru.reserve:160 2015-01-21 00:46:52,596 INFO [c.c.v.VirtualMachineManagerImpl] (Work-Job-Executor-4:ctx-b225fb2e job-222/job-223 ctx-6e4c92f9) Insufficient capacity com.cloud.exception.InsufficientAddressCapacityException: Insufficient address capacityScope=interface com.cloud.dc.Pod; id=4 --- Somesh CloudPlatform Escalations Citrix Systems, Inc. -Original Message- From: Tilak Raj Singh [mailto:tila...@gmail.com] Sent: Tuesday, January 20, 2015 3:15 PM To: users@cloudstack.apache.org Subject: Unable to create VM Hello evryone, I am unable to create a VM. Have been stuck at this problem for days now. Using cloudstack 4.4.1. Configuration is as follows Management server 172.31.101.202 Pod 1 - private ip range 172.31.101.210 - 172.31.101.220 Guest IP range 172.31.101.230 - 172.31.101.250 Cluster1 - KVM Host1 - 172.31.101.202 Pod 2 - private ip range 172.31.132.140-172.31.132.150 Didnt ask for guest ip range here Cluster2 - KVM Host2 - 172.31.132.132 VM creation is successsful on Host1 but not on Host 2. Here are the error logs 2015-01-21 00:46:52,457 DEBUG [c.c.c.CapacityManagerImpl] (Work-Job-Executor-4:ctx-b225fb2e job-222/job-223 ctx-6e4c92f9) CPU STATS after allocation: for host: 12, old used: 0, old reserved: 0, actual total: 10656, total with overprovisioning: 10656; new used:500, reserved:0; requested cpu:500,alloc_from_last:false 2015-01-21 00:46:52,457 DEBUG [c.c.c.CapacityManagerImpl] (Work-Job-Executor-4:ctx-b225fb2e job-222/job-223 ctx-6e4c92f9) RAM STATS after allocation: for host: 12, old used: 0, old reserved: 0, total: 1936789504; new used: 536870912, reserved: 0; requested mem: 536870912,alloc_from_last:false 2015-01-21 00:46:52,459 DEBUG [c.c.h.d.HostDaoImpl] (ClusteredAgentManager Timer:ctx-687f4bdb) Resetting hosts suitable for reconnect 2015-01-21 00:46:52,460 DEBUG [c.c.h.d.HostDaoImpl] (ClusteredAgentManager Timer:ctx-687f4bdb) Completed resetting hosts suitable for reconnect 2015-01-21 00:46:52,460 DEBUG [c.c.h.d.HostDaoImpl] (ClusteredAgentManager Timer:ctx-687f4bdb) Acquiring hosts for clusters already owned by this management server 2015-01-21 00:46:52,461 DEBUG [c.c.h.d.HostDaoImpl] (ClusteredAgentManager Timer:ctx-687f4bdb) Completed acquiring hosts for clusters already owned by this management server 2015-01-21 00:46:52,461 DEBUG [c.c.h.d.HostDaoImpl] (ClusteredAgentManager Timer:ctx-687f4bdb) Acquiring hosts for clusters not owned by any management server 2015-01-21 00:46:52,461 DEBUG [c.c.h.d.HostDaoImpl] (ClusteredAgentManager Timer:ctx-687f4bdb) Completed acquiring hosts for clusters not owned by any management server 2015-01-21 00:46:52,513 DEBUG [c.c.v.VirtualMachineManagerImpl] (Work-Job-Executor-4:ctx-b225fb2e job-222/job-223 ctx-6e4c92f9) VM is being created in podId: 4 2015-01-21 00:46:52,520 DEBUG [o.a.c.e.o.NetworkOrchestrator] (Work-Job-Executor-4:ctx-b225fb2e job-222/job-223 ctx-6e4c92f9) Network id=204 is already implemented 2015-01-21 00:46:52,595 DEBUG [c.c.u.d.T.Transaction] (Work-Job-Executor-4:ctx-b225fb2e job-222/job-223 ctx-6e4c92f9) Rolling back the transaction: Time = 7 Name = Work-Job-Executor-4; called by -TransactionLegacy.rollback:900-TransactionLegacy.removeUpTo:843-TransactionLegacy.close:667-Transaction.execute:41-IpAddressManagerImpl.fetchNewPublicIp:660-IpAddressManagerImpl.assignPublicIpAddress:647-DirectPodBasedNetworkGuru$2.doInTransactionWithoutResult:194-TransactionCallbackWithExceptionNoReturn.doInTransaction:25-TransactionCallbackWithExceptionNoReturn.doInTransaction:21-Transaction.execute:37-DirectPodBasedNetworkGuru.getIp:173-DirectPodBasedNetworkGuru.reserve:160 2015-01-21 00:46:52,596 INFO [c.c.v.VirtualMachineManagerImpl] (Work-Job-Executor-4:ctx-b225fb2e job-222/job-223 ctx-6e4c92f9) Insufficient capacity com.cloud.exception.InsufficientAddressCapacityException: Insufficient address capacityScope=interface com.cloud.dc.Pod; id=4 at com.cloud.network.IpAddressManagerImpl$2.doInTransaction(IpAddressManagerImpl.java:743) at com.cloud.network.IpAddressManagerImpl$2.doInTransaction(IpAddressManagerImpl.java:660) at com.cloud.utils.db.Transaction.execute(Transaction.java:37) at
RE: Unable to create VM
But my dashboard shows nothing of that sort..ip addresses are available both management and guests...creating vm on host1 works successfully..the error comes only when it tries to create vm on host2 Can i provide any other info so that you can help me further?? can u please confrm my zone setup if that is right..i think there is problem somewhere in there.. On 21-Jan-2015 2:37 AM, Somesh Naidu somesh.na...@citrix.com wrote: You have run out of IP addresses, should be visible on the Dashboard and/or on the Zone's resources page. --- 2015-01-21 00:46:52,595 DEBUG [c.c.u.d.T.Transaction] (Work-Job-Executor-4:ctx-b225fb2e job-222/job-223 ctx-6e4c92f9) Rolling back the transaction: Time = 7 Name = Work-Job-Executor-4; called by -TransactionLegacy.rollback:900-TransactionLegacy.removeUpTo:843-TransactionLegacy.close:667-Transaction.execute:41-IpAddressManagerImpl.fetchNewPublicIp:660-IpAddressManagerImpl.assignPublicIpAddress:647-DirectPodBasedNetworkGuru$2.doInTransactionWithoutResult:194-TransactionCallbackWithExceptionNoReturn.doInTransaction:25-TransactionCallbackWithExceptionNoReturn.doInTransaction:21-Transaction.execute:37-DirectPodBasedNetworkGuru.getIp:173-DirectPodBasedNetworkGuru.reserve:160 2015-01-21 00:46:52,596 INFO [c.c.v.VirtualMachineManagerImpl] (Work-Job-Executor-4:ctx-b225fb2e job-222/job-223 ctx-6e4c92f9) Insufficient capacity com.cloud.exception.InsufficientAddressCapacityException: Insufficient address capacityScope=interface com.cloud.dc.Pod; id=4 --- Somesh CloudPlatform Escalations Citrix Systems, Inc. -Original Message- From: Tilak Raj Singh [mailto:tila...@gmail.com] Sent: Tuesday, January 20, 2015 3:15 PM To: users@cloudstack.apache.org Subject: Unable to create VM Hello evryone, I am unable to create a VM. Have been stuck at this problem for days now. Using cloudstack 4.4.1. Configuration is as follows Management server 172.31.101.202 Pod 1 - private ip range 172.31.101.210 - 172.31.101.220 Guest IP range 172.31.101.230 - 172.31.101.250 Cluster1 - KVM Host1 - 172.31.101.202 Pod 2 - private ip range 172.31.132.140-172.31.132.150 Didnt ask for guest ip range here Cluster2 - KVM Host2 - 172.31.132.132 VM creation is successsful on Host1 but not on Host 2. Here are the error logs 2015-01-21 00:46:52,457 DEBUG [c.c.c.CapacityManagerImpl] (Work-Job-Executor-4:ctx-b225fb2e job-222/job-223 ctx-6e4c92f9) CPU STATS after allocation: for host: 12, old used: 0, old reserved: 0, actual total: 10656, total with overprovisioning: 10656; new used:500, reserved:0; requested cpu:500,alloc_from_last:false 2015-01-21 00:46:52,457 DEBUG [c.c.c.CapacityManagerImpl] (Work-Job-Executor-4:ctx-b225fb2e job-222/job-223 ctx-6e4c92f9) RAM STATS after allocation: for host: 12, old used: 0, old reserved: 0, total: 1936789504; new used: 536870912, reserved: 0; requested mem: 536870912,alloc_from_last:false 2015-01-21 00:46:52,459 DEBUG [c.c.h.d.HostDaoImpl] (ClusteredAgentManager Timer:ctx-687f4bdb) Resetting hosts suitable for reconnect 2015-01-21 00:46:52,460 DEBUG [c.c.h.d.HostDaoImpl] (ClusteredAgentManager Timer:ctx-687f4bdb) Completed resetting hosts suitable for reconnect 2015-01-21 00:46:52,460 DEBUG [c.c.h.d.HostDaoImpl] (ClusteredAgentManager Timer:ctx-687f4bdb) Acquiring hosts for clusters already owned by this management server 2015-01-21 00:46:52,461 DEBUG [c.c.h.d.HostDaoImpl] (ClusteredAgentManager Timer:ctx-687f4bdb) Completed acquiring hosts for clusters already owned by this management server 2015-01-21 00:46:52,461 DEBUG [c.c.h.d.HostDaoImpl] (ClusteredAgentManager Timer:ctx-687f4bdb) Acquiring hosts for clusters not owned by any management server 2015-01-21 00:46:52,461 DEBUG [c.c.h.d.HostDaoImpl] (ClusteredAgentManager Timer:ctx-687f4bdb) Completed acquiring hosts for clusters not owned by any management server 2015-01-21 00:46:52,513 DEBUG [c.c.v.VirtualMachineManagerImpl] (Work-Job-Executor-4:ctx-b225fb2e job-222/job-223 ctx-6e4c92f9) VM is being created in podId: 4 2015-01-21 00:46:52,520 DEBUG [o.a.c.e.o.NetworkOrchestrator] (Work-Job-Executor-4:ctx-b225fb2e job-222/job-223 ctx-6e4c92f9) Network id=204 is already implemented 2015-01-21 00:46:52,595 DEBUG [c.c.u.d.T.Transaction] (Work-Job-Executor-4:ctx-b225fb2e job-222/job-223 ctx-6e4c92f9) Rolling back the transaction: Time = 7 Name = Work-Job-Executor-4; called by -TransactionLegacy.rollback:900-TransactionLegacy.removeUpTo:843-TransactionLegacy.close:667-Transaction.execute:41-IpAddressManagerImpl.fetchNewPublicIp:660-IpAddressManagerImpl.assignPublicIpAddress:647-DirectPodBasedNetworkGuru$2.doInTransactionWithoutResult:194-TransactionCallbackWithExceptionNoReturn.doInTransaction:25-TransactionCallbackWithExceptionNoReturn.doInTransaction:21-Transaction.execute:37-DirectPodBasedNetworkGuru.getIp:173-DirectPodBasedNetworkGuru.reserve:160 2015-01-21 00:46:52,596 INFO [c.c.v.VirtualMachineManagerImpl] (Work-Job-Executor-4:ctx-b225fb2e
RE: unable to create VM in ACS 4.4 hypervisor XenServer
Hi Harikrishna,
Using the newest 4.4 template published on Jenkins 11th of August, console vm
pauses on creation, and site2site vpn does not establish, please find the
following log
(secstorage-1:ctx-e286a12e) Exception while trying to start secondary storage vm
java.lang.RuntimeException: Job failed due to exception Resource [Host:1] is
unreachable: Host 1: Unable to start instance due to Unable to acquire lock on
VMTemplateStoragePool: 1
2014-08-12 15:40:23,424 INFO [o.a.c.s.SecondaryStorageManagerImpl]
(secstorage-1:ctx-e286a12e) Unable to start secondary storage vm for standby
capacity, secStorageVm vm Id : 1, will
recycle it and start a new one
2014-08-12 15:40:23,516 WARN [c.c.u.d.Merovingian2]
(secstorage-1:ctx-a2a2ee4c) Was unable to find lock for the key vm_instance1
and thread id 1337390742
Unable to start secondary storage vm for standby capacity, secStorageVm vm Id :
1, will recycle it and start a new one
2014-08-12 16:19:54,294 WARN [c.c.a.d.ParamGenericValidationWorker]
(catalina-exec-12:ctx-db2ae77e ctx-c67a1655) Received unknown parameters for
command listNetworks. Unknown parameters
: details
2014-08-12 16:20:16,077 ERROR [c.c.u.s.SshHelper] (DirectAgent-62:ctx-2c9a8866)
SSH execution of command /opt/cloud/bin/router_proxy.sh ipsectunnel.sh
169.254.1.216 -A -l 192.168.1.52 -n
172.16.0.0/16 -g 192.168.1.1 -r 10.2.2.85 -N 10.10.10.0/24 -e aes128-sha1 -i
aes128-sha1;modp1024 -t 86400 -T 3600 -s aminsamir -d 1 has an error status
code in return. result
output: inet 192.168.1.52/24 brd 192.168.1.255 scope global eth1
2014-08-12 16:20:16,248 WARN [o.a.c.a.c.u.v.CreateVpnConnectionCmd]
(API-Job-Executor-20:ctx-79acdf9f job-103 ctx-ac82ecba) Exception:
com.cloud.exception.ResourceUnavailableException: Resource
[Site2SiteVpnConnection:1] is unreachable: Failed to apply site-to-site VPN
2014-08-12 16:20:16,250 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
(API-Job-Executor-20:ctx-79acdf9f job-103) Complete async job-103, jobStatus:
FAILED, resultCode: 530, result:
org.apache.cloudstack.api.response.ExceptionResponse/null/{uuidList:[],errorcode:534,errortext:Resource
[Site2SiteVpnConnection:1] is unreachable: Failed to apply site-to-site
VPN}
Kind Regards
-Original Message-
From: Harikrishna Patnala [mailto:harikrishna.patn...@citrix.com]
Sent: Tuesday, 12 August 2014 12:59 PM
To: users@cloudstack.apache.org
Subject: Re: unable to create VM in ACS 4.4 hypervisor XenServer
Hi,
You are trying to deploy a FreeBSD 10 instance right !
Try following the steps mentioned in the blog
http://shankerbalan.net/blog/freebsd-10-on-cloudstack-xenserver/
I think you are using the
FreeBSD-10.0-RELEASE-amd64-disc1.isohttp://ftp.freebsd.org/pub/FreeBSD/ISO-IMAGES-amd64/10.0/FreeBSD-10.0-RELEASE-amd64-disc1.iso
to deploy VM.
Please give a try using
FreeBSD-10.0-RELEASE-amd64-bootonly.isohttp://ftp.freebsd.org/pub/FreeBSD/ISO-IMAGES-amd64/10.0/FreeBSD-10.0-RELEASE-amd64-bootonly.iso
Thanks
Harikrishna
On 11-Aug-2014, at 8:28 pm, motty cruz
motty.c...@gmail.commailto:motty.c...@gmail.com wrote:
Hi Erik,
the attached file is my log,
virtual router started, I can ping anywhere from virtual router; System VMs are
up as well, except I can't build any instances.
On Sat, Aug 9, 2014 at 3:44 AM, Erik Weber
terbol...@gmail.commailto:terbol...@gmail.com wrote:
Yes, paste your log :-)
Erik
9. aug. 2014 00:25 skrev motty cruz
motty.c...@gmail.commailto:motty.c...@gmail.com følgende:
Hello All,
I am having the issue Job failed due to exception Unable to create a
deployment for VM[User]i-2-18-VM] it was able to create router but not VM.
Systems VMs are up,
any suggestions?
Thanks,
i-2-23-vm.txt
Re: unable to create VM in ACS 4.4 hypervisor XenServer
Hi Erik,
the attached file is my log,
virtual router started, I can ping anywhere from virtual router; System VMs
are up as well, except I can't build any instances.
On Sat, Aug 9, 2014 at 3:44 AM, Erik Weber terbol...@gmail.com wrote:
Yes, paste your log :-)
Erik
9. aug. 2014 00:25 skrev motty cruz motty.c...@gmail.com følgende:
Hello All,
I am having the issue Job failed due to exception Unable to create a
deployment for VM[User]i-2-18-VM] it was able to create router but not
VM.
Systems VMs are up,
any suggestions?
Thanks,
2014-08-11 07:17:51,903 DEBUG [c.c.v.VirtualMachineManagerImpl]
(catalina-exec-1:ctx-4d749382 ctx-a95ca79d) Allocating entries for VM:
VM[User|i-2-23-VM]
2014-08-11 07:17:51,906 DEBUG [c.c.v.VirtualMachineManagerImpl]
(catalina-exec-1:ctx-4d749382 ctx-a95ca79d) Allocating nics for
VM[User|i-2-23-VM]
2014-08-11 07:17:51,907 DEBUG [o.a.c.e.o.NetworkOrchestrator]
(catalina-exec-1:ctx-4d749382 ctx-a95ca79d) Allocating nic for vm
VM[User|i-2-23-VM] in network
Ntwk[442b3502-7074-4b6c-9bd6-572c6eee20e9|Guest|8] with requested profile
NicProfile[0-0-null-null-null
2014-08-11 07:17:51,963 DEBUG [c.c.v.VirtualMachineManagerImpl]
(catalina-exec-1:ctx-4d749382 ctx-a95ca79d) Allocating disks for
VM[User|i-2-23-VM]
2014-08-11 07:17:51,976 DEBUG [c.c.v.VirtualMachineManagerImpl]
(catalina-exec-1:ctx-4d749382 ctx-a95ca79d) Allocation completed for VM:
VM[User|i-2-23-VM]
2014-08-11 07:17:51,976 DEBUG [c.c.v.UserVmManagerImpl]
(catalina-exec-1:ctx-4d749382 ctx-a95ca79d) Successfully allocated DB entry for
VM[User|i-2-23-VM]
2014-08-11 07:17:54,029 DEBUG [c.c.v.VirtualMachineManagerImpl]
(Work-Job-Executor-4:ctx-dc46ff90 job-273/job-274 ctx-2e2c9774) Successfully
transitioned to start state for VM[User|i-2-23-VM] reservation id =
5d6a15eb-ef32-48b6-9d50-e73222f15d5b
2014-08-11 07:17:54,097 DEBUG [c.c.v.VirtualMachineManagerImpl]
(Work-Job-Executor-4:ctx-dc46ff90 job-273/job-274 ctx-2e2c9774) Deployment
found - P0=VM[User|i-2-23-VM],
P0=Dest[Zone(Id)-Pod(Id)-Cluster(Id)-Host(Id)-Storage(Volume(Id|Type--Pool(Id))]
: Dest[Zone(1)-Pod(1)-Cluster(1)-Host(2)-Storage(Volume(23|ROOT--Pool(1))]
2014-08-11 07:17:56,112 DEBUG [o.a.c.e.o.VolumeOrchestrator]
(Work-Job-Executor-4:ctx-dc46ff90 job-273/job-274 ctx-2e2c9774) Checking if we
need to prepare 1 volumes for VM[User|i-2-23-VM]
2014-08-11 07:17:56,225 DEBUG [c.c.a.t.Request]
(Work-Job-Executor-4:ctx-dc46ff90 job-273/job-274 ctx-2e2c9774) Seq
2-4235916924518662158: Sending { Cmd , MgmtId: 113356693032, via: 2(xen3),
Ver: v1, Flags: 100011,
[{org.apache.cloudstack.storage.command.CreateObjectCommand:{data:{org.apache.cloudstack.storage.to.VolumeObjectTO:{uuid:f341118e-626f-4b2c-a2f7-e3e1433cf0e4,volumeType:ROOT,dataStore:{org.apache.cloudstack.storage.to.PrimaryDataStoreTO:{uuid:xen-1,id:1,poolType:PreSetup,host:localhost,path:/xen-1,port:0,url:PreSetup://localhost/xen-1/?ROLE=PrimarySTOREUUID=xen-1}},name:ROOT-23,size:21474836480,volumeId:23,vmName:i-2-23-VM,accountId:2,format:VHD,id:23,deviceId:0,hypervisorType:XenServer}},wait:0}}]
}
2014-08-11 07:17:56,226 DEBUG [c.c.a.t.Request]
(Work-Job-Executor-4:ctx-dc46ff90 job-273/job-274 ctx-2e2c9774) Seq
2-4235916924518662158: Executing: { Cmd , MgmtId: 113356693032, via: 2(xen3),
Ver: v1, Flags: 100011,
[{org.apache.cloudstack.storage.command.CreateObjectCommand:{data:{org.apache.cloudstack.storage.to.VolumeObjectTO:{uuid:f341118e-626f-4b2c-a2f7-e3e1433cf0e4,volumeType:ROOT,dataStore:{org.apache.cloudstack.storage.to.PrimaryDataStoreTO:{uuid:xen-1,id:1,poolType:PreSetup,host:localhost,path:/xen-1,port:0,url:PreSetup://localhost/xen-1/?ROLE=PrimarySTOREUUID=xen-1}},name:ROOT-23,size:21474836480,volumeId:23,vmName:i-2-23-VM,accountId:2,format:VHD,id:23,deviceId:0,hypervisorType:XenServer}},wait:0}}]
}
2014-08-11 07:17:59,282 DEBUG [c.c.a.t.Request]
(Work-Job-Executor-4:ctx-dc46ff90 job-273/job-274 ctx-2e2c9774) Seq
2-4235916924518662159: Sending { Cmd , MgmtId: 113356693032, via: 2(xen3),
Ver: v1, Flags: 100011,
[{com.cloud.agent.api.StartCommand:{vm:{id:23,name:i-2-23-VM,bootloader:CD,type:User,cpus:2,minSpeed:2000,maxSpeed:2000,minRam:2147483648,maxRam:2147483648,arch:x86_64,os:FreeBSD
Re: unable to create VM in ACS 4.4 hypervisor XenServer
Hi, You are trying to deploy a FreeBSD 10 instance right ! Try following the steps mentioned in the blog http://shankerbalan.net/blog/freebsd-10-on-cloudstack-xenserver/ I think you are using the FreeBSD-10.0-RELEASE-amd64-disc1.isohttp://ftp.freebsd.org/pub/FreeBSD/ISO-IMAGES-amd64/10.0/FreeBSD-10.0-RELEASE-amd64-disc1.iso to deploy VM. Please give a try using FreeBSD-10.0-RELEASE-amd64-bootonly.isohttp://ftp.freebsd.org/pub/FreeBSD/ISO-IMAGES-amd64/10.0/FreeBSD-10.0-RELEASE-amd64-bootonly.iso Thanks Harikrishna On 11-Aug-2014, at 8:28 pm, motty cruz motty.c...@gmail.commailto:motty.c...@gmail.com wrote: Hi Erik, the attached file is my log, virtual router started, I can ping anywhere from virtual router; System VMs are up as well, except I can't build any instances. On Sat, Aug 9, 2014 at 3:44 AM, Erik Weber terbol...@gmail.commailto:terbol...@gmail.com wrote: Yes, paste your log :-) Erik 9. aug. 2014 00:25 skrev motty cruz motty.c...@gmail.commailto:motty.c...@gmail.com følgende: Hello All, I am having the issue Job failed due to exception Unable to create a deployment for VM[User]i-2-18-VM] it was able to create router but not VM. Systems VMs are up, any suggestions? Thanks, i-2-23-vm.txt
Re: unable to create VM in ACS 4.4 hypervisor XenServer
Yes, paste your log :-) Erik 9. aug. 2014 00:25 skrev motty cruz motty.c...@gmail.com følgende: Hello All, I am having the issue Job failed due to exception Unable to create a deployment for VM[User]i-2-18-VM] it was able to create router but not VM. Systems VMs are up, any suggestions? Thanks,
