Re: Unable to start a VM due to insufficient capacity CS 4.15.2 [urgent]

[Vivek Kumar]

Hello Oliver,

You will need to study the cloud-init. It works pretty well with all below 
mentioned OS. You can achieve a lot more then Hostname, Password and grow 
partition. You should use standard partition rather than LVM and there should 
be no portion after the root partition. Cloud-init will auto resize the 
partition if it finds any free sector in backend HDD.  You may also need to 
install few extra packages like - cloud-utils-growpart. Just have a look on the 
document. 

However, you can achieve same with Window’s instance as well. Cloud base-init 
works with windows and it provides the same functionality that way cloud-init 
provides with Linux OS.

Please find the link below - 

For Linux - 
https://cloudinit.readthedocs.io/en/latest/topics/modules.html#growpart 




For Windows - 
https://cloudbase-init.readthedocs.io/en/latest/config.html#cloudstack 





Vivek Kumar
Sr. Manager - Cloud & DevOps
TechOps | Indiqus Technologies

vivek.ku...@indiqus.com 
www.indiqus.com 




> On 12-Jul-2022, at 10:02 PM, Olivier GUIN  wrote:
> 
> Hello Vivek,
> 
> Can you help me to create template with xcp-ng.
> 
> Debian, Ubuntu and CentOS, also hostname, password, it's OK but Grow 
> partition not !
> 
> Best regards,
> 
> Olivier
> 
> Le 12/07/2022 à 11:10, Vivek Kumar a écrit :
>> Hello Oliver,
>> 
>> 
>> Can you check the path of your vhd in DB and then check on your XenServer. 
>> If this is giving error for ROOT disk then mention the ROOT disk name and if 
>> it is data disk then mention the data disk name.
>> 
>> 1- select * from volumes where name = ‘ROOT-’; ( Note the PATH ).
>> 2- Go to your XenServer and search - xe vdi-list name-label = ‘ROOT-***’
>> 
>> Check if the UUID from above XenServer command is matching with the path 
>> from DB. If not then try to manually update the path ( Note the UUID from xe 
>> vdi-list command and update in the volume table for that disk ).
>> 
>> 
>> 
>> 
>> Vivek Kumar
>> Sr. Manager - Cloud & DevOps
>> TechOps | Indiqus Technologies
>> 
>> vivek.ku...@indiqus.com  
>> >
>>  www.indiqus.com  > >
>> 
>> 
>> 
>> 
>>> On 12-Jul-2022, at 7:16 PM, Olivier GUIN 
>>>  wrote:
>>> 
>>> New message !
>>> 
>>> 2022-07-12 10:39:55,634 WARN [c.c.h.x.r.CitrixResourceBase] 
>>> (DirectAgent-245:ctx-055d42cb) (logid:d08a2c97) Unable to start i-40-76-VM 
>>> due to
>>> The uuid you supplied was invalid.
>>> 
>>> 2022-07-12 10:39:55,652 WARN [c.c.h.x.r.CitrixResourceBase] 
>>> (DirectAgent-245:ctx-055d42cb) (logid:d08a2c97) Unable to clean up VBD due 
>>> to
>>> You gave an invalid object reference. The object may have recently been 
>>> deleted. The class parameter gives the type of reference given, and the 
>>> handle parameter echoes the bad value given.
>>> 
>>> ?
>>> 
>>> Le 12/07/2022 à 09:16, Olivier GUIN a écrit :
 Hi there,
 
 I have a message 'Unable to start a VM due to insufficient capacity'I 
 can't find the problem.
 
 I have this problem on only 2 VMs!
 
 2022-07-12 09:00:10,692 ERROR [c.c.a.ApiAsyncJobDispatcher] 
 (API-Job-Executor-29:ctx-870c9fde job-462574) (logid:760cc3b8) Unexpected 
 exception while executing 
 org.apache.cloudstack.api.command.admin.vm.StartVMCmdByAdmin
 com.cloud.utils.exception.CloudRuntimeException: Unable to start a VM due 
 to insufficient capacity
 at 
 com.cloud.vm.VirtualMachineManagerImpl.start(VirtualMachineManagerImpl.java:751)
 at 
 org.apache.cloudstack.engine.cloud.entity.api.VMEntityManagerImpl.deployVirtualMachine(VMEntityManagerImpl.java:255)
 at 
 org.apache.cloudstack.engine.cloud.entity.api.VirtualMachineEntityImpl.deploy(VirtualMachineEntityImpl.java:214)
 at 
 com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:4938)
 at 
 com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:2897)
 at jdk.internal.reflect.GeneratedMethodAccessor940.invoke(Unknown Source)
 at 
 java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
 at java.base/java.lang.reflect.Method.invoke(Method.java:566)
 at 
 org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:344)
 at 
 org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:198)
 at 
 org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:163)
 at 
 

[SOLVE] Unable to start a VM due to insufficient capacity CS 4.15.2 [urgent]

[Olivier GUIN]

Hello Vivek,

It's OK now,

Thank's a lot

Olivier

Le 12/07/2022 à 11:10, Vivek Kumar a écrit :


Hello Oliver,


Can you check the path of your vhd in DB and then check on your XenServer. If 
this is giving error for ROOT disk then mention the ROOT disk name and if it is 
data disk then mention the data disk name.

1- select * from volumes where name = ‘ROOT-’; ( Note the PATH ).
2- Go to your XenServer and search - xe vdi-list name-label = ‘ROOT-***’

Check if the UUID from above XenServer command is matching with the path from 
DB. If not then try to manually update the path ( Note the UUID from xe 
vdi-list command and update in the volume table for that disk ).




Vivek Kumar
Sr. Manager - Cloud & DevOps
TechOps | Indiqus Technologies

vivek.ku...@indiqus.com 
www.indiqus.com 





On 12-Jul-2022, at 7:16 PM, Olivier GUIN  
wrote:

New message !

2022-07-12 10:39:55,634 WARN [c.c.h.x.r.CitrixResourceBase] 
(DirectAgent-245:ctx-055d42cb) (logid:d08a2c97) Unable to start i-40-76-VM due 
to
The uuid you supplied was invalid.

2022-07-12 10:39:55,652 WARN [c.c.h.x.r.CitrixResourceBase] 
(DirectAgent-245:ctx-055d42cb) (logid:d08a2c97) Unable to clean up VBD due to
You gave an invalid object reference.  The object may have recently been 
deleted.  The class parameter gives the type of reference given, and the handle 
parameter echoes the bad value given.

?

Le 12/07/2022 à 09:16, Olivier GUIN a écrit :

Hi there,

I have a message 'Unable to start a VM due to insufficient capacity'I can't 
find the problem.

I have this problem on only 2 VMs!

2022-07-12 09:00:10,692 ERROR [c.c.a.ApiAsyncJobDispatcher] 
(API-Job-Executor-29:ctx-870c9fde job-462574) (logid:760cc3b8) Unexpected 
exception while executing 
org.apache.cloudstack.api.command.admin.vm.StartVMCmdByAdmin
com.cloud.utils.exception.CloudRuntimeException: Unable to start a VM due to 
insufficient capacity
 at 
com.cloud.vm.VirtualMachineManagerImpl.start(VirtualMachineManagerImpl.java:751)
 at 
org.apache.cloudstack.engine.cloud.entity.api.VMEntityManagerImpl.deployVirtualMachine(VMEntityManagerImpl.java:255)
 at 
org.apache.cloudstack.engine.cloud.entity.api.VirtualMachineEntityImpl.deploy(VirtualMachineEntityImpl.java:214)
 at 
com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:4938)
 at 
com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:2897)
 at jdk.internal.reflect.GeneratedMethodAccessor940.invoke(Unknown 
Source)
 at 
java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
 at java.base/java.lang.reflect.Method.invoke(Method.java:566)
 at 
org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:344)
 at 
org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:198)
 at 
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:163)
 at 
org.apache.cloudstack.network.contrail.management.EventUtils$EventInterceptor.invoke(EventUtils.java:107)
 at 
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:175)
 at 
com.cloud.event.ActionEventInterceptor.invoke(ActionEventInterceptor.java:51)
 at 
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:175)
 at 
org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:97)
 at 
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:186)
 at 
org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:215)
 at com.sun.proxy.$Proxy127.startVirtualMachine(Unknown Source)
 at 
org.apache.cloudstack.api.command.user.vm.StartVMCmd.execute(StartVMCmd.java:169)
 at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:156)
 at 
com.cloud.api.ApiAsyncJobDispatcher.runJob(ApiAsyncJobDispatcher.java:108)
 at 
org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.runInContext(AsyncJobManagerImpl.java:620)
 at 
org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:48)
 at 
org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:55)
 at 
org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:102)
 at 
org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:52)
 at 
org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:45)
 at 

Re: Unable to start a VM due to insufficient capacity CS 4.15.2 [urgent]

[Vivek Kumar]

Hello Oliver, 


Can you check the path of your vhd in DB and then check on your XenServer. If 
this is giving error for ROOT disk then mention the ROOT disk name and if it is 
data disk then mention the data disk name.

1- select * from volumes where name = ‘ROOT-’; ( Note the PATH ).
2- Go to your XenServer and search - xe vdi-list name-label = ‘ROOT-***’

Check if the UUID from above XenServer command is matching with the path from 
DB. If not then try to manually update the path ( Note the UUID from xe 
vdi-list command and update in the volume table for that disk ).




Vivek Kumar
Sr. Manager - Cloud & DevOps
TechOps | Indiqus Technologies

vivek.ku...@indiqus.com 
www.indiqus.com 




> On 12-Jul-2022, at 7:16 PM, Olivier GUIN  
> wrote:
> 
> New message !
> 
> 2022-07-12 10:39:55,634 WARN [c.c.h.x.r.CitrixResourceBase] 
> (DirectAgent-245:ctx-055d42cb) (logid:d08a2c97) Unable to start i-40-76-VM 
> due to
> The uuid you supplied was invalid.
> 
> 2022-07-12 10:39:55,652 WARN [c.c.h.x.r.CitrixResourceBase] 
> (DirectAgent-245:ctx-055d42cb) (logid:d08a2c97) Unable to clean up VBD due to
> You gave an invalid object reference.  The object may have recently been 
> deleted.  The class parameter gives the type of reference given, and the 
> handle parameter echoes the bad value given.
> 
> ?
> 
> Le 12/07/2022 à 09:16, Olivier GUIN a écrit :
>> Hi there,
>> 
>> I have a message 'Unable to start a VM due to insufficient capacity'I can't 
>> find the problem.
>> 
>> I have this problem on only 2 VMs!
>> 
>> 2022-07-12 09:00:10,692 ERROR [c.c.a.ApiAsyncJobDispatcher] 
>> (API-Job-Executor-29:ctx-870c9fde job-462574) (logid:760cc3b8) Unexpected 
>> exception while executing 
>> org.apache.cloudstack.api.command.admin.vm.StartVMCmdByAdmin
>> com.cloud.utils.exception.CloudRuntimeException: Unable to start a VM due to 
>> insufficient capacity
>> at 
>> com.cloud.vm.VirtualMachineManagerImpl.start(VirtualMachineManagerImpl.java:751)
>> at 
>> org.apache.cloudstack.engine.cloud.entity.api.VMEntityManagerImpl.deployVirtualMachine(VMEntityManagerImpl.java:255)
>> at 
>> org.apache.cloudstack.engine.cloud.entity.api.VirtualMachineEntityImpl.deploy(VirtualMachineEntityImpl.java:214)
>> at 
>> com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:4938)
>> at 
>> com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:2897)
>> at jdk.internal.reflect.GeneratedMethodAccessor940.invoke(Unknown 
>> Source)
>> at 
>> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>> at java.base/java.lang.reflect.Method.invoke(Method.java:566)
>> at 
>> org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:344)
>> at 
>> org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:198)
>> at 
>> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:163)
>> at 
>> org.apache.cloudstack.network.contrail.management.EventUtils$EventInterceptor.invoke(EventUtils.java:107)
>> at 
>> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:175)
>> at 
>> com.cloud.event.ActionEventInterceptor.invoke(ActionEventInterceptor.java:51)
>> at 
>> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:175)
>> at 
>> org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:97)
>> at 
>> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:186)
>> at 
>> org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:215)
>> at com.sun.proxy.$Proxy127.startVirtualMachine(Unknown Source)
>> at 
>> org.apache.cloudstack.api.command.user.vm.StartVMCmd.execute(StartVMCmd.java:169)
>> at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:156)
>> at 
>> com.cloud.api.ApiAsyncJobDispatcher.runJob(ApiAsyncJobDispatcher.java:108)
>> at 
>> org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.runInContext(AsyncJobManagerImpl.java:620)
>> at 
>> org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:48)
>> at 
>> org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:55)
>> at 
>> org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:102)
>> at 
>> org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:52)
>> at 
>> 

Re: Unable to start a VM due to insufficient capacity CS 4.15.2 [urgent]

[Olivier GUIN]

New message !

2022-07-12 10:39:55,634 WARN [c.c.h.x.r.CitrixResourceBase] 
(DirectAgent-245:ctx-055d42cb) (logid:d08a2c97) Unable to start 
i-40-76-VM due to

The uuid you supplied was invalid.

2022-07-12 10:39:55,652 WARN [c.c.h.x.r.CitrixResourceBase] 
(DirectAgent-245:ctx-055d42cb) (logid:d08a2c97) Unable to clean up VBD 
due to
You gave an invalid object reference.  The object may have recently been 
deleted.  The class parameter gives the type of reference given, and the 
handle parameter echoes the bad value given.


?

Le 12/07/2022 à 09:16, Olivier GUIN a écrit :

Hi there,

I have a message 'Unable to start a VM due to insufficient capacity'I 
can't find the problem.


I have this problem on only 2 VMs!

2022-07-12 09:00:10,692 ERROR [c.c.a.ApiAsyncJobDispatcher] 
(API-Job-Executor-29:ctx-870c9fde job-462574) (logid:760cc3b8) 
Unexpected exception while executing 
org.apache.cloudstack.api.command.admin.vm.StartVMCmdByAdmin
com.cloud.utils.exception.CloudRuntimeException: Unable to start a VM 
due to insufficient capacity
    at 
com.cloud.vm.VirtualMachineManagerImpl.start(VirtualMachineManagerImpl.java:751)
    at 
org.apache.cloudstack.engine.cloud.entity.api.VMEntityManagerImpl.deployVirtualMachine(VMEntityManagerImpl.java:255)
    at 
org.apache.cloudstack.engine.cloud.entity.api.VirtualMachineEntityImpl.deploy(VirtualMachineEntityImpl.java:214)
    at 
com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:4938)
    at 
com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:2897)
    at 
jdk.internal.reflect.GeneratedMethodAccessor940.invoke(Unknown Source)
    at 
java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)

    at java.base/java.lang.reflect.Method.invoke(Method.java:566)
    at 
org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:344)
    at 
org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:198)
    at 
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:163)
    at 
org.apache.cloudstack.network.contrail.management.EventUtils$EventInterceptor.invoke(EventUtils.java:107)
    at 
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:175)
    at 
com.cloud.event.ActionEventInterceptor.invoke(ActionEventInterceptor.java:51)
    at 
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:175)
    at 
org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:97)
    at 
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:186)
    at 
org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:215)

    at com.sun.proxy.$Proxy127.startVirtualMachine(Unknown Source)
    at 
org.apache.cloudstack.api.command.user.vm.StartVMCmd.execute(StartVMCmd.java:169)

    at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:156)
    at 
com.cloud.api.ApiAsyncJobDispatcher.runJob(ApiAsyncJobDispatcher.java:108)
    at 
org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.runInContext(AsyncJobManagerImpl.java:620)
    at 
org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:48)
    at 
org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:55)
    at 
org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:102)
    at 
org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:52)
    at 
org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:45)
    at 
org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.run(AsyncJobManagerImpl.java:568)
    at 
java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
    at 
java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
    at 
java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
    at 
java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)

    at java.base/java.lang.Thread.run(Thread.java:829)
Caused by: com.cloud.exception.InsufficientServerCapacityException: 
Unable to create a deployment for VM[User|i-40-76-VM]Scope=interface 
com.cloud.dc.DataCenter; id=1
    at 
com.cloud.vm.VirtualMachineManagerImpl.orchestrateStart(VirtualMachineManagerImpl.java:1119)
    at 
com.cloud.vm.VirtualMachineManagerImpl.orchestrateStart(VirtualMachineManagerImpl.java:5502)
    at 

Unable to start a VM due to insufficient capacity CS 4.15.2 [urgent]

[Olivier GUIN]

Hi there,

I have a message 'Unable to start a VM due to insufficient capacity'I 
can't find the problem.


I have this problem on only 2 VMs!

2022-07-12 09:00:10,692 ERROR [c.c.a.ApiAsyncJobDispatcher] 
(API-Job-Executor-29:ctx-870c9fde job-462574) (logid:760cc3b8) 
Unexpected exception while executing 
org.apache.cloudstack.api.command.admin.vm.StartVMCmdByAdmin
com.cloud.utils.exception.CloudRuntimeException: Unable to start a VM 
due to insufficient capacity
    at 
com.cloud.vm.VirtualMachineManagerImpl.start(VirtualMachineManagerImpl.java:751)
    at 
org.apache.cloudstack.engine.cloud.entity.api.VMEntityManagerImpl.deployVirtualMachine(VMEntityManagerImpl.java:255)
    at 
org.apache.cloudstack.engine.cloud.entity.api.VirtualMachineEntityImpl.deploy(VirtualMachineEntityImpl.java:214)
    at 
com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:4938)
    at 
com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:2897)
    at 
jdk.internal.reflect.GeneratedMethodAccessor940.invoke(Unknown Source)
    at 
java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)

    at java.base/java.lang.reflect.Method.invoke(Method.java:566)
    at 
org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:344)
    at 
org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:198)
    at 
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:163)
    at 
org.apache.cloudstack.network.contrail.management.EventUtils$EventInterceptor.invoke(EventUtils.java:107)
    at 
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:175)
    at 
com.cloud.event.ActionEventInterceptor.invoke(ActionEventInterceptor.java:51)
    at 
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:175)
    at 
org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:97)
    at 
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:186)
    at 
org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:215)

    at com.sun.proxy.$Proxy127.startVirtualMachine(Unknown Source)
    at 
org.apache.cloudstack.api.command.user.vm.StartVMCmd.execute(StartVMCmd.java:169)

    at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:156)
    at 
com.cloud.api.ApiAsyncJobDispatcher.runJob(ApiAsyncJobDispatcher.java:108)
    at 
org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.runInContext(AsyncJobManagerImpl.java:620)
    at 
org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:48)
    at 
org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:55)
    at 
org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:102)
    at 
org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:52)
    at 
org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:45)
    at 
org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.run(AsyncJobManagerImpl.java:568)
    at 
java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
    at 
java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
    at 
java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
    at 
java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)

    at java.base/java.lang.Thread.run(Thread.java:829)
Caused by: com.cloud.exception.InsufficientServerCapacityException: 
Unable to create a deployment for VM[User|i-40-76-VM]Scope=interface 
com.cloud.dc.DataCenter; id=1
    at 
com.cloud.vm.VirtualMachineManagerImpl.orchestrateStart(VirtualMachineManagerImpl.java:1119)
    at 
com.cloud.vm.VirtualMachineManagerImpl.orchestrateStart(VirtualMachineManagerImpl.java:5502)
    at 
jdk.internal.reflect.GeneratedMethodAccessor908.invoke(Unknown Source)

    ... 17 more
