回复: cs+vmware 无法添加vmfs存储

2014-08-13 文章
官方cs文档:vsphere FC 或者 iSCSI的配置部分
For vSphere choose either VMFS (iSCSI or FiberChannel)‍

Server. The IP address or DNS name of the vCenter server.
Path. A combination of the datacenter name and
the datastore name. The format is / datacenter
name / datastore name. For example,
/cloud.dc.VM/cluster1datastore.

我感觉是不是 你的vCenter 主机名字格式和cs 的不兼容啊,怎么还有“/APAC+Cloud/Cloud-Primary‍” 为啥要用+好呢



-- 原始邮件 --
发件人: Darren Tang;d‍arrentang...@gmail.com;
发送时间: 2014年8月14日(星期四) 上午10:06
收件人: users-cnusers-cn@cloudstack.apache.org; 

主题: Re: cs+vmware 无法添加vmfs存储



添加nfs作为主存储,只需要在CS中操作一次即可。无需在VC中再次添加。
添加vmfs作为主存储时,需要在VC和CS中各添加一次。



2014-08-13 10:57 GMT+08:00 ma y breeze7...@gmail.com:

 存储在vsphere里面添加完成后,CS是自动发现的


 2014-08-13 10:32 GMT+08:00 Mr.博 289254...@qq.com:

  各位好:
我用CS4.3+vsphere搭建的环境,添加vmfs作为主存储的时候报错,nfs存储就可以添加成功。请各位高手帮忙看一下是什么问题。
  日志报错如下:
 
 
  华丽丽的分割线——
 
 
 
 
  2014-08-13 10:12:59,324 INFO  [c.c.h.v.r.VmwareResource]
  (DirectAgent-160:ctx-17f5a494 10.181.37.18) Executing resource
  ModifyStoragePoolCommand:
 
 {add:true,pool:{id:7,uuid:f3ddd813-7022-339f-85e9-e0c002723836,host:VMFS
  datastore:
 
 /APAC+Cloud/Cloud-Primary,path:/APAC+Cloud/Cloud-Primary,port:0,type:VMFS},localPath:/mnt//40e1b1df-08e2-37ab-9888-613b2fb38732,wait:0}
  2014-08-13 10:12:59,355 DEBUG [c.c.a.m.DirectAgentAttache]
  (DirectAgent-7:ctx-da779050) Seq 1-1512640205: Response Received:
  2014-08-13 10:12:59,355 DEBUG [c.c.a.t.Request]
  (StatsCollector-1:ctx-798b1475) Seq 1-1512640205: Received:  { Ans: ,
  MgmtId: 345052609028, via: 1, Ver: v1, Flags: 10, { GetVmStatsAnswer } }
  2014-08-13 10:12:59,451 ERROR [c.c.h.v.m.DatacenterMO]
  (DirectAgent-160:ctx-17f5a494 10.181.37.18) Unable to locate DC
 APAC+Cloud
  2014-08-13 10:12:59,457 ERROR [c.c.h.v.u.VmwareContext]
  (DirectAgent-160:ctx-17f5a494 10.181.37.18) Unable to locate the
 datacenter
  specified in path: /APAC+Cloud/Cloud-Primary
  2014-08-13 10:12:59,457 ERROR [c.c.h.v.m.HostMO]
  (DirectAgent-160:ctx-17f5a494 10.181.37.18) Unable to create VMFS
  datastore. host: VMFS datastore: /APAC+Cloud/Cloud-Primary, port: 0,
 path:
  /APAC+Cloud/Cloud-Primary, uuid: f3ddd8137022339f85e9e0c002723836
  2014-08-13 10:12:59,457 ERROR [c.c.h.v.r.VmwareResource]
  (DirectAgent-160:ctx-17f5a494 10.181.37.18) ModifyStoragePoolCommand
 failed
  due to Exception: java.lang.Exception
  Message: Unable to create VMFS datastore. host: VMFS datastore:
  /APAC+Cloud/Cloud-Primary, port: 0, path: /APAC+Cloud/Cloud-Primary,
 uuid:
  f3ddd8137022339f85e9e0c002723836
 
  java.lang.Exception: Unable to create VMFS datastore. host: VMFS
  datastore: /APAC+Cloud/Cloud-Primary, port: 0, path:
  /APAC+Cloud/Cloud-Primary, uuid: f3ddd8137022339f85e9e0c002723836
  at com.cloud.hypervisor.vmware.mo.HostMO.mountDatastore(HostMO.java:853)
  at
 
 com.cloud.hypervisor.vmware.resource.VmwareResource.execute(VmwareResource.java:4818)
  at
 
 com.cloud.hypervisor.vmware.resource.VmwareResource.executeRequest(VmwareResource.java:536)
  at
 
 com.cloud.agent.manager.DirectAgentAttache$Task.runInContext(DirectAgentAttache.java:215)
  at
 
 org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:50)
  at
 
 org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56)
  at
 
 org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103)
  at
 
 org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53)
  at
 
 org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:47)
  at
 java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
  at java.util.concurrent.FutureTask.run(FutureTask.java:262)
  at
 
 java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:178)
  at
 
 java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:292)
  at
 
 java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
  at
 
 java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
  at java.lang.Thread.run(Thread.java:744)
  2014-08-13 10:12:59,458 DEBUG [c.c.a.m.DirectAgentAttache]
  (DirectAgent-160:ctx-17f5a494) Seq 1-1512640207: Response Received:
  2014-08-13 10:12:59,458 DEBUG [c.c.a.t.Request]
  (DirectAgent-160:ctx-17f5a494) Seq 1-1512640207: Processing:  { Ans: ,
  MgmtId: 345052609028, via: 1, Ver: v1, Flags: 10,
 
 [{com.cloud.agent.api.Answer:{result:false,details:ModifyStoragePoolCommand
  failed due to Exception: java.lang.Exception\nMessage: Unable to create
  VMFS datastore. host: VMFS datastore: /APAC+Cloud/Cloud-Primary, port: 0,
  path: /APAC+Cloud/Cloud-Primary, uuid:
  f3ddd8137022339f85e9e0c002723836\n,wait:0}}] }
  2014-08-13 10:12:59,458 DEBUG [c.c.a.t.Request]
  

回复:vm迁移实体机状态问题

2014-07-10 文章
十台实体机的配置一样吗? 
vm迁移只能在同一个集群迁移 ,同一个集群主机配置最好一样 主要是CPU 类型相同





-- 原始邮件 --
发件人: 虚无缥缈;83675...@qq.com;
发送时间: 2014年7月11日(星期五) 中午11:35
收件人: users-cnusers-cn@cloudstack.apache.org; 

主题: vm迁移实体机状态问题



一共10台实体机,vm迁移有个实体机显示not suitable,有点实体机显示suitable,请问显示not 
suitable状态的原因,怎么查找,实体机负载都很低,刚刚建立,vm一共20左右。存储使用sharemountpoint.‍‍