You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cloudstack.apache.org by Mike Tutkowski <mi...@solidfire.com> on 2013/04/12 19:39:58 UTC
Issue launching VM on VMware
Hi,
Any thoughts on this? It seems like I should have plenty of memory (on
either of my two ESXi hosts) and plenty of storage space (on my
iSCSI-backed VMFS datastore).
Thanks!
INFO [user.vm.DeployVMCmd] (Job-Executor-11:job-11) Unable to create a
deployment for VM[User|5878531f-2164-48cc-b1b7-3b38e9b16b5f]
com.cloud.exception.InsufficientServerCapacityException: Unable to create a
deployment for VM[User|5878531f-2164-48cc-b1b7-3b38e9b16b5f]Scope=interface
com.cloud.dc.DataCenter; id=1
at
org.apache.cloudstack.engine.cloud.entity.api.VMEntityManagerImpl.reserveVirtualMachine(VMEntityManagerImpl.java:186)
at
org.apache.cloudstack.engine.cloud.entity.api.VirtualMachineEntityImpl.reserve(VirtualMachineEntityImpl.java:198)
at
com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:3859)
at
com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:3458)
at
com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:3444)
at
com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
at
org.apache.cloudstack.api.command.user.vm.DeployVMCmd.execute(DeployVMCmd.java:379)
at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:162)
at com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:437)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:439)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918)
at java.lang.Thread.run(Thread.java:680)
--
*Mike Tutkowski*
*Senior CloudStack Developer, SolidFire Inc.*
e: mike.tutkowski@solidfire.com
o: 303.746.7302
Advancing the way the world uses the
cloud<http://solidfire.com/solution/overview/?video=play>
*™*
Re: Issue launching VM on VMware
Posted by Mike Tutkowski <mi...@solidfire.com>.
Interesting...when I review one of my Compute Offerings, it says it is of
Storage Type "shared" and has a Storage Tag of "SF_iSCSI_1" and that
Storage Tag is only used by a Primary Storage of the same name that is
based on an iSCSI-backed VMFS datastore.
On Mon, Apr 15, 2013 at 11:53 AM, Kelven Yang <ke...@citrix.com>wrote:
> From the log, you seem to use a offering that directs to create volume in
> local storage and there is no such storage available in your setup
>
> Kelven
>
> On 4/13/13 4:14 PM, "Mike Tutkowski" <mi...@solidfire.com> wrote:
>
> >That's weird...I have three local storages (one from DevCloud2 by default,
> >one from one ESXi host, and one from another ESXi host). I also have
> >several shared storages (iSCSI-based datastores that were configured in CS
> >as VMFS-based primary storages). I tagged the shared primary storage I
> >wanted to use, referenced that storage tag from a compute offering, and
> >executed the compute offering.
> >
> >
> >On Sat, Apr 13, 2013 at 12:30 PM, Ahmad Emneina <ae...@gmail.com>
> >wrote:
> >
> >> looks as though your zone is set to use shared storage, and youre only
> >> providing local storage.
> >>
> >> 1. 2013-04-12 11:35:20,292 DEBUG [storage.allocator.
> >> AbstractStoragePoolAllocator] (Job-Executor-11:job-11) Checking if
> >> storage pool is suitable, name: devcloud Local Storage ,poolId: 200
> >> 2. 2013-04-12 11:35:20,292 DEBUG [storage.allocator.
> >> AbstractStoragePoolAllocator] (Job-Executor-11:job-11) Is
> >> localStorageAllocationNeeded? false
> >> 3. 2013-04-12 11:35:20,292 DEBUG [storage.allocator.
> >> AbstractStoragePoolAllocator] (Job-Executor-11:job-11) Is storage
> >>pool
> >> shared? false
> >> 4. 2013-04-12 11:35:20,292 DEBUG [storage.allocator.
> >> AbstractStoragePoolAllocator] (Job-Executor-11:job-11) StoragePool is
> >> not
> >> of correct type, skipping this pool
> >>
> >>
> >>
> >> On Fri, Apr 12, 2013 at 10:19 PM, Mike Tutkowski <
> >> mike.tutkowski@solidfire.com> wrote:
> >>
> >> > Hi,
> >> >
> >> > Thanks for the comments.
> >> >
> >> > In my case, I am just running a Basic Zone that was originally set up
> >> with
> >> > DevCloud2. I added a Pod and a Cluster with two ESXi Hosts in the
> >> Cluster.
> >> >
> >> > I am able to create iSCSI-based VMFS Datastores and Primary Storages
> >>in
> >> CS
> >> > from them.
> >> >
> >> > However, when I try to execute a Compute Offering that is storage
> >>tagged
> >> to
> >> > only use Primary Storage that is based on one of my VMFS Datastores, I
> >> get
> >> > a failure message.
> >> >
> >> > I've attached the log here:
> >> >
> >> > http://paste.cloudstack.org/rst0/
> >> >
> >> > Thanks!!
> >> >
> >> >
> >> > On Fri, Apr 12, 2013 at 2:49 PM, Musayev, Ilya <im...@webmd.net>
> >> wrote:
> >> >
> >> > > Mike,
> >> > >
> >> > > I've done many vmware install, I don't believe your issue is with VC
> >> > > running on the same hypervisor you are trying to manage - since one
> >>of
> >> my
> >> > > setups is doing just that.
> >> > >
> >> > > Also, while it maybe stated somewhere that you should dedicate this
> >> > > hypervisor to CS, CS does not know anything about other VMs it did
> >>not
> >> > > create. It maybe a best practice to dedicate your hypervisors,
> >>however,
> >> > its
> >> > > not a must requirement (please correct me if I'm wrong).
> >> > >
> >> > > Even when you place ESXi into maintenance mode in CS, it does not
> >> really
> >> > > take hypervisor into maintenance mode, it just evacuvates its VMs to
> >> > other
> >> > > hypervisors.
> >> > >
> >> > > Typical reasons for your problem:
> >> > > 1) you've changed "Management Network" port group
> >> > > 2) you are not using default vswitch0
> >> > > (both of the above can be changed in settings)
> >> > > 3) you attempting to use DVS, not yet supported in 4.1, supported in
> >> 4.2
> >> > > - I will release my version of ACS of 4.1 with DVS integrated as
> >>soon
> >> as
> >> > > 4.1 goes out.
> >> > >
> >> > > If none of the above are true, please submit a log through
> >> > > paste.cloudstack.org, the exception you've posted show the end
> >>result
> >> > > error - but not the original cause.
> >> > >
> >> > > Regards
> >> > > ilya
> >> > >
> >> > > > -----Original Message-----
> >> > > > From: Mike Tutkowski [mailto:mike.tutkowski@solidfire.com]
> >> > > > Sent: Friday, April 12, 2013 3:18 PM
> >> > > > To: dev@cloudstack.apache.org
> >> > > > Cc: cloudstack-dev@incubator.apache.org
> >> > > > Subject: Re: Issue launching VM on VMware
> >> > > >
> >> > > > So, could this be the problem:
> >> > > >
> >> > > > In the interest of efficiency, I am running a virtual appliance
> >>with
> >> > > vCenter
> >> > > > inside of it on one of the two ESXi hosts I'm using in CloudStack.
> >> > > >
> >> > > > Technically we're not supposed to have any VMs running that we're
> >>not
> >> > > > started by CloudStack, right?
> >> > > >
> >> > > > Could this be what's causing my troubles?
> >> > > >
> >> > > >
> >> > > > On Fri, Apr 12, 2013 at 12:56 PM, Mike Tutkowski <
> >> > > > mike.tutkowski@solidfire.com> wrote:
> >> > > >
> >> > > > > Looks like it might be because no virtual router is running?
> >> > > > >
> >> > > > > 2013-04-12 12:50:27,994 DEBUG
> >> > > > > [network.router.VirtualNetworkApplianceManagerImpl]
> >> > > > > (RouterStatusMonitor-1:null) Found 0 routers to update status.
> >> > > > > 2013-04-12 12:50:27,995 DEBUG
> >> > > > > [network.router.VirtualNetworkApplianceManagerImpl]
> >> > > > > (RouterStatusMonitor-1:null) Found 0 networks to update RvR
> >>status.
> >> > > > > 2013-04-12 12:50:28,026 DEBUG
> >> > > > > [network.router.VirtualNetworkApplianceManagerImpl]
> >> > > > > (RouterStatusMonitor-1:null) Found 0 routers to update status.
> >> > > > > 2013-04-12 12:50:28,027 DEBUG
> >> > > > > [network.router.VirtualNetworkApplianceManagerImpl]
> >> > > > > (RouterStatusMonitor-1:null) Found 0 networks to update RvR
> >>status.
> >> > > > >
> >> > > > > My SSVM is running, but it looks like no virtual router is.
> >> > > > >
> >> > > > >
> >> > > > > On Fri, Apr 12, 2013 at 12:11 PM, Kelven Yang
> >> > > > <ke...@citrix.com>wrote:
> >> > > > >
> >> > > > >> Look back from the exception in logs, this exception is the
> >>final
> >> > > > >> place that throws the failure exception, the actual reason may
> >>be
> >> > > > >> shown in logs earlier than this point.
> >> > > > >> Kelven
> >> > > > >>
> >> > > > >> On 4/12/13 10:46 AM, "Mike Tutkowski" <
> >> mike.tutkowski@solidfire.com
> >> > >
> >> > > > >> wrote:
> >> > > > >>
> >> > > > >> >Same problem when I try to start the VM on the local storage
> >>of
> >> > > > >> >either of my ESXi hosts.
> >> > > > >> >
> >> > > > >> >
> >> > > > >> >On Fri, Apr 12, 2013 at 11:39 AM, Mike Tutkowski <
> >> > > > >> >mike.tutkowski@solidfire.com> wrote:
> >> > > > >> >
> >> > > > >> >> Hi,
> >> > > > >> >>
> >> > > > >> >> Any thoughts on this? It seems like I should have plenty of
> >> > > > >> >> memory (on either of my two ESXi hosts) and plenty of
> >>storage
> >> > > > >> >> space (on my iSCSI-backed VMFS datastore).
> >> > > > >> >>
> >> > > > >> >> Thanks!
> >> > > > >> >>
> >> > > > >> >> INFO [user.vm.DeployVMCmd] (Job-Executor-11:job-11) Unable
> >>to
> >> > > > >> >>create a deployment for
> >> > > > >> >>VM[User|5878531f-2164-48cc-b1b7-3b38e9b16b5f]
> >> > > > >> >> com.cloud.exception.InsufficientServerCapacityException:
> >>Unable
> >> > to
> >> > > > >> >>create a deployment for
> >> > > > >> >>VM[User|5878531f-2164-48cc-b1b7-3b38e9b16b5f]Scope=interface
> >> > > > >> >> com.cloud.dc.DataCenter; id=1
> >> > > > >> >> at
> >> > > > >> >>
> >> > > > >>
> >> > > > >>
> >> > >>org.apache.cloudstack.engine.cloud.entity.api.VMEntityManagerImpl.r
> >> > > > >> >>eserve
> >> > > > >> >>VirtualMachine(VMEntityManagerImpl.java:186)
> >> > > > >> >> at
> >> > > > >> >>
> >> > > > >> >>
> >> > > > >>
> >> > org.apache.cloudstack.engine.cloud.entity.api.VirtualMachineEntityImp
> >> > > > >> l.re
> >> > > > >> >>serve(VirtualMachineEntityImpl.java:198)
> >> > > > >> >> at
> >> > > > >> >>
> >> > > > >>
> >> > > > >>
> >> > > > >>com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManage
> >> > > > rImp
> >> > > > >> >>l.java
> >> > > > >> >>:3859)
> >> > > > >> >> at
> >> > > > >> >>
> >> > > > >>
> >> > > > >>
> >> > > > >>com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManage
> >> > > > rImp
> >> > > > >> >>l.java
> >> > > > >> >>:3458)
> >> > > > >> >> at
> >> > > > >> >>
> >> > > > >>
> >> > > > >>
> >> > > > >>com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManage
> >> > > > rImp
> >> > > > >> >>l.java
> >> > > > >> >>:3444)
> >> > > > >> >> at
> >> > > > >> >>
> >> > > > >>
> >> > > > >>
> >> > > >
> >>>>com.cloud.utils.component.ComponentInstantiationPostProcessor$Inter
> >> > > > >> >>ceptor
> >> > > > >>
> >> >>Dispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
> >> > > > >> >> at
> >> > > > >> >>
> >> > > > >>
> >> > > > >>
> >> > > > >>org.apache.cloudstack.api.command.user.vm.DeployVMCmd.execute(De
> >> > > > plo
> >> > > > >> >>yVMCmd
> >> > > > >> >>.java:379)
> >> > > > >> >> at
> >>com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:162)
> >> > > > >> >> at
> >> > > > >> >>
> >> > > > >>
> >> > > >
> >>>>com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.jav
> >> > > > a:
> >> > > > >> >>437)
> >> > > > >> >> at
> >> > > > >>
> >> > >>java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:
> >> > > > >> >>439)
> >> > > > >> >> at
> >> > > > >>
> >> >>java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
> >> > > > >> >> at java.util.concurrent.FutureTask.run(FutureTask.java:138)
> >> > > > >> >> at
> >> > > > >> >>
> >> > > > >>
> >> > > > >>
> >> > > >
> >>>>java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolEx
> >> > > > >> >>ecutor
> >> > > > >> >>.java:895)
> >> > > > >> >> at
> >> > > > >> >>
> >> > > > >>
> >> > > > >>
> >> > > >
> >>>>java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecut
> >> > > > >> >>or.jav
> >> > > > >> >>a:918)
> >> > > > >> >> at java.lang.Thread.run(Thread.java:680)
> >> > > > >> >>
> >> > > > >> >>
> >> > > > >> >> --
> >> > > > >> >> *Mike Tutkowski*
> >> > > > >> >> *Senior CloudStack Developer, SolidFire Inc.*
> >> > > > >> >> e: mike.tutkowski@solidfire.com
> >> > > > >> >> o: 303.746.7302
> >> > > > >> >> Advancing the way the world uses the
> >> > > > >> >>cloud<http://solidfire.com/solution/overview/?video=play>
> >> > > > >> >> * *
> >> > > > >> >>
> >> > > > >> >
> >> > > > >> >
> >> > > > >> >
> >> > > > >> >--
> >> > > > >> >*Mike Tutkowski*
> >> > > > >> >*Senior CloudStack Developer, SolidFire Inc.*
> >> > > > >> >e: mike.tutkowski@solidfire.com
> >> > > > >> >o: 303.746.7302
> >> > > > >> >Advancing the way the world uses the
> >> > > > >> >cloud<http://solidfire.com/solution/overview/?video=play>
> >> > > > >> >* *
> >> > > > >>
> >> > > > >>
> >> > > > >
> >> > > > >
> >> > > > > --
> >> > > > > *Mike Tutkowski*
> >> > > > > *Senior CloudStack Developer, SolidFire Inc.*
> >> > > > > e: mike.tutkowski@solidfire.com
> >> > > > > o: 303.746.7302
> >> > > > > Advancing the way the world uses the
> >> > > > > cloud<http://solidfire.com/solution/overview/?video=play>
> >> > > > > *(tm)*
> >> > > > >
> >> > > >
> >> > > >
> >> > > >
> >> > > > --
> >> > > > *Mike Tutkowski*
> >> > > > *Senior CloudStack Developer, SolidFire Inc.*
> >> > > > e: mike.tutkowski@solidfire.com
> >> > > > o: 303.746.7302
> >> > > > Advancing the way the world uses the
> >> > > > cloud<http://solidfire.com/solution/overview/?video=play>
> >> > > > *(tm)*
> >> > >
> >> > >
> >> >
> >> >
> >> > --
> >> > *Mike Tutkowski*
> >> > *Senior CloudStack Developer, SolidFire Inc.*
> >> > e: mike.tutkowski@solidfire.com
> >> > o: 303.746.7302
> >> > Advancing the way the world uses the
> >> > cloud<http://solidfire.com/solution/overview/?video=play>
> >> > * *
> >> >
> >>
> >
> >
> >
> >--
> >*Mike Tutkowski*
> >*Senior CloudStack Developer, SolidFire Inc.*
> >e: mike.tutkowski@solidfire.com
> >o: 303.746.7302
> >Advancing the way the world uses the
> >cloud<http://solidfire.com/solution/overview/?video=play>
> >* *
>
>
--
*Mike Tutkowski*
*Senior CloudStack Developer, SolidFire Inc.*
e: mike.tutkowski@solidfire.com
o: 303.746.7302
Advancing the way the world uses the
cloud<http://solidfire.com/solution/overview/?video=play>
*™*
Re: Issue launching VM on VMware
Posted by Kelven Yang <ke...@citrix.com>.
>From the log, you seem to use a offering that directs to create volume in
local storage and there is no such storage available in your setup
Kelven
On 4/13/13 4:14 PM, "Mike Tutkowski" <mi...@solidfire.com> wrote:
>That's weird...I have three local storages (one from DevCloud2 by default,
>one from one ESXi host, and one from another ESXi host). I also have
>several shared storages (iSCSI-based datastores that were configured in CS
>as VMFS-based primary storages). I tagged the shared primary storage I
>wanted to use, referenced that storage tag from a compute offering, and
>executed the compute offering.
>
>
>On Sat, Apr 13, 2013 at 12:30 PM, Ahmad Emneina <ae...@gmail.com>
>wrote:
>
>> looks as though your zone is set to use shared storage, and youre only
>> providing local storage.
>>
>> 1. 2013-04-12 11:35:20,292 DEBUG [storage.allocator.
>> AbstractStoragePoolAllocator] (Job-Executor-11:job-11) Checking if
>> storage pool is suitable, name: devcloud Local Storage ,poolId: 200
>> 2. 2013-04-12 11:35:20,292 DEBUG [storage.allocator.
>> AbstractStoragePoolAllocator] (Job-Executor-11:job-11) Is
>> localStorageAllocationNeeded? false
>> 3. 2013-04-12 11:35:20,292 DEBUG [storage.allocator.
>> AbstractStoragePoolAllocator] (Job-Executor-11:job-11) Is storage
>>pool
>> shared? false
>> 4. 2013-04-12 11:35:20,292 DEBUG [storage.allocator.
>> AbstractStoragePoolAllocator] (Job-Executor-11:job-11) StoragePool is
>> not
>> of correct type, skipping this pool
>>
>>
>>
>> On Fri, Apr 12, 2013 at 10:19 PM, Mike Tutkowski <
>> mike.tutkowski@solidfire.com> wrote:
>>
>> > Hi,
>> >
>> > Thanks for the comments.
>> >
>> > In my case, I am just running a Basic Zone that was originally set up
>> with
>> > DevCloud2. I added a Pod and a Cluster with two ESXi Hosts in the
>> Cluster.
>> >
>> > I am able to create iSCSI-based VMFS Datastores and Primary Storages
>>in
>> CS
>> > from them.
>> >
>> > However, when I try to execute a Compute Offering that is storage
>>tagged
>> to
>> > only use Primary Storage that is based on one of my VMFS Datastores, I
>> get
>> > a failure message.
>> >
>> > I've attached the log here:
>> >
>> > http://paste.cloudstack.org/rst0/
>> >
>> > Thanks!!
>> >
>> >
>> > On Fri, Apr 12, 2013 at 2:49 PM, Musayev, Ilya <im...@webmd.net>
>> wrote:
>> >
>> > > Mike,
>> > >
>> > > I've done many vmware install, I don't believe your issue is with VC
>> > > running on the same hypervisor you are trying to manage - since one
>>of
>> my
>> > > setups is doing just that.
>> > >
>> > > Also, while it maybe stated somewhere that you should dedicate this
>> > > hypervisor to CS, CS does not know anything about other VMs it did
>>not
>> > > create. It maybe a best practice to dedicate your hypervisors,
>>however,
>> > its
>> > > not a must requirement (please correct me if I'm wrong).
>> > >
>> > > Even when you place ESXi into maintenance mode in CS, it does not
>> really
>> > > take hypervisor into maintenance mode, it just evacuvates its VMs to
>> > other
>> > > hypervisors.
>> > >
>> > > Typical reasons for your problem:
>> > > 1) you've changed "Management Network" port group
>> > > 2) you are not using default vswitch0
>> > > (both of the above can be changed in settings)
>> > > 3) you attempting to use DVS, not yet supported in 4.1, supported in
>> 4.2
>> > > - I will release my version of ACS of 4.1 with DVS integrated as
>>soon
>> as
>> > > 4.1 goes out.
>> > >
>> > > If none of the above are true, please submit a log through
>> > > paste.cloudstack.org, the exception you've posted show the end
>>result
>> > > error - but not the original cause.
>> > >
>> > > Regards
>> > > ilya
>> > >
>> > > > -----Original Message-----
>> > > > From: Mike Tutkowski [mailto:mike.tutkowski@solidfire.com]
>> > > > Sent: Friday, April 12, 2013 3:18 PM
>> > > > To: dev@cloudstack.apache.org
>> > > > Cc: cloudstack-dev@incubator.apache.org
>> > > > Subject: Re: Issue launching VM on VMware
>> > > >
>> > > > So, could this be the problem:
>> > > >
>> > > > In the interest of efficiency, I am running a virtual appliance
>>with
>> > > vCenter
>> > > > inside of it on one of the two ESXi hosts I'm using in CloudStack.
>> > > >
>> > > > Technically we're not supposed to have any VMs running that we're
>>not
>> > > > started by CloudStack, right?
>> > > >
>> > > > Could this be what's causing my troubles?
>> > > >
>> > > >
>> > > > On Fri, Apr 12, 2013 at 12:56 PM, Mike Tutkowski <
>> > > > mike.tutkowski@solidfire.com> wrote:
>> > > >
>> > > > > Looks like it might be because no virtual router is running?
>> > > > >
>> > > > > 2013-04-12 12:50:27,994 DEBUG
>> > > > > [network.router.VirtualNetworkApplianceManagerImpl]
>> > > > > (RouterStatusMonitor-1:null) Found 0 routers to update status.
>> > > > > 2013-04-12 12:50:27,995 DEBUG
>> > > > > [network.router.VirtualNetworkApplianceManagerImpl]
>> > > > > (RouterStatusMonitor-1:null) Found 0 networks to update RvR
>>status.
>> > > > > 2013-04-12 12:50:28,026 DEBUG
>> > > > > [network.router.VirtualNetworkApplianceManagerImpl]
>> > > > > (RouterStatusMonitor-1:null) Found 0 routers to update status.
>> > > > > 2013-04-12 12:50:28,027 DEBUG
>> > > > > [network.router.VirtualNetworkApplianceManagerImpl]
>> > > > > (RouterStatusMonitor-1:null) Found 0 networks to update RvR
>>status.
>> > > > >
>> > > > > My SSVM is running, but it looks like no virtual router is.
>> > > > >
>> > > > >
>> > > > > On Fri, Apr 12, 2013 at 12:11 PM, Kelven Yang
>> > > > <ke...@citrix.com>wrote:
>> > > > >
>> > > > >> Look back from the exception in logs, this exception is the
>>final
>> > > > >> place that throws the failure exception, the actual reason may
>>be
>> > > > >> shown in logs earlier than this point.
>> > > > >> Kelven
>> > > > >>
>> > > > >> On 4/12/13 10:46 AM, "Mike Tutkowski" <
>> mike.tutkowski@solidfire.com
>> > >
>> > > > >> wrote:
>> > > > >>
>> > > > >> >Same problem when I try to start the VM on the local storage
>>of
>> > > > >> >either of my ESXi hosts.
>> > > > >> >
>> > > > >> >
>> > > > >> >On Fri, Apr 12, 2013 at 11:39 AM, Mike Tutkowski <
>> > > > >> >mike.tutkowski@solidfire.com> wrote:
>> > > > >> >
>> > > > >> >> Hi,
>> > > > >> >>
>> > > > >> >> Any thoughts on this? It seems like I should have plenty of
>> > > > >> >> memory (on either of my two ESXi hosts) and plenty of
>>storage
>> > > > >> >> space (on my iSCSI-backed VMFS datastore).
>> > > > >> >>
>> > > > >> >> Thanks!
>> > > > >> >>
>> > > > >> >> INFO [user.vm.DeployVMCmd] (Job-Executor-11:job-11) Unable
>>to
>> > > > >> >>create a deployment for
>> > > > >> >>VM[User|5878531f-2164-48cc-b1b7-3b38e9b16b5f]
>> > > > >> >> com.cloud.exception.InsufficientServerCapacityException:
>>Unable
>> > to
>> > > > >> >>create a deployment for
>> > > > >> >>VM[User|5878531f-2164-48cc-b1b7-3b38e9b16b5f]Scope=interface
>> > > > >> >> com.cloud.dc.DataCenter; id=1
>> > > > >> >> at
>> > > > >> >>
>> > > > >>
>> > > > >>
>> > >>org.apache.cloudstack.engine.cloud.entity.api.VMEntityManagerImpl.r
>> > > > >> >>eserve
>> > > > >> >>VirtualMachine(VMEntityManagerImpl.java:186)
>> > > > >> >> at
>> > > > >> >>
>> > > > >> >>
>> > > > >>
>> > org.apache.cloudstack.engine.cloud.entity.api.VirtualMachineEntityImp
>> > > > >> l.re
>> > > > >> >>serve(VirtualMachineEntityImpl.java:198)
>> > > > >> >> at
>> > > > >> >>
>> > > > >>
>> > > > >>
>> > > > >>com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManage
>> > > > rImp
>> > > > >> >>l.java
>> > > > >> >>:3859)
>> > > > >> >> at
>> > > > >> >>
>> > > > >>
>> > > > >>
>> > > > >>com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManage
>> > > > rImp
>> > > > >> >>l.java
>> > > > >> >>:3458)
>> > > > >> >> at
>> > > > >> >>
>> > > > >>
>> > > > >>
>> > > > >>com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManage
>> > > > rImp
>> > > > >> >>l.java
>> > > > >> >>:3444)
>> > > > >> >> at
>> > > > >> >>
>> > > > >>
>> > > > >>
>> > > >
>>>>com.cloud.utils.component.ComponentInstantiationPostProcessor$Inter
>> > > > >> >>ceptor
>> > > > >>
>> >>Dispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
>> > > > >> >> at
>> > > > >> >>
>> > > > >>
>> > > > >>
>> > > > >>org.apache.cloudstack.api.command.user.vm.DeployVMCmd.execute(De
>> > > > plo
>> > > > >> >>yVMCmd
>> > > > >> >>.java:379)
>> > > > >> >> at
>>com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:162)
>> > > > >> >> at
>> > > > >> >>
>> > > > >>
>> > > >
>>>>com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.jav
>> > > > a:
>> > > > >> >>437)
>> > > > >> >> at
>> > > > >>
>> > >>java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:
>> > > > >> >>439)
>> > > > >> >> at
>> > > > >>
>> >>java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
>> > > > >> >> at java.util.concurrent.FutureTask.run(FutureTask.java:138)
>> > > > >> >> at
>> > > > >> >>
>> > > > >>
>> > > > >>
>> > > >
>>>>java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolEx
>> > > > >> >>ecutor
>> > > > >> >>.java:895)
>> > > > >> >> at
>> > > > >> >>
>> > > > >>
>> > > > >>
>> > > >
>>>>java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecut
>> > > > >> >>or.jav
>> > > > >> >>a:918)
>> > > > >> >> at java.lang.Thread.run(Thread.java:680)
>> > > > >> >>
>> > > > >> >>
>> > > > >> >> --
>> > > > >> >> *Mike Tutkowski*
>> > > > >> >> *Senior CloudStack Developer, SolidFire Inc.*
>> > > > >> >> e: mike.tutkowski@solidfire.com
>> > > > >> >> o: 303.746.7302
>> > > > >> >> Advancing the way the world uses the
>> > > > >> >>cloud<http://solidfire.com/solution/overview/?video=play>
>> > > > >> >> * *
>> > > > >> >>
>> > > > >> >
>> > > > >> >
>> > > > >> >
>> > > > >> >--
>> > > > >> >*Mike Tutkowski*
>> > > > >> >*Senior CloudStack Developer, SolidFire Inc.*
>> > > > >> >e: mike.tutkowski@solidfire.com
>> > > > >> >o: 303.746.7302
>> > > > >> >Advancing the way the world uses the
>> > > > >> >cloud<http://solidfire.com/solution/overview/?video=play>
>> > > > >> >* *
>> > > > >>
>> > > > >>
>> > > > >
>> > > > >
>> > > > > --
>> > > > > *Mike Tutkowski*
>> > > > > *Senior CloudStack Developer, SolidFire Inc.*
>> > > > > e: mike.tutkowski@solidfire.com
>> > > > > o: 303.746.7302
>> > > > > Advancing the way the world uses the
>> > > > > cloud<http://solidfire.com/solution/overview/?video=play>
>> > > > > *(tm)*
>> > > > >
>> > > >
>> > > >
>> > > >
>> > > > --
>> > > > *Mike Tutkowski*
>> > > > *Senior CloudStack Developer, SolidFire Inc.*
>> > > > e: mike.tutkowski@solidfire.com
>> > > > o: 303.746.7302
>> > > > Advancing the way the world uses the
>> > > > cloud<http://solidfire.com/solution/overview/?video=play>
>> > > > *(tm)*
>> > >
>> > >
>> >
>> >
>> > --
>> > *Mike Tutkowski*
>> > *Senior CloudStack Developer, SolidFire Inc.*
>> > e: mike.tutkowski@solidfire.com
>> > o: 303.746.7302
>> > Advancing the way the world uses the
>> > cloud<http://solidfire.com/solution/overview/?video=play>
>> > **
>> >
>>
>
>
>
>--
>*Mike Tutkowski*
>*Senior CloudStack Developer, SolidFire Inc.*
>e: mike.tutkowski@solidfire.com
>o: 303.746.7302
>Advancing the way the world uses the
>cloud<http://solidfire.com/solution/overview/?video=play>
>**
Re: Issue launching VM on VMware
Posted by Mike Tutkowski <mi...@solidfire.com>.
That's weird...I have three local storages (one from DevCloud2 by default,
one from one ESXi host, and one from another ESXi host). I also have
several shared storages (iSCSI-based datastores that were configured in CS
as VMFS-based primary storages). I tagged the shared primary storage I
wanted to use, referenced that storage tag from a compute offering, and
executed the compute offering.
On Sat, Apr 13, 2013 at 12:30 PM, Ahmad Emneina <ae...@gmail.com> wrote:
> looks as though your zone is set to use shared storage, and youre only
> providing local storage.
>
> 1. 2013-04-12 11:35:20,292 DEBUG [storage.allocator.
> AbstractStoragePoolAllocator] (Job-Executor-11:job-11) Checking if
> storage pool is suitable, name: devcloud Local Storage ,poolId: 200
> 2. 2013-04-12 11:35:20,292 DEBUG [storage.allocator.
> AbstractStoragePoolAllocator] (Job-Executor-11:job-11) Is
> localStorageAllocationNeeded? false
> 3. 2013-04-12 11:35:20,292 DEBUG [storage.allocator.
> AbstractStoragePoolAllocator] (Job-Executor-11:job-11) Is storage pool
> shared? false
> 4. 2013-04-12 11:35:20,292 DEBUG [storage.allocator.
> AbstractStoragePoolAllocator] (Job-Executor-11:job-11) StoragePool is
> not
> of correct type, skipping this pool
>
>
>
> On Fri, Apr 12, 2013 at 10:19 PM, Mike Tutkowski <
> mike.tutkowski@solidfire.com> wrote:
>
> > Hi,
> >
> > Thanks for the comments.
> >
> > In my case, I am just running a Basic Zone that was originally set up
> with
> > DevCloud2. I added a Pod and a Cluster with two ESXi Hosts in the
> Cluster.
> >
> > I am able to create iSCSI-based VMFS Datastores and Primary Storages in
> CS
> > from them.
> >
> > However, when I try to execute a Compute Offering that is storage tagged
> to
> > only use Primary Storage that is based on one of my VMFS Datastores, I
> get
> > a failure message.
> >
> > I've attached the log here:
> >
> > http://paste.cloudstack.org/rst0/
> >
> > Thanks!!
> >
> >
> > On Fri, Apr 12, 2013 at 2:49 PM, Musayev, Ilya <im...@webmd.net>
> wrote:
> >
> > > Mike,
> > >
> > > I've done many vmware install, I don't believe your issue is with VC
> > > running on the same hypervisor you are trying to manage - since one of
> my
> > > setups is doing just that.
> > >
> > > Also, while it maybe stated somewhere that you should dedicate this
> > > hypervisor to CS, CS does not know anything about other VMs it did not
> > > create. It maybe a best practice to dedicate your hypervisors, however,
> > its
> > > not a must requirement (please correct me if I'm wrong).
> > >
> > > Even when you place ESXi into maintenance mode in CS, it does not
> really
> > > take hypervisor into maintenance mode, it just evacuvates its VMs to
> > other
> > > hypervisors.
> > >
> > > Typical reasons for your problem:
> > > 1) you've changed "Management Network" port group
> > > 2) you are not using default vswitch0
> > > (both of the above can be changed in settings)
> > > 3) you attempting to use DVS, not yet supported in 4.1, supported in
> 4.2
> > > - I will release my version of ACS of 4.1 with DVS integrated as soon
> as
> > > 4.1 goes out.
> > >
> > > If none of the above are true, please submit a log through
> > > paste.cloudstack.org, the exception you've posted show the end result
> > > error - but not the original cause.
> > >
> > > Regards
> > > ilya
> > >
> > > > -----Original Message-----
> > > > From: Mike Tutkowski [mailto:mike.tutkowski@solidfire.com]
> > > > Sent: Friday, April 12, 2013 3:18 PM
> > > > To: dev@cloudstack.apache.org
> > > > Cc: cloudstack-dev@incubator.apache.org
> > > > Subject: Re: Issue launching VM on VMware
> > > >
> > > > So, could this be the problem:
> > > >
> > > > In the interest of efficiency, I am running a virtual appliance with
> > > vCenter
> > > > inside of it on one of the two ESXi hosts I'm using in CloudStack.
> > > >
> > > > Technically we're not supposed to have any VMs running that we're not
> > > > started by CloudStack, right?
> > > >
> > > > Could this be what's causing my troubles?
> > > >
> > > >
> > > > On Fri, Apr 12, 2013 at 12:56 PM, Mike Tutkowski <
> > > > mike.tutkowski@solidfire.com> wrote:
> > > >
> > > > > Looks like it might be because no virtual router is running?
> > > > >
> > > > > 2013-04-12 12:50:27,994 DEBUG
> > > > > [network.router.VirtualNetworkApplianceManagerImpl]
> > > > > (RouterStatusMonitor-1:null) Found 0 routers to update status.
> > > > > 2013-04-12 12:50:27,995 DEBUG
> > > > > [network.router.VirtualNetworkApplianceManagerImpl]
> > > > > (RouterStatusMonitor-1:null) Found 0 networks to update RvR status.
> > > > > 2013-04-12 12:50:28,026 DEBUG
> > > > > [network.router.VirtualNetworkApplianceManagerImpl]
> > > > > (RouterStatusMonitor-1:null) Found 0 routers to update status.
> > > > > 2013-04-12 12:50:28,027 DEBUG
> > > > > [network.router.VirtualNetworkApplianceManagerImpl]
> > > > > (RouterStatusMonitor-1:null) Found 0 networks to update RvR status.
> > > > >
> > > > > My SSVM is running, but it looks like no virtual router is.
> > > > >
> > > > >
> > > > > On Fri, Apr 12, 2013 at 12:11 PM, Kelven Yang
> > > > <ke...@citrix.com>wrote:
> > > > >
> > > > >> Look back from the exception in logs, this exception is the final
> > > > >> place that throws the failure exception, the actual reason may be
> > > > >> shown in logs earlier than this point.
> > > > >> Kelven
> > > > >>
> > > > >> On 4/12/13 10:46 AM, "Mike Tutkowski" <
> mike.tutkowski@solidfire.com
> > >
> > > > >> wrote:
> > > > >>
> > > > >> >Same problem when I try to start the VM on the local storage of
> > > > >> >either of my ESXi hosts.
> > > > >> >
> > > > >> >
> > > > >> >On Fri, Apr 12, 2013 at 11:39 AM, Mike Tutkowski <
> > > > >> >mike.tutkowski@solidfire.com> wrote:
> > > > >> >
> > > > >> >> Hi,
> > > > >> >>
> > > > >> >> Any thoughts on this? It seems like I should have plenty of
> > > > >> >> memory (on either of my two ESXi hosts) and plenty of storage
> > > > >> >> space (on my iSCSI-backed VMFS datastore).
> > > > >> >>
> > > > >> >> Thanks!
> > > > >> >>
> > > > >> >> INFO [user.vm.DeployVMCmd] (Job-Executor-11:job-11) Unable to
> > > > >> >>create a deployment for
> > > > >> >>VM[User|5878531f-2164-48cc-b1b7-3b38e9b16b5f]
> > > > >> >> com.cloud.exception.InsufficientServerCapacityException: Unable
> > to
> > > > >> >>create a deployment for
> > > > >> >>VM[User|5878531f-2164-48cc-b1b7-3b38e9b16b5f]Scope=interface
> > > > >> >> com.cloud.dc.DataCenter; id=1
> > > > >> >> at
> > > > >> >>
> > > > >>
> > > > >>
> > >>org.apache.cloudstack.engine.cloud.entity.api.VMEntityManagerImpl.r
> > > > >> >>eserve
> > > > >> >>VirtualMachine(VMEntityManagerImpl.java:186)
> > > > >> >> at
> > > > >> >>
> > > > >> >>
> > > > >>
> > org.apache.cloudstack.engine.cloud.entity.api.VirtualMachineEntityImp
> > > > >> l.re
> > > > >> >>serve(VirtualMachineEntityImpl.java:198)
> > > > >> >> at
> > > > >> >>
> > > > >>
> > > > >>
> > > > >>com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManage
> > > > rImp
> > > > >> >>l.java
> > > > >> >>:3859)
> > > > >> >> at
> > > > >> >>
> > > > >>
> > > > >>
> > > > >>com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManage
> > > > rImp
> > > > >> >>l.java
> > > > >> >>:3458)
> > > > >> >> at
> > > > >> >>
> > > > >>
> > > > >>
> > > > >>com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManage
> > > > rImp
> > > > >> >>l.java
> > > > >> >>:3444)
> > > > >> >> at
> > > > >> >>
> > > > >>
> > > > >>
> > > > >>com.cloud.utils.component.ComponentInstantiationPostProcessor$Inter
> > > > >> >>ceptor
> > > > >>
> >>Dispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
> > > > >> >> at
> > > > >> >>
> > > > >>
> > > > >>
> > > > >>org.apache.cloudstack.api.command.user.vm.DeployVMCmd.execute(De
> > > > plo
> > > > >> >>yVMCmd
> > > > >> >>.java:379)
> > > > >> >> at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:162)
> > > > >> >> at
> > > > >> >>
> > > > >>
> > > > >>com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.jav
> > > > a:
> > > > >> >>437)
> > > > >> >> at
> > > > >>
> > >>java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:
> > > > >> >>439)
> > > > >> >> at
> > > > >>
> >>java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
> > > > >> >> at java.util.concurrent.FutureTask.run(FutureTask.java:138)
> > > > >> >> at
> > > > >> >>
> > > > >>
> > > > >>
> > > > >>java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolEx
> > > > >> >>ecutor
> > > > >> >>.java:895)
> > > > >> >> at
> > > > >> >>
> > > > >>
> > > > >>
> > > > >>java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecut
> > > > >> >>or.jav
> > > > >> >>a:918)
> > > > >> >> at java.lang.Thread.run(Thread.java:680)
> > > > >> >>
> > > > >> >>
> > > > >> >> --
> > > > >> >> *Mike Tutkowski*
> > > > >> >> *Senior CloudStack Developer, SolidFire Inc.*
> > > > >> >> e: mike.tutkowski@solidfire.com
> > > > >> >> o: 303.746.7302
> > > > >> >> Advancing the way the world uses the
> > > > >> >>cloud<http://solidfire.com/solution/overview/?video=play>
> > > > >> >> * *
> > > > >> >>
> > > > >> >
> > > > >> >
> > > > >> >
> > > > >> >--
> > > > >> >*Mike Tutkowski*
> > > > >> >*Senior CloudStack Developer, SolidFire Inc.*
> > > > >> >e: mike.tutkowski@solidfire.com
> > > > >> >o: 303.746.7302
> > > > >> >Advancing the way the world uses the
> > > > >> >cloud<http://solidfire.com/solution/overview/?video=play>
> > > > >> >* *
> > > > >>
> > > > >>
> > > > >
> > > > >
> > > > > --
> > > > > *Mike Tutkowski*
> > > > > *Senior CloudStack Developer, SolidFire Inc.*
> > > > > e: mike.tutkowski@solidfire.com
> > > > > o: 303.746.7302
> > > > > Advancing the way the world uses the
> > > > > cloud<http://solidfire.com/solution/overview/?video=play>
> > > > > *(tm)*
> > > > >
> > > >
> > > >
> > > >
> > > > --
> > > > *Mike Tutkowski*
> > > > *Senior CloudStack Developer, SolidFire Inc.*
> > > > e: mike.tutkowski@solidfire.com
> > > > o: 303.746.7302
> > > > Advancing the way the world uses the
> > > > cloud<http://solidfire.com/solution/overview/?video=play>
> > > > *(tm)*
> > >
> > >
> >
> >
> > --
> > *Mike Tutkowski*
> > *Senior CloudStack Developer, SolidFire Inc.*
> > e: mike.tutkowski@solidfire.com
> > o: 303.746.7302
> > Advancing the way the world uses the
> > cloud<http://solidfire.com/solution/overview/?video=play>
> > *™*
> >
>
--
*Mike Tutkowski*
*Senior CloudStack Developer, SolidFire Inc.*
e: mike.tutkowski@solidfire.com
o: 303.746.7302
Advancing the way the world uses the
cloud<http://solidfire.com/solution/overview/?video=play>
*™*
Re: Issue launching VM on VMware
Posted by Ahmad Emneina <ae...@gmail.com>.
looks as though your zone is set to use shared storage, and youre only
providing local storage.
1. 2013-04-12 11:35:20,292 DEBUG [storage.allocator.
AbstractStoragePoolAllocator] (Job-Executor-11:job-11) Checking if
storage pool is suitable, name: devcloud Local Storage ,poolId: 200
2. 2013-04-12 11:35:20,292 DEBUG [storage.allocator.
AbstractStoragePoolAllocator] (Job-Executor-11:job-11) Is
localStorageAllocationNeeded? false
3. 2013-04-12 11:35:20,292 DEBUG [storage.allocator.
AbstractStoragePoolAllocator] (Job-Executor-11:job-11) Is storage pool
shared? false
4. 2013-04-12 11:35:20,292 DEBUG [storage.allocator.
AbstractStoragePoolAllocator] (Job-Executor-11:job-11) StoragePool is not
of correct type, skipping this pool
On Fri, Apr 12, 2013 at 10:19 PM, Mike Tutkowski <
mike.tutkowski@solidfire.com> wrote:
> Hi,
>
> Thanks for the comments.
>
> In my case, I am just running a Basic Zone that was originally set up with
> DevCloud2. I added a Pod and a Cluster with two ESXi Hosts in the Cluster.
>
> I am able to create iSCSI-based VMFS Datastores and Primary Storages in CS
> from them.
>
> However, when I try to execute a Compute Offering that is storage tagged to
> only use Primary Storage that is based on one of my VMFS Datastores, I get
> a failure message.
>
> I've attached the log here:
>
> http://paste.cloudstack.org/rst0/
>
> Thanks!!
>
>
> On Fri, Apr 12, 2013 at 2:49 PM, Musayev, Ilya <im...@webmd.net> wrote:
>
> > Mike,
> >
> > I've done many vmware install, I don't believe your issue is with VC
> > running on the same hypervisor you are trying to manage - since one of my
> > setups is doing just that.
> >
> > Also, while it maybe stated somewhere that you should dedicate this
> > hypervisor to CS, CS does not know anything about other VMs it did not
> > create. It maybe a best practice to dedicate your hypervisors, however,
> its
> > not a must requirement (please correct me if I'm wrong).
> >
> > Even when you place ESXi into maintenance mode in CS, it does not really
> > take hypervisor into maintenance mode, it just evacuvates its VMs to
> other
> > hypervisors.
> >
> > Typical reasons for your problem:
> > 1) you've changed "Management Network" port group
> > 2) you are not using default vswitch0
> > (both of the above can be changed in settings)
> > 3) you attempting to use DVS, not yet supported in 4.1, supported in 4.2
> > - I will release my version of ACS of 4.1 with DVS integrated as soon as
> > 4.1 goes out.
> >
> > If none of the above are true, please submit a log through
> > paste.cloudstack.org, the exception you've posted show the end result
> > error - but not the original cause.
> >
> > Regards
> > ilya
> >
> > > -----Original Message-----
> > > From: Mike Tutkowski [mailto:mike.tutkowski@solidfire.com]
> > > Sent: Friday, April 12, 2013 3:18 PM
> > > To: dev@cloudstack.apache.org
> > > Cc: cloudstack-dev@incubator.apache.org
> > > Subject: Re: Issue launching VM on VMware
> > >
> > > So, could this be the problem:
> > >
> > > In the interest of efficiency, I am running a virtual appliance with
> > vCenter
> > > inside of it on one of the two ESXi hosts I'm using in CloudStack.
> > >
> > > Technically we're not supposed to have any VMs running that we're not
> > > started by CloudStack, right?
> > >
> > > Could this be what's causing my troubles?
> > >
> > >
> > > On Fri, Apr 12, 2013 at 12:56 PM, Mike Tutkowski <
> > > mike.tutkowski@solidfire.com> wrote:
> > >
> > > > Looks like it might be because no virtual router is running?
> > > >
> > > > 2013-04-12 12:50:27,994 DEBUG
> > > > [network.router.VirtualNetworkApplianceManagerImpl]
> > > > (RouterStatusMonitor-1:null) Found 0 routers to update status.
> > > > 2013-04-12 12:50:27,995 DEBUG
> > > > [network.router.VirtualNetworkApplianceManagerImpl]
> > > > (RouterStatusMonitor-1:null) Found 0 networks to update RvR status.
> > > > 2013-04-12 12:50:28,026 DEBUG
> > > > [network.router.VirtualNetworkApplianceManagerImpl]
> > > > (RouterStatusMonitor-1:null) Found 0 routers to update status.
> > > > 2013-04-12 12:50:28,027 DEBUG
> > > > [network.router.VirtualNetworkApplianceManagerImpl]
> > > > (RouterStatusMonitor-1:null) Found 0 networks to update RvR status.
> > > >
> > > > My SSVM is running, but it looks like no virtual router is.
> > > >
> > > >
> > > > On Fri, Apr 12, 2013 at 12:11 PM, Kelven Yang
> > > <ke...@citrix.com>wrote:
> > > >
> > > >> Look back from the exception in logs, this exception is the final
> > > >> place that throws the failure exception, the actual reason may be
> > > >> shown in logs earlier than this point.
> > > >> Kelven
> > > >>
> > > >> On 4/12/13 10:46 AM, "Mike Tutkowski" <mike.tutkowski@solidfire.com
> >
> > > >> wrote:
> > > >>
> > > >> >Same problem when I try to start the VM on the local storage of
> > > >> >either of my ESXi hosts.
> > > >> >
> > > >> >
> > > >> >On Fri, Apr 12, 2013 at 11:39 AM, Mike Tutkowski <
> > > >> >mike.tutkowski@solidfire.com> wrote:
> > > >> >
> > > >> >> Hi,
> > > >> >>
> > > >> >> Any thoughts on this? It seems like I should have plenty of
> > > >> >> memory (on either of my two ESXi hosts) and plenty of storage
> > > >> >> space (on my iSCSI-backed VMFS datastore).
> > > >> >>
> > > >> >> Thanks!
> > > >> >>
> > > >> >> INFO [user.vm.DeployVMCmd] (Job-Executor-11:job-11) Unable to
> > > >> >>create a deployment for
> > > >> >>VM[User|5878531f-2164-48cc-b1b7-3b38e9b16b5f]
> > > >> >> com.cloud.exception.InsufficientServerCapacityException: Unable
> to
> > > >> >>create a deployment for
> > > >> >>VM[User|5878531f-2164-48cc-b1b7-3b38e9b16b5f]Scope=interface
> > > >> >> com.cloud.dc.DataCenter; id=1
> > > >> >> at
> > > >> >>
> > > >>
> > > >>
> >>org.apache.cloudstack.engine.cloud.entity.api.VMEntityManagerImpl.r
> > > >> >>eserve
> > > >> >>VirtualMachine(VMEntityManagerImpl.java:186)
> > > >> >> at
> > > >> >>
> > > >> >>
> > > >>
> org.apache.cloudstack.engine.cloud.entity.api.VirtualMachineEntityImp
> > > >> l.re
> > > >> >>serve(VirtualMachineEntityImpl.java:198)
> > > >> >> at
> > > >> >>
> > > >>
> > > >>
> > > >>com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManage
> > > rImp
> > > >> >>l.java
> > > >> >>:3859)
> > > >> >> at
> > > >> >>
> > > >>
> > > >>
> > > >>com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManage
> > > rImp
> > > >> >>l.java
> > > >> >>:3458)
> > > >> >> at
> > > >> >>
> > > >>
> > > >>
> > > >>com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManage
> > > rImp
> > > >> >>l.java
> > > >> >>:3444)
> > > >> >> at
> > > >> >>
> > > >>
> > > >>
> > > >>com.cloud.utils.component.ComponentInstantiationPostProcessor$Inter
> > > >> >>ceptor
> > > >> >>Dispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
> > > >> >> at
> > > >> >>
> > > >>
> > > >>
> > > >>org.apache.cloudstack.api.command.user.vm.DeployVMCmd.execute(De
> > > plo
> > > >> >>yVMCmd
> > > >> >>.java:379)
> > > >> >> at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:162)
> > > >> >> at
> > > >> >>
> > > >>
> > > >>com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.jav
> > > a:
> > > >> >>437)
> > > >> >> at
> > > >>
> >>java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:
> > > >> >>439)
> > > >> >> at
> > > >> >>java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
> > > >> >> at java.util.concurrent.FutureTask.run(FutureTask.java:138)
> > > >> >> at
> > > >> >>
> > > >>
> > > >>
> > > >>java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolEx
> > > >> >>ecutor
> > > >> >>.java:895)
> > > >> >> at
> > > >> >>
> > > >>
> > > >>
> > > >>java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecut
> > > >> >>or.jav
> > > >> >>a:918)
> > > >> >> at java.lang.Thread.run(Thread.java:680)
> > > >> >>
> > > >> >>
> > > >> >> --
> > > >> >> *Mike Tutkowski*
> > > >> >> *Senior CloudStack Developer, SolidFire Inc.*
> > > >> >> e: mike.tutkowski@solidfire.com
> > > >> >> o: 303.746.7302
> > > >> >> Advancing the way the world uses the
> > > >> >>cloud<http://solidfire.com/solution/overview/?video=play>
> > > >> >> * *
> > > >> >>
> > > >> >
> > > >> >
> > > >> >
> > > >> >--
> > > >> >*Mike Tutkowski*
> > > >> >*Senior CloudStack Developer, SolidFire Inc.*
> > > >> >e: mike.tutkowski@solidfire.com
> > > >> >o: 303.746.7302
> > > >> >Advancing the way the world uses the
> > > >> >cloud<http://solidfire.com/solution/overview/?video=play>
> > > >> >* *
> > > >>
> > > >>
> > > >
> > > >
> > > > --
> > > > *Mike Tutkowski*
> > > > *Senior CloudStack Developer, SolidFire Inc.*
> > > > e: mike.tutkowski@solidfire.com
> > > > o: 303.746.7302
> > > > Advancing the way the world uses the
> > > > cloud<http://solidfire.com/solution/overview/?video=play>
> > > > *(tm)*
> > > >
> > >
> > >
> > >
> > > --
> > > *Mike Tutkowski*
> > > *Senior CloudStack Developer, SolidFire Inc.*
> > > e: mike.tutkowski@solidfire.com
> > > o: 303.746.7302
> > > Advancing the way the world uses the
> > > cloud<http://solidfire.com/solution/overview/?video=play>
> > > *(tm)*
> >
> >
>
>
> --
> *Mike Tutkowski*
> *Senior CloudStack Developer, SolidFire Inc.*
> e: mike.tutkowski@solidfire.com
> o: 303.746.7302
> Advancing the way the world uses the
> cloud<http://solidfire.com/solution/overview/?video=play>
> *™*
>
Re: Issue launching VM on VMware
Posted by Mike Tutkowski <mi...@solidfire.com>.
Hi,
Thanks for the comments.
In my case, I am just running a Basic Zone that was originally set up with
DevCloud2. I added a Pod and a Cluster with two ESXi Hosts in the Cluster.
I am able to create iSCSI-based VMFS Datastores and Primary Storages in CS
from them.
However, when I try to execute a Compute Offering that is storage tagged to
only use Primary Storage that is based on one of my VMFS Datastores, I get
a failure message.
I've attached the log here:
http://paste.cloudstack.org/rst0/
Thanks!!
On Fri, Apr 12, 2013 at 2:49 PM, Musayev, Ilya <im...@webmd.net> wrote:
> Mike,
>
> I've done many vmware install, I don't believe your issue is with VC
> running on the same hypervisor you are trying to manage - since one of my
> setups is doing just that.
>
> Also, while it maybe stated somewhere that you should dedicate this
> hypervisor to CS, CS does not know anything about other VMs it did not
> create. It maybe a best practice to dedicate your hypervisors, however, its
> not a must requirement (please correct me if I'm wrong).
>
> Even when you place ESXi into maintenance mode in CS, it does not really
> take hypervisor into maintenance mode, it just evacuvates its VMs to other
> hypervisors.
>
> Typical reasons for your problem:
> 1) you've changed "Management Network" port group
> 2) you are not using default vswitch0
> (both of the above can be changed in settings)
> 3) you attempting to use DVS, not yet supported in 4.1, supported in 4.2
> - I will release my version of ACS of 4.1 with DVS integrated as soon as
> 4.1 goes out.
>
> If none of the above are true, please submit a log through
> paste.cloudstack.org, the exception you've posted show the end result
> error - but not the original cause.
>
> Regards
> ilya
>
> > -----Original Message-----
> > From: Mike Tutkowski [mailto:mike.tutkowski@solidfire.com]
> > Sent: Friday, April 12, 2013 3:18 PM
> > To: dev@cloudstack.apache.org
> > Cc: cloudstack-dev@incubator.apache.org
> > Subject: Re: Issue launching VM on VMware
> >
> > So, could this be the problem:
> >
> > In the interest of efficiency, I am running a virtual appliance with
> vCenter
> > inside of it on one of the two ESXi hosts I'm using in CloudStack.
> >
> > Technically we're not supposed to have any VMs running that we're not
> > started by CloudStack, right?
> >
> > Could this be what's causing my troubles?
> >
> >
> > On Fri, Apr 12, 2013 at 12:56 PM, Mike Tutkowski <
> > mike.tutkowski@solidfire.com> wrote:
> >
> > > Looks like it might be because no virtual router is running?
> > >
> > > 2013-04-12 12:50:27,994 DEBUG
> > > [network.router.VirtualNetworkApplianceManagerImpl]
> > > (RouterStatusMonitor-1:null) Found 0 routers to update status.
> > > 2013-04-12 12:50:27,995 DEBUG
> > > [network.router.VirtualNetworkApplianceManagerImpl]
> > > (RouterStatusMonitor-1:null) Found 0 networks to update RvR status.
> > > 2013-04-12 12:50:28,026 DEBUG
> > > [network.router.VirtualNetworkApplianceManagerImpl]
> > > (RouterStatusMonitor-1:null) Found 0 routers to update status.
> > > 2013-04-12 12:50:28,027 DEBUG
> > > [network.router.VirtualNetworkApplianceManagerImpl]
> > > (RouterStatusMonitor-1:null) Found 0 networks to update RvR status.
> > >
> > > My SSVM is running, but it looks like no virtual router is.
> > >
> > >
> > > On Fri, Apr 12, 2013 at 12:11 PM, Kelven Yang
> > <ke...@citrix.com>wrote:
> > >
> > >> Look back from the exception in logs, this exception is the final
> > >> place that throws the failure exception, the actual reason may be
> > >> shown in logs earlier than this point.
> > >> Kelven
> > >>
> > >> On 4/12/13 10:46 AM, "Mike Tutkowski" <mi...@solidfire.com>
> > >> wrote:
> > >>
> > >> >Same problem when I try to start the VM on the local storage of
> > >> >either of my ESXi hosts.
> > >> >
> > >> >
> > >> >On Fri, Apr 12, 2013 at 11:39 AM, Mike Tutkowski <
> > >> >mike.tutkowski@solidfire.com> wrote:
> > >> >
> > >> >> Hi,
> > >> >>
> > >> >> Any thoughts on this? It seems like I should have plenty of
> > >> >> memory (on either of my two ESXi hosts) and plenty of storage
> > >> >> space (on my iSCSI-backed VMFS datastore).
> > >> >>
> > >> >> Thanks!
> > >> >>
> > >> >> INFO [user.vm.DeployVMCmd] (Job-Executor-11:job-11) Unable to
> > >> >>create a deployment for
> > >> >>VM[User|5878531f-2164-48cc-b1b7-3b38e9b16b5f]
> > >> >> com.cloud.exception.InsufficientServerCapacityException: Unable to
> > >> >>create a deployment for
> > >> >>VM[User|5878531f-2164-48cc-b1b7-3b38e9b16b5f]Scope=interface
> > >> >> com.cloud.dc.DataCenter; id=1
> > >> >> at
> > >> >>
> > >>
> > >> >>org.apache.cloudstack.engine.cloud.entity.api.VMEntityManagerImpl.r
> > >> >>eserve
> > >> >>VirtualMachine(VMEntityManagerImpl.java:186)
> > >> >> at
> > >> >>
> > >> >>
> > >> org.apache.cloudstack.engine.cloud.entity.api.VirtualMachineEntityImp
> > >> l.re
> > >> >>serve(VirtualMachineEntityImpl.java:198)
> > >> >> at
> > >> >>
> > >>
> > >>
> > >>com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManage
> > rImp
> > >> >>l.java
> > >> >>:3859)
> > >> >> at
> > >> >>
> > >>
> > >>
> > >>com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManage
> > rImp
> > >> >>l.java
> > >> >>:3458)
> > >> >> at
> > >> >>
> > >>
> > >>
> > >>com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManage
> > rImp
> > >> >>l.java
> > >> >>:3444)
> > >> >> at
> > >> >>
> > >>
> > >>
> > >>com.cloud.utils.component.ComponentInstantiationPostProcessor$Inter
> > >> >>ceptor
> > >> >>Dispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
> > >> >> at
> > >> >>
> > >>
> > >>
> > >>org.apache.cloudstack.api.command.user.vm.DeployVMCmd.execute(De
> > plo
> > >> >>yVMCmd
> > >> >>.java:379)
> > >> >> at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:162)
> > >> >> at
> > >> >>
> > >>
> > >>com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.jav
> > a:
> > >> >>437)
> > >> >> at
> > >> >>java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:
> > >> >>439)
> > >> >> at
> > >> >>java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
> > >> >> at java.util.concurrent.FutureTask.run(FutureTask.java:138)
> > >> >> at
> > >> >>
> > >>
> > >>
> > >>java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolEx
> > >> >>ecutor
> > >> >>.java:895)
> > >> >> at
> > >> >>
> > >>
> > >>
> > >>java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecut
> > >> >>or.jav
> > >> >>a:918)
> > >> >> at java.lang.Thread.run(Thread.java:680)
> > >> >>
> > >> >>
> > >> >> --
> > >> >> *Mike Tutkowski*
> > >> >> *Senior CloudStack Developer, SolidFire Inc.*
> > >> >> e: mike.tutkowski@solidfire.com
> > >> >> o: 303.746.7302
> > >> >> Advancing the way the world uses the
> > >> >>cloud<http://solidfire.com/solution/overview/?video=play>
> > >> >> * *
> > >> >>
> > >> >
> > >> >
> > >> >
> > >> >--
> > >> >*Mike Tutkowski*
> > >> >*Senior CloudStack Developer, SolidFire Inc.*
> > >> >e: mike.tutkowski@solidfire.com
> > >> >o: 303.746.7302
> > >> >Advancing the way the world uses the
> > >> >cloud<http://solidfire.com/solution/overview/?video=play>
> > >> >* *
> > >>
> > >>
> > >
> > >
> > > --
> > > *Mike Tutkowski*
> > > *Senior CloudStack Developer, SolidFire Inc.*
> > > e: mike.tutkowski@solidfire.com
> > > o: 303.746.7302
> > > Advancing the way the world uses the
> > > cloud<http://solidfire.com/solution/overview/?video=play>
> > > *(tm)*
> > >
> >
> >
> >
> > --
> > *Mike Tutkowski*
> > *Senior CloudStack Developer, SolidFire Inc.*
> > e: mike.tutkowski@solidfire.com
> > o: 303.746.7302
> > Advancing the way the world uses the
> > cloud<http://solidfire.com/solution/overview/?video=play>
> > *(tm)*
>
>
--
*Mike Tutkowski*
*Senior CloudStack Developer, SolidFire Inc.*
e: mike.tutkowski@solidfire.com
o: 303.746.7302
Advancing the way the world uses the
cloud<http://solidfire.com/solution/overview/?video=play>
*™*
RE: Issue launching VM on VMware
Posted by "Musayev, Ilya" <im...@webmd.net>.
Mike,
I've done many vmware install, I don't believe your issue is with VC running on the same hypervisor you are trying to manage - since one of my setups is doing just that.
Also, while it maybe stated somewhere that you should dedicate this hypervisor to CS, CS does not know anything about other VMs it did not create. It maybe a best practice to dedicate your hypervisors, however, its not a must requirement (please correct me if I'm wrong).
Even when you place ESXi into maintenance mode in CS, it does not really take hypervisor into maintenance mode, it just evacuvates its VMs to other hypervisors.
Typical reasons for your problem:
1) you've changed "Management Network" port group
2) you are not using default vswitch0
(both of the above can be changed in settings)
3) you attempting to use DVS, not yet supported in 4.1, supported in 4.2
- I will release my version of ACS of 4.1 with DVS integrated as soon as 4.1 goes out.
If none of the above are true, please submit a log through paste.cloudstack.org, the exception you've posted show the end result error - but not the original cause.
Regards
ilya
> -----Original Message-----
> From: Mike Tutkowski [mailto:mike.tutkowski@solidfire.com]
> Sent: Friday, April 12, 2013 3:18 PM
> To: dev@cloudstack.apache.org
> Cc: cloudstack-dev@incubator.apache.org
> Subject: Re: Issue launching VM on VMware
>
> So, could this be the problem:
>
> In the interest of efficiency, I am running a virtual appliance with vCenter
> inside of it on one of the two ESXi hosts I'm using in CloudStack.
>
> Technically we're not supposed to have any VMs running that we're not
> started by CloudStack, right?
>
> Could this be what's causing my troubles?
>
>
> On Fri, Apr 12, 2013 at 12:56 PM, Mike Tutkowski <
> mike.tutkowski@solidfire.com> wrote:
>
> > Looks like it might be because no virtual router is running?
> >
> > 2013-04-12 12:50:27,994 DEBUG
> > [network.router.VirtualNetworkApplianceManagerImpl]
> > (RouterStatusMonitor-1:null) Found 0 routers to update status.
> > 2013-04-12 12:50:27,995 DEBUG
> > [network.router.VirtualNetworkApplianceManagerImpl]
> > (RouterStatusMonitor-1:null) Found 0 networks to update RvR status.
> > 2013-04-12 12:50:28,026 DEBUG
> > [network.router.VirtualNetworkApplianceManagerImpl]
> > (RouterStatusMonitor-1:null) Found 0 routers to update status.
> > 2013-04-12 12:50:28,027 DEBUG
> > [network.router.VirtualNetworkApplianceManagerImpl]
> > (RouterStatusMonitor-1:null) Found 0 networks to update RvR status.
> >
> > My SSVM is running, but it looks like no virtual router is.
> >
> >
> > On Fri, Apr 12, 2013 at 12:11 PM, Kelven Yang
> <ke...@citrix.com>wrote:
> >
> >> Look back from the exception in logs, this exception is the final
> >> place that throws the failure exception, the actual reason may be
> >> shown in logs earlier than this point.
> >> Kelven
> >>
> >> On 4/12/13 10:46 AM, "Mike Tutkowski" <mi...@solidfire.com>
> >> wrote:
> >>
> >> >Same problem when I try to start the VM on the local storage of
> >> >either of my ESXi hosts.
> >> >
> >> >
> >> >On Fri, Apr 12, 2013 at 11:39 AM, Mike Tutkowski <
> >> >mike.tutkowski@solidfire.com> wrote:
> >> >
> >> >> Hi,
> >> >>
> >> >> Any thoughts on this? It seems like I should have plenty of
> >> >> memory (on either of my two ESXi hosts) and plenty of storage
> >> >> space (on my iSCSI-backed VMFS datastore).
> >> >>
> >> >> Thanks!
> >> >>
> >> >> INFO [user.vm.DeployVMCmd] (Job-Executor-11:job-11) Unable to
> >> >>create a deployment for
> >> >>VM[User|5878531f-2164-48cc-b1b7-3b38e9b16b5f]
> >> >> com.cloud.exception.InsufficientServerCapacityException: Unable to
> >> >>create a deployment for
> >> >>VM[User|5878531f-2164-48cc-b1b7-3b38e9b16b5f]Scope=interface
> >> >> com.cloud.dc.DataCenter; id=1
> >> >> at
> >> >>
> >>
> >> >>org.apache.cloudstack.engine.cloud.entity.api.VMEntityManagerImpl.r
> >> >>eserve
> >> >>VirtualMachine(VMEntityManagerImpl.java:186)
> >> >> at
> >> >>
> >> >>
> >> org.apache.cloudstack.engine.cloud.entity.api.VirtualMachineEntityImp
> >> l.re
> >> >>serve(VirtualMachineEntityImpl.java:198)
> >> >> at
> >> >>
> >>
> >>
> >>com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManage
> rImp
> >> >>l.java
> >> >>:3859)
> >> >> at
> >> >>
> >>
> >>
> >>com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManage
> rImp
> >> >>l.java
> >> >>:3458)
> >> >> at
> >> >>
> >>
> >>
> >>com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManage
> rImp
> >> >>l.java
> >> >>:3444)
> >> >> at
> >> >>
> >>
> >>
> >>com.cloud.utils.component.ComponentInstantiationPostProcessor$Inter
> >> >>ceptor
> >> >>Dispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
> >> >> at
> >> >>
> >>
> >>
> >>org.apache.cloudstack.api.command.user.vm.DeployVMCmd.execute(De
> plo
> >> >>yVMCmd
> >> >>.java:379)
> >> >> at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:162)
> >> >> at
> >> >>
> >>
> >>com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.jav
> a:
> >> >>437)
> >> >> at
> >> >>java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:
> >> >>439)
> >> >> at
> >> >>java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
> >> >> at java.util.concurrent.FutureTask.run(FutureTask.java:138)
> >> >> at
> >> >>
> >>
> >>
> >>java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolEx
> >> >>ecutor
> >> >>.java:895)
> >> >> at
> >> >>
> >>
> >>
> >>java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecut
> >> >>or.jav
> >> >>a:918)
> >> >> at java.lang.Thread.run(Thread.java:680)
> >> >>
> >> >>
> >> >> --
> >> >> *Mike Tutkowski*
> >> >> *Senior CloudStack Developer, SolidFire Inc.*
> >> >> e: mike.tutkowski@solidfire.com
> >> >> o: 303.746.7302
> >> >> Advancing the way the world uses the
> >> >>cloud<http://solidfire.com/solution/overview/?video=play>
> >> >> * *
> >> >>
> >> >
> >> >
> >> >
> >> >--
> >> >*Mike Tutkowski*
> >> >*Senior CloudStack Developer, SolidFire Inc.*
> >> >e: mike.tutkowski@solidfire.com
> >> >o: 303.746.7302
> >> >Advancing the way the world uses the
> >> >cloud<http://solidfire.com/solution/overview/?video=play>
> >> >* *
> >>
> >>
> >
> >
> > --
> > *Mike Tutkowski*
> > *Senior CloudStack Developer, SolidFire Inc.*
> > e: mike.tutkowski@solidfire.com
> > o: 303.746.7302
> > Advancing the way the world uses the
> > cloud<http://solidfire.com/solution/overview/?video=play>
> > *(tm)*
> >
>
>
>
> --
> *Mike Tutkowski*
> *Senior CloudStack Developer, SolidFire Inc.*
> e: mike.tutkowski@solidfire.com
> o: 303.746.7302
> Advancing the way the world uses the
> cloud<http://solidfire.com/solution/overview/?video=play>
> *(tm)*
Re: Issue launching VM on VMware
Posted by Mike Tutkowski <mi...@solidfire.com>.
So, could this be the problem:
In the interest of efficiency, I am running a virtual appliance with
vCenter inside of it on one of the two ESXi hosts I'm using in CloudStack.
Technically we're not supposed to have any VMs running that we're not
started by CloudStack, right?
Could this be what's causing my troubles?
On Fri, Apr 12, 2013 at 12:56 PM, Mike Tutkowski <
mike.tutkowski@solidfire.com> wrote:
> Looks like it might be because no virtual router is running?
>
> 2013-04-12 12:50:27,994 DEBUG
> [network.router.VirtualNetworkApplianceManagerImpl]
> (RouterStatusMonitor-1:null) Found 0 routers to update status.
> 2013-04-12 12:50:27,995 DEBUG
> [network.router.VirtualNetworkApplianceManagerImpl]
> (RouterStatusMonitor-1:null) Found 0 networks to update RvR status.
> 2013-04-12 12:50:28,026 DEBUG
> [network.router.VirtualNetworkApplianceManagerImpl]
> (RouterStatusMonitor-1:null) Found 0 routers to update status.
> 2013-04-12 12:50:28,027 DEBUG
> [network.router.VirtualNetworkApplianceManagerImpl]
> (RouterStatusMonitor-1:null) Found 0 networks to update RvR status.
>
> My SSVM is running, but it looks like no virtual router is.
>
>
> On Fri, Apr 12, 2013 at 12:11 PM, Kelven Yang <ke...@citrix.com>wrote:
>
>> Look back from the exception in logs, this exception is the final place
>> that throws the failure exception, the actual reason may be shown in logs
>> earlier than this point.
>> Kelven
>>
>> On 4/12/13 10:46 AM, "Mike Tutkowski" <mi...@solidfire.com>
>> wrote:
>>
>> >Same problem when I try to start the VM on the local storage of either of
>> >my ESXi hosts.
>> >
>> >
>> >On Fri, Apr 12, 2013 at 11:39 AM, Mike Tutkowski <
>> >mike.tutkowski@solidfire.com> wrote:
>> >
>> >> Hi,
>> >>
>> >> Any thoughts on this? It seems like I should have plenty of memory (on
>> >> either of my two ESXi hosts) and plenty of storage space (on my
>> >> iSCSI-backed VMFS datastore).
>> >>
>> >> Thanks!
>> >>
>> >> INFO [user.vm.DeployVMCmd] (Job-Executor-11:job-11) Unable to create a
>> >> deployment for VM[User|5878531f-2164-48cc-b1b7-3b38e9b16b5f]
>> >> com.cloud.exception.InsufficientServerCapacityException: Unable to
>> >>create
>> >> a deployment for
>> >> VM[User|5878531f-2164-48cc-b1b7-3b38e9b16b5f]Scope=interface
>> >> com.cloud.dc.DataCenter; id=1
>> >> at
>> >>
>>
>> >>org.apache.cloudstack.engine.cloud.entity.api.VMEntityManagerImpl.reserve
>> >>VirtualMachine(VMEntityManagerImpl.java:186)
>> >> at
>> >>
>> >>
>> org.apache.cloudstack.engine.cloud.entity.api.VirtualMachineEntityImpl.re
>> >>serve(VirtualMachineEntityImpl.java:198)
>> >> at
>> >>
>>
>> >>com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java
>> >>:3859)
>> >> at
>> >>
>>
>> >>com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java
>> >>:3458)
>> >> at
>> >>
>>
>> >>com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java
>> >>:3444)
>> >> at
>> >>
>>
>> >>com.cloud.utils.component.ComponentInstantiationPostProcessor$Interceptor
>> >>Dispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
>> >> at
>> >>
>>
>> >>org.apache.cloudstack.api.command.user.vm.DeployVMCmd.execute(DeployVMCmd
>> >>.java:379)
>> >> at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:162)
>> >> at
>> >> com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:437)
>> >> at
>> >>java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:439)
>> >> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
>> >> at java.util.concurrent.FutureTask.run(FutureTask.java:138)
>> >> at
>> >>
>>
>> >>java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor
>> >>.java:895)
>> >> at
>> >>
>>
>> >>java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.jav
>> >>a:918)
>> >> at java.lang.Thread.run(Thread.java:680)
>> >>
>> >>
>> >> --
>> >> *Mike Tutkowski*
>> >> *Senior CloudStack Developer, SolidFire Inc.*
>> >> e: mike.tutkowski@solidfire.com
>> >> o: 303.746.7302
>> >> Advancing the way the world uses the
>> >>cloud<http://solidfire.com/solution/overview/?video=play>
>> >> * *
>> >>
>> >
>> >
>> >
>> >--
>> >*Mike Tutkowski*
>> >*Senior CloudStack Developer, SolidFire Inc.*
>> >e: mike.tutkowski@solidfire.com
>> >o: 303.746.7302
>> >Advancing the way the world uses the
>> >cloud<http://solidfire.com/solution/overview/?video=play>
>> >* *
>>
>>
>
>
> --
> *Mike Tutkowski*
> *Senior CloudStack Developer, SolidFire Inc.*
> e: mike.tutkowski@solidfire.com
> o: 303.746.7302
> Advancing the way the world uses the cloud<http://solidfire.com/solution/overview/?video=play>
> *™*
>
--
*Mike Tutkowski*
*Senior CloudStack Developer, SolidFire Inc.*
e: mike.tutkowski@solidfire.com
o: 303.746.7302
Advancing the way the world uses the
cloud<http://solidfire.com/solution/overview/?video=play>
*™*
Re: Issue launching VM on VMware
Posted by Mike Tutkowski <mi...@solidfire.com>.
Looks like it might be because no virtual router is running?
2013-04-12 12:50:27,994 DEBUG
[network.router.VirtualNetworkApplianceManagerImpl]
(RouterStatusMonitor-1:null) Found 0 routers to update status.
2013-04-12 12:50:27,995 DEBUG
[network.router.VirtualNetworkApplianceManagerImpl]
(RouterStatusMonitor-1:null) Found 0 networks to update RvR status.
2013-04-12 12:50:28,026 DEBUG
[network.router.VirtualNetworkApplianceManagerImpl]
(RouterStatusMonitor-1:null) Found 0 routers to update status.
2013-04-12 12:50:28,027 DEBUG
[network.router.VirtualNetworkApplianceManagerImpl]
(RouterStatusMonitor-1:null) Found 0 networks to update RvR status.
My SSVM is running, but it looks like no virtual router is.
On Fri, Apr 12, 2013 at 12:11 PM, Kelven Yang <ke...@citrix.com>wrote:
> Look back from the exception in logs, this exception is the final place
> that throws the failure exception, the actual reason may be shown in logs
> earlier than this point.
> Kelven
>
> On 4/12/13 10:46 AM, "Mike Tutkowski" <mi...@solidfire.com>
> wrote:
>
> >Same problem when I try to start the VM on the local storage of either of
> >my ESXi hosts.
> >
> >
> >On Fri, Apr 12, 2013 at 11:39 AM, Mike Tutkowski <
> >mike.tutkowski@solidfire.com> wrote:
> >
> >> Hi,
> >>
> >> Any thoughts on this? It seems like I should have plenty of memory (on
> >> either of my two ESXi hosts) and plenty of storage space (on my
> >> iSCSI-backed VMFS datastore).
> >>
> >> Thanks!
> >>
> >> INFO [user.vm.DeployVMCmd] (Job-Executor-11:job-11) Unable to create a
> >> deployment for VM[User|5878531f-2164-48cc-b1b7-3b38e9b16b5f]
> >> com.cloud.exception.InsufficientServerCapacityException: Unable to
> >>create
> >> a deployment for
> >> VM[User|5878531f-2164-48cc-b1b7-3b38e9b16b5f]Scope=interface
> >> com.cloud.dc.DataCenter; id=1
> >> at
> >>
> >>org.apache.cloudstack.engine.cloud.entity.api.VMEntityManagerImpl.reserve
> >>VirtualMachine(VMEntityManagerImpl.java:186)
> >> at
> >>
> >>
> org.apache.cloudstack.engine.cloud.entity.api.VirtualMachineEntityImpl.re
> >>serve(VirtualMachineEntityImpl.java:198)
> >> at
> >>
> >>com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java
> >>:3859)
> >> at
> >>
> >>com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java
> >>:3458)
> >> at
> >>
> >>com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java
> >>:3444)
> >> at
> >>
> >>com.cloud.utils.component.ComponentInstantiationPostProcessor$Interceptor
> >>Dispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
> >> at
> >>
> >>org.apache.cloudstack.api.command.user.vm.DeployVMCmd.execute(DeployVMCmd
> >>.java:379)
> >> at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:162)
> >> at
> >> com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:437)
> >> at
> >>java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:439)
> >> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
> >> at java.util.concurrent.FutureTask.run(FutureTask.java:138)
> >> at
> >>
> >>java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor
> >>.java:895)
> >> at
> >>
> >>java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.jav
> >>a:918)
> >> at java.lang.Thread.run(Thread.java:680)
> >>
> >>
> >> --
> >> *Mike Tutkowski*
> >> *Senior CloudStack Developer, SolidFire Inc.*
> >> e: mike.tutkowski@solidfire.com
> >> o: 303.746.7302
> >> Advancing the way the world uses the
> >>cloud<http://solidfire.com/solution/overview/?video=play>
> >> * *
> >>
> >
> >
> >
> >--
> >*Mike Tutkowski*
> >*Senior CloudStack Developer, SolidFire Inc.*
> >e: mike.tutkowski@solidfire.com
> >o: 303.746.7302
> >Advancing the way the world uses the
> >cloud<http://solidfire.com/solution/overview/?video=play>
> >* *
>
>
--
*Mike Tutkowski*
*Senior CloudStack Developer, SolidFire Inc.*
e: mike.tutkowski@solidfire.com
o: 303.746.7302
Advancing the way the world uses the
cloud<http://solidfire.com/solution/overview/?video=play>
*™*
Re: Issue launching VM on VMware
Posted by Kelven Yang <ke...@citrix.com>.
Look back from the exception in logs, this exception is the final place
that throws the failure exception, the actual reason may be shown in logs
earlier than this point.
Kelven
On 4/12/13 10:46 AM, "Mike Tutkowski" <mi...@solidfire.com> wrote:
>Same problem when I try to start the VM on the local storage of either of
>my ESXi hosts.
>
>
>On Fri, Apr 12, 2013 at 11:39 AM, Mike Tutkowski <
>mike.tutkowski@solidfire.com> wrote:
>
>> Hi,
>>
>> Any thoughts on this? It seems like I should have plenty of memory (on
>> either of my two ESXi hosts) and plenty of storage space (on my
>> iSCSI-backed VMFS datastore).
>>
>> Thanks!
>>
>> INFO [user.vm.DeployVMCmd] (Job-Executor-11:job-11) Unable to create a
>> deployment for VM[User|5878531f-2164-48cc-b1b7-3b38e9b16b5f]
>> com.cloud.exception.InsufficientServerCapacityException: Unable to
>>create
>> a deployment for
>> VM[User|5878531f-2164-48cc-b1b7-3b38e9b16b5f]Scope=interface
>> com.cloud.dc.DataCenter; id=1
>> at
>>
>>org.apache.cloudstack.engine.cloud.entity.api.VMEntityManagerImpl.reserve
>>VirtualMachine(VMEntityManagerImpl.java:186)
>> at
>>
>>org.apache.cloudstack.engine.cloud.entity.api.VirtualMachineEntityImpl.re
>>serve(VirtualMachineEntityImpl.java:198)
>> at
>>
>>com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java
>>:3859)
>> at
>>
>>com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java
>>:3458)
>> at
>>
>>com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java
>>:3444)
>> at
>>
>>com.cloud.utils.component.ComponentInstantiationPostProcessor$Interceptor
>>Dispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
>> at
>>
>>org.apache.cloudstack.api.command.user.vm.DeployVMCmd.execute(DeployVMCmd
>>.java:379)
>> at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:162)
>> at
>> com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:437)
>> at
>>java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:439)
>> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
>> at java.util.concurrent.FutureTask.run(FutureTask.java:138)
>> at
>>
>>java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor
>>.java:895)
>> at
>>
>>java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.jav
>>a:918)
>> at java.lang.Thread.run(Thread.java:680)
>>
>>
>> --
>> *Mike Tutkowski*
>> *Senior CloudStack Developer, SolidFire Inc.*
>> e: mike.tutkowski@solidfire.com
>> o: 303.746.7302
>> Advancing the way the world uses the
>>cloud<http://solidfire.com/solution/overview/?video=play>
>> **
>>
>
>
>
>--
>*Mike Tutkowski*
>*Senior CloudStack Developer, SolidFire Inc.*
>e: mike.tutkowski@solidfire.com
>o: 303.746.7302
>Advancing the way the world uses the
>cloud<http://solidfire.com/solution/overview/?video=play>
>**
Re: Issue launching VM on VMware
Posted by Mike Tutkowski <mi...@solidfire.com>.
Same problem when I try to start the VM on the local storage of either of
my ESXi hosts.
On Fri, Apr 12, 2013 at 11:39 AM, Mike Tutkowski <
mike.tutkowski@solidfire.com> wrote:
> Hi,
>
> Any thoughts on this? It seems like I should have plenty of memory (on
> either of my two ESXi hosts) and plenty of storage space (on my
> iSCSI-backed VMFS datastore).
>
> Thanks!
>
> INFO [user.vm.DeployVMCmd] (Job-Executor-11:job-11) Unable to create a
> deployment for VM[User|5878531f-2164-48cc-b1b7-3b38e9b16b5f]
> com.cloud.exception.InsufficientServerCapacityException: Unable to create
> a deployment for
> VM[User|5878531f-2164-48cc-b1b7-3b38e9b16b5f]Scope=interface
> com.cloud.dc.DataCenter; id=1
> at
> org.apache.cloudstack.engine.cloud.entity.api.VMEntityManagerImpl.reserveVirtualMachine(VMEntityManagerImpl.java:186)
> at
> org.apache.cloudstack.engine.cloud.entity.api.VirtualMachineEntityImpl.reserve(VirtualMachineEntityImpl.java:198)
> at
> com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:3859)
> at
> com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:3458)
> at
> com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:3444)
> at
> com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
> at
> org.apache.cloudstack.api.command.user.vm.DeployVMCmd.execute(DeployVMCmd.java:379)
> at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:162)
> at
> com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:437)
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:439)
> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
> at java.util.concurrent.FutureTask.run(FutureTask.java:138)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918)
> at java.lang.Thread.run(Thread.java:680)
>
>
> --
> *Mike Tutkowski*
> *Senior CloudStack Developer, SolidFire Inc.*
> e: mike.tutkowski@solidfire.com
> o: 303.746.7302
> Advancing the way the world uses the cloud<http://solidfire.com/solution/overview/?video=play>
> *™*
>
--
*Mike Tutkowski*
*Senior CloudStack Developer, SolidFire Inc.*
e: mike.tutkowski@solidfire.com
o: 303.746.7302
Advancing the way the world uses the
cloud<http://solidfire.com/solution/overview/?video=play>
*™*