2022-07-12 09:00:10,694 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl] 
(API-Job-Executor-29:ctx-870c9fde job-462574) (logid:760cc3b8) Complete 
async job-462574, jobStatus: FAILED, resultCode: 530, result: 
org.apache.cloudstack.api.response.ExceptionResponse/null/{"uuidList":[],"errorcode":"530","errortext":"Unable 
to start a VM due to insufficient capacity"}


Can someone help me?

Best regards,
Olivier

Re: Unable to start a VM due to insufficient capacity

[Michael Kesper]

Am 02.09.21 um 09:54 schrieb technologyrss.mail:
> *Hi,*
> 
> I setup Advanced zone using *ACS v4.15.1* but can't instance properly. I 
> attached ACS log file with my system dashboard as like below image.
> 
> For small environment for testing purposes. All servers are centos 7.8 with 
> separate NFS storage.
> 
> *This is ACS log.*

Please do not post screenshots of logfiles but the text instead.

Michael



OpenPGP_signature
Description: OpenPGP digital signature

Re: Unable to start a VM due to insufficient capacity

[Ivan Kudryavtsev]

Hi, the actual error is earlier (above) the mentioned log part. Please
provide about 100 lines before.

On Thu, Sep 2, 2021 at 2:55 PM technologyrss.mail <
technologyrss.m...@gmail.com> wrote:

> *Hi,*
>
> I setup Advanced zone using *ACS v4.15.1* but can't instance properly. I
> attached ACS log file with my system dashboard as like below image.
>
> For small environment for testing purposes. All servers are centos 7.8
> with separate NFS storage.
>
> *This is ACS log.*
>
>
> *This is web browser error when I create instance.*
>
>
> *This is my server system capacity,*
>
>
> Please give me some idea what is issue for my system capacity?
>
>
> *---*
> *alamin*
>
>
>

Re: Unable to start a VM due to insufficient capacity

[pradeep pal]

Hi,

Ok, let me check.

Thanks
Pradeep


Get Outlook for iOS

From: li jerry 
Sent: Sunday, December 1, 2019 7:55:18 AM
To: users@cloudstack.apache.org 
Subject: 回复: Unable to start a VM due to insufficient capacity

Please check the connection between your XenServer and NFS primary storage


-邮件原件-
发件人: pradeep pal 
发送时间: 2019年12月1日 7:23
收件人: users@cloudstack.apache.org
主题: Unable to start a VM due to insufficient capacity



Hi,

I am new for the CloudStack.


I have installed and configure ACS 4.11.3.0+mysql5.6+XenServer 7.1.CU2 in my 
office.

But when we launch instance I always get "Unable to start a VM due to 
insufficient capacity" Can anyone help me to solve this issue.

Please find the attached log.


2019-12-01 02:58:13,483 ERROR [c.c.a.ApiAsyncJobDispatcher] 
(API-Job-Executor-4:ctx-a1580e0a job-90) (logid:ede69855) Unexpected exception 
while executing org.apache.cloudstack.api.command.admin.vm.DeployVMCmdByAdmin

com.cloud.utils.exception.CloudRuntimeException: Unable to start a VM due to 
insufficient capacity

Caused by: com.cloud.exception.InsufficientServerCapacityException: Unable to 
create a deployment for VM[User|i-2-13-VM]Scope=interface 
com.cloud.dc.DataCenter; id=1

2019-12-01 02:58:13,486 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl] 
(API-Job-Executor-4:ctx-a1580e0a job-90) (logid:ede69855) Complete async 
job-90, jobStatus: FAILED, resultCode: 530, result: 
org.apache.cloudstack.api.response.ExceptionResponse/null/{"uuidList":[],"errorcode":530,"errortext":"Unable
 to start a VM due to insufficient capacity"}

2019-12-01 03:07:17,393 ERROR [c.c.c.ClusterServiceServletContainer] 
(Thread-20:null) (logid:) Unexpected exception

2019-12-01 03:08:29,357 WARN  [n.s.e.c.ConfigurationFactory] (main:null) 
(logid:) No configuration found. Configuring ehcache from ehcache-failsafe.xml  
found in the classpath: 
jar:file:/usr/share/cloudstack-management/lib/cloudstack-4.11.3.0.jar!/ehcache-failsafe.xml

2019-12-01 03:08:50,346 INFO  [c.c.h.x.r.XenServerConnectionPool] (main:null) 
(logid:) XenServer Connection Pool Configs: sleep.interval.on.error=1

2019-12-01 03:08:59,000 ERROR [c.c.u.s.SshHelper] 
(AgentTaskPool-1:ctx-55835787) (logid:58f334e3) SSH execution of command xe 
sm-list | grep "resigning of duplicates" has an error status code in return. 
Result output:

2019-12-01 03:08:59,124 ERROR [c.c.u.s.SshHelper] 
(AgentTaskPool-2:ctx-79d54dc9) (logid:b94602f7) SSH execution of command xe 
sm-list | grep "resigning of duplicates" has an error status code in return. 
Result output:

com.cloud.utils.exception.CloudRuntimeException: Unable to setup heartbeat file 
entry on SR 1562e840-29e3-ba00-e148-6dad6353042a due to #3# Unable to find the 
host uuid: 0e9f60c3-cfb7-4038-b00f-319d7e22d7f6

2019-12-01 03:09:10,715 INFO  [c.c.u.e.CSExceptionErrorCode] 
(AgentTaskPool-2:ctx-79d54dc9) (logid:b94602f7) Could not find exception: 
com.cloud.exception.ConnectionException in error code list for exceptions

2019-12-01 03:09:10,715 WARN  [c.c.a.m.AgentManagerImpl] 
(AgentTaskPool-2:ctx-79d54dc9) (logid:b94602f7) Monitor StoragePoolMonitor says 
there is an error in the connect process for 4 due to Unable to connect host 4 
to storage pool id 1 due to com.cloud.utils.exception.CloudRuntimeException: 
Unable establish connection from storage head to storage pool 1 due to 
ModifyStoragePoolCommand add XenAPIException:Unable to setup heartbeat file 
entry on SR 1562e840-29e3-ba00-e148-6dad6353042a due to #3# Unable to find the 
host uuid: 0e9f60c3-cfb7-4038-b00f-319d7e22d7f6 
host:0e9f60c3-cfb7-4038-b00f-319d7e22d7f6 pool: 172.29.1.97/nfs/export/primary1

com.cloud.exception.ConnectionException: Unable to connect host 4 to storage 
pool id 1 due to com.cloud.utils.exception.CloudRuntimeException: Unable 
establish connection from storage head to storage pool 1 due to 
ModifyStoragePoolCommand add XenAPIException:Unable to setup heartbeat file 
entry on SR 1562e840-29e3-ba00-e148-6dad6353042a due to #3# Unable to find the 
host uuid: 0e9f60c3-cfb7-4038-b00f-319d7e22d7f6 
host:0e9f60c3-cfb7-4038-b00f-319d7e22d7f6 pool: 172.29.1.97/nfs/export/primary1

Caused by: com.cloud.utils.exception.CloudRuntimeException: Unable establish 
connection from storage head to storage pool 1 due to ModifyStoragePoolCommand 
add XenAPIException:Unable to setup heartbeat file entry on SR 
1562e840-29e3-ba00-e148-6dad6353042a due to #3# Unable to find the host uuid: 
0e9f60c3-cfb7-4038-b00f-319d7e22d7f6 host:0e9f60c3-cfb7-4038-b00f-319d7e22d7f6 
pool: 172.29.1.97/nfs/export/primary1

2019-12-01 03:10:27,667 ERROR [c.c.u.s.SshHelper] 
(AgentTaskPool-3:ctx-f701d1f9) (logid:ceb4daae) SSH execution of command xe 
sm-list | grep "resigning of duplicates" has an error status code in return. 
Result output:

2019-12-01 03:23:49,476 DEBUG [o.a.c.e.o.NetworkOrchestrator] 
(Work-Job-Executor-1:ctx-f035b3f6 job-99/job-100 ctx-1ee73f54) 

回复: Unable to start a VM due to insufficient capacity

[li jerry]

Please check the connection between your XenServer and NFS primary storage


-邮件原件-
发件人: pradeep pal  
发送时间: 2019年12月1日 7:23
收件人: users@cloudstack.apache.org
主题: Unable to start a VM due to insufficient capacity



Hi,

I am new for the CloudStack.


I have installed and configure ACS 4.11.3.0+mysql5.6+XenServer 7.1.CU2 in my 
office.

But when we launch instance I always get "Unable to start a VM due to 
insufficient capacity" Can anyone help me to solve this issue.

Please find the attached log.


2019-12-01 02:58:13,483 ERROR [c.c.a.ApiAsyncJobDispatcher] 
(API-Job-Executor-4:ctx-a1580e0a job-90) (logid:ede69855) Unexpected exception 
while executing org.apache.cloudstack.api.command.admin.vm.DeployVMCmdByAdmin

com.cloud.utils.exception.CloudRuntimeException: Unable to start a VM due to 
insufficient capacity

Caused by: com.cloud.exception.InsufficientServerCapacityException: Unable to 
create a deployment for VM[User|i-2-13-VM]Scope=interface 
com.cloud.dc.DataCenter; id=1

2019-12-01 02:58:13,486 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl] 
(API-Job-Executor-4:ctx-a1580e0a job-90) (logid:ede69855) Complete async 
job-90, jobStatus: FAILED, resultCode: 530, result: 
org.apache.cloudstack.api.response.ExceptionResponse/null/{"uuidList":[],"errorcode":530,"errortext":"Unable
 to start a VM due to insufficient capacity"}

2019-12-01 03:07:17,393 ERROR [c.c.c.ClusterServiceServletContainer] 
(Thread-20:null) (logid:) Unexpected exception

2019-12-01 03:08:29,357 WARN  [n.s.e.c.ConfigurationFactory] (main:null) 
(logid:) No configuration found. Configuring ehcache from ehcache-failsafe.xml  
found in the classpath: 
jar:file:/usr/share/cloudstack-management/lib/cloudstack-4.11.3.0.jar!/ehcache-failsafe.xml

2019-12-01 03:08:50,346 INFO  [c.c.h.x.r.XenServerConnectionPool] (main:null) 
(logid:) XenServer Connection Pool Configs: sleep.interval.on.error=1

2019-12-01 03:08:59,000 ERROR [c.c.u.s.SshHelper] 
(AgentTaskPool-1:ctx-55835787) (logid:58f334e3) SSH execution of command xe 
sm-list | grep "resigning of duplicates" has an error status code in return. 
Result output:

2019-12-01 03:08:59,124 ERROR [c.c.u.s.SshHelper] 
(AgentTaskPool-2:ctx-79d54dc9) (logid:b94602f7) SSH execution of command xe 
sm-list | grep "resigning of duplicates" has an error status code in return. 
Result output:

com.cloud.utils.exception.CloudRuntimeException: Unable to setup heartbeat file 
entry on SR 1562e840-29e3-ba00-e148-6dad6353042a due to #3# Unable to find the 
host uuid: 0e9f60c3-cfb7-4038-b00f-319d7e22d7f6

2019-12-01 03:09:10,715 INFO  [c.c.u.e.CSExceptionErrorCode] 
(AgentTaskPool-2:ctx-79d54dc9) (logid:b94602f7) Could not find exception: 
com.cloud.exception.ConnectionException in error code list for exceptions

2019-12-01 03:09:10,715 WARN  [c.c.a.m.AgentManagerImpl] 
(AgentTaskPool-2:ctx-79d54dc9) (logid:b94602f7) Monitor StoragePoolMonitor says 
there is an error in the connect process for 4 due to Unable to connect host 4 
to storage pool id 1 due to com.cloud.utils.exception.CloudRuntimeException: 
Unable establish connection from storage head to storage pool 1 due to 
ModifyStoragePoolCommand add XenAPIException:Unable to setup heartbeat file 
entry on SR 1562e840-29e3-ba00-e148-6dad6353042a due to #3# Unable to find the 
host uuid: 0e9f60c3-cfb7-4038-b00f-319d7e22d7f6 
host:0e9f60c3-cfb7-4038-b00f-319d7e22d7f6 pool: 172.29.1.97/nfs/export/primary1

com.cloud.exception.ConnectionException: Unable to connect host 4 to storage 
pool id 1 due to com.cloud.utils.exception.CloudRuntimeException: Unable 
establish connection from storage head to storage pool 1 due to 
ModifyStoragePoolCommand add XenAPIException:Unable to setup heartbeat file 
entry on SR 1562e840-29e3-ba00-e148-6dad6353042a due to #3# Unable to find the 
host uuid: 0e9f60c3-cfb7-4038-b00f-319d7e22d7f6 
host:0e9f60c3-cfb7-4038-b00f-319d7e22d7f6 pool: 172.29.1.97/nfs/export/primary1

Caused by: com.cloud.utils.exception.CloudRuntimeException: Unable establish 
connection from storage head to storage pool 1 due to ModifyStoragePoolCommand 
add XenAPIException:Unable to setup heartbeat file entry on SR 
1562e840-29e3-ba00-e148-6dad6353042a due to #3# Unable to find the host uuid: 
0e9f60c3-cfb7-4038-b00f-319d7e22d7f6 host:0e9f60c3-cfb7-4038-b00f-319d7e22d7f6 
pool: 172.29.1.97/nfs/export/primary1

2019-12-01 03:10:27,667 ERROR [c.c.u.s.SshHelper] 
(AgentTaskPool-3:ctx-f701d1f9) (logid:ceb4daae) SSH execution of command xe 
sm-list | grep "resigning of duplicates" has an error status code in return. 
Result output:

2019-12-01 03:23:49,476 DEBUG [o.a.c.e.o.NetworkOrchestrator] 
(Work-Job-Executor-1:ctx-f035b3f6 job-99/job-100 ctx-1ee73f54) (logid:0eb71d41) 
Cleaning up because we're unable to implement the network Ntwk[206|Guest|11]

com.cloud.exception.InsufficientVirtualNetworkCapacityException: Unable to 
allocate vnet as a part of network Ntwk[206|Guest|11] implement Scope=interface 

Unable to start a VM due to insufficient capacity

[pradeep pal]

Hi,

I am new for the CloudStack.


I have installed and configure ACS 4.11.3.0+mysql5.6+XenServer 7.1.CU2 in my 
office.

But when we launch instance I always get "Unable to start a VM due to 
insufficient capacity" Can anyone help me to solve this issue.

Please find the attached log.


2019-12-01 02:58:13,483 ERROR [c.c.a.ApiAsyncJobDispatcher] 
(API-Job-Executor-4:ctx-a1580e0a job-90) (logid:ede69855) Unexpected exception 
while executing org.apache.cloudstack.api.command.admin.vm.DeployVMCmdByAdmin

com.cloud.utils.exception.CloudRuntimeException: Unable to start a VM due to 
insufficient capacity

Caused by: com.cloud.exception.InsufficientServerCapacityException: Unable to 
create a deployment for VM[User|i-2-13-VM]Scope=interface 
com.cloud.dc.DataCenter; id=1

2019-12-01 02:58:13,486 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl] 
(API-Job-Executor-4:ctx-a1580e0a job-90) (logid:ede69855) Complete async 
job-90, jobStatus: FAILED, resultCode: 530, result: 
org.apache.cloudstack.api.response.ExceptionResponse/null/{"uuidList":[],"errorcode":530,"errortext":"Unable
 to start a VM due to insufficient capacity"}

2019-12-01 03:07:17,393 ERROR [c.c.c.ClusterServiceServletContainer] 
(Thread-20:null) (logid:) Unexpected exception

2019-12-01 03:08:29,357 WARN  [n.s.e.c.ConfigurationFactory] (main:null) 
(logid:) No configuration found. Configuring ehcache from ehcache-failsafe.xml  
found in the classpath: 
jar:file:/usr/share/cloudstack-management/lib/cloudstack-4.11.3.0.jar!/ehcache-failsafe.xml

2019-12-01 03:08:50,346 INFO  [c.c.h.x.r.XenServerConnectionPool] (main:null) 
(logid:) XenServer Connection Pool Configs: sleep.interval.on.error=1

2019-12-01 03:08:59,000 ERROR [c.c.u.s.SshHelper] 
(AgentTaskPool-1:ctx-55835787) (logid:58f334e3) SSH execution of command xe 
sm-list | grep "resigning of duplicates" has an error status code in return. 
Result output:

2019-12-01 03:08:59,124 ERROR [c.c.u.s.SshHelper] 
(AgentTaskPool-2:ctx-79d54dc9) (logid:b94602f7) SSH execution of command xe 
sm-list | grep "resigning of duplicates" has an error status code in return. 
Result output:

com.cloud.utils.exception.CloudRuntimeException: Unable to setup heartbeat file 
entry on SR 1562e840-29e3-ba00-e148-6dad6353042a due to #3# Unable to find the 
host uuid: 0e9f60c3-cfb7-4038-b00f-319d7e22d7f6

2019-12-01 03:09:10,715 INFO  [c.c.u.e.CSExceptionErrorCode] 
(AgentTaskPool-2:ctx-79d54dc9) (logid:b94602f7) Could not find exception: 
com.cloud.exception.ConnectionException in error code list for exceptions

2019-12-01 03:09:10,715 WARN  [c.c.a.m.AgentManagerImpl] 
(AgentTaskPool-2:ctx-79d54dc9) (logid:b94602f7) Monitor StoragePoolMonitor says 
there is an error in the connect process for 4 due to Unable to connect host 4 
to storage pool id 1 due to com.cloud.utils.exception.CloudRuntimeException: 
Unable establish connection from storage head to storage pool 1 due to 
ModifyStoragePoolCommand add XenAPIException:Unable to setup heartbeat file 
entry on SR 1562e840-29e3-ba00-e148-6dad6353042a due to #3# Unable to find the 
host uuid: 0e9f60c3-cfb7-4038-b00f-319d7e22d7f6 
host:0e9f60c3-cfb7-4038-b00f-319d7e22d7f6 pool: 172.29.1.97/nfs/export/primary1

com.cloud.exception.ConnectionException: Unable to connect host 4 to storage 
pool id 1 due to com.cloud.utils.exception.CloudRuntimeException: Unable 
establish connection from storage head to storage pool 1 due to 
ModifyStoragePoolCommand add XenAPIException:Unable to setup heartbeat file 
entry on SR 1562e840-29e3-ba00-e148-6dad6353042a due to #3# Unable to find the 
host uuid: 0e9f60c3-cfb7-4038-b00f-319d7e22d7f6 
host:0e9f60c3-cfb7-4038-b00f-319d7e22d7f6 pool: 172.29.1.97/nfs/export/primary1

Caused by: com.cloud.utils.exception.CloudRuntimeException: Unable establish 
connection from storage head to storage pool 1 due to ModifyStoragePoolCommand 
add XenAPIException:Unable to setup heartbeat file entry on SR 
1562e840-29e3-ba00-e148-6dad6353042a due to #3# Unable to find the host uuid: 
0e9f60c3-cfb7-4038-b00f-319d7e22d7f6 host:0e9f60c3-cfb7-4038-b00f-319d7e22d7f6 
pool: 172.29.1.97/nfs/export/primary1

2019-12-01 03:10:27,667 ERROR [c.c.u.s.SshHelper] 
(AgentTaskPool-3:ctx-f701d1f9) (logid:ceb4daae) SSH execution of command xe 
sm-list | grep "resigning of duplicates" has an error status code in return. 
Result output:

2019-12-01 03:23:49,476 DEBUG [o.a.c.e.o.NetworkOrchestrator] 
(Work-Job-Executor-1:ctx-f035b3f6 job-99/job-100 ctx-1ee73f54) (logid:0eb71d41) 
Cleaning up because we're unable to implement the network Ntwk[206|Guest|11]

com.cloud.exception.InsufficientVirtualNetworkCapacityException: Unable to 
allocate vnet as a part of network Ntwk[206|Guest|11] implement Scope=interface 
com.cloud.dc.DataCenter; id=1

com.cloud.exception.ResourceUnavailableException: Resource [DataCenter:1] is 
unreachable: Can't find at least one router!

2019-12-01 03:23:50,229 ERROR [c.c.v.VmWorkJobHandlerProxy] 

Re: Unable to start a VM due to insufficient capacity

[Yiping Zhang]

When you say there is enough resources on hosts, exactly what’s memory and cpu 
allocation on each of the hosts?  Unless you have updated following global 
settings, the default settings are to disable VM allocation if cluster’s 
overall CPU or memory allocation is over 75%, and you will get insufficient 
resources error when you creating new instances.

cluster.cpu.allocated.capacity.disablethreshold = 0.75
cluster.memory.allocated.capacity.disablethreshold = 0.75

There are other situations where you could also receive this error, such as if 
you specified wrong network or the tagged resources are not available (storage, 
host, etc, or wrong tag was specified) and so on.  This error message is pretty 
much useless as it is given, not to cloud operators or administrators anyway.

Yiping

On 4/21/17, 4:21 PM, "Marty Godsey"  wrote:

Without looking too deep into this it seems that there maybe a stuck task 
trying to snapshot the VHD.

result:
errorInfo: [OTHER_OPERATION_IN_PROGRESS, VDI, 
OpaqueRef:1d681250-d950-81ec-9f87-f7eb3d8b0cc1, snapshot]
  otherConfig: {}

Again, based on what you sent, I would look at any hung xapi tasks on the 
host in question.

Regards,
Marty Godsey
nSource Solutions

-Original Message-
From: J Andersons 
Sent: Friday, April 21, 2017 2:20 AM
To: users@cloudstack.apache.org
Subject: Unable to start a VM due to insufficient capacity

Hi!
Just like that it is impossible to start any vm. ACS4.8, Xenservers 6.5 
Unable to start a VM due to insufficient capacity. I can see in xencenter it is 
trying to start VM on all hosts but fails. Also there is enough resources on 
hosts.
Maybe its an XenServer issue, because it is also unable to stop VMS.

In log when starting VM:
2017-04-21 08:50:35,806 WARN  [c.c.h.x.r.CitrixResourceBase]
(DirectAgent-28:ctx-6bbd1566) (logid:91c36627) Task failed! Task 
record: uuid: a9ac4c12-a6ba-6d9a-556f-b5d88f8cd2d3
nameLabel: Async.VM.start_on
  nameDescription:
allowedOperations: []
currentOperations: {}
  created: Fri Apr 21 08:48:34 EEST 2017
 finished: Fri Apr 21 08:50:35 EEST 2017
   status: failure
   residentOn: com.xensource.xenapi.Host@c07df7eb
 progress: 1.0
 type: 
   result:
errorInfo: [OTHER_OPERATION_IN_PROGRESS, VDI, 
OpaqueRef:1d681250-d950-81ec-9f87-f7eb3d8b0cc1, snapshot]
  otherConfig: {}
subtaskOf: com.xensource.xenapi.Task@aaf13f6f
 subtasks: []

2017-04-21 08:50:35,818 WARN  [c.c.h.x.r.CitrixResourceBase]
(DirectAgent-28:ctx-6bbd1566) (logid:91c36627) Unable to start
VM(i-95-292-VM) on host(a6601054-b730-460a-b654-a29f1a5b8a1c) due to 
Task failed! Task record: uuid: 
a9ac4c12-a6ba-6d9a-556f-b5d88f8cd2d3
nameLabel: Async.VM.start_on
  nameDescription:
allowedOperations: []
currentOperations: {}
  created: Fri Apr 21 08:48:34 EEST 2017
 finished: Fri Apr 21 08:50:35 EEST 2017
   status: failure
   residentOn: com.xensource.xenapi.Host@c07df7eb
 progress: 1.0
 type: 
   result:
errorInfo: [OTHER_OPERATION_IN_PROGRESS, VDI, 
OpaqueRef:1d681250-d950-81ec-9f87-f7eb3d8b0cc1, snapshot]
  otherConfig: {}
subtaskOf: com.xensource.xenapi.Task@aaf13f6f
 subtasks: []

Task failed! Task record: uuid: 
a9ac4c12-a6ba-6d9a-556f-b5d88f8cd2d3
nameLabel: Async.VM.start_on
  nameDescription:
allowedOperations: []
currentOperations: {}
  created: Fri Apr 21 08:48:34 EEST 2017
 finished: Fri Apr 21 08:50:35 EEST 2017
   status: failure
   residentOn: com.xensource.xenapi.Host@c07df7eb
 progress: 1.0
 type: 
   result:
errorInfo: [OTHER_OPERATION_IN_PROGRESS, VDI, 
OpaqueRef:1d681250-d950-81ec-9f87-f7eb3d8b0cc1, snapshot]
  otherConfig: {}
subtaskOf: com.xensource.xenapi.Task@aaf13f6f
 subtasks: []

 at

com.cloud.hypervisor.xenserver.resource.CitrixResourceBase.checkForSuccess(CitrixResourceBase.java:461)
 at

com.cloud.hypervisor.xenserver.resource.CitrixResourceBase.startVM(CitrixResourceBase.java:4807)
 at

com.cloud.hypervisor.xenserver.resource.wrapper.xenbase.CitrixStartCommandWrapper.execute(CitrixStartCommandWrapper.java:126)
 at

RE: Unable to start a VM due to insufficient capacity

[Marty Godsey]

Without looking too deep into this it seems that there maybe a stuck task 
trying to snapshot the VHD.

result:
errorInfo: [OTHER_OPERATION_IN_PROGRESS, VDI, 
OpaqueRef:1d681250-d950-81ec-9f87-f7eb3d8b0cc1, snapshot]
  otherConfig: {}

Again, based on what you sent, I would look at any hung xapi tasks on the host 
in question.

Regards,
Marty Godsey
nSource Solutions

-Original Message-
From: J Andersons 
Sent: Friday, April 21, 2017 2:20 AM
To: users@cloudstack.apache.org
Subject: Unable to start a VM due to insufficient capacity

Hi!
Just like that it is impossible to start any vm. ACS4.8, Xenservers 6.5 Unable 
to start a VM due to insufficient capacity. I can see in xencenter it is trying 
to start VM on all hosts but fails. Also there is enough resources on hosts.
Maybe its an XenServer issue, because it is also unable to stop VMS.

In log when starting VM:
2017-04-21 08:50:35,806 WARN  [c.c.h.x.r.CitrixResourceBase]
(DirectAgent-28:ctx-6bbd1566) (logid:91c36627) Task failed! Task 
record: uuid: a9ac4c12-a6ba-6d9a-556f-b5d88f8cd2d3
nameLabel: Async.VM.start_on
  nameDescription:
allowedOperations: []
currentOperations: {}
  created: Fri Apr 21 08:48:34 EEST 2017
 finished: Fri Apr 21 08:50:35 EEST 2017
   status: failure
   residentOn: com.xensource.xenapi.Host@c07df7eb
 progress: 1.0
 type: 
   result:
errorInfo: [OTHER_OPERATION_IN_PROGRESS, VDI, 
OpaqueRef:1d681250-d950-81ec-9f87-f7eb3d8b0cc1, snapshot]
  otherConfig: {}
subtaskOf: com.xensource.xenapi.Task@aaf13f6f
 subtasks: []

2017-04-21 08:50:35,818 WARN  [c.c.h.x.r.CitrixResourceBase]
(DirectAgent-28:ctx-6bbd1566) (logid:91c36627) Unable to start
VM(i-95-292-VM) on host(a6601054-b730-460a-b654-a29f1a5b8a1c) due to 
Task failed! Task record: uuid: 
a9ac4c12-a6ba-6d9a-556f-b5d88f8cd2d3
nameLabel: Async.VM.start_on
  nameDescription:
allowedOperations: []
currentOperations: {}
  created: Fri Apr 21 08:48:34 EEST 2017
 finished: Fri Apr 21 08:50:35 EEST 2017
   status: failure
   residentOn: com.xensource.xenapi.Host@c07df7eb
 progress: 1.0
 type: 
   result:
errorInfo: [OTHER_OPERATION_IN_PROGRESS, VDI, 
OpaqueRef:1d681250-d950-81ec-9f87-f7eb3d8b0cc1, snapshot]
  otherConfig: {}
subtaskOf: com.xensource.xenapi.Task@aaf13f6f
 subtasks: []

Task failed! Task record: uuid: 
a9ac4c12-a6ba-6d9a-556f-b5d88f8cd2d3
nameLabel: Async.VM.start_on
  nameDescription:
allowedOperations: []
currentOperations: {}
  created: Fri Apr 21 08:48:34 EEST 2017
 finished: Fri Apr 21 08:50:35 EEST 2017
   status: failure
   residentOn: com.xensource.xenapi.Host@c07df7eb
 progress: 1.0
 type: 
   result:
errorInfo: [OTHER_OPERATION_IN_PROGRESS, VDI, 
OpaqueRef:1d681250-d950-81ec-9f87-f7eb3d8b0cc1, snapshot]
  otherConfig: {}
subtaskOf: com.xensource.xenapi.Task@aaf13f6f
 subtasks: []

 at
com.cloud.hypervisor.xenserver.resource.CitrixResourceBase.checkForSuccess(CitrixResourceBase.java:461)
 at
com.cloud.hypervisor.xenserver.resource.CitrixResourceBase.startVM(CitrixResourceBase.java:4807)
 at
com.cloud.hypervisor.xenserver.resource.wrapper.xenbase.CitrixStartCommandWrapper.execute(CitrixStartCommandWrapper.java:126)
 at
com.cloud.hypervisor.xenserver.resource.wrapper.xenbase.CitrixStartCommandWrapper.execute(CitrixStartCommandWrapper.java:53)
 at
com.cloud.hypervisor.xenserver.resource.wrapper.xenbase.CitrixRequestWrapper.execute(CitrixRequestWrapper.java:122)
 at
com.cloud.hypervisor.xenserver.resource.CitrixResourceBase.executeRequest(CitrixResourceBase.java:1677)
 at
com.cloud.agent.manager.DirectAgentAttache$Task.runInContext(DirectAgentAttache.java:315)
 at
org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:49)
 at
org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56)
 at
org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103)
 at
org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53)
 at
org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:46)
 at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
 at java.util.concurrent.FutureTask.run(FutureTask.java:262)
 at

Unable to start a VM due to insufficient capacity

[J Andersons]

Hi!
Just like that it is impossible to start any vm. ACS4.8, Xenservers 6.5
Unable to start a VM due to insufficient capacity. I can see in 
xencenter it is trying to start VM on all hosts but fails. Also there is 
enough resources on hosts.

Maybe its an XenServer issue, because it is also unable to stop VMS.

