【已解决】cloudstack 系统VM无法启动,二级存储容量为0

问题描述
==========================

最近部署了一个cloudstack环境  操作系统linux6.4,主机xenserver 4cpu 8G内存,创建并启动zone之后发现二级存储容量为0,两个系统VM状态stopped并且无法正常启动,下面是management-server的log

环境描述
==========================

CloudStack 4.4.2
XenServer 6.0.2
linux 6.4
区域类型xenserver,网络全部用的内网同网段IP,主存储二级存储全部用的nfs代替 主存储40G 二级存储110G,主存储能附加并显示大小,二级存储容量为0
日志文件所在网盘地址:http://pan.baidu.com/s/1c02M6tE

QQ图片20150701151852.png

错误日志
==========================
ps:感谢ak_qq,2020human两位大神的悉心指导,最后问题的解决离不开二位大神。
 问题分析:1.最开始我的系统VM 启动失败,确实如两位大神所说的我即开启了使用本地存储的选项,又是使用的nfs模拟存储,导致系统VM找不到存储,无法创建,而后出现的starting后自动删除的问题,我估计与版本兼容性有关,我使用的是cloudstack二次开发版本,刚开始的xenserver为6.0.2安装CSP补丁包失败,关闭了ovs,上传了vhd-util,最终实验结果失败,后来重新安装了xenserver6.2,按照原先步骤,成功搭建环境,人生有涯而学海无涯,与诸君共勉
 
已邀请:

2020human

赞同来自: ak_qq 玉子

No suitable pools found for volume: Vol[38|vm=38|ROOT] under cluster: 1
 
可能你的NFS存储不能挂载到指定的目录,查看xen的SR是否正常

ak_qq

赞同来自: 601373142

同 2020human。

仔细分析你的日志:
2015-07-01 15:40:10,704 DEBUG [allocator.impl.FirstFitAllocator] (consoleproxy-1:FirstFitRoutingAllocator) Found a suitable host, adding to list: 1
2015-07-01 15:40:10,704 DEBUG [allocator.impl.FirstFitAllocator] (consoleproxy-1:FirstFitRoutingAllocator) Host Allocator returning 1 suitable hosts
2015-07-01 15:40:10,706 DEBUG [cloud.deploy.DeploymentPlanningManagerImpl] (consoleproxy-1:null) Checking suitable pools for volume (Id, Type): (2,ROOT)
2015-07-01 15:40:10,706 DEBUG [cloud.deploy.DeploymentPlanningManagerImpl] (consoleproxy-1:null) We need to allocate new storagepool for this volume
2015-07-01 15:40:10,706 DEBUG [cloud.deploy.DeploymentPlanningManagerImpl] (consoleproxy-1:null) Calling StoragePoolAllocators to find suitable pools
2015-07-01 15:40:10,707 DEBUG [storage.allocator.LocalStoragePoolAllocator] (consoleproxy-1:null) LocalStoragePoolAllocator trying to find storage pool to fit the vm
2015-07-01 15:40:10,710 DEBUG [storage.allocator.LocalStoragePoolAllocator] (consoleproxy-1:null) LocalStoragePoolAllocator returning 0 suitable storage pools
2015-07-01 15:40:10,710 DEBUG [storage.allocator.ClusterScopeStoragePoolAllocator] (consoleproxy-1:null) ClusterScopeStoragePoolAllocator looking for storage pool
2015-07-01 15:40:10,710 DEBUG [storage.allocator.ZoneWideStoragePoolAllocator] (consoleproxy-1:null) ZoneWideStoragePoolAllocator to find storage pool
2015-07-01 15:40:10,710 DEBUG [cloud.deploy.DeploymentPlanningManagerImpl] (consoleproxy-1:null) No suitable pools found for volume: Vol[2|vm=2|ROOT] under cluster: 1
2015-07-01 15:40:10,710 DEBUG [cloud.deploy.DeploymentPlanningManagerImpl] (consoleproxy-1:null) No suitable pools found
2015-07-01 15:40:10,710 DEBUG [cloud.deploy.DeploymentPlanningManagerImpl] (consoleproxy-1:null) No suitable storagePools found under this Cluster: 1
2015-07-01 15:40:10,713 DEBUG [cloud.deploy.DeploymentPlanningManagerImpl] (consoleproxy-1:null) Could not find suitable Deployment Destination for this VM under any clusters, returning.
2015-07-01 15:40:10,713 DEBUG [cloud.deploy.FirstFitPlanner] (consoleproxy-1:null) Searching all possible resources under this Zone: 1
2015-07-01 15:40:10,714 DEBUG [cloud.deploy.FirstFitPlanner] (consoleproxy-1:null) Listing clusters in order of aggregate capacity, that have (atleast one host with) enough CPU and RAM capacity under this Zone: 1
2015-07-01 15:40:10,718 DEBUG [cloud.deploy.FirstFitPlanner] (consoleproxy-1:null) Removing from the clusterId list these clusters from avoid set: [1]
2015-07-01 15:40:10,718 DEBUG [cloud.deploy.FirstFitPlanner] (consoleproxy-1:null) No clusters found after removing disabled clusters and clusters in avoid list, returning.
2015-07-01 15:40:10,858 DEBUG [cloud.capacity.CapacityManagerImpl] (consoleproxy-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
2015-07-01 15:40:10,862 WARN [cloud.consoleproxy.ConsoleProxyManagerImpl] (consoleproxy-1:null) Exception while trying to start console proxy
com.cloud.exception.InsufficientServerCapacityException: Unable to create a deployment for VM[ConsoleProxy|v-2-VM]Scope=interface com.cloud.dc.DataCenter; id=1
at com.cloud.vm.VirtualMachineManagerImpl.advanceStart(VirtualMachineManagerImpl.java:841)
其中关于:

2015-07-01 15:40:10,710 DEBUG [storage.allocator.ClusterScopeStoragePoolAllocator] (consoleproxy-1:null) ClusterScopeStoragePoolAllocator looking for storage pool
2015-07-01 15:40:10,710 DEBUG [storage.allocator.ZoneWideStoragePoolAllocator] (consoleproxy-1:null) ZoneWideStoragePoolAllocator to find storage pool
2015-07-01 15:40:10,710 DEBUG [cloud.deploy.DeploymentPlanningManagerImpl] (consoleproxy-1:null) No suitable pools found for volume: Vol[2|vm=2|ROOT] under cluster: 1
2015-07-01 15:40:10,710 DEBUG [cloud.deploy.DeploymentPlanningManagerImpl] (consoleproxy-1:null) No suitable pools found
2015-07-01 15:40:10,710 DEBUG [cloud.deploy.DeploymentPlanningManagerImpl] (consoleproxy-1:null) No suitable storagePools found under this Cluster: 1


找不到合适的主存储。

1.检测nfs主存储是否可以在xs主机中挂载,并正常写入文件。
2.确保nfs安全设置中,运行xs主机的ip网段。
3.确保主存储未加入任何tag。
 

ak_qq

赞同来自:

麻烦把 管理端日志以附件形式上传上来,如果日志过大,请存放到网盘中,贴出链接。
另外,系统虚拟机无法启动,与区域类型,网络,存储等都有关系,所以请尽可能详细,详细,详细(重要的事情说三遍)的描述你的环境。

玉子

赞同来自:

区域类型xenserver,网络全部用的内网同网段IP,主存储二级存储全部用的nfs代替 主存储40G 二级存储110G,主存储能附加并显示大小,二级存储容量为0
日志文件所在网盘地址:http://pan.baidu.com/s/1c02M6tE

要回复问题请先登录注册