Console Proxy Starts but SSVM stuck in start loop

[Josh Davis <cl...@outlook.com>]

Hello all,
SSVM keeps trying to start on both hosts but CP starts fine. 
Have a gut feeling it's because I'm running the storage network over a VLAN and I configured the network wrongly or something. Here's what I've done:
1. Physical network is named "cloud_storage_link"2. Created an interface for VLAN 999 named "cloud_storage_vlan"3. Add an IP for the XS Host under "cloud_storage_vlan"4. In Advanced Network settings I put the label "cloud_storage_vlan" under the tag
Should I have put the name of the physical network instead? I can't ping the SAN if I put the IP on the physical network (SAN is on VLAN 999). Also, if I don't create "cloud_storage_vlan" to assign an IP it seems that CS is unable to add the primary storage to the zone.
I could technically make the ports on the switch to untagged on VLAN 999 as they are dedicated ports just for the primary storage network but I would like not to tear down the config yet if it can be salvaged.
Thanks in advance!
Excerpt from log:
2016-06-11 11:42:40,394 INFO  [c.c.v.VirtualMachineManagerImpl] (Work-Job-Executor-7:ctx-0cc2dd06 job-173/job-185 ctx-33a98c91) (logid:7c0ce39b) Unable to start VM on Host[-3-Routing] due to Unable to start s-20-VM due to2016-06-11 11:42:40,581 DEBUG [c.c.c.CapacityManagerImpl] (Work-Job-Executor-7:ctx-0cc2dd06 job-173/job-185 ctx-33a98c91) (logid:7c0ce39b) VM state transitted from :Starting to Stopped with event: OperationFailedvm's original host id: null new host id: null host id before state transition: 32016-06-11 11:42:40,597 ERROR [c.c.v.VmWorkJobHandlerProxy] (Work-Job-Executor-7:ctx-0cc2dd06 job-173/job-185 ctx-33a98c91) (logid:7c0ce39b) Invocation exception, caused by: com.cloud.exception.InsufficientServerCapacityException: Unable to create a deployment for VM[SecondaryStorageVm|s-20-VM]Scope=interface com.cloud.dc.DataCenter; id=32016-06-11 11:42:40,598 INFO  [c.c.v.VmWorkJobHandlerProxy] (Work-Job-Executor-7:ctx-0cc2dd06 job-173/job-185 ctx-33a98c91) (logid:7c0ce39b) Rethrow exception com.cloud.exception.InsufficientServerCapacityException: Unable to create a deployment for VM[SecondaryStorageVm|s-20-VM]Scope=interface com.cloud.dc.DataCenter; id=32016-06-11 11:42:40,598 ERROR [c.c.v.VmWorkJobDispatcher] (Work-Job-Executor-7:ctx-0cc2dd06 job-173/job-185) (logid:7c0ce39b) Unable to complete AsyncJobVO {id:185, userId: 1, accountId: 1, instanceType: null, instanceId: null, cmd: com.cloud.vm.VmWorkStart, cmdInfo: 
 		 	   		  

Re: Console Proxy Starts but SSVM stuck in start loop

[Marc-Andre Jutras <ma...@marcuspocus.com>]

There's probably another message before this one saying that CS cannot 
find a specific interface on Xen...

Make sure your name that you configure in CS match what's in XenServer...


On 2016-06-11 12:19 AM, Josh Davis wrote:
> Invocation exception, caused by: com.cloud.exception.InsufficientServerCapacityException: Unable to create a deployment for VM[SecondaryStorageVm|s-20-VM]Scope=interface com.cloud.dc.DataCenter; id=32016-06-11 11:42:40,598 INFO  [c.c.v.VmWorkJobHandlerProxy] (Work-Job-Executor-7:ctx-0cc2dd06 job-173/job-185 ctx-33a98c91) (logid:7c0ce39b) Rethrow exception com.cloud.exception.InsufficientServerCapacityException: Unable to create a deployment for VM[SecondaryStorageVm|s-20-VM]Scope=interface com.cloud.dc.DataCenter;