You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cloudstack.apache.org by Tilak Raj Singh <ti...@gmail.com> on 2015/01/20 21:14:40 UTC
Unable to create VM
Hello evryone,
I am unable to create a VM. Have been stuck at this problem for days now.
Using cloudstack 4.4.1. Configuration is as follows
Management server 172.31.101.202
Pod 1 - private ip range 172.31.101.210 - 172.31.101.220
Guest IP range 172.31.101.230 - 172.31.101.250
Cluster1 - KVM
Host1 - 172.31.101.202
Pod 2 -> private ip range 172.31.132.140-172.31.132.150
Didnt ask for guest ip range here
Cluster2 - KVM
Host2 - 172.31.132.132
VM creation is successsful on Host1 but not on Host 2.
Here are the error logs
2015-01-21 00:46:52,457 DEBUG [c.c.c.CapacityManagerImpl]
(Work-Job-Executor-4:ctx-b225fb2e job-222/job-223 ctx-6e4c92f9) CPU STATS
after allocation: for host: 12, old used: 0, old reserved: 0, actual total:
10656, total with overprovisioning: 10656; new used:500, reserved:0;
requested cpu:500,alloc_from_last:false
2015-01-21 00:46:52,457 DEBUG [c.c.c.CapacityManagerImpl]
(Work-Job-Executor-4:ctx-b225fb2e job-222/job-223 ctx-6e4c92f9) RAM STATS
after allocation: for host: 12, old used: 0, old reserved: 0, total:
1936789504; new used: 536870912, reserved: 0; requested mem:
536870912,alloc_from_last:false
2015-01-21 00:46:52,459 DEBUG [c.c.h.d.HostDaoImpl] (ClusteredAgentManager
Timer:ctx-687f4bdb) Resetting hosts suitable for reconnect
2015-01-21 00:46:52,460 DEBUG [c.c.h.d.HostDaoImpl] (ClusteredAgentManager
Timer:ctx-687f4bdb) Completed resetting hosts suitable for reconnect
2015-01-21 00:46:52,460 DEBUG [c.c.h.d.HostDaoImpl] (ClusteredAgentManager
Timer:ctx-687f4bdb) Acquiring hosts for clusters already owned by this
management server
2015-01-21 00:46:52,461 DEBUG [c.c.h.d.HostDaoImpl] (ClusteredAgentManager
Timer:ctx-687f4bdb) Completed acquiring hosts for clusters already owned by
this management server
2015-01-21 00:46:52,461 DEBUG [c.c.h.d.HostDaoImpl] (ClusteredAgentManager
Timer:ctx-687f4bdb) Acquiring hosts for clusters not owned by any
management server
2015-01-21 00:46:52,461 DEBUG [c.c.h.d.HostDaoImpl] (ClusteredAgentManager
Timer:ctx-687f4bdb) Completed acquiring hosts for clusters not owned by any
management server
2015-01-21 00:46:52,513 DEBUG [c.c.v.VirtualMachineManagerImpl]
(Work-Job-Executor-4:ctx-b225fb2e job-222/job-223 ctx-6e4c92f9) VM is being
created in podId: 4
2015-01-21 00:46:52,520 DEBUG [o.a.c.e.o.NetworkOrchestrator]
(Work-Job-Executor-4:ctx-b225fb2e job-222/job-223 ctx-6e4c92f9) Network
id=204 is already implemented
2015-01-21 00:46:52,595 DEBUG [c.c.u.d.T.Transaction]
(Work-Job-Executor-4:ctx-b225fb2e job-222/job-223 ctx-6e4c92f9) Rolling
back the transaction: Time = 7 Name = Work-Job-Executor-4; called by
-TransactionLegacy.rollback:900-TransactionLegacy.removeUpTo:843-TransactionLegacy.close:667-Transaction.execute:41-IpAddressManagerImpl.fetchNewPublicIp:660-IpAddressManagerImpl.assignPublicIpAddress:647-DirectPodBasedNetworkGuru$2.doInTransactionWithoutResult:194-TransactionCallbackWithExceptionNoReturn.doInTransaction:25-TransactionCallbackWithExceptionNoReturn.doInTransaction:21-Transaction.execute:37-DirectPodBasedNetworkGuru.getIp:173-DirectPodBasedNetworkGuru.reserve:160
2015-01-21 00:46:52,596 INFO [c.c.v.VirtualMachineManagerImpl]
(Work-Job-Executor-4:ctx-b225fb2e job-222/job-223 ctx-6e4c92f9)
Insufficient capacity
com.cloud.exception.InsufficientAddressCapacityException: Insufficient
address capacityScope=interface com.cloud.dc.Pod; id=4
at
com.cloud.network.IpAddressManagerImpl$2.doInTransaction(IpAddressManagerImpl.java:743)
at
com.cloud.network.IpAddressManagerImpl$2.doInTransaction(IpAddressManagerImpl.java:660)
at com.cloud.utils.db.Transaction.execute(Transaction.java:37)
at
com.cloud.network.IpAddressManagerImpl.fetchNewPublicIp(IpAddressManagerImpl.java:660)
at
com.cloud.network.IpAddressManagerImpl.assignPublicIpAddress(IpAddressManagerImpl.java:647)
at
com.cloud.network.guru.DirectPodBasedNetworkGuru$2.doInTransactionWithoutResult(DirectPodBasedNetworkGuru.java:194)
at
com.cloud.utils.db.TransactionCallbackWithExceptionNoReturn.doInTransaction(TransactionCallbackWithExceptionNoReturn.java:25)
at
com.cloud.utils.db.TransactionCallbackWithExceptionNoReturn.doInTransaction(TransactionCallbackWithExceptionNoReturn.java:21)
at com.cloud.utils.db.Transaction.execute(Transaction.java:37)
Regards
RE: Unable to create VM
Posted by Tilak Raj Singh <ti...@gmail.com>.
But my dashboard shows nothing of that sort..ip addresses are available
both management and guests...creating vm on host1 works successfully..the
error comes only when it tries to create vm on host2....
Can i provide any other info so that you can help me further??
can u please confrm my zone setup if that is right..i think there is
problem somewhere in there..
On 21-Jan-2015 2:37 AM, "Somesh Naidu" <So...@citrix.com> wrote:
> You have run out of IP addresses, should be visible on the Dashboard
> and/or on the Zone's resources page.
>
> ---
> 2015-01-21 00:46:52,595 DEBUG [c.c.u.d.T.Transaction]
> (Work-Job-Executor-4:ctx-b225fb2e job-222/job-223 ctx-6e4c92f9) Rolling
> back the transaction: Time = 7 Name = Work-Job-Executor-4; called by
>
> -TransactionLegacy.rollback:900-TransactionLegacy.removeUpTo:843-TransactionLegacy.close:667-Transaction.execute:41-IpAddressManagerImpl.fetchNewPublicIp:660-IpAddressManagerImpl.assignPublicIpAddress:647-DirectPodBasedNetworkGuru$2.doInTransactionWithoutResult:194-TransactionCallbackWithExceptionNoReturn.doInTransaction:25-TransactionCallbackWithExceptionNoReturn.doInTransaction:21-Transaction.execute:37-DirectPodBasedNetworkGuru.getIp:173-DirectPodBasedNetworkGuru.reserve:160
> 2015-01-21 00:46:52,596 INFO [c.c.v.VirtualMachineManagerImpl]
> (Work-Job-Executor-4:ctx-b225fb2e job-222/job-223 ctx-6e4c92f9)
> Insufficient capacity
> com.cloud.exception.InsufficientAddressCapacityException: Insufficient
> address capacityScope=interface com.cloud.dc.Pod; id=4
> ---
>
> Somesh
> CloudPlatform Escalations
> Citrix Systems, Inc.
>
> -----Original Message-----
> From: Tilak Raj Singh [mailto:tilak72@gmail.com]
> Sent: Tuesday, January 20, 2015 3:15 PM
> To: users@cloudstack.apache.org
> Subject: Unable to create VM
>
> Hello evryone,
>
> I am unable to create a VM. Have been stuck at this problem for days now.
> Using cloudstack 4.4.1. Configuration is as follows
>
> Management server 172.31.101.202
> Pod 1 - private ip range 172.31.101.210 - 172.31.101.220
> Guest IP range 172.31.101.230 - 172.31.101.250
> Cluster1 - KVM
> Host1 - 172.31.101.202
>
> Pod 2 -> private ip range 172.31.132.140-172.31.132.150
> Didnt ask for guest ip range here
> Cluster2 - KVM
> Host2 - 172.31.132.132
>
> VM creation is successsful on Host1 but not on Host 2.
>
> Here are the error logs
>
> 2015-01-21 00:46:52,457 DEBUG [c.c.c.CapacityManagerImpl]
> (Work-Job-Executor-4:ctx-b225fb2e job-222/job-223 ctx-6e4c92f9) CPU STATS
> after allocation: for host: 12, old used: 0, old reserved: 0, actual total:
> 10656, total with overprovisioning: 10656; new used:500, reserved:0;
> requested cpu:500,alloc_from_last:false
> 2015-01-21 00:46:52,457 DEBUG [c.c.c.CapacityManagerImpl]
> (Work-Job-Executor-4:ctx-b225fb2e job-222/job-223 ctx-6e4c92f9) RAM STATS
> after allocation: for host: 12, old used: 0, old reserved: 0, total:
> 1936789504; new used: 536870912, reserved: 0; requested mem:
> 536870912,alloc_from_last:false
> 2015-01-21 00:46:52,459 DEBUG [c.c.h.d.HostDaoImpl] (ClusteredAgentManager
> Timer:ctx-687f4bdb) Resetting hosts suitable for reconnect
> 2015-01-21 00:46:52,460 DEBUG [c.c.h.d.HostDaoImpl] (ClusteredAgentManager
> Timer:ctx-687f4bdb) Completed resetting hosts suitable for reconnect
> 2015-01-21 00:46:52,460 DEBUG [c.c.h.d.HostDaoImpl] (ClusteredAgentManager
> Timer:ctx-687f4bdb) Acquiring hosts for clusters already owned by this
> management server
> 2015-01-21 00:46:52,461 DEBUG [c.c.h.d.HostDaoImpl] (ClusteredAgentManager
> Timer:ctx-687f4bdb) Completed acquiring hosts for clusters already owned by
> this management server
> 2015-01-21 00:46:52,461 DEBUG [c.c.h.d.HostDaoImpl] (ClusteredAgentManager
> Timer:ctx-687f4bdb) Acquiring hosts for clusters not owned by any
> management server
> 2015-01-21 00:46:52,461 DEBUG [c.c.h.d.HostDaoImpl] (ClusteredAgentManager
> Timer:ctx-687f4bdb) Completed acquiring hosts for clusters not owned by any
> management server
> 2015-01-21 00:46:52,513 DEBUG [c.c.v.VirtualMachineManagerImpl]
> (Work-Job-Executor-4:ctx-b225fb2e job-222/job-223 ctx-6e4c92f9) VM is being
> created in podId: 4
> 2015-01-21 00:46:52,520 DEBUG [o.a.c.e.o.NetworkOrchestrator]
> (Work-Job-Executor-4:ctx-b225fb2e job-222/job-223 ctx-6e4c92f9) Network
> id=204 is already implemented
> 2015-01-21 00:46:52,595 DEBUG [c.c.u.d.T.Transaction]
> (Work-Job-Executor-4:ctx-b225fb2e job-222/job-223 ctx-6e4c92f9) Rolling
> back the transaction: Time = 7 Name = Work-Job-Executor-4; called by
>
> -TransactionLegacy.rollback:900-TransactionLegacy.removeUpTo:843-TransactionLegacy.close:667-Transaction.execute:41-IpAddressManagerImpl.fetchNewPublicIp:660-IpAddressManagerImpl.assignPublicIpAddress:647-DirectPodBasedNetworkGuru$2.doInTransactionWithoutResult:194-TransactionCallbackWithExceptionNoReturn.doInTransaction:25-TransactionCallbackWithExceptionNoReturn.doInTransaction:21-Transaction.execute:37-DirectPodBasedNetworkGuru.getIp:173-DirectPodBasedNetworkGuru.reserve:160
> 2015-01-21 00:46:52,596 INFO [c.c.v.VirtualMachineManagerImpl]
> (Work-Job-Executor-4:ctx-b225fb2e job-222/job-223 ctx-6e4c92f9)
> Insufficient capacity
> com.cloud.exception.InsufficientAddressCapacityException: Insufficient
> address capacityScope=interface com.cloud.dc.Pod; id=4
> at
>
> com.cloud.network.IpAddressManagerImpl$2.doInTransaction(IpAddressManagerImpl.java:743)
> at
>
> com.cloud.network.IpAddressManagerImpl$2.doInTransaction(IpAddressManagerImpl.java:660)
> at com.cloud.utils.db.Transaction.execute(Transaction.java:37)
> at
>
> com.cloud.network.IpAddressManagerImpl.fetchNewPublicIp(IpAddressManagerImpl.java:660)
> at
>
> com.cloud.network.IpAddressManagerImpl.assignPublicIpAddress(IpAddressManagerImpl.java:647)
> at
>
> com.cloud.network.guru.DirectPodBasedNetworkGuru$2.doInTransactionWithoutResult(DirectPodBasedNetworkGuru.java:194)
> at
>
> com.cloud.utils.db.TransactionCallbackWithExceptionNoReturn.doInTransaction(TransactionCallbackWithExceptionNoReturn.java:25)
> at
>
> com.cloud.utils.db.TransactionCallbackWithExceptionNoReturn.doInTransaction(TransactionCallbackWithExceptionNoReturn.java:21)
> at com.cloud.utils.db.Transaction.execute(Transaction.java:37)
>
>
> Regards
>
RE: Unable to create VM
Posted by Somesh Naidu <So...@citrix.com>.
You have run out of IP addresses, should be visible on the Dashboard and/or on the Zone's resources page.
---
2015-01-21 00:46:52,595 DEBUG [c.c.u.d.T.Transaction]
(Work-Job-Executor-4:ctx-b225fb2e job-222/job-223 ctx-6e4c92f9) Rolling
back the transaction: Time = 7 Name = Work-Job-Executor-4; called by
-TransactionLegacy.rollback:900-TransactionLegacy.removeUpTo:843-TransactionLegacy.close:667-Transaction.execute:41-IpAddressManagerImpl.fetchNewPublicIp:660-IpAddressManagerImpl.assignPublicIpAddress:647-DirectPodBasedNetworkGuru$2.doInTransactionWithoutResult:194-TransactionCallbackWithExceptionNoReturn.doInTransaction:25-TransactionCallbackWithExceptionNoReturn.doInTransaction:21-Transaction.execute:37-DirectPodBasedNetworkGuru.getIp:173-DirectPodBasedNetworkGuru.reserve:160
2015-01-21 00:46:52,596 INFO [c.c.v.VirtualMachineManagerImpl]
(Work-Job-Executor-4:ctx-b225fb2e job-222/job-223 ctx-6e4c92f9)
Insufficient capacity
com.cloud.exception.InsufficientAddressCapacityException: Insufficient
address capacityScope=interface com.cloud.dc.Pod; id=4
---
Somesh
CloudPlatform Escalations
Citrix Systems, Inc.
-----Original Message-----
From: Tilak Raj Singh [mailto:tilak72@gmail.com]
Sent: Tuesday, January 20, 2015 3:15 PM
To: users@cloudstack.apache.org
Subject: Unable to create VM
Hello evryone,
I am unable to create a VM. Have been stuck at this problem for days now.
Using cloudstack 4.4.1. Configuration is as follows
Management server 172.31.101.202
Pod 1 - private ip range 172.31.101.210 - 172.31.101.220
Guest IP range 172.31.101.230 - 172.31.101.250
Cluster1 - KVM
Host1 - 172.31.101.202
Pod 2 -> private ip range 172.31.132.140-172.31.132.150
Didnt ask for guest ip range here
Cluster2 - KVM
Host2 - 172.31.132.132
VM creation is successsful on Host1 but not on Host 2.
Here are the error logs
2015-01-21 00:46:52,457 DEBUG [c.c.c.CapacityManagerImpl]
(Work-Job-Executor-4:ctx-b225fb2e job-222/job-223 ctx-6e4c92f9) CPU STATS
after allocation: for host: 12, old used: 0, old reserved: 0, actual total:
10656, total with overprovisioning: 10656; new used:500, reserved:0;
requested cpu:500,alloc_from_last:false
2015-01-21 00:46:52,457 DEBUG [c.c.c.CapacityManagerImpl]
(Work-Job-Executor-4:ctx-b225fb2e job-222/job-223 ctx-6e4c92f9) RAM STATS
after allocation: for host: 12, old used: 0, old reserved: 0, total:
1936789504; new used: 536870912, reserved: 0; requested mem:
536870912,alloc_from_last:false
2015-01-21 00:46:52,459 DEBUG [c.c.h.d.HostDaoImpl] (ClusteredAgentManager
Timer:ctx-687f4bdb) Resetting hosts suitable for reconnect
2015-01-21 00:46:52,460 DEBUG [c.c.h.d.HostDaoImpl] (ClusteredAgentManager
Timer:ctx-687f4bdb) Completed resetting hosts suitable for reconnect
2015-01-21 00:46:52,460 DEBUG [c.c.h.d.HostDaoImpl] (ClusteredAgentManager
Timer:ctx-687f4bdb) Acquiring hosts for clusters already owned by this
management server
2015-01-21 00:46:52,461 DEBUG [c.c.h.d.HostDaoImpl] (ClusteredAgentManager
Timer:ctx-687f4bdb) Completed acquiring hosts for clusters already owned by
this management server
2015-01-21 00:46:52,461 DEBUG [c.c.h.d.HostDaoImpl] (ClusteredAgentManager
Timer:ctx-687f4bdb) Acquiring hosts for clusters not owned by any
management server
2015-01-21 00:46:52,461 DEBUG [c.c.h.d.HostDaoImpl] (ClusteredAgentManager
Timer:ctx-687f4bdb) Completed acquiring hosts for clusters not owned by any
management server
2015-01-21 00:46:52,513 DEBUG [c.c.v.VirtualMachineManagerImpl]
(Work-Job-Executor-4:ctx-b225fb2e job-222/job-223 ctx-6e4c92f9) VM is being
created in podId: 4
2015-01-21 00:46:52,520 DEBUG [o.a.c.e.o.NetworkOrchestrator]
(Work-Job-Executor-4:ctx-b225fb2e job-222/job-223 ctx-6e4c92f9) Network
id=204 is already implemented
2015-01-21 00:46:52,595 DEBUG [c.c.u.d.T.Transaction]
(Work-Job-Executor-4:ctx-b225fb2e job-222/job-223 ctx-6e4c92f9) Rolling
back the transaction: Time = 7 Name = Work-Job-Executor-4; called by
-TransactionLegacy.rollback:900-TransactionLegacy.removeUpTo:843-TransactionLegacy.close:667-Transaction.execute:41-IpAddressManagerImpl.fetchNewPublicIp:660-IpAddressManagerImpl.assignPublicIpAddress:647-DirectPodBasedNetworkGuru$2.doInTransactionWithoutResult:194-TransactionCallbackWithExceptionNoReturn.doInTransaction:25-TransactionCallbackWithExceptionNoReturn.doInTransaction:21-Transaction.execute:37-DirectPodBasedNetworkGuru.getIp:173-DirectPodBasedNetworkGuru.reserve:160
2015-01-21 00:46:52,596 INFO [c.c.v.VirtualMachineManagerImpl]
(Work-Job-Executor-4:ctx-b225fb2e job-222/job-223 ctx-6e4c92f9)
Insufficient capacity
com.cloud.exception.InsufficientAddressCapacityException: Insufficient
address capacityScope=interface com.cloud.dc.Pod; id=4
at
com.cloud.network.IpAddressManagerImpl$2.doInTransaction(IpAddressManagerImpl.java:743)
at
com.cloud.network.IpAddressManagerImpl$2.doInTransaction(IpAddressManagerImpl.java:660)
at com.cloud.utils.db.Transaction.execute(Transaction.java:37)
at
com.cloud.network.IpAddressManagerImpl.fetchNewPublicIp(IpAddressManagerImpl.java:660)
at
com.cloud.network.IpAddressManagerImpl.assignPublicIpAddress(IpAddressManagerImpl.java:647)
at
com.cloud.network.guru.DirectPodBasedNetworkGuru$2.doInTransactionWithoutResult(DirectPodBasedNetworkGuru.java:194)
at
com.cloud.utils.db.TransactionCallbackWithExceptionNoReturn.doInTransaction(TransactionCallbackWithExceptionNoReturn.java:25)
at
com.cloud.utils.db.TransactionCallbackWithExceptionNoReturn.doInTransaction(TransactionCallbackWithExceptionNoReturn.java:21)
at com.cloud.utils.db.Transaction.execute(Transaction.java:37)
Regards