刚刚查了一下agent的情况，应该是能看到存储的。NFS和management在一起，IP是192.168.100.55 [root@agent1 ~]# df -h Filesystem Size Used Avail Use% Mounted on /dev/mapper/vg_agent1-lv_root 50G 6.9G 40G 15% / tmpfs 1.9G 300K 1.9G 1% /dev/shm /dev/sda1 485M 34M 426M 8% /boot /dev/mapper/vg_agent1-lv_home 405G 200M 385G 1% /home 192.168.100.55:/home/storage/primary 405G 513M 384G 1% /mnt/01a375f9-e672-3ca2-b915-898dbec892f3
[root@agent1 ~]# virsh pool-list Name State Autostart ----------------------------------------- 01a375f9-e672-3ca2-b915-898dbec892f3 active no d7ec0866-46c8-4521-825e-8c99d347670b active no 2014-04-09 14:38 GMT+08:00 鲍金城 <baojc85413...@gmail.com>: > 可以试着重启一下 agent 然后查看， virsh pool-list 看看是否能够看到你的存 > 储。 > > 于 2014-04-09 14:27, Ji.Wikki 写道: > > 好的，我再尝试一下，非常感谢您的指导！ > > > > 发自我的 iPad > > > >> 在 2014年4月9日，14:21，Royal Yang <rayang2...@gmail.com> 写道： > >> > >> 可以尝试到host上看下agent日志，顺便df看下是否有nfs挂载上了 > >> 2014-4-9 下午2:15于 "Ji.Wikki" <ji.wi...@gmail.com>写道： > >> > >>> 是的，主存储也用的网络存储，物理空间应该是够的。另外，在“基础设施”中，主存储显示的是Up状态。。。所以纠结了很久，不知道到底哪里出了问题 > >>> > >>> 发自我的 iPad > >>> > >>>> 在 2014年4月9日，13:44，Royal Yang <rayang2...@gmail.com> 写道： > >>>> > >>>> 主存储也用的nfs看日志显示好像是不能获取到存储池或存储池空间不够。 > >>>> 2014-4-9 下午1:25于 "Ji.Wikki" <ji.wi...@gmail.com>写道： > >>>> > >>>>> 是在新机器上装的，应该物理资源上没有问题。已经按照安装说明导入kvm模板，显示是导入完成，在二级存储文件夹下能找到相应的模板文件 > >>>>> > >>>>> 发自我的 iPad > >>>>> > >>>>>> 在 2014年4月9日，13:01，Royal Yang <rayang2...@gmail.com> 写道： > >>>>>> > >>>>>> 导入kvm的系统虚拟机模版了吗？ > >>>>>> 2014-4-9 上午9:26于 "王吉" <ji.wi...@gmail.com>写道： > >>> > 安装环境是Cloudstack+KVM，使用网络存储模式，可以成功添加域，但之后系统虚拟机无法启动，一直显示的是stopped状态。日志显示，域已经做好启动系统VM的准备，系统VM成功转入正在启动状态，能找到合适的主机，但似乎在寻找StoragePool时出现了问题。另外，NFS可以正常读写，通过showmount命令可以找到主存储、二级存储。日志如下： > >>> > *********************************************************************************************************************************************************************************************** > >>>>>>> 2014-04-08 16:37:39,914 DEBUG > >>>>>>> [storage.secondary.SecondaryStorageManagerImpl] (secstorage-1:null) > >>>>> Zone 1 > >>>>>>> is ready to launch secondary storage VM > >>>>>>> 2014-04-08 16:37:39,915 INFO > >>>>>>> [cloud.secstorage.PremiumSecondaryStorageManagerImpl] > >>>>> (secstorage-1:null) > >>>>>>> No running secondary storage vms found in datacenter id=1, starting > >>> one > >>>>>>> 2014-04-08 16:37:39,921 INFO > >>>>>>> [storage.secondary.SecondaryStorageManagerImpl] (secstorage-1:null) > >>>>> Found > >>>>>>> a stopped secondary storage vm, bring it up to running pool. > >>>>> secStorageVm > >>>>>>> vm id : 633 > >>>>>>> 2014-04-08 16:37:39,928 DEBUG [cloud.capacity.CapacityManagerImpl] > >>>>>>> (secstorage-1:null) VM state transitted from :Stopped to Starting > with > >>>>>>> event: StartRequestedvm's original host id: null new host id: null > >>> host > >>>>> id > >>>>>>> before state transition: null > >>>>>>> 2014-04-08 16:37:39,928 DEBUG [cloud.vm.VirtualMachineManagerImpl] > >>>>>>> (secstorage-1:null) Successfully transitioned to start state for > >>>>>>> VM[SecondaryStorageVm|s-633-VM] reservation id = > >>>>>>> 1e9f3ece-0f40-4266-a975-8290c0fad486 > >>>>>>> 2014-04-08 16:37:39,990 DEBUG [cloud.vm.VirtualMachineManagerImpl] > >>>>>>> (secstorage-1:null) Trying to deploy VM, vm has dcId: 1 and podId: > >>> null > >>>>>>> 2014-04-08 16:37:39,990 DEBUG [cloud.vm.VirtualMachineManagerImpl] > >>>>>>> (secstorage-1:null) Deploy avoids pods: null, clusters: null, > hosts: > >>>>> null > >>>>>>> 2014-04-08 16:37:39,992 DEBUG > >>>>> [cloud.deploy.DeploymentPlanningManagerImpl] > >>>>>>> (secstorage-1:null) Deploy avoids pods: null, clusters: null, > hosts: > >>>>> null > >>>>>>> 2014-04-08 16:37:39,992 DEBUG > >>>>> [cloud.deploy.DeploymentPlanningManagerImpl] > >>>>>>> (secstorage-1:null) DeploymentPlanner allocation algorithm: > >>> com.cloud.deploy.FirstFitPlanner_EnhancerByCloudStack_15f9c30e@6e3091c2 > >>>>>>> 2014-04-08 16:37:39,992 DEBUG > >>>>> [cloud.deploy.DeploymentPlanningManagerImpl] > >>>>>>> (secstorage-1:null) Trying to allocate a host and storage pools > from > >>>>> dc:1, > >>>>>>> pod:null,cluster:null, requested cpu: 500, requested ram: 268435456 > >>>>>>> 2014-04-08 16:37:39,992 DEBUG > >>>>> [cloud.deploy.DeploymentPlanningManagerImpl] > >>>>>>> (secstorage-1:null) Is ROOT volume READY (pool already > allocated)?: No > >>>>>>> 2014-04-08 16:37:39,992 DEBUG [cloud.deploy.FirstFitPlanner] > >>>>>>> (secstorage-1:null) Searching all possible resources under this > Zone: > >>> 1 > >>>>>>> 2014-04-08 16:37:39,992 DEBUG [cloud.deploy.FirstFitPlanner] > >>>>>>> (secstorage-1:null) Listing clusters in order of aggregate > capacity, > >>>>> that > >>>>>>> have (atleast one host with) enough CPU and RAM capacity under this > >>>>> Zone: 1 > >>>>>>> 2014-04-08 16:37:39,995 DEBUG > >>>>> [cloud.deploy.DeploymentPlanningManagerImpl] > >>>>>>> (secstorage-1:null) Checking resources in Cluster: 1 under Pod: 1 > >>>>>>> 2014-04-08 16:37:39,995 DEBUG [allocator.impl.FirstFitAllocator] > >>>>>>> (secstorage-1:FirstFitRoutingAllocator) Looking for hosts in dc: 1 > >>>>> pod:1 > >>>>>>> cluster:1 > >>>>>>> 2014-04-08 16:37:39,996 DEBUG [allocator.impl.FirstFitAllocator] > >>>>>>> (secstorage-1:FirstFitRoutingAllocator) FirstFitAllocator has 1 > hosts > >>> to > >>>>>>> check for allocation: [Host[-1-Routing]] > >>>>>>> 2014-04-08 16:37:39,997 DEBUG [allocator.impl.FirstFitAllocator] > >>>>>>> (secstorage-1:FirstFitRoutingAllocator) Found 1 hosts for > allocation > >>>>> after > >>>>>>> prioritization: [Host[-1-Routing]] > >>>>>>> 2014-04-08 16:37:39,997 DEBUG [allocator.impl.FirstFitAllocator] > >>>>>>> (secstorage-1:FirstFitRoutingAllocator) Looking for speed=500Mhz, > >>>>> Ram=256 > >>>>>>> 2014-04-08 16:37:39,999 DEBUG [cloud.capacity.CapacityManagerImpl] > >>>>>>> (secstorage-1:FirstFitRoutingAllocator) Checking if host: 1 has > enough > >>>>>>> capacity for requested CPU: 500 and requested RAM: 268435456 , > >>>>>>> cpuOverprovisioningFactor: 1.0 > >>>>>>> 2014-04-08 16:37:40,000 DEBUG [cloud.capacity.CapacityManagerImpl] > >>>>>>> (secstorage-1:FirstFitRoutingAllocator) Hosts's actual total CPU: > >>> 13568 > >>>>> and > >>>>>>> CPU after applying overprovisioning: 13568 > >>>>>>> 2014-04-08 16:37:40,000 DEBUG [cloud.capacity.CapacityManagerImpl] > >>>>>>> (secstorage-1:FirstFitRoutingAllocator) Free CPU: 13568 , Requested > >>> CPU: > >>>>>>> 500 > >>>>>>> 2014-04-08 16:37:40,000 DEBUG [cloud.capacity.CapacityManagerImpl] > >>>>>>> (secstorage-1:FirstFitRoutingAllocator) Free RAM: 3985661952 , > >>> Requested > >>>>>>> RAM: 268435456 > >>>>>>> 2014-04-08 16:37:40,000 DEBUG [cloud.capacity.CapacityManagerImpl] > >>>>>>> (secstorage-1:FirstFitRoutingAllocator) Host has enough CPU and RAM > >>>>>>> available > >>>>>>> 2014-04-08 16:37:40,000 DEBUG [cloud.capacity.CapacityManagerImpl] > >>>>>>> (secstorage-1:FirstFitRoutingAllocator) STATS: Can alloc CPU from > >>> host: > >>>>> 1, > >>>>>>> used: 0, reserved: 0, actual total: 13568, total with > >>> overprovisioning: > >>>>>>> 13568; requested cpu:500,alloc_from_last_host?:false > >>>>>>> ,considerReservedCapacity?: true > >>>>>>> 2014-04-08 16:37:40,000 DEBUG [cloud.capacity.CapacityManagerImpl] > >>>>>>> (secstorage-1:FirstFitRoutingAllocator) STATS: Can alloc MEM from > >>> host: > >>>>> 1, > >>>>>>> used: 0, reserved: 0, total: 3985661952; requested mem: > >>>>>>> 268435456,alloc_from_last_host?:false ,considerReservedCapacity?: > true > >>>>>>> 2014-04-08 16:37:40,000 DEBUG [allocator.impl.FirstFitAllocator] > >>>>>>> (secstorage-1:FirstFitRoutingAllocator) Found a suitable host, > adding > >>> to > >>>>>>> list: 1 > >>>>>>> 2014-04-08 16:37:40,000 DEBUG [allocator.impl.FirstFitAllocator] > >>>>>>> (secstorage-1:FirstFitRoutingAllocator) Host Allocator returning 1 > >>>>> suitable > >>>>>>> hosts > >>>>>>> 2014-04-08 16:37:40,001 DEBUG > >>>>> [cloud.deploy.DeploymentPlanningManagerImpl] > >>>>>>> (secstorage-1:null) Checking suitable pools for volume (Id, Type): > >>>>>>> (633,ROOT) > >>>>>>> 2014-04-08 16:37:40,001 DEBUG > >>>>> [cloud.deploy.DeploymentPlanningManagerImpl] > >>>>>>> (secstorage-1:null) We need to allocate new storagepool for this > >>> volume > >>>>>>> 2014-04-08 16:37:40,001 DEBUG > >>>>> [cloud.deploy.DeploymentPlanningManagerImpl] > >>>>>>> (secstorage-1:null) Calling StoragePoolAllocators to find suitable > >>> pools > >>>>>>> 2014-04-08 16:37:40,001 DEBUG > >>>>> [storage.allocator.LocalStoragePoolAllocator] > >>>>>>> (secstorage-1:null) LocalStoragePoolAllocator trying to find > storage > >>>>> pool > >>>>>>> to fit the vm > >>>>>>> 2014-04-08 16:37:40,002 DEBUG > >>>>> [storage.allocator.LocalStoragePoolAllocator] > >>>>>>> (secstorage-1:null) LocalStoragePoolAllocator returning 0 suitable > >>>>> storage > >>>>>>> pools > >>>>>>> 2014-04-08 16:37:40,002 DEBUG > >>>>>>> [storage.allocator.ClusterScopeStoragePoolAllocator] > >>> (secstorage-1:null) > >>>>>>> ClusterScopeStoragePoolAllocator looking for storage pool > >>>>>>> 2014-04-08 16:37:40,002 DEBUG > >>>>>>> [storage.allocator.ZoneWideStoragePoolAllocator] > (secstorage-1:null) > >>>>>>> ZoneWideStoragePoolAllocator to find storage pool > >>>>>>> 2014-04-08 16:37:40,002 DEBUG > >>>>> [cloud.deploy.DeploymentPlanningManagerImpl] > >>>>>>> (secstorage-1:null) No suitable pools found for volume: > >>>>>>> Vol[633|vm=633|ROOT] under cluster: 1 > >>>>>>> 2014-04-08 16:37:40,002 DEBUG > >>>>> [cloud.deploy.DeploymentPlanningManagerImpl] > >>>>>>> (secstorage-1:null) No suitable pools found > >>>>>>> 2014-04-08 16:37:40,002 DEBUG > >>>>> [cloud.deploy.DeploymentPlanningManagerImpl] > >>>>>>> (secstorage-1:null) No suitable storagePools found under this > >>> Cluster: 1 > >>>>>>> 2014-04-08 16:37:40,002 DEBUG > >>>>> [cloud.deploy.DeploymentPlanningManagerImpl] > >>>>>>> (secstorage-1:null) Could not find suitable Deployment Destination > for > >>>>> this > >>>>>>> VM under any clusters, returning. > >>>>>>> 2014-04-08 16:37:40,002 DEBUG [cloud.deploy.FirstFitPlanner] > >>>>>>> (secstorage-1:null) Searching all possible resources under this > Zone: > >>> 1 > >>>>>>> 2014-04-08 16:37:40,003 DEBUG [cloud.deploy.FirstFitPlanner] > >>>>>>> (secstorage-1:null) Listing clusters in order of aggregate > capacity, > >>>>> that > >>>>>>> have (atleast one host with) enough CPU and RAM capacity under this > >>>>> Zone: 1 > >>>>>>> 2014-04-08 16:37:40,004 DEBUG [cloud.deploy.FirstFitPlanner] > >>>>>>> (secstorage-1:null) Removing from the clusterId list these clusters > >>> from > >>>>>>> avoid set: [1] > >>>>>>> 2014-04-08 16:37:40,004 DEBUG [cloud.deploy.FirstFitPlanner] > >>>>>>> (secstorage-1:null) No clusters found after removing disabled > clusters > >>>>> and > >>>>>>> clusters in avoid list, returning. > >>>>>>> 2014-04-08 16:37:40,153 DEBUG [cloud.capacity.CapacityManagerImpl] > >>>>>>> (secstorage-1:null) VM state transitted from :Starting to Stopped > with > >>>>>>> event: OperationFailedvm's original host id: null new host id: null > >>>>> host id > >>>>>>> before state transition: null > >>>>>>> 2014-04-08 16:37:40,154 WARN > >>>>>>> [storage.secondary.SecondaryStorageManagerImpl] (secstorage-1:null) > >>>>>>> Exception while trying to start secondary storage vm > >>>>>>> com.cloud.exception.InsufficientServerCapacityException: Unable to > >>>>> create a > >>>>>>> deployment for VM[SecondaryStorageVm|s-633-VM]Scope=interface > >>>>>>> com.cloud.dc.DataCenter; id=1 > >>>>>>> at > >>> > com.cloud.vm.VirtualMachineManagerImpl.advanceStart(VirtualMachineManagerImpl.java:841) > >>>>>>> at > >>> > com.cloud.vm.VirtualMachineManagerImpl.start(VirtualMachineManagerImpl.java:577) > >>>>>>> at > >>> > com.cloud.vm.VirtualMachineManagerImpl.start(VirtualMachineManagerImpl.java:570) > >>>>>>> at > >>> > com.cloud.storage.secondary.SecondaryStorageManagerImpl.startSecStorageVm(SecondaryStorageManagerImpl.java:267) > >>>>>>> at > >>> > com.cloud.storage.secondary.SecondaryStorageManagerImpl.allocCapacity(SecondaryStorageManagerImpl.java:696) > >>>>>>> at > >>> > com.cloud.storage.secondary.SecondaryStorageManagerImpl.expandPool(SecondaryStorageManagerImpl.java:1300) > >>>>>>> at > >>> > com.cloud.secstorage.PremiumSecondaryStorageManagerImpl.scanPool(PremiumSecondaryStorageManagerImpl.java:123) > >>>>>>> at > >>> > com.cloud.secstorage.PremiumSecondaryStorageManagerImpl.scanPool(PremiumSecondaryStorageManagerImpl.java:50) > >>>>>>> at > >>>>> > com.cloud.vm.SystemVmLoadScanner.loadScan(SystemVmLoadScanner.java:104) > >>>>>>> at > >>>>> > com.cloud.vm.SystemVmLoadScanner.access$100(SystemVmLoadScanner.java:33) > >>>>>>> at > >>> > com.cloud.vm.SystemVmLoadScanner$1.reallyRun(SystemVmLoadScanner.java:81) > >>>>>>> at > com.cloud.vm.SystemVmLoadScanner$1.run(SystemVmLoadScanner.java:72) > >>>>>>> at > >>>>> > java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) > >>>>>>> at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:304) > >>>>>>> at > >>> > java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:178) > >>>>>>> at > >>> > java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293) > >>>>>>> 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-04-08 16:37:40,155 INFO > >>>>>>> [storage.secondary.SecondaryStorageManagerImpl] (secstorage-1:null) > >>>>> Unable > >>>>>>> to start secondary storage vm for standby capacity, secStorageVm vm > >>> Id : > >>>>>>> 633, will recycle it and start a new one > >>>>>>> 2014-04-08 16:37:40,157 DEBUG [cloud.vm.VirtualMachineManagerImpl] > >>>>>>> (secstorage-1:null) VM is already stopped: > >>>>> VM[SecondaryStorageVm|s-633-VM] > >>> > *********************************************************************************************************************************************************************************************** > >>>>>>> 这个问题困扰我很多天了，一直无法解决，烦请哪位大牛可以关注下，万分感谢！ > >