In log when starting VM:
2017-04-21 08:50:35,806 WARN  [c.c.h.x.r.CitrixResourceBase] 
(DirectAgent-28:ctx-6bbd1566) (logid:91c36627) Task failed! Task 
record: uuid: a9ac4c12-a6ba-6d9a-556f-b5d88f8cd2d3

   nameLabel: Async.VM.start_on
 nameDescription:
   allowedOperations: []
   currentOperations: {}
 created: Fri Apr 21 08:48:34 EEST 2017
finished: Fri Apr 21 08:50:35 EEST 2017
  status: failure
  residentOn: com.xensource.xenapi.Host@c07df7eb
progress: 1.0
type: 
  result:
   errorInfo: [OTHER_OPERATION_IN_PROGRESS, VDI, 
OpaqueRef:1d681250-d950-81ec-9f87-f7eb3d8b0cc1, snapshot]

 otherConfig: {}
   subtaskOf: com.xensource.xenapi.Task@aaf13f6f
subtasks: []

2017-04-21 08:50:35,818 WARN  [c.c.h.x.r.CitrixResourceBase] 
(DirectAgent-28:ctx-6bbd1566) (logid:91c36627) Unable to start 
VM(i-95-292-VM) on host(a6601054-b730-460a-b654-a29f1a5b8a1c) due to 
Task failed! Task record: uuid: 
a9ac4c12-a6ba-6d9a-556f-b5d88f8cd2d3

   nameLabel: Async.VM.start_on
 nameDescription:
   allowedOperations: []
   currentOperations: {}
 created: Fri Apr 21 08:48:34 EEST 2017
finished: Fri Apr 21 08:50:35 EEST 2017
  status: failure
  residentOn: com.xensource.xenapi.Host@c07df7eb
progress: 1.0
type: 
  result:
   errorInfo: [OTHER_OPERATION_IN_PROGRESS, VDI, 
OpaqueRef:1d681250-d950-81ec-9f87-f7eb3d8b0cc1, snapshot]

 otherConfig: {}
   subtaskOf: com.xensource.xenapi.Task@aaf13f6f
subtasks: []

Task failed! Task record: uuid: 
a9ac4c12-a6ba-6d9a-556f-b5d88f8cd2d3

   nameLabel: Async.VM.start_on
 nameDescription:
   allowedOperations: []
   currentOperations: {}
 created: Fri Apr 21 08:48:34 EEST 2017
finished: Fri Apr 21 08:50:35 EEST 2017
  status: failure
  residentOn: com.xensource.xenapi.Host@c07df7eb
progress: 1.0
type: 
  result:
   errorInfo: [OTHER_OPERATION_IN_PROGRESS, VDI, 
OpaqueRef:1d681250-d950-81ec-9f87-f7eb3d8b0cc1, snapshot]

 otherConfig: {}
   subtaskOf: com.xensource.xenapi.Task@aaf13f6f
subtasks: []

at 
com.cloud.hypervisor.xenserver.resource.CitrixResourceBase.checkForSuccess(CitrixResourceBase.java:461)
at 
com.cloud.hypervisor.xenserver.resource.CitrixResourceBase.startVM(CitrixResourceBase.java:4807)
at 
com.cloud.hypervisor.xenserver.resource.wrapper.xenbase.CitrixStartCommandWrapper.execute(CitrixStartCommandWrapper.java:126)
at 
com.cloud.hypervisor.xenserver.resource.wrapper.xenbase.CitrixStartCommandWrapper.execute(CitrixStartCommandWrapper.java:53)
at 
com.cloud.hypervisor.xenserver.resource.wrapper.xenbase.CitrixRequestWrapper.execute(CitrixRequestWrapper.java:122)
at 
com.cloud.hypervisor.xenserver.resource.CitrixResourceBase.executeRequest(CitrixResourceBase.java:1677)
at 
com.cloud.agent.manager.DirectAgentAttache$Task.runInContext(DirectAgentAttache.java:315)
at 
org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:49)
at 
org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56)
at 
org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103)
at 
org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53)
at 
org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:46)
at 
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)

at java.util.concurrent.FutureTask.run(FutureTask.java:262)
at 
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:178)
at 
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:292)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)

at java.lang.Thread.run(Thread.java:745)
2017-04-21 08:50:35,826 DEBUG [c.c.h.x.r.CitrixResourceBase] 
(DirectAgent-28:ctx-6bbd1566) (logid:91c36627) unable to destroy 
task(com.xensource.xenapi.Task@27d940e) on 
host(a6601054-b730-460a-b654-a29f1a5b8a1c) due to You 

Re: Unable to start a VM due to insufficient capacity

[Gian Paolo Buono]

Hi,

I solved, the problem was the affinity group.

Bye

On 01/21/2017 09:44 AM, Gian Paolo Buono wrote:
Hi all,

i have an installation of cloudstack with two hypervisor; one hypervistor is 
now down and when I try to start a vm i receive the following message:

Unable to start a VM due to insufficient capacity

The hypervisor is only to the 50% of RAM, how can I change  the behavior ?

Thanks

Unable to start a VM due to insufficient capacity

[Gian Paolo Buono]

Hi all,

i have an installation of cloudstack with two hypervisor; one hypervistor is 
now down and when I try to start a vm i receive the following message:

Unable to start a VM due to insufficient capacity

The hypervisor is only to the 50% of RAM, how can I change  the behavior ?

Thanks

[solved] CS 4.5.1: Unable to start a VM due to insufficient capacity

[Vadim Kimlaychuk]

This was my fault -- I have built NAS storage on FreeBSD and didn't add 
--alldirs option to /etc/exports file. So my sub-folders were not exported 
automatically. Mounting particlur folder failed at any host while root folders 
were accessable. 

Vadim

From: Vadim Kimlaychuk [vadim.kimlayc...@elion.ee]
Sent: Saturday, April 25, 2015 19:19
To: users@cloudstack.apache.org
Cc: dmi...@ant.ee
Subject: RE: CS 4.5.1:  Unable to start a VM due to insufficient capacity

Hi Timothy,

 I have mounted SS on the slave host manually (didn't restart anything 
yet), but the next VM started on the primary node has also failed with the same 
error. I don't think this is connected to host's mount points. Primary node has 
had this mount from the beggining and new VM fails on the primary as well.
At the same time templates (that are also located at SS) are executed 
correctly and VM-s are created on any host.  I don't understand which way ISO 
and template are different ?

Vadim.

From: Timothy Lothering [tlother...@datacentrix.co.za]
Sent: Saturday, April 25, 2015 16:19
To: users@cloudstack.apache.org
Cc: dmi...@ant.ee
Subject: RE: CS 4.5.1:  Unable to start a VM due to insufficient capacity

Hi Vadim,

Can you manually mount the SS on the Cluster Slave Node?

I had a similar issue, and in the end needed to reboot the host. Don't know if 
this would resolve your issue?

Regards,
Timothy Lothering
Solutions Architect
Managed Services

T: +27877415535
F: +27877415100
C: +27824904099
E: tlother...@datacentrix.co.za


DISCLAIMER NOTICE:

Everything in this e-mail and any attachments relating to the official business 
of Datacentrix Holdings Ltd. and its subsidiaries
('Datacentrix') is proprietary to Datacentrix. It is confidential, legally 
privileged and protected by law. Datacentrix does not
own and endorse any other content. Views and opinions are those of the sender 
unless clearly stated as being that of Datacentrix.
The person addressed in the e-mail is the sole authorised recipient. Please 
notify the sender immediately if it has unintentionally
reached you and do not read, disclose or use the content in any way. 
Datacentrix cannot assure that the integrity of this communication
has been maintained nor that it is free of errors, virus, interception or 
interference.
-Original Message-
From: Vadim Kimlaychuk [mailto:vadim.kimlayc...@elion.ee]
Sent: 25 April 2015 07:49 AM
To: users@cloudstack.apache.org
Cc: dmi...@ant.ee
Subject: CS 4.5.1: Unable to start a VM due to insufficient capacity

Hello all,

 After fresh install for subj. Got problem creating new VM from ISO.  
Installing VM from templates is working.  Management log said that :

2015-04-25 08:36:32,066 DEBUG [c.c.a.m.DirectAgentAttache] 
(DirectAgent-185:ctx-9207cdf3) Seq 2-635851972389374824: Executing request
2015-04-25 08:36:32,071 DEBUG [c.c.h.x.r.CitrixResourceBase] 
(DirectAgent-185:ctx-9207cdf3) 1. The VM i-2-13-VM is in Starting state.
2015-04-25 08:36:32,089 DEBUG [c.c.h.x.r.CitrixResourceBase] 
(DirectAgent-185:ctx-9207cdf3) Created VM 834101d6-e316-3fc9-5f8d-6c55f641d986 
for i-2-13-VM
2015-04-25 08:36:32,107 DEBUG [c.c.h.x.r.CitrixResourceBase] 
(DirectAgent-185:ctx-9207cdf3) VBD 0524ba7b-dcd9-f227-349e-caa83d486939 created 
for com.cloud.agent.api.to.DiskTO@5213a905
2015-04-25 08:36:32,254 WARN  [c.c.h.x.r.CitrixResourceBase] 
(DirectAgent-185:ctx-9207cdf3) createIsoSRbyURI failed! mountpoint: 
secondary.storage.ant.ee/export/secondary/template/tmpl/2/206 due to 
SR_BACKEND_FAILURE_222Could not mount the directory specified in Device 
Configuration SR_BACKEND_FAILURE_222Could not mount the directory specified in 
Device Configuration
at com.xensource.xenapi.Types.checkResponse(Types.java:2021)

   ISO file in storage present and uploaded using cloudstack UI. Secondary 
storage was mounted on the cluster node, but not on slave node.  I have created 
the same mount point on the slave, but problem still exists.  I have separate 
network for secondary storage -- may be this is a problem? Please, give me a 
hint

Thanks,

Vadim.

RE: CS 4.5.1: Unable to start a VM due to insufficient capacity

[Timothy Lothering]

Hi Vadim,

Can you manually mount the SS on the Cluster Slave Node?

I had a similar issue, and in the end needed to reboot the host. Don't know if 
this would resolve your issue?

Regards,
Timothy Lothering
Solutions Architect
Managed Services

T: +27877415535
F: +27877415100
C: +27824904099
E: tlother...@datacentrix.co.za


DISCLAIMER NOTICE: 

Everything in this e-mail and any attachments relating to the official business 
of Datacentrix Holdings Ltd. and its subsidiaries 
('Datacentrix') is proprietary to Datacentrix. It is confidential, legally 
privileged and protected by law. Datacentrix does not 
own and endorse any other content. Views and opinions are those of the sender 
unless clearly stated as being that of Datacentrix. 
The person addressed in the e-mail is the sole authorised recipient. Please 
notify the sender immediately if it has unintentionally 
reached you and do not read, disclose or use the content in any way. 
Datacentrix cannot assure that the integrity of this communication 
has been maintained nor that it is free of errors, virus, interception or 
interference.
-Original Message-
From: Vadim Kimlaychuk [mailto:vadim.kimlayc...@elion.ee] 
Sent: 25 April 2015 07:49 AM
To: users@cloudstack.apache.org
Cc: dmi...@ant.ee
Subject: CS 4.5.1: Unable to start a VM due to insufficient capacity

Hello all,

 After fresh install for subj. Got problem creating new VM from ISO.  
Installing VM from templates is working.  Management log said that :

2015-04-25 08:36:32,066 DEBUG [c.c.a.m.DirectAgentAttache] 
(DirectAgent-185:ctx-9207cdf3) Seq 2-635851972389374824: Executing request
2015-04-25 08:36:32,071 DEBUG [c.c.h.x.r.CitrixResourceBase] 
(DirectAgent-185:ctx-9207cdf3) 1. The VM i-2-13-VM is in Starting state.
2015-04-25 08:36:32,089 DEBUG [c.c.h.x.r.CitrixResourceBase] 
(DirectAgent-185:ctx-9207cdf3) Created VM 834101d6-e316-3fc9-5f8d-6c55f641d986 
for i-2-13-VM
2015-04-25 08:36:32,107 DEBUG [c.c.h.x.r.CitrixResourceBase] 
(DirectAgent-185:ctx-9207cdf3) VBD 0524ba7b-dcd9-f227-349e-caa83d486939 created 
for com.cloud.agent.api.to.DiskTO@5213a905
2015-04-25 08:36:32,254 WARN  [c.c.h.x.r.CitrixResourceBase] 
(DirectAgent-185:ctx-9207cdf3) createIsoSRbyURI failed! mountpoint: 
secondary.storage.ant.ee/export/secondary/template/tmpl/2/206 due to 
SR_BACKEND_FAILURE_222Could not mount the directory specified in Device 
Configuration SR_BACKEND_FAILURE_222Could not mount the directory specified in 
Device Configuration
at com.xensource.xenapi.Types.checkResponse(Types.java:2021)

   ISO file in storage present and uploaded using cloudstack UI. Secondary 
storage was mounted on the cluster node, but not on slave node.  I have created 
the same mount point on the slave, but problem still exists.  I have separate 
network for secondary storage -- may be this is a problem? Please, give me a 
hint

Thanks,

Vadim.

RE: CS 4.5.1: Unable to start a VM due to insufficient capacity

[Vadim Kimlaychuk]

Hi Timothy,

 I have mounted SS on the slave host manually (didn't restart anything 
yet), but the next VM started on the primary node has also failed with the same 
error. I don't think this is connected to host's mount points. Primary node has 
had this mount from the beggining and new VM fails on the primary as well. 
At the same time templates (that are also located at SS) are executed 
correctly and VM-s are created on any host.  I don't understand which way ISO 
and template are different ? 

Vadim.

From: Timothy Lothering [tlother...@datacentrix.co.za]
Sent: Saturday, April 25, 2015 16:19
To: users@cloudstack.apache.org
Cc: dmi...@ant.ee
Subject: RE: CS 4.5.1:  Unable to start a VM due to insufficient capacity

Hi Vadim,

Can you manually mount the SS on the Cluster Slave Node?

I had a similar issue, and in the end needed to reboot the host. Don't know if 
this would resolve your issue?

Regards,
Timothy Lothering
Solutions Architect
Managed Services

T: +27877415535
F: +27877415100
C: +27824904099
E: tlother...@datacentrix.co.za


DISCLAIMER NOTICE:

Everything in this e-mail and any attachments relating to the official business 
of Datacentrix Holdings Ltd. and its subsidiaries
('Datacentrix') is proprietary to Datacentrix. It is confidential, legally 
privileged and protected by law. Datacentrix does not
own and endorse any other content. Views and opinions are those of the sender 
unless clearly stated as being that of Datacentrix.
The person addressed in the e-mail is the sole authorised recipient. Please 
notify the sender immediately if it has unintentionally
reached you and do not read, disclose or use the content in any way. 
Datacentrix cannot assure that the integrity of this communication
has been maintained nor that it is free of errors, virus, interception or 
interference.
-Original Message-
From: Vadim Kimlaychuk [mailto:vadim.kimlayc...@elion.ee]
Sent: 25 April 2015 07:49 AM
To: users@cloudstack.apache.org
Cc: dmi...@ant.ee
Subject: CS 4.5.1: Unable to start a VM due to insufficient capacity

Hello all,

 After fresh install for subj. Got problem creating new VM from ISO.  
Installing VM from templates is working.  Management log said that :

2015-04-25 08:36:32,066 DEBUG [c.c.a.m.DirectAgentAttache] 
(DirectAgent-185:ctx-9207cdf3) Seq 2-635851972389374824: Executing request
2015-04-25 08:36:32,071 DEBUG [c.c.h.x.r.CitrixResourceBase] 
(DirectAgent-185:ctx-9207cdf3) 1. The VM i-2-13-VM is in Starting state.
2015-04-25 08:36:32,089 DEBUG [c.c.h.x.r.CitrixResourceBase] 
(DirectAgent-185:ctx-9207cdf3) Created VM 834101d6-e316-3fc9-5f8d-6c55f641d986 
for i-2-13-VM
2015-04-25 08:36:32,107 DEBUG [c.c.h.x.r.CitrixResourceBase] 
(DirectAgent-185:ctx-9207cdf3) VBD 0524ba7b-dcd9-f227-349e-caa83d486939 created 
for com.cloud.agent.api.to.DiskTO@5213a905
2015-04-25 08:36:32,254 WARN  [c.c.h.x.r.CitrixResourceBase] 
(DirectAgent-185:ctx-9207cdf3) createIsoSRbyURI failed! mountpoint: 
secondary.storage.ant.ee/export/secondary/template/tmpl/2/206 due to 
SR_BACKEND_FAILURE_222Could not mount the directory specified in Device 
Configuration SR_BACKEND_FAILURE_222Could not mount the directory specified in 
Device Configuration
at com.xensource.xenapi.Types.checkResponse(Types.java:2021)

   ISO file in storage present and uploaded using cloudstack UI. Secondary 
storage was mounted on the cluster node, but not on slave node.  I have created 
the same mount point on the slave, but problem still exists.  I have separate 
network for secondary storage -- may be this is a problem? Please, give me a 
hint

Thanks,

Vadim.

CS 4.5.1: Unable to start a VM due to insufficient capacity

[Vadim Kimlaychuk]

Hello all,

 After fresh install for subj. Got problem creating new VM from ISO.  
Installing VM from templates is working.  Management log said that :

2015-04-25 08:36:32,066 DEBUG [c.c.a.m.DirectAgentAttache] 
(DirectAgent-185:ctx-9207cdf3) Seq 2-635851972389374824: Executing request
2015-04-25 08:36:32,071 DEBUG [c.c.h.x.r.CitrixResourceBase] 
(DirectAgent-185:ctx-9207cdf3) 1. The VM i-2-13-VM is in Starting state.
2015-04-25 08:36:32,089 DEBUG [c.c.h.x.r.CitrixResourceBase] 
(DirectAgent-185:ctx-9207cdf3) Created VM 834101d6-e316-3fc9-5f8d-6c55f641d986 
for i-2-13-VM
2015-04-25 08:36:32,107 DEBUG [c.c.h.x.r.CitrixResourceBase] 
(DirectAgent-185:ctx-9207cdf3) VBD 0524ba7b-dcd9-f227-349e-caa83d486939 created 
for com.cloud.agent.api.to.DiskTO@5213a905
2015-04-25 08:36:32,254 WARN  [c.c.h.x.r.CitrixResourceBase] 
(DirectAgent-185:ctx-9207cdf3) createIsoSRbyURI failed! mountpoint: 
secondary.storage.ant.ee/export/secondary/template/tmpl/2/206 due to 
SR_BACKEND_FAILURE_222Could not mount the directory specified in Device 
Configuration
SR_BACKEND_FAILURE_222Could not mount the directory specified in Device 
Configuration
at com.xensource.xenapi.Types.checkResponse(Types.java:2021)

   ISO file in storage present and uploaded using cloudstack UI. Secondary 
storage was mounted on the cluster node, but not on slave node.  I have created 
the same mount point on the slave, but problem still exists.  I have separate 
network for secondary storage -- may be this is a problem? Please, give me a 
hint

Thanks,

Vadim.

Re: Unable to start a VM due to insufficient capacity

[Ugo Vasi]

Hi Geoff,
so I can try adding some CPU and RAM to router VM. Can I monitor system 
VM resources?


Thanks

Il 19/02/2015 16:16, Geoff Higginbottom ha scritto:

HI Ugo,

Unfortunately we still continue to run into this problem on a regular basis.

I've had some success increasing the RAM  CPU allocations to the VR, 
especially where I was starting a large number of VMs which were all requesting new 
Passwords from the VR and causing it to lock up.

Regards

Geoff Higginbottom

D: +44 20 3603 0542 | S: +44 20 3603 0540 | M: +447968161581

geoff.higginbot...@shapeblue.com

-Original Message-
From: Ugo Vasi [mailto:ugo.v...@procne.it]
Sent: 19 February 2015 14:09
To: users@cloudstack.apache.org
Subject: Re: Unable to start a VM due to insufficient capacity

Hi Geoff,
we continue to find the problem on networks in a (seemingly) random.

The only solution is to do the cleaning of the network by hand, but it is not a 
good method, because it is not automatic and freeze for a moment all hosts on 
the network.

I would understand if this problem is related to version 4.3.0 or if it's been 
fixed in some later version.


thanks


Il 06/10/2014 12:55, Geoff Higginbottom ha scritto:

Hi Ugo,

What system VM template did you use?  (exact download URL please)

Regards

Geoff Higginbottom

D: +44 20 3603 0542 | S: +44 20 3603 0540 | M: +447968161581

geoff.higginbot...@shapeblue.com

-Original Message-
From: Ugo Vasi [mailto:ugo.v...@procne.it]
Sent: 06 October 2014 10:57
To: users@cloudstack.apache.org
Subject: Re: Unable to start a VM due to insufficient capacity

Hi Geoff,
the problem is occurring in different networks (all?) that are not changed.

For us is a big problem because I can not predict when it occurs and the 
creation of new machines is blocked until a network restarts (this method, 
among other things, cause a small interruption of service).

What can I do to  fix the problem?


Il 11/09/2014 09:28, Geoff Higginbottom ha scritto:

Hi Ugo,

Did restarting the network with cleanup option resolve your issue last time, if 
yes have you tried the same on this network?

Regards

Geoff Higginbottom
CTO / Cloud Architect

D: +44 20 3603 0542tel:+442036030542 | S: +44 20 3603
0540tel:+442036030540 | M: +447968161581tel:+447968161581

geoff.higginbot...@shapeblue.commailto:geoff.higginbottom@shapeblue.c
om | www.shapeblue.comhtp://www.shapeblue.com/ |
Twitter:@cloudstackguruhttps://twitter.com/#!/cloudstackguru

ShapeBlue Ltd, 53 Chandos Place, Covent Garden, London, WC2N
4HSx-apple-data-detectors://5


On 11 Sep 2014, at 08:17, Ugo Vasi 
ugo.v...@procne.itmailto:ugo.v...@procne.it wrote:

Hi Geoff,
I still have the problem creating new VMs but in another isolated network. The 
problem seems to be the same:

2014-09-11 08:55:27,048 DEBUG [c.c.v.VirtualMachineManagerImpl]
(Job-Executor-55:ctx-b5c34ec7 ctx-3715f5de) VM is being created in
podId: 1
2014-09-11 08:55:27,050 DEBUG [o.a.c.e.o.NetworkOrchestrator]
(Job-Executor-55:ctx-b5c34ec7 ctx-3715f5de) Network id=212 is already
implemented
2014-09-11 08:55:27,118 DEBUG [c.c.n.NetworkModelImpl]
(Job-Executor-55:ctx-b5c34ec7 ctx-3715f5de) Service SecurityGroup is
not supported in the network id=212
2014-09-11 08:55:27,122 DEBUG [o.a.c.e.o.NetworkOrchestrator]
(Job-Executor-55:ctx-b5c34ec7 ctx-3715f5de) Changing active number of
nics for network id=212 on 1
2014-09-11 08:55:27,174 DEBUG [o.a.c.e.o.NetworkOrchestrator]
(Job-Executor-55:ctx-b5c34ec7 ctx-3715f5de) Asking VirtualRouter to
prepare for Nic[116-86-8429f13f-7c3b-4b8a-aea3-9b8e9a3f4c03-10.1.1.19]
2014-09-11 08:55:27,181 DEBUG
[c.c.n.r.VirtualNetworkApplianceManagerImpl]
(Job-Executor-55:ctx-b5c34ec7 ctx-3715f5de) Lock is acquired for
network id 212 as a part of router startup in
Dest[Zone(Id)-Pod(Id)-Cluster(Id)-Host(Id)-Storage(Volume(Id|Type--Po
ol(Id))] :
Dest[Zone(1)-Pod(1)-Cluster(1)-Host(7)-Storage(Volume(98|ROOT--Pool(6
))]
2014-09-11 08:55:27,183 DEBUG
[c.c.n.r.VirtualNetworkApplianceManagerImpl]
(Job-Executor-55:ctx-b5c34ec7 ctx-3715f5de) Lock is released for
network id 212 as a part of router startup in
Dest[Zone(Id)-Pod(Id)-Cluster(Id)-Host(Id)-Storage(Volume(Id|Type--Po
ol(Id))] :
Dest[Zone(1)-Pod(1)-Cluster(1)-Host(7)-Storage(Volume(98|ROOT--Pool(6
))]
2014-09-11 08:55:27,189 DEBUG [c.c.n.NetworkModelImpl]
(Job-Executor-55:ctx-b5c34ec7 ctx-3715f5de) Service SecurityGroup is
not supported in the network id=212
2014-09-11 08:55:27,198 DEBUG [c.c.n.NetworkModelImpl]
(Job-Executor-55:ctx-b5c34ec7 ctx-3715f5de) Service SecurityGroup is
not supported in the network id=212
2014-09-11 08:55:27,202 DEBUG
[c.c.n.r.VirtualNetworkApplianceManagerImpl]
(Job-Executor-55:ctx-b5c34ec7 ctx-3715f5de) Applying dhcp entry in
network Ntwk[212|Guest|8]
2014-09-11 08:55:27,215 DEBUG [c.c.a.t.Request]
(Job-Executor-55:ctx-b5c34ec7 ctx-3715f5de) Seq 7-564304056: Sending
{ Cmd , MgmtId: 77916390353436, via: 7(csh1b), Ver: v1, Flags: 100011,
[{com.cloud.agent.api.routing.DhcpEntryCommand:{vmMac:02:00:15:76

Re: Unable to start a VM due to insufficient capacity

[Ugo Vasi]

Hi Geoff,
we continue to find the problem on networks in a (seemingly) random.

The only solution is to do the cleaning of the network by hand, but it 
is not a good method, because it is not automatic and freeze for a 
moment all hosts on the network.


I would understand if this problem is related to version 4.3.0 or if 
it's been fixed in some later version.



thanks


Il 06/10/2014 12:55, Geoff Higginbottom ha scritto:

Hi Ugo,

What system VM template did you use?  (exact download URL please)

Regards

Geoff Higginbottom

D: +44 20 3603 0542 | S: +44 20 3603 0540 | M: +447968161581

geoff.higginbot...@shapeblue.com

-Original Message-
From: Ugo Vasi [mailto:ugo.v...@procne.it]
Sent: 06 October 2014 10:57
To: users@cloudstack.apache.org
Subject: Re: Unable to start a VM due to insufficient capacity

Hi Geoff,
the problem is occurring in different networks (all?) that are not changed.

For us is a big problem because I can not predict when it occurs and the 
creation of new machines is blocked until a network restarts (this method, 
among other things, cause a small interruption of service).

What can I do to  fix the problem?


Il 11/09/2014 09:28, Geoff Higginbottom ha scritto:

Hi Ugo,

Did restarting the network with cleanup option resolve your issue last time, if 
yes have you tried the same on this network?

Regards

Geoff Higginbottom
CTO / Cloud Architect

D: +44 20 3603 0542tel:+442036030542 | S: +44 20 3603
0540tel:+442036030540 | M: +447968161581tel:+447968161581

geoff.higginbot...@shapeblue.commailto:geoff.higginbottom@shapeblue.c
om | www.shapeblue.comhtp://www.shapeblue.com/ |
Twitter:@cloudstackguruhttps://twitter.com/#!/cloudstackguru

ShapeBlue Ltd, 53 Chandos Place, Covent Garden, London, WC2N
4HSx-apple-data-detectors://5


On 11 Sep 2014, at 08:17, Ugo Vasi 
ugo.v...@procne.itmailto:ugo.v...@procne.it wrote:

Hi Geoff,
I still have the problem creating new VMs but in another isolated network. The 
problem seems to be the same:

2014-09-11 08:55:27,048 DEBUG [c.c.v.VirtualMachineManagerImpl]
(Job-Executor-55:ctx-b5c34ec7 ctx-3715f5de) VM is being created in
podId: 1
2014-09-11 08:55:27,050 DEBUG [o.a.c.e.o.NetworkOrchestrator]
(Job-Executor-55:ctx-b5c34ec7 ctx-3715f5de) Network id=212 is already
implemented
2014-09-11 08:55:27,118 DEBUG [c.c.n.NetworkModelImpl]
(Job-Executor-55:ctx-b5c34ec7 ctx-3715f5de) Service SecurityGroup is
not supported in the network id=212
2014-09-11 08:55:27,122 DEBUG [o.a.c.e.o.NetworkOrchestrator]
(Job-Executor-55:ctx-b5c34ec7 ctx-3715f5de) Changing active number of
nics for network id=212 on 1
2014-09-11 08:55:27,174 DEBUG [o.a.c.e.o.NetworkOrchestrator]
(Job-Executor-55:ctx-b5c34ec7 ctx-3715f5de) Asking VirtualRouter to
prepare for Nic[116-86-8429f13f-7c3b-4b8a-aea3-9b8e9a3f4c03-10.1.1.19]
2014-09-11 08:55:27,181 DEBUG
[c.c.n.r.VirtualNetworkApplianceManagerImpl]
(Job-Executor-55:ctx-b5c34ec7 ctx-3715f5de) Lock is acquired for
network id 212 as a part of router startup in
Dest[Zone(Id)-Pod(Id)-Cluster(Id)-Host(Id)-Storage(Volume(Id|Type--Po
ol(Id))] :
Dest[Zone(1)-Pod(1)-Cluster(1)-Host(7)-Storage(Volume(98|ROOT--Pool(6
))]
2014-09-11 08:55:27,183 DEBUG
[c.c.n.r.VirtualNetworkApplianceManagerImpl]
(Job-Executor-55:ctx-b5c34ec7 ctx-3715f5de) Lock is released for
network id 212 as a part of router startup in
Dest[Zone(Id)-Pod(Id)-Cluster(Id)-Host(Id)-Storage(Volume(Id|Type--Po
ol(Id))] :
Dest[Zone(1)-Pod(1)-Cluster(1)-Host(7)-Storage(Volume(98|ROOT--Pool(6
))]
2014-09-11 08:55:27,189 DEBUG [c.c.n.NetworkModelImpl]
(Job-Executor-55:ctx-b5c34ec7 ctx-3715f5de) Service SecurityGroup is
not supported in the network id=212
2014-09-11 08:55:27,198 DEBUG [c.c.n.NetworkModelImpl]
(Job-Executor-55:ctx-b5c34ec7 ctx-3715f5de) Service SecurityGroup is
not supported in the network id=212
2014-09-11 08:55:27,202 DEBUG
[c.c.n.r.VirtualNetworkApplianceManagerImpl]
(Job-Executor-55:ctx-b5c34ec7 ctx-3715f5de) Applying dhcp entry in
network Ntwk[212|Guest|8]
2014-09-11 08:55:27,215 DEBUG [c.c.a.t.Request]
(Job-Executor-55:ctx-b5c34ec7 ctx-3715f5de) Seq 7-564304056: Sending
{ Cmd , MgmtId: 77916390353436, via: 7(csh1b), Ver: v1, Flags: 100011,
[{com.cloud.agent.api.routing.DhcpEntryCommand:{vmMac:02:00:15:76
:00:0e,vmIpAddress:10.1.1.19,vmName:giannitest,defaultRouter
:10.1.1.1,defaultDns:10.1.1.1,duid:00:03:00:01:02:00:15:76:0
0:0e,isDefault:true,executeInSequence:false,accessDetails:{rou
ter.guest.ip:10.1.1.1,zone.network.type:Advanced,router.name:
r-60-VM,router.ip:169.254.1.230},wait:0}}] }
2014-09-11 08:55:27,941 DEBUG [c.c.s.s.SecondaryStorageManagerImpl]
(secstorage-1:ctx-327037b2) Zone 1 is ready to launch secondary
storage VM
2014-09-11 08:55:28,022 DEBUG [c.c.c.ConsoleProxyManagerImpl]
(consoleproxy-1:ctx-a8ba3b1e) Zone 1 is ready to launch console proxy
2014-09-11 08:55:28,820 DEBUG [c.c.a.ApiServlet]
(catalina-exec-16:ctx-58e92382) ===START===  192.168.130.89 -- GET
command=queryAsyncJobResultjobId=195bf80a-9823-4ec3-add4-8907b98fbaf0

Re: Unable to start a VM due to insufficient capacity

[Ugo Vasi]

Hi Geoff,
We still have problems with the networks and we don't understand what 
causes them, it seems to be randomly generate.



Thanks


Il 06/10/2014 12:55, Geoff Higginbottom ha scritto:

Hi Ugo,

What system VM template did you use?  (exact download URL please)

Regards

Geoff Higginbottom

D: +44 20 3603 0542 | S: +44 20 3603 0540 | M: +447968161581

geoff.higginbot...@shapeblue.com

-Original Message-
From: Ugo Vasi [mailto:ugo.v...@procne.it]
Sent: 06 October 2014 10:57
To: users@cloudstack.apache.org
Subject: Re: Unable to start a VM due to insufficient capacity

Hi Geoff,
the problem is occurring in different networks (all?) that are not changed.

For us is a big problem because I can not predict when it occurs and the 
creation of new machines is blocked until a network restarts (this method, 
among other things, cause a small interruption of service).

What can I do to  fix the problem?


Il 11/09/2014 09:28, Geoff Higginbottom ha scritto:

Hi Ugo,

Did restarting the network with cleanup option resolve your issue last time, if 
yes have you tried the same on this network?

Regards

Geoff Higginbottom
CTO / Cloud Architect

D: +44 20 3603 0542tel:+442036030542 | S: +44 20 3603
0540tel:+442036030540 | M: +447968161581tel:+447968161581

geoff.higginbot...@shapeblue.commailto:geoff.higginbottom@shapeblue.c
om | www.shapeblue.comhtp://www.shapeblue.com/ |
Twitter:@cloudstackguruhttps://twitter.com/#!/cloudstackguru

ShapeBlue Ltd, 53 Chandos Place, Covent Garden, London, WC2N
4HSx-apple-data-detectors://5


On 11 Sep 2014, at 08:17, Ugo Vasi 
ugo.v...@procne.itmailto:ugo.v...@procne.it wrote:

Hi Geoff,
I still have the problem creating new VMs but in another isolated network. The 
problem seems to be the same:

2014-09-11 08:55:27,048 DEBUG [c.c.v.VirtualMachineManagerImpl]
(Job-Executor-55:ctx-b5c34ec7 ctx-3715f5de) VM is being created in
podId: 1
2014-09-11 08:55:27,050 DEBUG [o.a.c.e.o.NetworkOrchestrator]
(Job-Executor-55:ctx-b5c34ec7 ctx-3715f5de) Network id=212 is already
implemented
2014-09-11 08:55:27,118 DEBUG [c.c.n.NetworkModelImpl]
(Job-Executor-55:ctx-b5c34ec7 ctx-3715f5de) Service SecurityGroup is
not supported in the network id=212
2014-09-11 08:55:27,122 DEBUG [o.a.c.e.o.NetworkOrchestrator]
(Job-Executor-55:ctx-b5c34ec7 ctx-3715f5de) Changing active number of
nics for network id=212 on 1
2014-09-11 08:55:27,174 DEBUG [o.a.c.e.o.NetworkOrchestrator]
(Job-Executor-55:ctx-b5c34ec7 ctx-3715f5de) Asking VirtualRouter to
prepare for Nic[116-86-8429f13f-7c3b-4b8a-aea3-9b8e9a3f4c03-10.1.1.19]
2014-09-11 08:55:27,181 DEBUG
[c.c.n.r.VirtualNetworkApplianceManagerImpl]
(Job-Executor-55:ctx-b5c34ec7 ctx-3715f5de) Lock is acquired for
network id 212 as a part of router startup in
Dest[Zone(Id)-Pod(Id)-Cluster(Id)-Host(Id)-Storage(Volume(Id|Type--Po
ol(Id))] :
Dest[Zone(1)-Pod(1)-Cluster(1)-Host(7)-Storage(Volume(98|ROOT--Pool(6
))]
2014-09-11 08:55:27,183 DEBUG
[c.c.n.r.VirtualNetworkApplianceManagerImpl]
(Job-Executor-55:ctx-b5c34ec7 ctx-3715f5de) Lock is released for
network id 212 as a part of router startup in
Dest[Zone(Id)-Pod(Id)-Cluster(Id)-Host(Id)-Storage(Volume(Id|Type--Po
ol(Id))] :
Dest[Zone(1)-Pod(1)-Cluster(1)-Host(7)-Storage(Volume(98|ROOT--Pool(6
))]
2014-09-11 08:55:27,189 DEBUG [c.c.n.NetworkModelImpl]
(Job-Executor-55:ctx-b5c34ec7 ctx-3715f5de) Service SecurityGroup is
not supported in the network id=212
2014-09-11 08:55:27,198 DEBUG [c.c.n.NetworkModelImpl]
(Job-Executor-55:ctx-b5c34ec7 ctx-3715f5de) Service SecurityGroup is
not supported in the network id=212
2014-09-11 08:55:27,202 DEBUG
[c.c.n.r.VirtualNetworkApplianceManagerImpl]
(Job-Executor-55:ctx-b5c34ec7 ctx-3715f5de) Applying dhcp entry in
network Ntwk[212|Guest|8]
2014-09-11 08:55:27,215 DEBUG [c.c.a.t.Request]
(Job-Executor-55:ctx-b5c34ec7 ctx-3715f5de) Seq 7-564304056: Sending
{ Cmd , MgmtId: 77916390353436, via: 7(csh1b), Ver: v1, Flags: 100011,
[{com.cloud.agent.api.routing.DhcpEntryCommand:{vmMac:02:00:15:76
:00:0e,vmIpAddress:10.1.1.19,vmName:giannitest,defaultRouter
:10.1.1.1,defaultDns:10.1.1.1,duid:00:03:00:01:02:00:15:76:0
0:0e,isDefault:true,executeInSequence:false,accessDetails:{rou
ter.guest.ip:10.1.1.1,zone.network.type:Advanced,router.name:
r-60-VM,router.ip:169.254.1.230},wait:0}}] }
2014-09-11 08:55:27,941 DEBUG [c.c.s.s.SecondaryStorageManagerImpl]
(secstorage-1:ctx-327037b2) Zone 1 is ready to launch secondary
storage VM
2014-09-11 08:55:28,022 DEBUG [c.c.c.ConsoleProxyManagerImpl]
(consoleproxy-1:ctx-a8ba3b1e) Zone 1 is ready to launch console proxy
2014-09-11 08:55:28,820 DEBUG [c.c.a.ApiServlet]
(catalina-exec-16:ctx-58e92382) ===START===  192.168.130.89 -- GET
command=queryAsyncJobResultjobId=195bf80a-9823-4ec3-add4-8907b98fbaf0
response=jsonsessionkey=qGZA6KYoc1SB%2Bq2k70HoM%2BBBQTU%3D_=1410418
528731
2014-09-11 08:55:29,069 DEBUG [c.c.a.t.Request]
(AgentManager-Handler-13:null) Seq 7-564304056: Processing:  { Ans: ,
MgmtId: 77916390353436, via: 7, Ver: v1, Flags: 10,

Re: Unable to start a VM due to insufficient capacity

[Ugo Vasi]

Hi Geoff,
I used this URL:

 
http://download.cloud.com/templates/4.3/systemvm64template-2014-01-14-master-kvm.qcow2.bz2

Il 06/10/2014 12:55, Geoff Higginbottom ha scritto:

Hi Ugo,

What system VM template did you use?  (exact download URL please)

Regards

Geoff Higginbottom

D: +44 20 3603 0542 | S: +44 20 3603 0540 | M: +447968161581

geoff.higginbot...@shapeblue.com

-Original Message-
From: Ugo Vasi [mailto:ugo.v...@procne.it]
Sent: 06 October 2014 10:57
To: users@cloudstack.apache.org
Subject: Re: Unable to start a VM due to insufficient capacity

Hi Geoff,
the problem is occurring in different networks (all?) that are not changed.

For us is a big problem because I can not predict when it occurs and the 
creation of new machines is blocked until a network restarts (this method, 
among other things, cause a small interruption of service).

What can I do to  fix the problem?


Il 11/09/2014 09:28, Geoff Higginbottom ha scritto:

Hi Ugo,

Did restarting the network with cleanup option resolve your issue last time, if 
yes have you tried the same on this network?

Regards

Geoff Higginbottom
CTO / Cloud Architect

D: +44 20 3603 0542tel:+442036030542 | S: +44 20 3603
0540tel:+442036030540 | M: +447968161581tel:+447968161581

geoff.higginbot...@shapeblue.commailto:geoff.higginbottom@shapeblue.c
om | www.shapeblue.comhtp://www.shapeblue.com/ |
Twitter:@cloudstackguruhttps://twitter.com/#!/cloudstackguru

ShapeBlue Ltd, 53 Chandos Place, Covent Garden, London, WC2N
4HSx-apple-data-detectors://5


On 11 Sep 2014, at 08:17, Ugo Vasi 
ugo.v...@procne.itmailto:ugo.v...@procne.it wrote:

Hi Geoff,
I still have the problem creating new VMs but in another isolated network. The 
problem seems to be the same:

2014-09-11 08:55:27,048 DEBUG [c.c.v.VirtualMachineManagerImpl]
(Job-Executor-55:ctx-b5c34ec7 ctx-3715f5de) VM is being created in
podId: 1
2014-09-11 08:55:27,050 DEBUG [o.a.c.e.o.NetworkOrchestrator]
(Job-Executor-55:ctx-b5c34ec7 ctx-3715f5de) Network id=212 is already
implemented
2014-09-11 08:55:27,118 DEBUG [c.c.n.NetworkModelImpl]
(Job-Executor-55:ctx-b5c34ec7 ctx-3715f5de) Service SecurityGroup is
not supported in the network id=212
2014-09-11 08:55:27,122 DEBUG [o.a.c.e.o.NetworkOrchestrator]
(Job-Executor-55:ctx-b5c34ec7 ctx-3715f5de) Changing active number of
nics for network id=212 on 1
2014-09-11 08:55:27,174 DEBUG [o.a.c.e.o.NetworkOrchestrator]
(Job-Executor-55:ctx-b5c34ec7 ctx-3715f5de) Asking VirtualRouter to
prepare for Nic[116-86-8429f13f-7c3b-4b8a-aea3-9b8e9a3f4c03-10.1.1.19]
2014-09-11 08:55:27,181 DEBUG
[c.c.n.r.VirtualNetworkApplianceManagerImpl]
(Job-Executor-55:ctx-b5c34ec7 ctx-3715f5de) Lock is acquired for
network id 212 as a part of router startup in
Dest[Zone(Id)-Pod(Id)-Cluster(Id)-Host(Id)-Storage(Volume(Id|Type--Po
ol(Id))] :
Dest[Zone(1)-Pod(1)-Cluster(1)-Host(7)-Storage(Volume(98|ROOT--Pool(6
))]
2014-09-11 08:55:27,183 DEBUG
[c.c.n.r.VirtualNetworkApplianceManagerImpl]
(Job-Executor-55:ctx-b5c34ec7 ctx-3715f5de) Lock is released for
network id 212 as a part of router startup in
Dest[Zone(Id)-Pod(Id)-Cluster(Id)-Host(Id)-Storage(Volume(Id|Type--Po
ol(Id))] :
Dest[Zone(1)-Pod(1)-Cluster(1)-Host(7)-Storage(Volume(98|ROOT--Pool(6
))]
2014-09-11 08:55:27,189 DEBUG [c.c.n.NetworkModelImpl]
(Job-Executor-55:ctx-b5c34ec7 ctx-3715f5de) Service SecurityGroup is
not supported in the network id=212
2014-09-11 08:55:27,198 DEBUG [c.c.n.NetworkModelImpl]
(Job-Executor-55:ctx-b5c34ec7 ctx-3715f5de) Service SecurityGroup is
not supported in the network id=212
2014-09-11 08:55:27,202 DEBUG
[c.c.n.r.VirtualNetworkApplianceManagerImpl]
(Job-Executor-55:ctx-b5c34ec7 ctx-3715f5de) Applying dhcp entry in
network Ntwk[212|Guest|8]
2014-09-11 08:55:27,215 DEBUG [c.c.a.t.Request]
(Job-Executor-55:ctx-b5c34ec7 ctx-3715f5de) Seq 7-564304056: Sending
{ Cmd , MgmtId: 77916390353436, via: 7(csh1b), Ver: v1, Flags: 100011,
[{com.cloud.agent.api.routing.DhcpEntryCommand:{vmMac:02:00:15:76
:00:0e,vmIpAddress:10.1.1.19,vmName:giannitest,defaultRouter
:10.1.1.1,defaultDns:10.1.1.1,duid:00:03:00:01:02:00:15:76:0
0:0e,isDefault:true,executeInSequence:false,accessDetails:{rou
ter.guest.ip:10.1.1.1,zone.network.type:Advanced,router.name:
r-60-VM,router.ip:169.254.1.230},wait:0}}] }
2014-09-11 08:55:27,941 DEBUG [c.c.s.s.SecondaryStorageManagerImpl]
(secstorage-1:ctx-327037b2) Zone 1 is ready to launch secondary
storage VM
2014-09-11 08:55:28,022 DEBUG [c.c.c.ConsoleProxyManagerImpl]
(consoleproxy-1:ctx-a8ba3b1e) Zone 1 is ready to launch console proxy
2014-09-11 08:55:28,820 DEBUG [c.c.a.ApiServlet]
(catalina-exec-16:ctx-58e92382) ===START===  192.168.130.89 -- GET
command=queryAsyncJobResultjobId=195bf80a-9823-4ec3-add4-8907b98fbaf0
response=jsonsessionkey=qGZA6KYoc1SB%2Bq2k70HoM%2BBBQTU%3D_=1410418
528731
2014-09-11 08:55:29,069 DEBUG [c.c.a.t.Request]
(AgentManager-Handler-13:null) Seq 7-564304056: Processing:  { Ans: ,
MgmtId: 77916390353436, via: 7, Ver: v1, Flags: 10,

Re: Unable to start a VM due to insufficient capacity

[Ugo Vasi]

Hi Geoff,
the problem is occurring in different networks (all?) that are not changed.

For us is a big problem because I can not predict when it occurs and the 
creation of new machines is blocked until a network restarts (this 
method, among other things, cause a small interruption of service).


What can I do to  fix the problem?


Il 11/09/2014 09:28, Geoff Higginbottom ha scritto:

Hi Ugo,

Did restarting the network with cleanup option resolve your issue last time, if 
yes have you tried the same on this network?

Regards

Geoff Higginbottom
CTO / Cloud Architect

D: +44 20 3603 0542tel:+442036030542 | S: +44 20 3603 0540tel:+442036030540 | M: 
+447968161581tel:+447968161581

geoff.higginbot...@shapeblue.commailto:geoff.higginbot...@shapeblue.com | 
www.shapeblue.comhtp://www.shapeblue.com/ | 
Twitter:@cloudstackguruhttps://twitter.com/#!/cloudstackguru

ShapeBlue Ltd, 53 Chandos Place, Covent Garden, London, WC2N 
4HSx-apple-data-detectors://5


On 11 Sep 2014, at 08:17, Ugo Vasi 
ugo.v...@procne.itmailto:ugo.v...@procne.it wrote:

Hi Geoff,
I still have the problem creating new VMs but in another isolated network. The 
problem seems to be the same:

2014-09-11 08:55:27,048 DEBUG [c.c.v.VirtualMachineManagerImpl] 
(Job-Executor-55:ctx-b5c34ec7 ctx-3715f5de) VM is being created in podId: 1
2014-09-11 08:55:27,050 DEBUG [o.a.c.e.o.NetworkOrchestrator] 
(Job-Executor-55:ctx-b5c34ec7 ctx-3715f5de) Network id=212 is already 
implemented
2014-09-11 08:55:27,118 DEBUG [c.c.n.NetworkModelImpl] 
(Job-Executor-55:ctx-b5c34ec7 ctx-3715f5de) Service SecurityGroup is not 
supported in the network id=212
2014-09-11 08:55:27,122 DEBUG [o.a.c.e.o.NetworkOrchestrator] 
(Job-Executor-55:ctx-b5c34ec7 ctx-3715f5de) Changing active number of nics for 
network id=212 on 1
2014-09-11 08:55:27,174 DEBUG [o.a.c.e.o.NetworkOrchestrator] 
(Job-Executor-55:ctx-b5c34ec7 ctx-3715f5de) Asking VirtualRouter to prepare for 
Nic[116-86-8429f13f-7c3b-4b8a-aea3-9b8e9a3f4c03-10.1.1.19]
2014-09-11 08:55:27,181 DEBUG [c.c.n.r.VirtualNetworkApplianceManagerImpl] 
(Job-Executor-55:ctx-b5c34ec7 ctx-3715f5de) Lock is acquired for network id 212 as a 
part of router startup in 
Dest[Zone(Id)-Pod(Id)-Cluster(Id)-Host(Id)-Storage(Volume(Id|Type--Pool(Id))] : 
Dest[Zone(1)-Pod(1)-Cluster(1)-Host(7)-Storage(Volume(98|ROOT--Pool(6))]
2014-09-11 08:55:27,183 DEBUG [c.c.n.r.VirtualNetworkApplianceManagerImpl] 
(Job-Executor-55:ctx-b5c34ec7 ctx-3715f5de) Lock is released for network id 212 as a 
part of router startup in 
Dest[Zone(Id)-Pod(Id)-Cluster(Id)-Host(Id)-Storage(Volume(Id|Type--Pool(Id))] : 
Dest[Zone(1)-Pod(1)-Cluster(1)-Host(7)-Storage(Volume(98|ROOT--Pool(6))]
2014-09-11 08:55:27,189 DEBUG [c.c.n.NetworkModelImpl] 
(Job-Executor-55:ctx-b5c34ec7 ctx-3715f5de) Service SecurityGroup is not 
supported in the network id=212
2014-09-11 08:55:27,198 DEBUG [c.c.n.NetworkModelImpl] 
(Job-Executor-55:ctx-b5c34ec7 ctx-3715f5de) Service SecurityGroup is not 
supported in the network id=212
2014-09-11 08:55:27,202 DEBUG [c.c.n.r.VirtualNetworkApplianceManagerImpl] 
(Job-Executor-55:ctx-b5c34ec7 ctx-3715f5de) Applying dhcp entry in network 
Ntwk[212|Guest|8]
2014-09-11 08:55:27,215 DEBUG [c.c.a.t.Request] (Job-Executor-55:ctx-b5c34ec7 ctx-3715f5de) Seq 7-564304056: Sending  { Cmd , MgmtId: 77916390353436, via: 7(csh1b), Ver: v1, Flags: 100011, 
[{com.cloud.agent.api.routing.DhcpEntryCommand:{vmMac:02:00:15:76:00:0e,vmIpAddress:10.1.1.19,vmName:giannitest,defaultRouter:10.1.1.1,defaultDns:10.1.1.1,duid:00:03:00:01:02:00:15:76:00:0e,isDefault:true,executeInSequence:false,accessDetails:{router.guest.ip:10.1.1.1,zone.network.type:Advanced,router.name:r-60-VM,router.ip:169.254.1.230},wait:0}}]
 }
2014-09-11 08:55:27,941 DEBUG [c.c.s.s.SecondaryStorageManagerImpl] 
(secstorage-1:ctx-327037b2) Zone 1 is ready to launch secondary storage VM
2014-09-11 08:55:28,022 DEBUG [c.c.c.ConsoleProxyManagerImpl] 
(consoleproxy-1:ctx-a8ba3b1e) Zone 1 is ready to launch console proxy
2014-09-11 08:55:28,820 DEBUG [c.c.a.ApiServlet] (catalina-exec-16:ctx-58e92382) ===START===  
192.168.130.89 -- GET 
command=queryAsyncJobResultjobId=195bf80a-9823-4ec3-add4-8907b98fbaf0response=jsonsessionkey=qGZA6KYoc1SB%2Bq2k70HoM%2BBBQTU%3D_=1410418528731
2014-09-11 08:55:29,069 DEBUG [c.c.a.t.Request] (AgentManager-Handler-13:null) Seq 7-564304056: Processing:  
{ Ans: , MgmtId: 77916390353436, via: 7, Ver: v1, Flags: 10, 
[{com.cloud.agent.api.Answer:{result:true,wait:0}}] }
2014-09-11 08:55:29,069 DEBUG [c.c.a.t.Request] (Job-Executor-55:ctx-b5c34ec7 
ctx-3715f5de) Seq 7-564304056: Received:  { Ans: , MgmtId: 77916390353436, via: 
7, Ver: v1, Flags: 10, { Answer } }
2014-09-11 08:55:29,075 DEBUG [c.c.n.NetworkModelImpl] 
(Job-Executor-55:ctx-b5c34ec7 ctx-3715f5de) Service SecurityGroup is not 
supported in the network id=212
2014-09-11 08:55:29,078 DEBUG [c.c.n.r.VirtualNetworkApplianceManagerImpl] 
(Job-Executor-55:ctx-b5c34ec7 ctx-3715f5de) Applying userdata and password 
entry in 

RE: Unable to start a VM due to insufficient capacity

[Geoff Higginbottom]

Hi Ugo,

What system VM template did you use?  (exact download URL please)

Regards

Geoff Higginbottom

D: +44 20 3603 0542 | S: +44 20 3603 0540 | M: +447968161581

geoff.higginbot...@shapeblue.com

-Original Message-
From: Ugo Vasi [mailto:ugo.v...@procne.it]
Sent: 06 October 2014 10:57
To: users@cloudstack.apache.org
Subject: Re: Unable to start a VM due to insufficient capacity

Hi Geoff,
the problem is occurring in different networks (all?) that are not changed.

For us is a big problem because I can not predict when it occurs and the 
creation of new machines is blocked until a network restarts (this method, 
among other things, cause a small interruption of service).

What can I do to  fix the problem?


Il 11/09/2014 09:28, Geoff Higginbottom ha scritto:
 Hi Ugo,

 Did restarting the network with cleanup option resolve your issue last time, 
 if yes have you tried the same on this network?

 Regards

 Geoff Higginbottom
 CTO / Cloud Architect

 D: +44 20 3603 0542tel:+442036030542 | S: +44 20 3603
 0540tel:+442036030540 | M: +447968161581tel:+447968161581

 geoff.higginbot...@shapeblue.commailto:geoff.higginbottom@shapeblue.c
 om | www.shapeblue.comhtp://www.shapeblue.com/ |
 Twitter:@cloudstackguruhttps://twitter.com/#!/cloudstackguru

 ShapeBlue Ltd, 53 Chandos Place, Covent Garden, London, WC2N
 4HSx-apple-data-detectors://5


 On 11 Sep 2014, at 08:17, Ugo Vasi 
 ugo.v...@procne.itmailto:ugo.v...@procne.it wrote:

 Hi Geoff,
 I still have the problem creating new VMs but in another isolated network. 
 The problem seems to be the same:

 2014-09-11 08:55:27,048 DEBUG [c.c.v.VirtualMachineManagerImpl]
 (Job-Executor-55:ctx-b5c34ec7 ctx-3715f5de) VM is being created in
 podId: 1
 2014-09-11 08:55:27,050 DEBUG [o.a.c.e.o.NetworkOrchestrator]
 (Job-Executor-55:ctx-b5c34ec7 ctx-3715f5de) Network id=212 is already
 implemented
 2014-09-11 08:55:27,118 DEBUG [c.c.n.NetworkModelImpl]
 (Job-Executor-55:ctx-b5c34ec7 ctx-3715f5de) Service SecurityGroup is
 not supported in the network id=212
 2014-09-11 08:55:27,122 DEBUG [o.a.c.e.o.NetworkOrchestrator]
 (Job-Executor-55:ctx-b5c34ec7 ctx-3715f5de) Changing active number of
 nics for network id=212 on 1
 2014-09-11 08:55:27,174 DEBUG [o.a.c.e.o.NetworkOrchestrator]
 (Job-Executor-55:ctx-b5c34ec7 ctx-3715f5de) Asking VirtualRouter to
 prepare for Nic[116-86-8429f13f-7c3b-4b8a-aea3-9b8e9a3f4c03-10.1.1.19]
 2014-09-11 08:55:27,181 DEBUG
 [c.c.n.r.VirtualNetworkApplianceManagerImpl]
 (Job-Executor-55:ctx-b5c34ec7 ctx-3715f5de) Lock is acquired for
 network id 212 as a part of router startup in
 Dest[Zone(Id)-Pod(Id)-Cluster(Id)-Host(Id)-Storage(Volume(Id|Type--Po
 ol(Id))] :
 Dest[Zone(1)-Pod(1)-Cluster(1)-Host(7)-Storage(Volume(98|ROOT--Pool(6
 ))]
 2014-09-11 08:55:27,183 DEBUG
 [c.c.n.r.VirtualNetworkApplianceManagerImpl]
 (Job-Executor-55:ctx-b5c34ec7 ctx-3715f5de) Lock is released for
 network id 212 as a part of router startup in
 Dest[Zone(Id)-Pod(Id)-Cluster(Id)-Host(Id)-Storage(Volume(Id|Type--Po
 ol(Id))] :
 Dest[Zone(1)-Pod(1)-Cluster(1)-Host(7)-Storage(Volume(98|ROOT--Pool(6
 ))]
 2014-09-11 08:55:27,189 DEBUG [c.c.n.NetworkModelImpl]
 (Job-Executor-55:ctx-b5c34ec7 ctx-3715f5de) Service SecurityGroup is
 not supported in the network id=212
 2014-09-11 08:55:27,198 DEBUG [c.c.n.NetworkModelImpl]
 (Job-Executor-55:ctx-b5c34ec7 ctx-3715f5de) Service SecurityGroup is
 not supported in the network id=212
 2014-09-11 08:55:27,202 DEBUG
 [c.c.n.r.VirtualNetworkApplianceManagerImpl]
 (Job-Executor-55:ctx-b5c34ec7 ctx-3715f5de) Applying dhcp entry in
 network Ntwk[212|Guest|8]
 2014-09-11 08:55:27,215 DEBUG [c.c.a.t.Request]
 (Job-Executor-55:ctx-b5c34ec7 ctx-3715f5de) Seq 7-564304056: Sending
 { Cmd , MgmtId: 77916390353436, via: 7(csh1b), Ver: v1, Flags: 100011,
 [{com.cloud.agent.api.routing.DhcpEntryCommand:{vmMac:02:00:15:76
 :00:0e,vmIpAddress:10.1.1.19,vmName:giannitest,defaultRouter
 :10.1.1.1,defaultDns:10.1.1.1,duid:00:03:00:01:02:00:15:76:0
 0:0e,isDefault:true,executeInSequence:false,accessDetails:{rou
 ter.guest.ip:10.1.1.1,zone.network.type:Advanced,router.name:
 r-60-VM,router.ip:169.254.1.230},wait:0}}] }
 2014-09-11 08:55:27,941 DEBUG [c.c.s.s.SecondaryStorageManagerImpl]
 (secstorage-1:ctx-327037b2) Zone 1 is ready to launch secondary
 storage VM
 2014-09-11 08:55:28,022 DEBUG [c.c.c.ConsoleProxyManagerImpl]
 (consoleproxy-1:ctx-a8ba3b1e) Zone 1 is ready to launch console proxy
 2014-09-11 08:55:28,820 DEBUG [c.c.a.ApiServlet]
 (catalina-exec-16:ctx-58e92382) ===START===  192.168.130.89 -- GET
 command=queryAsyncJobResultjobId=195bf80a-9823-4ec3-add4-8907b98fbaf0
 response=jsonsessionkey=qGZA6KYoc1SB%2Bq2k70HoM%2BBBQTU%3D_=1410418
 528731
 2014-09-11 08:55:29,069 DEBUG [c.c.a.t.Request]
 (AgentManager-Handler-13:null) Seq 7-564304056: Processing:  { Ans: ,
 MgmtId: 77916390353436, via: 7, Ver: v1, Flags: 10,
 [{com.cloud.agent.api.Answer:{result:true,wait:0}}] }
 2014-09-11 08:55:29,069 DEBUG [c.c.a.t.Request]
 

Re: Unable to start a VM due to insufficient capacity

[Ugo Vasi]

Hi Geoff,
I restarted the network and now I can create new VM without errors.

Now, how can I prevent this issue?




Il 11/09/2014 09:28, Geoff Higginbottom ha scritto:

Hi Ugo,

Did restarting the network with cleanup option resolve your issue last time, if 
yes have you tried the same on this network?

Regards

Geoff Higginbottom
CTO / Cloud Architect

D: +44 20 3603 0542tel:+442036030542 | S: +44 20 3603 0540tel:+442036030540 | M: 
+447968161581tel:+447968161581

geoff.higginbot...@shapeblue.commailto:geoff.higginbot...@shapeblue.com | 
www.shapeblue.comhtp://www.shapeblue.com/ | 
Twitter:@cloudstackguruhttps://twitter.com/#!/cloudstackguru

ShapeBlue Ltd, 53 Chandos Place, Covent Garden, London, WC2N 
4HSx-apple-data-detectors://5


On 11 Sep 2014, at 08:17, Ugo Vasi 
ugo.v...@procne.itmailto:ugo.v...@procne.it wrote:

Hi Geoff,
I still have the problem creating new VMs but in another isolated network. The 
problem seems to be the same:

2014-09-11 08:55:27,048 DEBUG [c.c.v.VirtualMachineManagerImpl] 
(Job-Executor-55:ctx-b5c34ec7 ctx-3715f5de) VM is being created in podId: 1
2014-09-11 08:55:27,050 DEBUG [o.a.c.e.o.NetworkOrchestrator] 
(Job-Executor-55:ctx-b5c34ec7 ctx-3715f5de) Network id=212 is already 
implemented
2014-09-11 08:55:27,118 DEBUG [c.c.n.NetworkModelImpl] 
(Job-Executor-55:ctx-b5c34ec7 ctx-3715f5de) Service SecurityGroup is not 
supported in the network id=212
2014-09-11 08:55:27,122 DEBUG [o.a.c.e.o.NetworkOrchestrator] 
(Job-Executor-55:ctx-b5c34ec7 ctx-3715f5de) Changing active number of nics for 
network id=212 on 1
2014-09-11 08:55:27,174 DEBUG [o.a.c.e.o.NetworkOrchestrator] 
(Job-Executor-55:ctx-b5c34ec7 ctx-3715f5de) Asking VirtualRouter to prepare for 
Nic[116-86-8429f13f-7c3b-4b8a-aea3-9b8e9a3f4c03-10.1.1.19]
2014-09-11 08:55:27,181 DEBUG [c.c.n.r.VirtualNetworkApplianceManagerImpl] 
(Job-Executor-55:ctx-b5c34ec7 ctx-3715f5de) Lock is acquired for network id 212 as a 
part of router startup in 
Dest[Zone(Id)-Pod(Id)-Cluster(Id)-Host(Id)-Storage(Volume(Id|Type--Pool(Id))] : 
Dest[Zone(1)-Pod(1)-Cluster(1)-Host(7)-Storage(Volume(98|ROOT--Pool(6))]
2014-09-11 08:55:27,183 DEBUG [c.c.n.r.VirtualNetworkApplianceManagerImpl] 
(Job-Executor-55:ctx-b5c34ec7 ctx-3715f5de) Lock is released for network id 212 as a 
part of router startup in 
Dest[Zone(Id)-Pod(Id)-Cluster(Id)-Host(Id)-Storage(Volume(Id|Type--Pool(Id))] : 
Dest[Zone(1)-Pod(1)-Cluster(1)-Host(7)-Storage(Volume(98|ROOT--Pool(6))]
2014-09-11 08:55:27,189 DEBUG [c.c.n.NetworkModelImpl] 
(Job-Executor-55:ctx-b5c34ec7 ctx-3715f5de) Service SecurityGroup is not 
supported in the network id=212
2014-09-11 08:55:27,198 DEBUG [c.c.n.NetworkModelImpl] 
(Job-Executor-55:ctx-b5c34ec7 ctx-3715f5de) Service SecurityGroup is not 
supported in the network id=212
2014-09-11 08:55:27,202 DEBUG [c.c.n.r.VirtualNetworkApplianceManagerImpl] 
(Job-Executor-55:ctx-b5c34ec7 ctx-3715f5de) Applying dhcp entry in network 
Ntwk[212|Guest|8]
2014-09-11 08:55:27,215 DEBUG [c.c.a.t.Request] (Job-Executor-55:ctx-b5c34ec7 ctx-3715f5de) Seq 7-564304056: Sending  { Cmd , MgmtId: 77916390353436, via: 7(csh1b), Ver: v1, Flags: 100011, 
[{com.cloud.agent.api.routing.DhcpEntryCommand:{vmMac:02:00:15:76:00:0e,vmIpAddress:10.1.1.19,vmName:giannitest,defaultRouter:10.1.1.1,defaultDns:10.1.1.1,duid:00:03:00:01:02:00:15:76:00:0e,isDefault:true,executeInSequence:false,accessDetails:{router.guest.ip:10.1.1.1,zone.network.type:Advanced,router.name:r-60-VM,router.ip:169.254.1.230},wait:0}}]
 }
2014-09-11 08:55:27,941 DEBUG [c.c.s.s.SecondaryStorageManagerImpl] 
(secstorage-1:ctx-327037b2) Zone 1 is ready to launch secondary storage VM
2014-09-11 08:55:28,022 DEBUG [c.c.c.ConsoleProxyManagerImpl] 
(consoleproxy-1:ctx-a8ba3b1e) Zone 1 is ready to launch console proxy
2014-09-11 08:55:28,820 DEBUG [c.c.a.ApiServlet] (catalina-exec-16:ctx-58e92382) ===START===  
192.168.130.89 -- GET 
command=queryAsyncJobResultjobId=195bf80a-9823-4ec3-add4-8907b98fbaf0response=jsonsessionkey=qGZA6KYoc1SB%2Bq2k70HoM%2BBBQTU%3D_=1410418528731
2014-09-11 08:55:29,069 DEBUG [c.c.a.t.Request] (AgentManager-Handler-13:null) Seq 7-564304056: Processing:  
{ Ans: , MgmtId: 77916390353436, via: 7, Ver: v1, Flags: 10, 
[{com.cloud.agent.api.Answer:{result:true,wait:0}}] }
2014-09-11 08:55:29,069 DEBUG [c.c.a.t.Request] (Job-Executor-55:ctx-b5c34ec7 
ctx-3715f5de) Seq 7-564304056: Received:  { Ans: , MgmtId: 77916390353436, via: 
7, Ver: v1, Flags: 10, { Answer } }
2014-09-11 08:55:29,075 DEBUG [c.c.n.NetworkModelImpl] 
(Job-Executor-55:ctx-b5c34ec7 ctx-3715f5de) Service SecurityGroup is not 
supported in the network id=212
2014-09-11 08:55:29,078 DEBUG [c.c.n.r.VirtualNetworkApplianceManagerImpl] 
(Job-Executor-55:ctx-b5c34ec7 ctx-3715f5de) Applying userdata and password 
entry in network Ntwk[212|Guest|8]
2014-09-11 08:55:29,089 DEBUG [c.c.a.t.Request] (Job-Executor-55:ctx-b5c34ec7 ctx-3715f5de) Seq 7-564304057: Sending  { Cmd , MgmtId: 77916390353436, via: 7(csh1b), Ver: v1, Flags: 100011, 

RE: Unable to start a VM due to insufficient capacity

[Matthew Midgett]

Ugo, I am having an issue just like you. I can deploy the default centos
template but if I try to deploy a iso it looks like its failing in the
network area. I've been reading your emails to Geoff and I have restarted
the network with a clean and that didn't fix my problem. I also restarted
the management servers during this process. I don't know what happed but
ssvm and console quit working. I've spent all day deleting the whole thing
and setting it back up again. Just to find that it's not working. 

Now I just saw this in the logs

Cannot delete or update a parent row: a foreign key constraint fails
(`cloud`.`async_job_join_map`, CONSTRAINT
`fk_async_job_join_map__join_job_id` FOREIGN KEY (`join_job_id`) REFERENCES
`async_job` (`id`))

I am running a 2 node haproxy with virtual ip in front of a galera sql
cluster. 

I dropped the DB, gave the cloud user more permissions. Deleted everything
and restarted and it's doing this all over again. I am running xenserver 6.2
and acs4.4. I even tried 4.3 again and it started doing the same thing.



-Original Message-
From: Ugo Vasi [mailto:ugo.v...@procne.it] 
Sent: Tuesday, September 16, 2014 5:36 AM
To: users@cloudstack.apache.org
Subject: Re: Unable to start a VM due to insufficient capacity

Hi Geoff,
I restarted the network and now I can create new VM without errors.

Now, how can I prevent this issue?




Il 11/09/2014 09:28, Geoff Higginbottom ha scritto:
 Hi Ugo,

 Did restarting the network with cleanup option resolve your issue last
time, if yes have you tried the same on this network?

 Regards

 Geoff Higginbottom
 CTO / Cloud Architect

 D: +44 20 3603 0542tel:+442036030542 | S: +44 20 3603 
 0540tel:+442036030540 | M: +447968161581tel:+447968161581

 geoff.higginbot...@shapeblue.commailto:geoff.higginbottom@shapeblue.c
 om | www.shapeblue.comhtp://www.shapeblue.com/ | 
 Twitter:@cloudstackguruhttps://twitter.com/#!/cloudstackguru

 ShapeBlue Ltd, 53 Chandos Place, Covent Garden, London, WC2N 
 4HSx-apple-data-detectors://5


 On 11 Sep 2014, at 08:17, Ugo Vasi
ugo.v...@procne.itmailto:ugo.v...@procne.it wrote:

 Hi Geoff,
 I still have the problem creating new VMs but in another isolated network.
The problem seems to be the same:

 2014-09-11 08:55:27,048 DEBUG [c.c.v.VirtualMachineManagerImpl] 
 (Job-Executor-55:ctx-b5c34ec7 ctx-3715f5de) VM is being created in 
 podId: 1
 2014-09-11 08:55:27,050 DEBUG [o.a.c.e.o.NetworkOrchestrator] 
 (Job-Executor-55:ctx-b5c34ec7 ctx-3715f5de) Network id=212 is already 
 implemented
 2014-09-11 08:55:27,118 DEBUG [c.c.n.NetworkModelImpl] 
 (Job-Executor-55:ctx-b5c34ec7 ctx-3715f5de) Service SecurityGroup is 
 not supported in the network id=212
 2014-09-11 08:55:27,122 DEBUG [o.a.c.e.o.NetworkOrchestrator] 
 (Job-Executor-55:ctx-b5c34ec7 ctx-3715f5de) Changing active number of 
 nics for network id=212 on 1
 2014-09-11 08:55:27,174 DEBUG [o.a.c.e.o.NetworkOrchestrator] 
 (Job-Executor-55:ctx-b5c34ec7 ctx-3715f5de) Asking VirtualRouter to 
 prepare for Nic[116-86-8429f13f-7c3b-4b8a-aea3-9b8e9a3f4c03-10.1.1.19]
 2014-09-11 08:55:27,181 DEBUG 
 [c.c.n.r.VirtualNetworkApplianceManagerImpl] 
 (Job-Executor-55:ctx-b5c34ec7 ctx-3715f5de) Lock is acquired for 
 network id 212 as a part of router startup in 
 Dest[Zone(Id)-Pod(Id)-Cluster(Id)-Host(Id)-Storage(Volume(Id|Type--Po
 ol(Id))] : 
 Dest[Zone(1)-Pod(1)-Cluster(1)-Host(7)-Storage(Volume(98|ROOT--Pool(6
 ))]
 2014-09-11 08:55:27,183 DEBUG 
 [c.c.n.r.VirtualNetworkApplianceManagerImpl] 
 (Job-Executor-55:ctx-b5c34ec7 ctx-3715f5de) Lock is released for 
 network id 212 as a part of router startup in 
 Dest[Zone(Id)-Pod(Id)-Cluster(Id)-Host(Id)-Storage(Volume(Id|Type--Po
 ol(Id))] : 
 Dest[Zone(1)-Pod(1)-Cluster(1)-Host(7)-Storage(Volume(98|ROOT--Pool(6
 ))]
 2014-09-11 08:55:27,189 DEBUG [c.c.n.NetworkModelImpl] 
 (Job-Executor-55:ctx-b5c34ec7 ctx-3715f5de) Service SecurityGroup is 
 not supported in the network id=212
 2014-09-11 08:55:27,198 DEBUG [c.c.n.NetworkModelImpl] 
 (Job-Executor-55:ctx-b5c34ec7 ctx-3715f5de) Service SecurityGroup is 
 not supported in the network id=212
 2014-09-11 08:55:27,202 DEBUG 
 [c.c.n.r.VirtualNetworkApplianceManagerImpl] 
 (Job-Executor-55:ctx-b5c34ec7 ctx-3715f5de) Applying dhcp entry in 
 network Ntwk[212|Guest|8]
 2014-09-11 08:55:27,215 DEBUG [c.c.a.t.Request] 
 (Job-Executor-55:ctx-b5c34ec7 ctx-3715f5de) Seq 7-564304056: Sending  
 { Cmd , MgmtId: 77916390353436, via: 7(csh1b), Ver: v1, Flags: 100011, 
 [{com.cloud.agent.api.routing.DhcpEntryCommand:{vmMac:02:00:15:76
 :00:0e,vmIpAddress:10.1.1.19,vmName:giannitest,defaultRouter
 :10.1.1.1,defaultDns:10.1.1.1,duid:00:03:00:01:02:00:15:76:0
 0:0e,isDefault:true,executeInSequence:false,accessDetails:{rou
 ter.guest.ip:10.1.1.1,zone.network.type:Advanced,router.name:
 r-60-VM,router.ip:169.254.1.230},wait:0}}] }
 2014-09-11 08:55:27,941 DEBUG [c.c.s.s.SecondaryStorageManagerImpl] 
 (secstorage-1:ctx-327037b2) Zone 1 is ready to launch secondary 
 storage VM
 2014-09-11 

Re: Unable to start a VM due to insufficient capacity

[ilya musayev]

I've seen this before and had similar issues.

Instead of re-installing or dropping DB, you can delete all job_ids that 
are stuck.


For example, this is what i would see in my logs.

(1013,VmWorkJobQueue, 2375) is reaching concurrency limit 1
(1013,VmWorkJobQueue, 2375) is reaching concurrency limit 1
(1433,VmWorkJobQueue, 2470) is reaching concurrency limit 1
(1434,VmWorkJobQueue, 2471) is reaching concurrency limit 1
(1475,VmWorkJobQueue, 2483) is reaching concurrency limit 1
(1477,VmWorkJobQueue, 2484) is reaching concurrency limit 1
(1478,VmWorkJobQueue, 596) is reaching concurrency limit 1
(981,VmWorkJobQueue, 2371) is reaching concurrency limit 1

DELETE ALL FROM BELOW:
SELECT * FROM cloud.sync_queue_item where queue_id=981 or queue_id=1478 
or queue_id=1477 or queue_id=1475 or queue_id=1434 or queue_id=1433 or 
queue_id=1013 ;
SELECT * FROM cloud.sync_queue where id=1433 or id=1434 or id=1475 or 
id=1477 or id=1478 or id=981;


While i did SELECT statement, you can alter to DELETE.

Regards
ilya

On 9/16/14, 6:31 PM, Matthew Midgett wrote:

Ugo, I am having an issue just like you. I can deploy the default centos
template but if I try to deploy a iso it looks like its failing in the
network area. I've been reading your emails to Geoff and I have restarted
the network with a clean and that didn't fix my problem. I also restarted
the management servers during this process. I don't know what happed but
ssvm and console quit working. I've spent all day deleting the whole thing
and setting it back up again. Just to find that it's not working.

Now I just saw this in the logs

Cannot delete or update a parent row: a foreign key constraint fails
(`cloud`.`async_job_join_map`, CONSTRAINT
`fk_async_job_join_map__join_job_id` FOREIGN KEY (`join_job_id`) REFERENCES
`async_job` (`id`))

I am running a 2 node haproxy with virtual ip in front of a galera sql
cluster.

I dropped the DB, gave the cloud user more permissions. Deleted everything
and restarted and it's doing this all over again. I am running xenserver 6.2
and acs4.4. I even tried 4.3 again and it started doing the same thing.



-Original Message-
From: Ugo Vasi [mailto:ugo.v...@procne.it]
Sent: Tuesday, September 16, 2014 5:36 AM
To: users@cloudstack.apache.org
Subject: Re: Unable to start a VM due to insufficient capacity

Hi Geoff,
I restarted the network and now I can create new VM without errors.

Now, how can I prevent this issue?




Il 11/09/2014 09:28, Geoff Higginbottom ha scritto:

Hi Ugo,

Did restarting the network with cleanup option resolve your issue last

time, if yes have you tried the same on this network?

Regards

Geoff Higginbottom
CTO / Cloud Architect

D: +44 20 3603 0542tel:+442036030542 | S: +44 20 3603
0540tel:+442036030540 | M: +447968161581tel:+447968161581

geoff.higginbot...@shapeblue.commailto:geoff.higginbottom@shapeblue.c
om | www.shapeblue.comhtp://www.shapeblue.com/ |
Twitter:@cloudstackguruhttps://twitter.com/#!/cloudstackguru

ShapeBlue Ltd, 53 Chandos Place, Covent Garden, London, WC2N
4HSx-apple-data-detectors://5


On 11 Sep 2014, at 08:17, Ugo Vasi

ugo.v...@procne.itmailto:ugo.v...@procne.it wrote:

Hi Geoff,
I still have the problem creating new VMs but in another isolated network.

The problem seems to be the same:

2014-09-11 08:55:27,048 DEBUG [c.c.v.VirtualMachineManagerImpl]
(Job-Executor-55:ctx-b5c34ec7 ctx-3715f5de) VM is being created in
podId: 1
2014-09-11 08:55:27,050 DEBUG [o.a.c.e.o.NetworkOrchestrator]
(Job-Executor-55:ctx-b5c34ec7 ctx-3715f5de) Network id=212 is already
implemented
2014-09-11 08:55:27,118 DEBUG [c.c.n.NetworkModelImpl]
(Job-Executor-55:ctx-b5c34ec7 ctx-3715f5de) Service SecurityGroup is
not supported in the network id=212
2014-09-11 08:55:27,122 DEBUG [o.a.c.e.o.NetworkOrchestrator]
(Job-Executor-55:ctx-b5c34ec7 ctx-3715f5de) Changing active number of
nics for network id=212 on 1
2014-09-11 08:55:27,174 DEBUG [o.a.c.e.o.NetworkOrchestrator]
(Job-Executor-55:ctx-b5c34ec7 ctx-3715f5de) Asking VirtualRouter to
prepare for Nic[116-86-8429f13f-7c3b-4b8a-aea3-9b8e9a3f4c03-10.1.1.19]
2014-09-11 08:55:27,181 DEBUG
[c.c.n.r.VirtualNetworkApplianceManagerImpl]
(Job-Executor-55:ctx-b5c34ec7 ctx-3715f5de) Lock is acquired for
network id 212 as a part of router startup in
Dest[Zone(Id)-Pod(Id)-Cluster(Id)-Host(Id)-Storage(Volume(Id|Type--Po
ol(Id))] :
Dest[Zone(1)-Pod(1)-Cluster(1)-Host(7)-Storage(Volume(98|ROOT--Pool(6
))]
2014-09-11 08:55:27,183 DEBUG
[c.c.n.r.VirtualNetworkApplianceManagerImpl]
(Job-Executor-55:ctx-b5c34ec7 ctx-3715f5de) Lock is released for
network id 212 as a part of router startup in
Dest[Zone(Id)-Pod(Id)-Cluster(Id)-Host(Id)-Storage(Volume(Id|Type--Po
ol(Id))] :
Dest[Zone(1)-Pod(1)-Cluster(1)-Host(7)-Storage(Volume(98|ROOT--Pool(6
))]
2014-09-11 08:55:27,189 DEBUG [c.c.n.NetworkModelImpl]
(Job-Executor-55:ctx-b5c34ec7 ctx-3715f5de) Service SecurityGroup is
not supported in the network id=212
2014-09-11 08:55:27,198 DEBUG [c.c.n.NetworkModelImpl]

RE: Unable to start a VM due to insufficient capacity

[Matthew Midgett]

Thank you for your answer and I will try that.

-Original Message-
From: ilya musayev [mailto:ilya.mailing.li...@gmail.com] 
Sent: Tuesday, September 16, 2014 11:19 PM
To: users@cloudstack.apache.org
Subject: Re: Unable to start a VM due to insufficient capacity

I've seen this before and had similar issues.

Instead of re-installing or dropping DB, you can delete all job_ids that are
stuck.

For example, this is what i would see in my logs.

(1013,VmWorkJobQueue, 2375) is reaching concurrency limit 1
(1013,VmWorkJobQueue, 2375) is reaching concurrency limit 1
(1433,VmWorkJobQueue, 2470) is reaching concurrency limit 1
(1434,VmWorkJobQueue, 2471) is reaching concurrency limit 1
(1475,VmWorkJobQueue, 2483) is reaching concurrency limit 1
(1477,VmWorkJobQueue, 2484) is reaching concurrency limit 1
(1478,VmWorkJobQueue, 596) is reaching concurrency limit 1
(981,VmWorkJobQueue, 2371) is reaching concurrency limit 1

DELETE ALL FROM BELOW:
SELECT * FROM cloud.sync_queue_item where queue_id=981 or queue_id=1478 or
queue_id=1477 or queue_id=1475 or queue_id=1434 or queue_id=1433 or
queue_id=1013 ;
SELECT * FROM cloud.sync_queue where id=1433 or id=1434 or id=1475 or
id=1477 or id=1478 or id=981;

While i did SELECT statement, you can alter to DELETE.

Regards
ilya

On 9/16/14, 6:31 PM, Matthew Midgett wrote:
 Ugo, I am having an issue just like you. I can deploy the default 
 centos template but if I try to deploy a iso it looks like its failing 
 in the network area. I've been reading your emails to Geoff and I have 
 restarted the network with a clean and that didn't fix my problem. I 
 also restarted the management servers during this process. I don't 
 know what happed but ssvm and console quit working. I've spent all day 
 deleting the whole thing and setting it back up again. Just to find that
it's not working.

 Now I just saw this in the logs

 Cannot delete or update a parent row: a foreign key constraint fails 
 (`cloud`.`async_job_join_map`, CONSTRAINT 
 `fk_async_job_join_map__join_job_id` FOREIGN KEY (`join_job_id`) 
 REFERENCES `async_job` (`id`))

 I am running a 2 node haproxy with virtual ip in front of a galera sql 
 cluster.

 I dropped the DB, gave the cloud user more permissions. Deleted 
 everything and restarted and it's doing this all over again. I am 
 running xenserver 6.2 and acs4.4. I even tried 4.3 again and it started
doing the same thing.



 -Original Message-
 From: Ugo Vasi [mailto:ugo.v...@procne.it]
 Sent: Tuesday, September 16, 2014 5:36 AM
 To: users@cloudstack.apache.org
 Subject: Re: Unable to start a VM due to insufficient capacity

 Hi Geoff,
 I restarted the network and now I can create new VM without errors.

 Now, how can I prevent this issue?




 Il 11/09/2014 09:28, Geoff Higginbottom ha scritto:
 Hi Ugo,

 Did restarting the network with cleanup option resolve your issue 
 last
 time, if yes have you tried the same on this network?
 Regards

 Geoff Higginbottom
 CTO / Cloud Architect

 D: +44 20 3603 0542tel:+442036030542 | S: +44 20 3603 
 0540tel:+442036030540 | M: +447968161581tel:+447968161581

 geoff.higginbot...@shapeblue.commailto:geoff.higginbottom@shapeblue.
 c
 om | www.shapeblue.comhtp://www.shapeblue.com/ |
 Twitter:@cloudstackguruhttps://twitter.com/#!/cloudstackguru

 ShapeBlue Ltd, 53 Chandos Place, Covent Garden, London, WC2N 
 4HSx-apple-data-detectors://5


 On 11 Sep 2014, at 08:17, Ugo Vasi
 ugo.v...@procne.itmailto:ugo.v...@procne.it wrote:
 Hi Geoff,
 I still have the problem creating new VMs but in another isolated
network.
 The problem seems to be the same:
 2014-09-11 08:55:27,048 DEBUG [c.c.v.VirtualMachineManagerImpl]
 (Job-Executor-55:ctx-b5c34ec7 ctx-3715f5de) VM is being created in
 podId: 1
 2014-09-11 08:55:27,050 DEBUG [o.a.c.e.o.NetworkOrchestrator]
 (Job-Executor-55:ctx-b5c34ec7 ctx-3715f5de) Network id=212 is already 
 implemented
 2014-09-11 08:55:27,118 DEBUG [c.c.n.NetworkModelImpl]
 (Job-Executor-55:ctx-b5c34ec7 ctx-3715f5de) Service SecurityGroup is 
 not supported in the network id=212
 2014-09-11 08:55:27,122 DEBUG [o.a.c.e.o.NetworkOrchestrator]
 (Job-Executor-55:ctx-b5c34ec7 ctx-3715f5de) Changing active number of 
 nics for network id=212 on 1
 2014-09-11 08:55:27,174 DEBUG [o.a.c.e.o.NetworkOrchestrator]
 (Job-Executor-55:ctx-b5c34ec7 ctx-3715f5de) Asking VirtualRouter to 
 prepare for 
 Nic[116-86-8429f13f-7c3b-4b8a-aea3-9b8e9a3f4c03-10.1.1.19]
 2014-09-11 08:55:27,181 DEBUG
 [c.c.n.r.VirtualNetworkApplianceManagerImpl]
 (Job-Executor-55:ctx-b5c34ec7 ctx-3715f5de) Lock is acquired for 
 network id 212 as a part of router startup in 
 Dest[Zone(Id)-Pod(Id)-Cluster(Id)-Host(Id)-Storage(Volume(Id|Type--P
 o
 ol(Id))] :
 Dest[Zone(1)-Pod(1)-Cluster(1)-Host(7)-Storage(Volume(98|ROOT--Pool(
 6
 ))]
 2014-09-11 08:55:27,183 DEBUG
 [c.c.n.r.VirtualNetworkApplianceManagerImpl]
 (Job-Executor-55:ctx-b5c34ec7 ctx-3715f5de) Lock is released for 
 network id 212 as a part of router startup in 
 

Re: Unable to start a VM due to insufficient capacity

[Ugo Vasi]

Hi Geoff,
I still have the problem creating new VMs but in another isolated 
network. The problem seems to be the same:


2014-09-11 08:55:27,048 DEBUG [c.c.v.VirtualMachineManagerImpl] 
(Job-Executor-55:ctx-b5c34ec7 ctx-3715f5de) VM is being created in podId: 1
2014-09-11 08:55:27,050 DEBUG [o.a.c.e.o.NetworkOrchestrator] 
(Job-Executor-55:ctx-b5c34ec7 ctx-3715f5de) Network id=212 is already 
implemented
2014-09-11 08:55:27,118 DEBUG [c.c.n.NetworkModelImpl] 
(Job-Executor-55:ctx-b5c34ec7 ctx-3715f5de) Service SecurityGroup is not 
supported in the network id=212
2014-09-11 08:55:27,122 DEBUG [o.a.c.e.o.NetworkOrchestrator] 
(Job-Executor-55:ctx-b5c34ec7 ctx-3715f5de) Changing active number of 
nics for network id=212 on 1
2014-09-11 08:55:27,174 DEBUG [o.a.c.e.o.NetworkOrchestrator] 
(Job-Executor-55:ctx-b5c34ec7 ctx-3715f5de) Asking VirtualRouter to 
prepare for Nic[116-86-8429f13f-7c3b-4b8a-aea3-9b8e9a3f4c03-10.1.1.19]
2014-09-11 08:55:27,181 DEBUG 
[c.c.n.r.VirtualNetworkApplianceManagerImpl] 
(Job-Executor-55:ctx-b5c34ec7 ctx-3715f5de) Lock is acquired for network 
id 212 as a part of router startup in 
Dest[Zone(Id)-Pod(Id)-Cluster(Id)-Host(Id)-Storage(Volume(Id|Type--Pool(Id))] 
: Dest[Zone(1)-Pod(1)-Cluster(1)-Host(7)-Storage(Volume(98|ROOT--Pool(6))]
2014-09-11 08:55:27,183 DEBUG 
[c.c.n.r.VirtualNetworkApplianceManagerImpl] 
(Job-Executor-55:ctx-b5c34ec7 ctx-3715f5de) Lock is released for network 
id 212 as a part of router startup in 
Dest[Zone(Id)-Pod(Id)-Cluster(Id)-Host(Id)-Storage(Volume(Id|Type--Pool(Id))] 
: Dest[Zone(1)-Pod(1)-Cluster(1)-Host(7)-Storage(Volume(98|ROOT--Pool(6))]
2014-09-11 08:55:27,189 DEBUG [c.c.n.NetworkModelImpl] 
(Job-Executor-55:ctx-b5c34ec7 ctx-3715f5de) Service SecurityGroup is not 
supported in the network id=212
2014-09-11 08:55:27,198 DEBUG [c.c.n.NetworkModelImpl] 
(Job-Executor-55:ctx-b5c34ec7 ctx-3715f5de) Service SecurityGroup is not 
supported in the network id=212
2014-09-11 08:55:27,202 DEBUG 
[c.c.n.r.VirtualNetworkApplianceManagerImpl] 
(Job-Executor-55:ctx-b5c34ec7 ctx-3715f5de) Applying dhcp entry in 
network Ntwk[212|Guest|8]
2014-09-11 08:55:27,215 DEBUG [c.c.a.t.Request] 
(Job-Executor-55:ctx-b5c34ec7 ctx-3715f5de) Seq 7-564304056: Sending  { 
Cmd , MgmtId: 77916390353436, via: 7(csh1b), Ver: v1, Flags: 100011, 
[{com.cloud.agent.api.routing.DhcpEntryCommand:{vmMac:02:00:15:76:00:0e,vmIpAddress:10.1.1.19,vmName:giannitest,defaultRouter:10.1.1.1,defaultDns:10.1.1.1,duid:00:03:00:01:02:00:15:76:00:0e,isDefault:true,executeInSequence:false,accessDetails:{router.guest.ip:10.1.1.1,zone.network.type:Advanced,router.name:r-60-VM,router.ip:169.254.1.230},wait:0}}] 
}
2014-09-11 08:55:27,941 DEBUG [c.c.s.s.SecondaryStorageManagerImpl] 
(secstorage-1:ctx-327037b2) Zone 1 is ready to launch secondary storage VM
2014-09-11 08:55:28,022 DEBUG [c.c.c.ConsoleProxyManagerImpl] 
(consoleproxy-1:ctx-a8ba3b1e) Zone 1 is ready to launch console proxy
2014-09-11 08:55:28,820 DEBUG [c.c.a.ApiServlet] 
(catalina-exec-16:ctx-58e92382) ===START===  192.168.130.89 -- GET 
command=queryAsyncJobResultjobId=195bf80a-9823-4ec3-add4-8907b98fbaf0response=jsonsessionkey=qGZA6KYoc1SB%2Bq2k70HoM%2BBBQTU%3D_=1410418528731
2014-09-11 08:55:29,069 DEBUG [c.c.a.t.Request] 
(AgentManager-Handler-13:null) Seq 7-564304056: Processing:  { Ans: , 
MgmtId: 77916390353436, via: 7, Ver: v1, Flags: 10, 
[{com.cloud.agent.api.Answer:{result:true,wait:0}}] }
2014-09-11 08:55:29,069 DEBUG [c.c.a.t.Request] 
(Job-Executor-55:ctx-b5c34ec7 ctx-3715f5de) Seq 7-564304056: Received:  
{ Ans: , MgmtId: 77916390353436, via: 7, Ver: v1, Flags: 10, { Answer } }
2014-09-11 08:55:29,075 DEBUG [c.c.n.NetworkModelImpl] 
(Job-Executor-55:ctx-b5c34ec7 ctx-3715f5de) Service SecurityGroup is not 
supported in the network id=212
2014-09-11 08:55:29,078 DEBUG 
[c.c.n.r.VirtualNetworkApplianceManagerImpl] 
(Job-Executor-55:ctx-b5c34ec7 ctx-3715f5de) Applying userdata and 
password entry in network Ntwk[212|Guest|8]
2014-09-11 08:55:29,089 DEBUG [c.c.a.t.Request] 
(Job-Executor-55:ctx-b5c34ec7 ctx-3715f5de) Seq 7-564304057: Sending  { 
Cmd , MgmtId: 77916390353436, via: 7(csh1b), Ver: v1, Flags: 100011, 
[{com.cloud.agent.api.routing.SavePasswordCommand:{,vmIpAddress:10.1.1.19,vmName:giannitest,executeInSequence:false,accessDetails:{router.guest.ip:10.1.1.1,zone.network.type:Advanced,router.ip:169.254.1.230,router.name:r-60-VM},wait:0}},{com.cloud.agent.api.routing.VmDataCommand:{vmIpAddress:10.1.1.19,vmName:giannitest,executeInSequence:false,accessDetails:{router.guest.ip:10.1.1.1,zone.network.type:Advanced,router.ip:169.254.1.230,router.name:r-60-VM},wait:0}}] 
}
2014-09-11 08:55:29,399 DEBUG [c.c.a.t.Request] 
(AgentManager-Handler-10:null) Seq 7-564304057: Processing:  { Ans: , 
MgmtId: 77916390353436, via: 7, Ver: v1, Flags: 10, 
[{com.cloud.agent.api.Answer:{result:true,wait:0}},{com.cloud.agent.api.Answer:{result:false,details:VmDataCommand 
failed, check agent logs,wait:0}}] }
2014-09-11 08:55:29,491 DEBUG 

Re: Unable to start a VM due to insufficient capacity

[Geoff Higginbottom]

Hi Ugo,

Did restarting the network with cleanup option resolve your issue last time, if 
yes have you tried the same on this network?

Regards

Geoff Higginbottom
CTO / Cloud Architect

D: +44 20 3603 0542tel:+442036030542 | S: +44 20 3603 0540tel:+442036030540 
| M: +447968161581tel:+447968161581

geoff.higginbot...@shapeblue.commailto:geoff.higginbot...@shapeblue.com | 
www.shapeblue.comhtp://www.shapeblue.com/ | 
Twitter:@cloudstackguruhttps://twitter.com/#!/cloudstackguru

ShapeBlue Ltd, 53 Chandos Place, Covent Garden, London, WC2N 
4HSx-apple-data-detectors://5


On 11 Sep 2014, at 08:17, Ugo Vasi 
ugo.v...@procne.itmailto:ugo.v...@procne.it wrote:

Hi Geoff,
I still have the problem creating new VMs but in another isolated network. The 
problem seems to be the same:

2014-09-11 08:55:27,048 DEBUG [c.c.v.VirtualMachineManagerImpl] 
(Job-Executor-55:ctx-b5c34ec7 ctx-3715f5de) VM is being created in podId: 1
2014-09-11 08:55:27,050 DEBUG [o.a.c.e.o.NetworkOrchestrator] 
(Job-Executor-55:ctx-b5c34ec7 ctx-3715f5de) Network id=212 is already 
implemented
2014-09-11 08:55:27,118 DEBUG [c.c.n.NetworkModelImpl] 
(Job-Executor-55:ctx-b5c34ec7 ctx-3715f5de) Service SecurityGroup is not 
supported in the network id=212
2014-09-11 08:55:27,122 DEBUG [o.a.c.e.o.NetworkOrchestrator] 
(Job-Executor-55:ctx-b5c34ec7 ctx-3715f5de) Changing active number of nics for 
network id=212 on 1
2014-09-11 08:55:27,174 DEBUG [o.a.c.e.o.NetworkOrchestrator] 
(Job-Executor-55:ctx-b5c34ec7 ctx-3715f5de) Asking VirtualRouter to prepare for 
Nic[116-86-8429f13f-7c3b-4b8a-aea3-9b8e9a3f4c03-10.1.1.19]
2014-09-11 08:55:27,181 DEBUG [c.c.n.r.VirtualNetworkApplianceManagerImpl] 
(Job-Executor-55:ctx-b5c34ec7 ctx-3715f5de) Lock is acquired for network id 212 
as a part of router startup in 
Dest[Zone(Id)-Pod(Id)-Cluster(Id)-Host(Id)-Storage(Volume(Id|Type--Pool(Id))] 
: Dest[Zone(1)-Pod(1)-Cluster(1)-Host(7)-Storage(Volume(98|ROOT--Pool(6))]
2014-09-11 08:55:27,183 DEBUG [c.c.n.r.VirtualNetworkApplianceManagerImpl] 
(Job-Executor-55:ctx-b5c34ec7 ctx-3715f5de) Lock is released for network id 212 
as a part of router startup in 
Dest[Zone(Id)-Pod(Id)-Cluster(Id)-Host(Id)-Storage(Volume(Id|Type--Pool(Id))] 
: Dest[Zone(1)-Pod(1)-Cluster(1)-Host(7)-Storage(Volume(98|ROOT--Pool(6))]
2014-09-11 08:55:27,189 DEBUG [c.c.n.NetworkModelImpl] 
(Job-Executor-55:ctx-b5c34ec7 ctx-3715f5de) Service SecurityGroup is not 
supported in the network id=212
2014-09-11 08:55:27,198 DEBUG [c.c.n.NetworkModelImpl] 
(Job-Executor-55:ctx-b5c34ec7 ctx-3715f5de) Service SecurityGroup is not 
supported in the network id=212
2014-09-11 08:55:27,202 DEBUG [c.c.n.r.VirtualNetworkApplianceManagerImpl] 
(Job-Executor-55:ctx-b5c34ec7 ctx-3715f5de) Applying dhcp entry in network 
Ntwk[212|Guest|8]
2014-09-11 08:55:27,215 DEBUG [c.c.a.t.Request] (Job-Executor-55:ctx-b5c34ec7 
ctx-3715f5de) Seq 7-564304056: Sending  { Cmd , MgmtId: 77916390353436, via: 
7(csh1b), Ver: v1, Flags: 100011, 
[{com.cloud.agent.api.routing.DhcpEntryCommand:{vmMac:02:00:15:76:00:0e,vmIpAddress:10.1.1.19,vmName:giannitest,defaultRouter:10.1.1.1,defaultDns:10.1.1.1,duid:00:03:00:01:02:00:15:76:00:0e,isDefault:true,executeInSequence:false,accessDetails:{router.guest.ip:10.1.1.1,zone.network.type:Advanced,router.name:r-60-VM,router.ip:169.254.1.230},wait:0}}]
 }
2014-09-11 08:55:27,941 DEBUG [c.c.s.s.SecondaryStorageManagerImpl] 
(secstorage-1:ctx-327037b2) Zone 1 is ready to launch secondary storage VM
2014-09-11 08:55:28,022 DEBUG [c.c.c.ConsoleProxyManagerImpl] 
(consoleproxy-1:ctx-a8ba3b1e) Zone 1 is ready to launch console proxy
2014-09-11 08:55:28,820 DEBUG [c.c.a.ApiServlet] 
(catalina-exec-16:ctx-58e92382) ===START===  192.168.130.89 -- GET 
command=queryAsyncJobResultjobId=195bf80a-9823-4ec3-add4-8907b98fbaf0response=jsonsessionkey=qGZA6KYoc1SB%2Bq2k70HoM%2BBBQTU%3D_=1410418528731
2014-09-11 08:55:29,069 DEBUG [c.c.a.t.Request] (AgentManager-Handler-13:null) 
Seq 7-564304056: Processing:  { Ans: , MgmtId: 77916390353436, via: 7, Ver: v1, 
Flags: 10, [{com.cloud.agent.api.Answer:{result:true,wait:0}}] }
2014-09-11 08:55:29,069 DEBUG [c.c.a.t.Request] (Job-Executor-55:ctx-b5c34ec7 
ctx-3715f5de) Seq 7-564304056: Received:  { Ans: , MgmtId: 77916390353436, via: 
7, Ver: v1, Flags: 10, { Answer } }
2014-09-11 08:55:29,075 DEBUG [c.c.n.NetworkModelImpl] 
(Job-Executor-55:ctx-b5c34ec7 ctx-3715f5de) Service SecurityGroup is not 
supported in the network id=212
2014-09-11 08:55:29,078 DEBUG [c.c.n.r.VirtualNetworkApplianceManagerImpl] 
(Job-Executor-55:ctx-b5c34ec7 ctx-3715f5de) Applying userdata and password 
entry in network Ntwk[212|Guest|8]
2014-09-11 08:55:29,089 DEBUG [c.c.a.t.Request] (Job-Executor-55:ctx-b5c34ec7 
ctx-3715f5de) Seq 7-564304057: Sending  { Cmd , MgmtId: 77916390353436, via: 
7(csh1b), Ver: v1, Flags: 100011, 

Re: Unable to start a VM due to insufficient capacity

[Giri Prasad]

Hi Kirk,

I uninstalled CS 4.3 on Ubuntu 14.04 LTS, and fresh installed CS 4.1. Instance 
creation works correctly. Same hardware and same network setup.

CS 4.3 on Ubuntu 14.04 LTS, had instance creation problem, not sure why.


Best Regards,
Giri




 From: Kirk Kosinski kirkkosin...@gmail.com
To: users@cloudstack.apache.org 
Sent: Wednesday, 3 September 2014 10:47 AM
Subject: Re: Unable to start a VM due to insufficient capacity
 

Hi, Giri.  There was a problem configuring the network fro the VM (see
below log entries).  I'm not sure why, but if the network already exists
it may be out of IPs, or if it doesn't exist there may be no free VLANs
available for a new network.

Best regards,
Kirk



On 09/02/2014 09:34 PM, Giri Prasad wrote:
 2014-09-01 17:21:24,063 INFO  [c.c.u.e.CSExceptionErrorCode] 
 (Job-Executor-6:ctx-d1e72afb ctx-21bde336) Could not find exception: 
 com.cloud.exception.InsufficientVirtualNetworkCapcityException in error code 
 list for exceptions
 2014-09-01 17:21:24,063 DEBUG [o.a.c.e.o.NetworkOrchestrator] 
 (Job-Executor-6:ctx-d1e72afb ctx-21bde336) Cleaning up because we're unable 
 to implement the network Ntwk[204|Guest|8]

Re: Unable to start a VM due to insufficient capacity

[ilya musayev]

grep ctx-d1e72afb /var/log/cloudstack/management-server.log


Read through to see what happens, or post here...

On 9/1/14, 9:23 AM, abhisek basu wrote:

You may want to review entire flow for job-27, which is related to this 
deployment failure. There are multiple possibilities for this  insufficient 
capacity error.

Sent from my iPhone


On 1 Sep 2014, at 6:49 pm, Giri Prasad g_p...@yahoo.com.INVALID wrote:

Hello,

I have installed cs 4.3 on Ubuntu 14.04 LTS.


Created the usual infra, registered a couple of ISO's, and tried to created a 
instance using the ISO, via the gui. Comes out with some error. Any ideas on 
how to fix this?

Thanks  Regards,
Giri
2014-09-01 17:21:26,551 DEBUG [c.c.a.ApiServlet] (catalina-exec-6:ctx-703486f7 ctx-ee65bd67) 
===END===  XXX.XXX.XXX.5 -- GET  
command=queryAsyncJobResultjobId=1b7d53c6-256a-4721-b69c-d68c1f6d7d42response=jsonsessionkey=e6F89zbOUS4dR2%2FmrkznQBxeQ%2BM%3D_=1409572286355
2014-09-01 17:21:26,733 ERROR [c.c.a.ApiAsyncJobDispatcher] 
(Job-Executor-6:ctx-d1e72afb) Unexpected exception while executing 
org.apache.cloudstack.api.command.user.vm.DeployVMCmd
com.cloud.utils.exception.CloudRuntimeException: Unable to start a VM due to 
insufficient capacity
at 
com.cloud.vm.VirtualMachineManagerImpl.start(VirtualMachineManagerImpl.java:605)
at 
org.apache.cloudstack.engine.cloud.entity.api.VMEntityManagerImpl.deployVirtualMachine(VMEntityManagerImpl.java:237)
at 
org.apache.cloudstack.engine.cloud.entity.api.VirtualMachineEntityImpl.deploy(VirtualMachineEntityImpl.java:207)
at 
com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:3581)
at 
com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:3161)
at 
com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:3147)
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:622)
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 
com.cloud.event.ActionEventInterceptor.invoke(ActionEventInterceptor.java:50)
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.$Proxy169.startVirtualMachine(Unknown Source)
at 
org.apache.cloudstack.api.command.user.vm.DeployVMCmd.execute(DeployVMCmd.java:443)
at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:161)
at 
com.cloud.api.ApiAsyncJobDispatcher.runJobInContext(ApiAsyncJobDispatcher.java:109)
at com.cloud.api.ApiAsyncJobDispatcher$1.run(ApiAsyncJobDispatcher.java:66)
at 
org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56)
at 
org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103)
at 
org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53)
at com.cloud.api.ApiAsyncJobDispatcher.runJob(ApiAsyncJobDispatcher.java:63)
at 
org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.runInContext(AsyncJobManagerImpl.java:509)
at 
org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:49)
at 
org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56)
at 
org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103)
at 
org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53)
at 
org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:46)
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.java:1146)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:701)
Caused by: 

Re: Unable to start a VM due to insufficient capacity

[Giri Prasad]

CS on Ubuntu 12.04 LTS, 4.1 is working correctly on the same hardware 
(partition1).

This problem is with CS 4.3 on Ubuntu 14.04 LTS (partition2):


2014-09-01 17:21:23,267 INFO  [o.a.c.f.j.i.AsyncJobMonitor] 
(Job-Executor-6:ctx-d1e72afb) Add job-27 into job monitoring
2014-09-01 17:21:23,267 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl] 
(Job-Executor-6:ctx-d1e72afb) Executing AsyncJobVO {id:27, userId: 2, 
accountId: 2, instanceType: VirtualMachine, instanceId: 6, cmd: 
org.apache.cloudstack.api.command.user.vm.DeployVMCmd, cmdInfo: 
{sessionkey:aa/b/,serviceofferingid:,cmdEventType:VM.CREATE,ctxUserId:2,zoneid:,httpmethod:GET,networkids:,response:json,id:6,hypervisor:KVM,name:ubuntu-12-04-64bit-admin-Instance,_:1409572282666,ctxAccountId:2,diskofferingid:99218ad6-b601-4dc1-a266-9b0616e7474a,ctxStartEventId:105,displayname:ubuntu-12-04-64bit-admin-Instance},
 cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0, result: 
null, initMsid: 279278805451282, completeMsid: null, lastUpdated: null, 
lastPolled: null, created: null}
2014-09-01 17:21:23,272 DEBUG [c.c.a.ApiDispatcher] 
(Job-Executor-6:ctx-d1e72afb ctx-21bde336) InfrastructureEntity name 
is:com.cloud.offering.ServiceOffering
2014-09-01 17:21:23,273 DEBUG [c.c.a.ApiDispatcher] 
(Job-Executor-6:ctx-d1e72afb ctx-21bde336) ControlledEntity name 
is:com.cloud.template.VirtualMachineTemplate
2014-09-01 17:21:23,275 DEBUG [c.c.a.ApiDispatcher] 
(Job-Executor-6:ctx-d1e72afb ctx-21bde336) ControlledEntity name 
is:com.cloud.network.Network
2014-09-01 17:21:23,277 DEBUG [c.c.a.ApiDispatcher] 
(Job-Executor-6:ctx-d1e72afb ctx-21bde336) InfrastructureEntity name 
is:com.cloud.offering.DiskOffering
2014-09-01 17:21:23,443 DEBUG [c.c.n.NetworkModelImpl] 
(Job-Executor-6:ctx-d1e72afb ctx-21bde336) Service SecurityGroup is not 
supported in the network id=204
2014-09-01 17:21:23,445 DEBUG [c.c.n.NetworkModelImpl] 
(Job-Executor-6:ctx-d1e72afb ctx-21bde336) Service SecurityGroup is not 
supported in the network id=204
2014-09-01 17:21:23,455 DEBUG [c.c.d.DeploymentPlanningManagerImpl] 
(Job-Executor-6:ctx-d1e72afb ctx-21bde336) Deploy avoids pods: [], clusters: 
[], hosts: []
2014-09-01 17:21:23,456 DEBUG [c.c.d.DeploymentPlanningManagerImpl] 
(Job-Executor-6:ctx-d1e72afb ctx-21bde336) DeploymentPlanner allocation 
algorithm: com.cloud.deploy.FirstFitPlanner@7c4a754a
2014-09-01 17:21:23,456 DEBUG [c.c.d.DeploymentPlanningManagerImpl] 
(Job-Executor-6:ctx-d1e72afb ctx-21bde336) Trying to allocate a host and 
storage pools from dc:1, pod:null,cluster:null, requested cpu: 1000, requested 
ram: 1073741824
2014-09-01 17:21:23,456 DEBUG [c.c.d.DeploymentPlanningManagerImpl] 
(Job-Executor-6:ctx-d1e72afb ctx-21bde336) Is ROOT volume READY (pool already 
allocated)?: No
2014-09-01 17:21:23,456 DEBUG [c.c.d.FirstFitPlanner] 
(Job-Executor-6:ctx-d1e72afb ctx-21bde336) Searching all possible resources 
under this Zone: 1
2014-09-01 17:21:23,457 DEBUG [c.c.d.FirstFitPlanner] 
(Job-Executor-6:ctx-d1e72afb ctx-21bde336) Listing clusters in order of 
aggregate capacity, that have (atleast one host with) enough CPU and RAM 
capacity under this Zone: 1
2014-09-01 17:21:23,459 DEBUG [c.c.d.FirstFitPlanner] 
(Job-Executor-6:ctx-d1e72afb ctx-21bde336) Removing from the clusterId list 
these clusters from avoid set: []
2014-09-01 17:21:23,463 DEBUG [c.c.d.DeploymentPlanningManagerImpl] 
(Job-Executor-6:ctx-d1e72afb ctx-21bde336) Checking resources in Cluster: 1 
under Pod: 1
2014-09-01 17:21:23,463 DEBUG [c.c.a.m.a.i.FirstFitAllocator] 
(Job-Executor-6:ctx-d1e72afb ctx-21bde336 FirstFitRoutingAllocator) Looking for 
hosts in dc: 1  pod:1  cluster:1
2014-09-01 17:21:23,465 DEBUG [c.c.a.m.a.i.FirstFitAllocator] 
(Job-Executor-6:ctx-d1e72afb ctx-21bde336 FirstFitRoutingAllocator) 
FirstFitAllocator has 1 hosts to check for allocation: [Host[-1-Routing]]
2014-09-01 17:21:23,466 DEBUG [c.c.a.m.a.i.FirstFitAllocator] 
(Job-Executor-6:ctx-d1e72afb ctx-21bde336 FirstFitRoutingAllocator) Found 1 
hosts for allocation after prioritization: [Host[-1-Routing]]
2014-09-01 17:21:23,466 DEBUG [c.c.a.m.a.i.FirstFitAllocator] 
(Job-Executor-6:ctx-d1e72afb ctx-21bde336 FirstFitRoutingAllocator) Looking for 
speed=1000Mhz, Ram=1024
2014-09-01 17:21:23,469 DEBUG [c.c.c.CapacityManagerImpl] 
(Job-Executor-6:ctx-d1e72afb ctx-21bde336 FirstFitRoutingAllocator) Host: 1 has 
cpu capability (cpu:4, speed:2801) to support requested CPU: 1 and requested 
speed: 1000
2014-09-01 17:21:23,469 DEBUG [c.c.c.CapacityManagerImpl] 
(Job-Executor-6:ctx-d1e72afb ctx-21bde336 FirstFitRoutingAllocator) Checking if 
host: 1 has enough capacity for requested CPU: 1000 and requested RAM: 
1073741824 , cpuOverprovisioningFactor: 1.0
2014-09-01 17:21:23,471 DEBUG [c.c.c.CapacityManagerImpl] 
(Job-Executor-6:ctx-d1e72afb ctx-21bde336 FirstFitRoutingAllocator) Hosts's 
actual total CPU: 11204 and CPU after 

Re: Unable to start a VM due to insufficient capacity

[Kirk Kosinski]

Hi, Giri.  There was a problem configuring the network fro the VM (see
below log entries).  I'm not sure why, but if the network already exists
it may be out of IPs, or if it doesn't exist there may be no free VLANs
available for a new network.

Best regards,
Kirk


On 09/02/2014 09:34 PM, Giri Prasad wrote:
 2014-09-01 17:21:24,063 INFO  [c.c.u.e.CSExceptionErrorCode] 
 (Job-Executor-6:ctx-d1e72afb ctx-21bde336) Could not find exception: 
 com.cloud.exception.InsufficientVirtualNetworkCapcityException in error code 
 list for exceptions
 2014-09-01 17:21:24,063 DEBUG [o.a.c.e.o.NetworkOrchestrator] 
 (Job-Executor-6:ctx-d1e72afb ctx-21bde336) Cleaning up because we're unable 
 to implement the network Ntwk[204|Guest|8]

Unable to start a VM due to insufficient capacity

[Giri Prasad]

Hello,

 I have installed cs 4.3 on Ubuntu 14.04 LTS. 


Created the usual infra, registered a couple of ISO's, and tried to created a 
instance using the ISO, via the gui. Comes out with some error. Any ideas on 
how to fix this?

Thanks  Regards,
Giri
2014-09-01 17:21:26,551 DEBUG [c.c.a.ApiServlet] (catalina-exec-6:ctx-703486f7 
ctx-ee65bd67) ===END===  XXX.XXX.XXX.5 -- GET  
command=queryAsyncJobResultjobId=1b7d53c6-256a-4721-b69c-d68c1f6d7d42response=jsonsessionkey=e6F89zbOUS4dR2%2FmrkznQBxeQ%2BM%3D_=1409572286355
2014-09-01 17:21:26,733 ERROR [c.c.a.ApiAsyncJobDispatcher] 
(Job-Executor-6:ctx-d1e72afb) Unexpected exception while executing 
org.apache.cloudstack.api.command.user.vm.DeployVMCmd
com.cloud.utils.exception.CloudRuntimeException: Unable to start a VM due to 
insufficient capacity
at 
com.cloud.vm.VirtualMachineManagerImpl.start(VirtualMachineManagerImpl.java:605)
at 
org.apache.cloudstack.engine.cloud.entity.api.VMEntityManagerImpl.deployVirtualMachine(VMEntityManagerImpl.java:237)
at 
org.apache.cloudstack.engine.cloud.entity.api.VirtualMachineEntityImpl.deploy(VirtualMachineEntityImpl.java:207)
at 
com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:3581)
at 
com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:3161)
at 
com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:3147)
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:622)
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 
com.cloud.event.ActionEventInterceptor.invoke(ActionEventInterceptor.java:50)
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.$Proxy169.startVirtualMachine(Unknown Source)
at 
org.apache.cloudstack.api.command.user.vm.DeployVMCmd.execute(DeployVMCmd.java:443)
at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:161)
at 
com.cloud.api.ApiAsyncJobDispatcher.runJobInContext(ApiAsyncJobDispatcher.java:109)
at com.cloud.api.ApiAsyncJobDispatcher$1.run(ApiAsyncJobDispatcher.java:66)
at 
org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56)
at 
org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103)
at 
org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53)
at com.cloud.api.ApiAsyncJobDispatcher.runJob(ApiAsyncJobDispatcher.java:63)
at 
org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.runInContext(AsyncJobManagerImpl.java:509)
at 
org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:49)
at 
org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56)
at 
org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103)
at 
org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53)
at 
org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:46)
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.java:1146)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:701)
Caused by: com.cloud.exception.InsufficientServerCapacityException: Unable to 
create a deployment for 
VM[User|ubuntu-12-04-64bit-admin-Instance]Scope=interface 
com.cloud.dc.DataCenter; id=1
at 
com.cloud.vm.VirtualMachineManagerImpl.orchestrateStart(VirtualMachineManagerImpl.java:921)
at 
com.cloud.vm.VirtualMachineManagerImpl.advanceStart(VirtualMachineManagerImpl.java:761)
at 
com.cloud.vm.VirtualMachineManagerImpl.start(VirtualMachineManagerImpl.java:601)
  

Re: Unable to start a VM due to insufficient capacity

[abhisek basu]

You may want to review entire flow for job-27, which is related to this 
deployment failure. There are multiple possibilities for this  insufficient 
capacity error.

Sent from my iPhone

 On 1 Sep 2014, at 6:49 pm, Giri Prasad g_p...@yahoo.com.INVALID wrote:
 
 Hello,
 
 I have installed cs 4.3 on Ubuntu 14.04 LTS. 
 
 
 Created the usual infra, registered a couple of ISO's, and tried to created a 
 instance using the ISO, via the gui. Comes out with some error. Any ideas on 
 how to fix this?
 
 Thanks  Regards,
 Giri
 2014-09-01 17:21:26,551 DEBUG [c.c.a.ApiServlet] 
 (catalina-exec-6:ctx-703486f7 ctx-ee65bd67) ===END===  XXX.XXX.XXX.5 -- GET  
 command=queryAsyncJobResultjobId=1b7d53c6-256a-4721-b69c-d68c1f6d7d42response=jsonsessionkey=e6F89zbOUS4dR2%2FmrkznQBxeQ%2BM%3D_=1409572286355
 2014-09-01 17:21:26,733 ERROR [c.c.a.ApiAsyncJobDispatcher] 
 (Job-Executor-6:ctx-d1e72afb) Unexpected exception while executing 
 org.apache.cloudstack.api.command.user.vm.DeployVMCmd
 com.cloud.utils.exception.CloudRuntimeException: Unable to start a VM due to 
 insufficient capacity
at 
 com.cloud.vm.VirtualMachineManagerImpl.start(VirtualMachineManagerImpl.java:605)
at 
 org.apache.cloudstack.engine.cloud.entity.api.VMEntityManagerImpl.deployVirtualMachine(VMEntityManagerImpl.java:237)
at 
 org.apache.cloudstack.engine.cloud.entity.api.VirtualMachineEntityImpl.deploy(VirtualMachineEntityImpl.java:207)
at 
 com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:3581)
at 
 com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:3161)
at 
 com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:3147)
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:622)
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 
 com.cloud.event.ActionEventInterceptor.invoke(ActionEventInterceptor.java:50)
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.$Proxy169.startVirtualMachine(Unknown Source)
at 
 org.apache.cloudstack.api.command.user.vm.DeployVMCmd.execute(DeployVMCmd.java:443)
at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:161)
at 
 com.cloud.api.ApiAsyncJobDispatcher.runJobInContext(ApiAsyncJobDispatcher.java:109)
at com.cloud.api.ApiAsyncJobDispatcher$1.run(ApiAsyncJobDispatcher.java:66)
at 
 org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56)
at 
 org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103)
at 
 org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53)
at 
 com.cloud.api.ApiAsyncJobDispatcher.runJob(ApiAsyncJobDispatcher.java:63)
at 
 org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.runInContext(AsyncJobManagerImpl.java:509)
at 
 org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:49)
at 
 org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56)
at 
 org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103)
at 
 org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53)
at 
 org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:46)
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.java:1146)
at 
 java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:701)
 Caused by: com.cloud.exception.InsufficientServerCapacityException: Unable to 
 create a deployment for 
 VM[User|ubuntu-12-04-64bit-admin-Instance]Scope=interface 
 

Re: Unable to start a VM due to insufficient capacity

[Ugo Vasi]

Hi Geoff,
I tried restarting r-29-VM but the problem is still blocking creation of 
new VM in that isolated network.


Creating a new VM in another isolated network, it works. Where can I 
look at to find the problem?




Il 31/07/2014 21:53, Geoff Higginbottom ha scritto:

Ugo,

Looks like CS is failing to update the VR with details for the new VM, try 
restarting the VR.

Regards

Geoff Higginbottom
CTO / Cloud Architect


D: +44 20 3603 0542tel:+442036030542 | S: +44 20 3603 0540tel:+442036030540 | M: 
+447968161581tel:+447968161581

geoff.higginbot...@shapeblue.commailto:geoff.higginbot...@shapeblue.com | 
www.shapeblue.comhtp://www.shapeblue.com/

ShapeBlue Ltd, 53 Chandos Place, Covent Garden, London, WC2N 
4HSx-apple-data-detectors://37



On 31 Jul 2014, at 15:40, Ugo Vasi 
ugo.v...@procne.itmailto:ugo.v...@procne.it wrote:

Hi everybody,
I installed a CloudStack 4.3.0 system with a manager (in a virtual machine), 
two NFS primary storage, one NFS secondary storare and two host agent on ubuntu 
distribution.

The cluster have one advanced zone without security group configuration with 
KVM hipervisors.

I create some VM but now does not allow me to create more giving the error message 
Unable to start a VM due to insufficient capacity.

I am sure that the resources (ip, ram, cpu and storage) are enough to create 
new instances. In dashboard I see all ok.

From the management-server.log I see this errors messages (see attachment for 
full version) when I try to deploy a new virtual machine with 1x1GHz cpu, 1GB or 
RAM and 20GB disk space:

2014-07-31 14:59:11,983 DEBUG [c.c.a.t.Request] (AgentManager-Handler-12:null) Seq 1-684594119: Processing:  { Ans: , MgmtId: 77916390353436, via: 1, Ver: v1, 
Flags: 10, 
[{com.cloud.agent.api.Answer:{result:true,wait:0}},{com.cloud.agent.api.Answer:{result:false,details:VmDataCommand
 failed, check agent logs,wait:0}}] }
2014-07-31 14:59:11,983 INFO  [c.c.v.VirtualMachineManagerImpl] 
(Job-Executor-26:ctx-ab3aee38 ctx-d8600c16) Unable to contact resource.
com.cloud.exception.ResourceUnavailableException: Resource [DataCenter:1] is 
unreachable: Unable to apply userdata and password entry on router
2014-07-31 14:59:12,453 DEBUG [c.c.c.CapacityManagerImpl] 
(Job-Executor-26:ctx-ab3aee38 ctx-d8600c16) VM state transitted from :Starting 
to Stopped with event: OperationFailedvm's original host id: null new host id: 
null host id before state transition: 7
2014-07-31 14:59:12,677 DEBUG [c.c.c.CapacityManagerImpl] 
(Job-Executor-26:ctx-ab3aee38 ctx-d8600c16) VM state transitted from :Starting 
to Stopped with event: OperationFailedvm's original host id: null new host id: 
null host id before state transition: null
2014-07-31 14:59:12,708 DEBUG [c.c.v.UserVmManagerImpl] 
(Job-Executor-26:ctx-ab3aee38 ctx-d8600c16) Destroying vm VM[User|csweb2] as it 
failed to create on Host with Id:null
2014-07-31 14:59:12,738 DEBUG [c.c.c.CapacityManagerImpl] 
(Job-Executor-26:ctx-ab3aee38 ctx-d8600c16) 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-07-31 14:59:12,929 WARN  [o.a.c.alerts] (Job-Executor-26:ctx-ab3aee38 
ctx-d8600c16)  alertType:: 8 // dataCenterId:: 1 // podId:: 1 // clusterId:: 
null // message:: Failed to deploy Vm with Id: 70, on Host with Id: null
2014-07-31 14:59:13,159 ERROR [c.c.a.ApiAsyncJobDispatcher] 
(Job-Executor-26:ctx-ab3aee38) Unexpected exception while executing 
org.apache.cloudstack.api.command.user.vm.DeployVMCmd
com.cloud.utils.exception.CloudRuntimeException: Unable to start a VM due to 
insufficient capacity
Caused by: com.cloud.exception.InsufficientServerCapacityException: Unable to 
create a deployment for VM[User|csweb2]Scope=interface com.cloud.dc.DataCenter; 
id=1
2014-07-31 14:59:13,161 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl] (Job-Executor-26:ctx-ab3aee38) Complete async job-783, 
jobStatus: FAILED, resultCode: 530, result: 
org.apache.cloudstack.api.response.ExceptionResponse/null/{uuidList:[],errorcode:530,errortext:Unable
 to start a VM due to insufficient capacity}
2014-07-31 14:59:46,280 DEBUG [c.c.v.VirtualMachineManagerImpl] 
(Job-Executor-27:ctx-82be396e ctx-41f0cf24) Stopped called on VM[User|csweb2] 
but the state is Error
2014-07-31 14:59:46,330 DEBUG [c.c.c.CapacityManagerImpl] 
(Job-Executor-27:ctx-82be396e ctx-41f0cf24) VM state transitted from :Error to 
Expunging with event: DestroyRequestedvm's original host id: null new host id: 
null host id before state transition: null

I tried to search in others log file (VmDataCommand failed, check agent 
logs), but I don't found nothing...

Can anyone Help me?

--

  U g o   V a s iugo.v...@procne.itmailto:ugo.v...@procne.it
  P r o c n e  s.r.l)
  via Cotonificio 45  33010 Tavagnacco IT
  phone: +390432486523 fax: +390432486523

Le informazioni contenute in questo messaggio sono riservate e
confidenziali ed ? vietata la diffusione in qualunque modo 

Re: Unable to start a VM due to insufficient capacity

[Geoff Higginbottom]

Ugo,

Login to the VR and tail the messages log then attempt to start the VM, you 
should see various messages re DHCP updating etc in the VR.  If you don't see 
the VR update try restarting the network Iain the 'cleanup' option, this will 
create a new VR.

Regards

Geoff Higginbottom
CTO / Cloud Architect

D: +44 20 3603 0542tel:+442036030542 | S: +44 20 3603 0540tel:+442036030540 
| M: +447968161581tel:+447968161581

geoff.higginbot...@shapeblue.commailto:geoff.higginbot...@shapeblue.com | 
www.shapeblue.comhtp://www.shapeblue.com/ | 
Twitter:@cloudstackguruhttps://twitter.com/#!/cloudstackguru

ShapeBlue Ltd, 53 Chandos Place, Covent Garden, London, WC2N 
4HSx-apple-data-detectors://5


On 1 Aug 2014, at 09:06, Ugo Vasi 
ugo.v...@procne.itmailto:ugo.v...@procne.it wrote:

Hi Geoff,
I tried restarting r-29-VM but the problem is still blocking creation of new VM 
in that isolated network.

Creating a new VM in another isolated network, it works. Where can I look at to 
find the problem?



Il 31/07/2014 21:53, Geoff Higginbottom ha scritto:
Ugo,

Looks like CS is failing to update the VR with details for the new VM, try 
restarting the VR.

Regards

Geoff Higginbottom
CTO / Cloud Architect


D: +44 20 3603 0542tel:+442036030542 | S: +44 20 3603 0540tel:+442036030540 
| M: +447968161581tel:+447968161581

geoff.higginbot...@shapeblue.commailto:geoff.higginbot...@shapeblue.commailto:geoff.higginbot...@shapeblue.com
 | www.shapeblue.comhttp://www.shapeblue.comhtp://www.shapeblue.com/

ShapeBlue Ltd, 53 Chandos Place, Covent Garden, London, WC2N 
4HSx-apple-data-detectors://37



On 31 Jul 2014, at 15:40, Ugo Vasi 
ugo.v...@procne.itmailto:ugo.v...@procne.itmailto:ugo.v...@procne.it 
wrote:

Hi everybody,
I installed a CloudStack 4.3.0 system with a manager (in a virtual machine), 
two NFS primary storage, one NFS secondary storare and two host agent on ubuntu 
distribution.

The cluster have one advanced zone without security group configuration with 
KVM hipervisors.

I create some VM but now does not allow me to create more giving the error 
message Unable to start a VM due to insufficient capacity.

I am sure that the resources (ip, ram, cpu and storage) are enough to create 
new instances. In dashboard I see all ok.

From the management-server.log I see this errors messages (see attachment for 
full version) when I try to deploy a new virtual machine with 1x1GHz cpu, 1GB 
or RAM and 20GB disk space:

2014-07-31 14:59:11,983 DEBUG [c.c.a.t.Request] (AgentManager-Handler-12:null) 
Seq 1-684594119: Processing:  { Ans: , MgmtId: 77916390353436, via: 1, Ver: v1, 
Flags: 10, 
[{com.cloud.agent.api.Answer:{result:true,wait:0}},{com.cloud.agent.api.Answer:{result:false,details:VmDataCommand
 failed, check agent logs,wait:0}}] }
2014-07-31 14:59:11,983 INFO  [c.c.v.VirtualMachineManagerImpl] 
(Job-Executor-26:ctx-ab3aee38 ctx-d8600c16) Unable to contact resource.
com.cloud.exception.ResourceUnavailableException: Resource [DataCenter:1] is 
unreachable: Unable to apply userdata and password entry on router
2014-07-31 14:59:12,453 DEBUG [c.c.c.CapacityManagerImpl] 
(Job-Executor-26:ctx-ab3aee38 ctx-d8600c16) VM state transitted from :Starting 
to Stopped with event: OperationFailedvm's original host id: null new host id: 
null host id before state transition: 7
2014-07-31 14:59:12,677 DEBUG [c.c.c.CapacityManagerImpl] 
(Job-Executor-26:ctx-ab3aee38 ctx-d8600c16) VM state transitted from :Starting 
to Stopped with event: OperationFailedvm's original host id: null new host id: 
null host id before state transition: null
2014-07-31 14:59:12,708 DEBUG [c.c.v.UserVmManagerImpl] 
(Job-Executor-26:ctx-ab3aee38 ctx-d8600c16) Destroying vm VM[User|csweb2] as it 
failed to create on Host with Id:null
2014-07-31 14:59:12,738 DEBUG [c.c.c.CapacityManagerImpl] 
(Job-Executor-26:ctx-ab3aee38 ctx-d8600c16) 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-07-31 14:59:12,929 WARN  [o.a.c.alerts] (Job-Executor-26:ctx-ab3aee38 
ctx-d8600c16)  alertType:: 8 // dataCenterId:: 1 // podId:: 1 // clusterId:: 
null // message:: Failed to deploy Vm with Id: 70, on Host with Id: null
2014-07-31 14:59:13,159 ERROR [c.c.a.ApiAsyncJobDispatcher] 
(Job-Executor-26:ctx-ab3aee38) Unexpected exception while executing 
org.apache.cloudstack.api.command.user.vm.DeployVMCmd
com.cloud.utils.exception.CloudRuntimeException: Unable to start a VM due to 
insufficient capacity
Caused by: com.cloud.exception.InsufficientServerCapacityException: Unable to 
create a deployment for VM[User|csweb2]Scope=interface com.cloud.dc.DataCenter; 
id=1
2014-07-31 14:59:13,161 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl] 
(Job-Executor-26:ctx-ab3aee38) Complete async job-783, jobStatus: FAILED, 
resultCode: 530, result: 
org.apache.cloudstack.api.response.ExceptionResponse/null/{uuidList:[],errorcode:530,errortext:Unable
 to start a VM due to insufficient 

Re: Unable to start a VM due to insufficient capacity

[Ugo Vasi]

Hi,
after that error, I can only destroy the virtual machine, I cannot 
restart it via web interface.
I had looked inside the log files any trace of the error but have not 
found anything.


These are the files I see, which of these I should see in the next test?

root@r-29-VM:~# ls -ltr /var/log/
total 212373
drwxr-xr-x 2 ntp ntp   1024 May 12  2012 ntpstats
drwxr-x--- 2 rootadm   1024 Dec  3  2013 samba
-rw-rw 1 rootutmp 0 Jan 15  2014 btmp-20140701
drwxr-xr-x 2 rootroot  1024 Jan 15  2014 fsck
-rw-r- 1 rootadm 59 Jan 15  2014 dmesg.3.gz
-rw-r--r-- 1 rootroot   531 Jan 15  2014 aptitude-20140701.gz
drwxr-xr-x 3 rootroot  1024 Jan 15  2014 installer
drwxr-xr-x 2 rootroot  1024 Jan 15  2014 news
-rw-r- 1 rootadm  0 Jan 15  2014 mail.warn
-rw-r- 1 rootadm  0 Jan 15  2014 mail.log
-rw-r- 1 rootadm  0 Jan 15  2014 mail.info
-rw-r- 1 rootadm  0 Jan 15  2014 mail.err
-rw-r- 1 rootadm  0 Jan 15  2014 lpr.log
-rw-r- 1 rootadm   7136 Jan 15  2014 dmesg.2.gz
-rw-r- 1 rootadm   8647 Jan 15  2014 debug-20140626
-rw-r--r-- 1 rootroot 32032 Jan 15  2014 faillog
-rw-r--r-- 1 rootroot 18329 Jan 15  2014 alternatives.log-20140701
-rw-r--r-- 1 rootroot258369 Jan 15  2014 dpkg.log-20140701
-rw-r- 1 rootadm  11920 Jan 15  2014 user.log-20140626
-rw-r- 1 rootadm  51165 Jan 15  2014 syslog-20140626
-rw-r- 1 rootadm498 Jan 15  2014 monit.log
-rw-r- 1 rootadm  0 Jun 24 14:51 haproxy.log
-rw-r- 1 rootadm  27326 Jun 24 15:25 dmesg.0
-rw-rw-r-- 1 rootutmp 43776 Jun 24 15:25 wtmp-20140701
-rw-r- 1 dnsmasq root  2885 Jun 24 15:26 dnsmasq.log-20140626
-rw-r- 1 rootadm  0 Jun 26 06:25 user.log
-rw-r- 1 rootadm  0 Jun 26 06:25 syslog
-rw-r- 1 rootadm  0 Jun 26 06:25 debug
-rw-r- 1 rootadm 118687 Jun 29 06:25 kern.log-20140626
-rw-r--r-- 1 rootroot 0 Jul  1 06:25 dpkg.log
-rw--- 1 rootutmp 0 Jul  1 06:25 btmp
-rw-r--r-- 1 rootroot 0 Jul  1 06:25 aptitude
drwxr-xr-x 2 rootroot  1024 Jul  1 06:25 apt
-rw-r--r-- 1 rootroot 0 Jul  1 06:25 alternatives.log
-rw--- 1 rootroot  88352117 Jul  6 06:25 
conntrackd-stats.log-20140706

drwxr-x--- 2 rootadm   1024 Jul  9 06:25 apache2
-rw--- 1 rootroot 119645113 Jul 13 06:25 
conntrackd-stats.log-20140713

drwxr-xr-x 2 rootroot  1024 Aug  1 06:25 sysstat
-rw-r- 1 rootadm 976874 Aug  1 06:27 cron.log-20140626
-rw-r- 1 rootadm 325622 Aug  1 06:29 messages-20140626
-rw-r--r-- 1 rootroot  5091 Aug  1 06:29 cloud.log-20140626
-rw--- 1 rootroot   2758246 Aug  1 06:30 conntrackd-stats.log
-rw-r- 1 rootadm 145694 Aug  1 06:30 daemon.log-20140626
-rw-r- 1 rootadm4623344 Aug  1 06:30 auth.log-20140626
-rw-r--r-- 1 rootroot  1021 Aug  1 06:30 cloud.log
-rw-r- 1 rootadm  0 Aug  1 06:30 kern.log
-rw-r- 1 rootadm  27326 Aug  1 06:30 dmesg
-rw-r- 1 dnsmasq root 0 Aug  1 06:30 dnsmasq.log
-rw-r- 1 rootadm  0 Aug  1 07:56 messages
-rw-r- 1 rootadm  0 Aug  1 07:56 daemon.log
-rw-r- 1 rootadm  0 Aug  1 10:17 cron.log
-rw-rw-r-- 1 rootutmp 0 Aug  1 10:17 wtmp
-rw-rw-r-- 1 rootutmp292292 Aug  1 10:17 lastlog
-rw-r- 1 rootadm  0 Aug  1 10:17 auth.log


Il 01/08/2014 11:44, Geoff Higginbottom ha scritto:

Ugo,

Login to the VR and tail the messages log then attempt to start the VM, you 
should see various messages re DHCP updating etc in the VR.  If you don't see 
the VR update try restarting the network Iain the 'cleanup' option, this will 
create a new VR.

Regards

Geoff Higginbottom
CTO / Cloud Architect

D: +44 20 3603 0542tel:+442036030542 | S: +44 20 3603 0540tel:+442036030540 | M: 
+447968161581tel:+447968161581

geoff.higginbot...@shapeblue.commailto:geoff.higginbot...@shapeblue.com | 
www.shapeblue.comhtp://www.shapeblue.com/ | 
Twitter:@cloudstackguruhttps://twitter.com/#!/cloudstackguru

ShapeBlue Ltd, 53 Chandos Place, Covent Garden, London, WC2N 
4HSx-apple-data-detectors://5


On 1 Aug 2014, at 09:06, Ugo Vasi 
ugo.v...@procne.itmailto:ugo.v...@procne.it wrote:

Hi Geoff,
I tried restarting r-29-VM but the problem is still blocking creation of new VM 
in that isolated network.

Creating a new VM in another isolated network, it works. Where can I look at to 
find the problem?



Il 31/07/2014 21:53, Geoff Higginbottom ha scritto:
Ugo,

Looks like CS is failing to update the VR with details for the new VM, try 
restarting the VR.

Regards

Geoff Higginbottom
CTO / Cloud Architect


D: +44 20 3603 0542tel:+442036030542 | S: +44 20 3603 0540tel:+442036030540 | M: 

Unable to start a VM due to insufficient capacity

[Ugo Vasi]

Hi everybody,
I installed a CloudStack 4.3.0 system with a manager (in a virtual machine), 
two NFS primary storage, one NFS secondary storare and two host agent on ubuntu 
distribution.

The cluster have one advanced zone without security group configuration with 
KVM hipervisors.

I create some VM but now does not allow me to create more giving the error message 
Unable to start a VM due to insufficient capacity.

I am sure that the resources (ip, ram, cpu and storage) are enough to create 
new instances. In dashboard I see all ok.

From the management-server.log I see this errors messages (see attachment for 
full version) when I try to deploy a new virtual machine with 1x1GHz cpu, 1GB 
or RAM and 20GB disk space:

2014-07-31 14:59:11,983 DEBUG [c.c.a.t.Request] (AgentManager-Handler-12:null) Seq 1-684594119: Processing:  { Ans: , MgmtId: 77916390353436, via: 1, Ver: v1, 
Flags: 10, 
[{com.cloud.agent.api.Answer:{result:true,wait:0}},{com.cloud.agent.api.Answer:{result:false,details:VmDataCommand
 failed, check agent logs,wait:0}}] }
2014-07-31 14:59:11,983 INFO  [c.c.v.VirtualMachineManagerImpl] 
(Job-Executor-26:ctx-ab3aee38 ctx-d8600c16) Unable to contact resource.
com.cloud.exception.ResourceUnavailableException: Resource [DataCenter:1] is 
unreachable: Unable to apply userdata and password entry on router
2014-07-31 14:59:12,453 DEBUG [c.c.c.CapacityManagerImpl] 
(Job-Executor-26:ctx-ab3aee38 ctx-d8600c16) VM state transitted from :Starting 
to Stopped with event: OperationFailedvm's original host id: null new host id: 
null host id before state transition: 7
2014-07-31 14:59:12,677 DEBUG [c.c.c.CapacityManagerImpl] 
(Job-Executor-26:ctx-ab3aee38 ctx-d8600c16) VM state transitted from :Starting 
to Stopped with event: OperationFailedvm's original host id: null new host id: 
null host id before state transition: null
2014-07-31 14:59:12,708 DEBUG [c.c.v.UserVmManagerImpl] 
(Job-Executor-26:ctx-ab3aee38 ctx-d8600c16) Destroying vm VM[User|csweb2] as it 
failed to create on Host with Id:null
2014-07-31 14:59:12,738 DEBUG [c.c.c.CapacityManagerImpl] 
(Job-Executor-26:ctx-ab3aee38 ctx-d8600c16) 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-07-31 14:59:12,929 WARN  [o.a.c.alerts] (Job-Executor-26:ctx-ab3aee38 
ctx-d8600c16)  alertType:: 8 // dataCenterId:: 1 // podId:: 1 // clusterId:: 
null // message:: Failed to deploy Vm with Id: 70, on Host with Id: null
2014-07-31 14:59:13,159 ERROR [c.c.a.ApiAsyncJobDispatcher] 
(Job-Executor-26:ctx-ab3aee38) Unexpected exception while executing 
org.apache.cloudstack.api.command.user.vm.DeployVMCmd
com.cloud.utils.exception.CloudRuntimeException: Unable to start a VM due to 
insufficient capacity
Caused by: com.cloud.exception.InsufficientServerCapacityException: Unable to 
create a deployment for VM[User|csweb2]Scope=interface com.cloud.dc.DataCenter; 
id=1
2014-07-31 14:59:13,161 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl] (Job-Executor-26:ctx-ab3aee38) Complete async job-783, 
jobStatus: FAILED, resultCode: 530, result: 
org.apache.cloudstack.api.response.ExceptionResponse/null/{uuidList:[],errorcode:530,errortext:Unable
 to start a VM due to insufficient capacity}
2014-07-31 14:59:46,280 DEBUG [c.c.v.VirtualMachineManagerImpl] 
(Job-Executor-27:ctx-82be396e ctx-41f0cf24) Stopped called on VM[User|csweb2] 
but the state is Error
2014-07-31 14:59:46,330 DEBUG [c.c.c.CapacityManagerImpl] 
(Job-Executor-27:ctx-82be396e ctx-41f0cf24) VM state transitted from :Error to 
Expunging with event: DestroyRequestedvm's original host id: null new host id: 
null host id before state transition: null

I tried to search in others log file (VmDataCommand failed, check agent 
logs), but I don't found nothing...

Can anyone Help me?

--

  U g o   V a s iugo.v...@procne.it
  P r o c n e  s.r.l)
  via Cotonificio 45  33010 Tavagnacco IT
  phone: +390432486523 fax: +390432486523

Le informazioni contenute in questo messaggio sono riservate e
confidenziali ed è vietata la diffusione in qualunque modo eseguita.
Qualora Lei non fosse la persona a cui il presente messaggio è
destinato, La invitiamo ad eliminarlo e a non leggerlo, dandocene
gentilmente comunicazione.
Per qualsiasi informazione si prega di contattare supp...@procne.it .
Rif. D.L. 196/2003




2014-07-31 14:59:10,556 DEBUG [c.c.a.ApiServlet] (catalina-exec-5:ctx-c61df92d) ===START===  127.0.0.1 -- GET  command=deployVirtualMachineresponse=jsonsessionkey=JYBJ9eNoOH5hAbD%2BDNV0M8Dr7JI%3Dzoneid=ed6ce5de-2ff4-4d57-aa88-27e904082928templateid=0d935ed9-38b0-4a59-8651-927ba09f2597hypervisor=KVMserviceofferingid=ba47a8d5-6984-40fa-bf3a-a1aa39d0195bdiskofferingid=b487cedd-dc96-4c73-9045-c070c5dd0f29networkids=14e56990-ee1f-46e4-b0c1-eac18daaf433displayname=csweb2name=csweb2_=1406811550539
2014-07-31 14:59:10,562 DEBUG [c.c.a.ApiDispatcher] (catalina-exec-5:ctx-c61df92d ctx-d8600c16) InfrastructureEntity 

Re: Unable to start a VM due to insufficient capacity

[Geoff Higginbottom]

Ugo,

Looks like CS is failing to update the VR with details for the new VM, try 
restarting the VR.

Regards

Geoff Higginbottom
CTO / Cloud Architect


D: +44 20 3603 0542tel:+442036030542 | S: +44 20 3603 0540tel:+442036030540 
| M: +447968161581tel:+447968161581

geoff.higginbot...@shapeblue.commailto:geoff.higginbot...@shapeblue.com | 
www.shapeblue.comhtp://www.shapeblue.com/

ShapeBlue Ltd, 53 Chandos Place, Covent Garden, London, WC2N 
4HSx-apple-data-detectors://37



On 31 Jul 2014, at 15:40, Ugo Vasi 
ugo.v...@procne.itmailto:ugo.v...@procne.it wrote:

Hi everybody,
I installed a CloudStack 4.3.0 system with a manager (in a virtual machine), 
two NFS primary storage, one NFS secondary storare and two host agent on ubuntu 
distribution.

The cluster have one advanced zone without security group configuration with 
KVM hipervisors.

I create some VM but now does not allow me to create more giving the error 
message Unable to start a VM due to insufficient capacity.

I am sure that the resources (ip, ram, cpu and storage) are enough to create 
new instances. In dashboard I see all ok.

From the management-server.log I see this errors messages (see attachment for 
full version) when I try to deploy a new virtual machine with 1x1GHz cpu, 1GB 
or RAM and 20GB disk space:

2014-07-31 14:59:11,983 DEBUG [c.c.a.t.Request] (AgentManager-Handler-12:null) 
Seq 1-684594119: Processing:  { Ans: , MgmtId: 77916390353436, via: 1, Ver: v1, 
Flags: 10, 
[{com.cloud.agent.api.Answer:{result:true,wait:0}},{com.cloud.agent.api.Answer:{result:false,details:VmDataCommand
 failed, check agent logs,wait:0}}] }
2014-07-31 14:59:11,983 INFO  [c.c.v.VirtualMachineManagerImpl] 
(Job-Executor-26:ctx-ab3aee38 ctx-d8600c16) Unable to contact resource.
com.cloud.exception.ResourceUnavailableException: Resource [DataCenter:1] is 
unreachable: Unable to apply userdata and password entry on router
2014-07-31 14:59:12,453 DEBUG [c.c.c.CapacityManagerImpl] 
(Job-Executor-26:ctx-ab3aee38 ctx-d8600c16) VM state transitted from :Starting 
to Stopped with event: OperationFailedvm's original host id: null new host id: 
null host id before state transition: 7
2014-07-31 14:59:12,677 DEBUG [c.c.c.CapacityManagerImpl] 
(Job-Executor-26:ctx-ab3aee38 ctx-d8600c16) VM state transitted from :Starting 
to Stopped with event: OperationFailedvm's original host id: null new host id: 
null host id before state transition: null
2014-07-31 14:59:12,708 DEBUG [c.c.v.UserVmManagerImpl] 
(Job-Executor-26:ctx-ab3aee38 ctx-d8600c16) Destroying vm VM[User|csweb2] as it 
failed to create on Host with Id:null
2014-07-31 14:59:12,738 DEBUG [c.c.c.CapacityManagerImpl] 
(Job-Executor-26:ctx-ab3aee38 ctx-d8600c16) 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-07-31 14:59:12,929 WARN  [o.a.c.alerts] (Job-Executor-26:ctx-ab3aee38 
ctx-d8600c16)  alertType:: 8 // dataCenterId:: 1 // podId:: 1 // clusterId:: 
null // message:: Failed to deploy Vm with Id: 70, on Host with Id: null
2014-07-31 14:59:13,159 ERROR [c.c.a.ApiAsyncJobDispatcher] 
(Job-Executor-26:ctx-ab3aee38) Unexpected exception while executing 
org.apache.cloudstack.api.command.user.vm.DeployVMCmd
com.cloud.utils.exception.CloudRuntimeException: Unable to start a VM due to 
insufficient capacity
Caused by: com.cloud.exception.InsufficientServerCapacityException: Unable to 
create a deployment for VM[User|csweb2]Scope=interface com.cloud.dc.DataCenter; 
id=1
2014-07-31 14:59:13,161 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl] 
(Job-Executor-26:ctx-ab3aee38) Complete async job-783, jobStatus: FAILED, 
resultCode: 530, result: 
org.apache.cloudstack.api.response.ExceptionResponse/null/{uuidList:[],errorcode:530,errortext:Unable
 to start a VM due to insufficient capacity}
2014-07-31 14:59:46,280 DEBUG [c.c.v.VirtualMachineManagerImpl] 
(Job-Executor-27:ctx-82be396e ctx-41f0cf24) Stopped called on VM[User|csweb2] 
but the state is Error
2014-07-31 14:59:46,330 DEBUG [c.c.c.CapacityManagerImpl] 
(Job-Executor-27:ctx-82be396e ctx-41f0cf24) VM state transitted from :Error to 
Expunging with event: DestroyRequestedvm's original host id: null new host id: 
null host id before state transition: null

I tried to search in others log file (VmDataCommand failed, check agent 
logs), but I don't found nothing...

Can anyone Help me?

--

 U g o   V a s iugo.v...@procne.itmailto:ugo.v...@procne.it
 P r o c n e  s.r.l)
 via Cotonificio 45  33010 Tavagnacco IT
 phone: +390432486523 fax: +390432486523

Le informazioni contenute in questo messaggio sono riservate e
confidenziali ed ? vietata la diffusione in qualunque modo eseguita.
Qualora Lei non fosse la persona a cui il presente messaggio ?
destinato, La invitiamo ad eliminarlo e a non leggerlo, dandocene
gentilmente comunicazione.
Per qualsiasi informazione si prega di contattare 
supp...@procne.itmailto:supp...@procne.it .
Rif. D.L. 196/2003