回复: 回复： cloudstack删除VM主存储空间不释放
删除虚拟机默认还会保留86400秒，修改expunge.delay 和expunge.interval 参数，将时间设置短些，重启服务生效就会很快释放了 ganglin_lan From: 刘宝刚 Date: 2014-05-20 09:35 To: users-cn; users-cn Subject: 回复： cloudstack删除VM主存储空间不释放 我们是通过cloudstack界面删除，但是空间还没有降下来 -- 原始邮件 -- 发件人: linux...@gmail.comlinux...@gmail.com; 发送时间: 2014年5月20日(星期二) 上午9:31 收件人: users-cnusers-cn@cloudstack.apache.org; 主题: Re: cloudstack删除VM主存储空间不释放 建议你通过cloudstack界面进行删除，通过xencenter删除时，cloudstack不知道VM被删除，相应的数据库的表的值当然不会发生变化 在 2014年5月16日 下午12:01，刘宝刚 793249...@qq.com写道： cloudstack提示存储空间不足，告警百分之九十，在xencenter删除VM，cloudstack主存储不释放空间。 -- 白清杰 (Born Bai) 北京开源愿景信息技术有限公司 Mail: linux...@gmail.com
回复: 回复： cloudstack删除VM主存储空间不释放
从ui上还能看到被删除的虚拟机吗，从卷里面能看到被删除虚拟机的卷信息吗 ganglin_lan From: 刘宝刚 Date: 2014-05-20 09:50 To: users-cn@cloudstack.apache.orgganglin_lan; users-cn Subject: 回复： 回复： cloudstack删除VM主存储空间不释放 那两个参数都已经改成600秒了。还是没用 -- 原始邮件 -- 发件人: ganglin_langanglin_...@tcloudcomputing.com; 发送时间: 2014年5月20日(星期二) 上午9:47 收件人: users-cnusers-cn@cloudstack.apache.org; 主题: 回复: 回复： cloudstack删除VM主存储空间不释放 删除虚拟机默认还会保留86400秒，修改expunge.delay 和expunge.interval 参数，将时间设置短些，重启服务生效就会很快释放了 ganglin_lan From: 刘宝刚 Date: 2014-05-20 09:35 To: users-cn; users-cn Subject: 回复： cloudstack删除VM主存储空间不释放 我们是通过cloudstack界面删除，但是空间还没有降下来 -- 原始邮件 -- 发件人: linux...@gmail.comlinux...@gmail.com; 发送时间: 2014年5月20日(星期二) 上午9:31 收件人: users-cnusers-cn@cloudstack.apache.org; 主题: Re: cloudstack删除VM主存储空间不释放 建议你通过cloudstack界面进行删除，通过xencenter删除时，cloudstack不知道VM被删除，相应的数据库的表的值当然不会发生变化 在 2014年5月16日 下午12:01，刘宝刚 793249...@qq.com写道： cloudstack提示存储空间不足，告警百分之九十，在xencenter删除VM，cloudstack主存储不释放空间。 -- 白清杰 (Born Bai) 北京开源愿景信息技术有限公司 Mail: linux...@gmail.com
回复: 回复： cloudstack删除VM主存储空间不释放
你是不是从xenserver上直接删过，这样会有问题 ganglin_lan From: 刘宝刚 Date: 2014-05-20 12:05 To: users-cn@cloudstack.apache.orgganglin_lan; users-cn Subject: 回复： 回复： cloudstack删除VM主存储空间不释放 ui上没有了，卷里面也看不到了。 -- 原始邮件 -- 发件人: users...@cloudstack.apache.orggganglin_...@tcloudcomputing.com; 发送时间: 2014年5月20日(星期二) 上午10:06 收件人: users-cnusers-cn@cloudstack.apache.org; 主题: 回复: 回复： cloudstack删除VM主存储空间不释放 从ui上还能看到被删除的虚拟机吗，从卷里面能看到被删除虚拟机的卷信息吗 ganglin_lan From: 刘宝刚 Date: 2014-05-20 09:50 To: users-cn@cloudstack.apache.orgganglin_lan; users-cn Subject: 回复： 回复： cloudstack删除VM主存储空间不释放 那两个参数都已经改成600秒了。还是没用 -- 原始邮件 -- 发件人: ganglin_langanglin_...@tcloudcomputing.com; 发送时间: 2014年5月20日(星期二) 上午9:47 收件人: users-cnusers-cn@cloudstack.apache.org; 主题: 回复: 回复： cloudstack删除VM主存储空间不释放 删除虚拟机默认还会保留86400秒，修改expunge.delay 和expunge.interval 参数，将时间设置短些，重启服务生效就会很快释放了 ganglin_lan From: 刘宝刚 Date: 2014-05-20 09:35 To: users-cn; users-cn Subject: 回复： cloudstack删除VM主存储空间不释放 我们是通过cloudstack界面删除，但是空间还没有降下来 -- 原始邮件 -- 发件人: linux...@gmail.comlinux...@gmail.com; 发送时间: 2014年5月20日(星期二) 上午9:31 收件人: users-cnusers-cn@cloudstack.apache.org; 主题: Re: cloudstack删除VM主存储空间不释放 建议你通过cloudstack界面进行删除，通过xencenter删除时，cloudstack不知道VM被删除，相应的数据库的表的值当然不会发生变化 在 2014年5月16日 下午12:01，刘宝刚 793249...@qq.com写道： cloudstack提示存储空间不足，告警百分之九十，在xencenter删除VM，cloudstack主存储不释放空间。 -- 白清杰 (Born Bai) 北京开源愿景信息技术有限公司 Mail: linux...@gmail.com
Re: 答复: 二级存储丢失
cloudstack高可用可以配置cloudstack slave 服务器，正常安装cloudstack，初始化数据库时，不要用--deploy-as参数，这样两个cloudstack就可以同时管理了，当然前面还可以加个ngiinx之类的做负载均衡，重点是mysql数据库要做主从 ganglin_lan 发件人： 许叁征 发送时间： 2014-04-17 16:02 收件人： users-cn@cloudstack.apache.org 主题： 答复: 答复: 二级存储丢失 Hi linuxbqj 故障修复过程，北京-steelen会发布一个恢复过程到社区里面哈，另外后面发现服务器硬盘坏了，现在又要开始迁移的过程恢复数据了。。 对了，想问大家一个问题，如何做高可用的cloudstack，就是说一台cloudstac k主机宕机机了，另一台备机cloudstac k仍能工作。 目前cloudstack能做到吗？如果有，可有推荐的解决方案链接。。求解。谢谢 -邮件原件- 发件人: users-cn-return-3491-xusz=chinanetcenter@cloudstack.apache.org [mailto:users-cn-return-3491-xusz=chinanetcenter@cloudstack.apache.org] 代表 linux...@gmail.com 发送时间: 2014年4月16日星期三 15:11 收件人: users-cn@cloudstack.apache.org 主题: Re: 答复: 二级存储丢失 hey 叁征，是否可以把你的解决过程整理一个文章发布到社区网站呢 2014-04-16 14:12 GMT+08:00 Royal Yang rayang2...@gmail.com: 添加一个服务方案，勾选高可用，将虚拟机的服务方案更改为这个新建的方案。当host故障的时候应用此方案的虚拟机就能自动启动了 2014-04-16 13:23 GMT+08:00 许叁征 x...@chinanetcenter.com: 二级存储是使用NFS的，后面经“北京-steelen”的协助支持下，启用本地存储后经相应检查后，虚拟机多数可以启动了。在这里面要特别感谢下steelen，来到厦门的时候，记得告诉我，请你吃大餐以表心意， 目前有两个问题，在平时中一直困扰的。 1.使用两台XENserver为一个pool集群后，xenserver,有自时它会自动在XEN面板上变红色图标，然后节点会自动消失，一台xenserver 就会ping不通掉，看起来是机器在重启了。这样就造成虚拟机也瞬间停止运行了。。隔了2分钟后，它会可能会自动加载成同一个pool。 1.1想问下各位，造成这个问题的原因是什么，如何处理？ 1.2 如何在节点故障恢复后，虚拟机也能自动启动起来免人工手动启动。 谢谢大家了。 -邮件原件- 发件人: users-cn-return-3485-xusz=chinanetcenter@cloudstack.apache.org[mailto: users-cn-return-3485-xusz=chinanetcenter@cloudstack.apache.org] 代表 linux...@gmail.com 发送时间: 2014年4月16日星期三 7:49 收件人: users-cn@cloudstack.apache.org 主题: Re: 二级存储丢失 二级存储是使用的iscsi还是NFS呢？ 二级存储手动挂载有没有问题？看日志，分析是二级存储挂载不上 2014-04-15 10:18 GMT+08:00 许叁征 x...@chinanetcenter.com: HI ALL 最近一节点因为innode文件满了，造成虚拟机挺止，修复好节点却发现虚拟机无法启动， 环境：CS4.0.1 +XENSERVER。 添加了XEN主存储还是不能启动虚拟机。 2014-04-15 10:12:48,114 DEBUG [storage.allocator.LocalStoragePoolAllocator] (secstorage-1:null) Unable to find storage pool to fit the vm 2014-04-15 10:12:48,114 DEBUG [cloud.deploy.FirstFitPlanner] (secstorage-1:null) No suitable pools found for volume: Vol[67635|vm=67556|ROOT] under cluster: 20 2014-04-15 10:12:48,114 DEBUG [cloud.deploy.FirstFitPlanner] (secstorage-1:null) No suitable pools found 2014-04-15 10:12:48,114 DEBUG [cloud.deploy.FirstFitPlanner] (secstorage-1:null) No suitable storagePools found under this Cluster: 20 2014-04-15 10:12:48,115 DEBUG [cloud.deploy.FirstFitPlanner] (secstorage-1:null) Checking resources in Cluster: 1 under Pod: 1 2014-04-15 10:12:48,115 DEBUG [cloud.deploy.FirstFitPlanner] (secstorage-1:null) Calling HostAllocators to find suitable hosts 2014-04-15 10:12:48,115 DEBUG [allocator.impl.FirstFitAllocator] (secstorage-1:FirstFitRoutingAllocator) Looking for hosts in dc: 1 pod:1 cluster:1 2014-04-15 10:12:48,117 DEBUG [allocator.impl.FirstFitAllocator] (secstorage-1:FirstFitRoutingAllocator) FirstFitAllocator has 1 hosts to check for allocation: [Host[-68-Routing]] 2014-04-15 10:12:48,119 DEBUG [allocator.impl.FirstFitAllocator] (secstorage-1:FirstFitRoutingAllocator) Found 1 hosts for allocation after prioritization: [Host[-68-Routing]] 2014-04-15 10:12:48,119 DEBUG [allocator.impl.FirstFitAllocator] (secstorage-1:FirstFitRoutingAllocator) Looking for speed=500Mhz, Ram=256 2014-04-15 10:12:48,120 DEBUG [cloud.capacity.CapacityManagerImpl] (secstorage-1:FirstFitRoutingAllocator) Checking if host: 68 has enough capacity for requested CPU: 500 and requested RAM: 268435456 , cpuOverprovisioningFactor: 6.0 2014-04-15 10:12:48,122 DEBUG [cloud.capacity.CapacityManagerImpl] (secstorage-1:FirstFitRoutingAllocator) Hosts's actual total CPU: 34128 and CPU after applying overprovisioning: 204768 2014-04-15 10:12:48,122 DEBUG [cloud.capacity.CapacityManagerImpl] (secstorage-1:FirstFitRoutingAllocator) Free CPU: 204768 , Requested CPU: 500 2014-04-15 10:12:48,122 DEBUG [cloud.capacity.CapacityManagerImpl] (secstorage-1:FirstFitRoutingAllocator) Free RAM: 24472994112 , Requested RAM: 268435456 2014-04-15 10:12:48,122 DEBUG [cloud.capacity.CapacityManagerImpl] (secstorage-1:FirstFitRoutingAllocator) Host has enough CPU and RAM available 2014-04-15 10:12:48,122 DEBUG [cloud.capacity.CapacityManagerImpl] (secstorage-1:FirstFitRoutingAllocator) STATS: Can alloc CPU from host: 68, used: 0, reserved: 0, actual total: 34128, total with overprovisioning: 204768; requested cpu:500,alloc_from_last_host?:false ,considerReservedCapacity?: true 2014-04-15 10:12:48,122 DEBUG [cloud.capacity.CapacityManagerImpl] (secstorage-1:FirstFitRoutingAllocator) STATS: Can alloc MEM from host: 68, used: 0, reserved: 0, total: 24472994112; requested mem: 268435456,alloc_from_last_host?:false ,considerReservedCapacity?: true 2014-04-15 10:12:48,122 DEBUG [allocator.impl.FirstFitAllocator] (secstorage-1:FirstFitRoutingAllocator) Found a suitable host, adding to list: 68 2014-04-15 10:12:48,122 DEBUG
Re: 答复: 二级存储丢失
生产环境不建议这样干，cs服务器只提供cs服务。你这样相当于主存储和cs在一台机器上 ganglin_lan 发件人： 许叁征 发送时间： 2014-04-17 17:20 收件人： users-cn@cloudstack.apache.org; 'ganglin_lan' 主题： 答复: 答复: 二级存储丢失 目前 使用的环境 是CS主机具有虚拟机文件，全为home目录下， 那这个CS备用机器/home目录下是不是也要同步，这个同步是如何用的同步？。 -邮件原件- 发件人: users-cn-return-3501-xusz=chinanetcenter@cloudstack.apache.org [mailto:users-cn-return-3501-xusz=chinanetcenter@cloudstack.apache.org] 代表 ganglin_lan 发送时间: 2014年4月17日星期四 16:05 收件人: users-cn 主题: Re: 答复: 二级存储丢失 cloudstack高可用可以配置cloudstack slave 服务器，正常安装cloudstack，初始化数据库时，不要用--deploy-as参数，这样两个cloudstack就可以同时管理了，当然前面还可以加个ngiinx之类的做负载均衡，重点是mysql数据库要做主从 ganglin_lan 发件人： 许叁征 发送时间： 2014-04-17 16:02 收件人： users-cn@cloudstack.apache.org 主题： 答复: 答复: 二级存储丢失 Hi linuxbqj 故障修复过程，北京-steelen会发布一个恢复过程到社区里面哈，另外后面发现服务器硬盘坏了，现在又要开始迁移的过程恢复数据了。。 对了，想问大家一个问题，如何做高可用的cloudstack，就是说一台cloudstac k主机宕机机了，另一台备机cloudstac k仍能工作。 目前cloudstack能做到吗？如果有，可有推荐的解决方案链接。。求解。谢谢 -邮件原件- 发件人: users-cn-return-3491-xusz=chinanetcenter@cloudstack.apache.org [mailto:users-cn-return-3491-xusz=chinanetcenter@cloudstack.apache.org] 代表 linux...@gmail.com 发送时间: 2014年4月16日星期三 15:11 收件人: users-cn@cloudstack.apache.org 主题: Re: 答复: 二级存储丢失 hey 叁征，是否可以把你的解决过程整理一个文章发布到社区网站呢 2014-04-16 14:12 GMT+08:00 Royal Yang rayang2...@gmail.com: 添加一个服务方案，勾选高可用，将虚拟机的服务方案更改为这个新建的方案。当host故障的时候应用此方案的虚拟机就能自动启动了 2014-04-16 13:23 GMT+08:00 许叁征 x...@chinanetcenter.com: 二级存储是使用NFS的，后面经“北京-steelen”的协助支持下，启用本地存储后经相应检查后，虚拟机多数可以启动了。在这里面要特别感谢下steelen，来到厦门的时候，记得告诉我，请你吃大餐以表心意， 目前有两个问题，在平时中一直困扰的。 1.使用两台XENserver为一个pool集群后，xenserver,有自时它会自动在XEN面板上变红色图标，然后节点会自动消失，一台xenserver 就会ping不通掉，看起来是机器在重启了。这样就造成虚拟机也瞬间停止运行了。。隔了2分钟后，它会可能会自动加载成同一个pool。 1.1想问下各位，造成这个问题的原因是什么，如何处理？ 1.2 如何在节点故障恢复后，虚拟机也能自动启动起来免人工手动启动。 谢谢大家了。 -邮件原件- 发件人: users-cn-return-3485-xusz=chinanetcenter@cloudstack.apache.org[mailto: users-cn-return-3485-xusz=chinanetcenter@cloudstack.apache.org] 代表 linux...@gmail.com 发送时间: 2014年4月16日星期三 7:49 收件人: users-cn@cloudstack.apache.org 主题: Re: 二级存储丢失 二级存储是使用的iscsi还是NFS呢？ 二级存储手动挂载有没有问题？看日志，分析是二级存储挂载不上 2014-04-15 10:18 GMT+08:00 许叁征 x...@chinanetcenter.com: HI ALL 最近一节点因为innode文件满了，造成虚拟机挺止，修复好节点却发现虚拟机无法启动， 环境：CS4.0.1 +XENSERVER。 添加了XEN主存储还是不能启动虚拟机。 2014-04-15 10:12:48,114 DEBUG [storage.allocator.LocalStoragePoolAllocator] (secstorage-1:null) Unable to find storage pool to fit the vm 2014-04-15 10:12:48,114 DEBUG [cloud.deploy.FirstFitPlanner] (secstorage-1:null) No suitable pools found for volume: Vol[67635|vm=67556|ROOT] under cluster: 20 2014-04-15 10:12:48,114 DEBUG [cloud.deploy.FirstFitPlanner] (secstorage-1:null) No suitable pools found 2014-04-15 10:12:48,114 DEBUG [cloud.deploy.FirstFitPlanner] (secstorage-1:null) No suitable storagePools found under this Cluster: 20 2014-04-15 10:12:48,115 DEBUG [cloud.deploy.FirstFitPlanner] (secstorage-1:null) Checking resources in Cluster: 1 under Pod: 1 2014-04-15 10:12:48,115 DEBUG [cloud.deploy.FirstFitPlanner] (secstorage-1:null) Calling HostAllocators to find suitable hosts 2014-04-15 10:12:48,115 DEBUG [allocator.impl.FirstFitAllocator] (secstorage-1:FirstFitRoutingAllocator) Looking for hosts in dc: 1 pod:1 cluster:1 2014-04-15 10:12:48,117 DEBUG [allocator.impl.FirstFitAllocator] (secstorage-1:FirstFitRoutingAllocator) FirstFitAllocator has 1 hosts to check for allocation: [Host[-68-Routing]] 2014-04-15 10:12:48,119 DEBUG [allocator.impl.FirstFitAllocator] (secstorage-1:FirstFitRoutingAllocator) Found 1 hosts for allocation after prioritization: [Host[-68-Routing]] 2014-04-15 10:12:48,119 DEBUG [allocator.impl.FirstFitAllocator] (secstorage-1:FirstFitRoutingAllocator) Looking for speed=500Mhz, Ram=256 2014-04-15 10:12:48,120 DEBUG [cloud.capacity.CapacityManagerImpl] (secstorage-1:FirstFitRoutingAllocator) Checking if host: 68 has enough capacity for requested CPU: 500 and requested RAM: 268435456 , cpuOverprovisioningFactor: 6.0 2014-04-15 10:12:48,122 DEBUG [cloud.capacity.CapacityManagerImpl] (secstorage-1:FirstFitRoutingAllocator) Hosts's actual total CPU: 34128 and CPU after applying overprovisioning: 204768 2014-04-15 10:12:48,122 DEBUG [cloud.capacity.CapacityManagerImpl] (secstorage-1:FirstFitRoutingAllocator) Free CPU: 204768 , Requested CPU: 500 2014-04-15 10:12:48,122 DEBUG [cloud.capacity.CapacityManagerImpl] (secstorage-1:FirstFitRoutingAllocator) Free RAM: 24472994112 , Requested RAM: 268435456 2014-04-15 10:12:48,122 DEBUG [cloud.capacity.CapacityManagerImpl] (secstorage-1:FirstFitRoutingAllocator) Host has enough CPU and RAM available 2014-04-15 10:12:48,122 DEBUG [cloud.capacity.CapacityManagerImpl] (secstorage-1:FirstFitRoutingAllocator) STATS: Can alloc CPU from host: 68, used: 0, reserved: 0, actual total: 34128, total with overprovisioning: 204768; requested cpu:500,alloc_from_last_host?:false ,considerReservedCapacity?: true
回复: 回复： 求助无法创建虚拟机
日志中没看出是主存储问题，请问你是怎么判断主存储问题的？ ganglin_lan From: 虚无缥缈 Date: 2014-04-03 18:05 To: users-cn Subject: 回复： 回复: 回复： 求助无法创建虚拟机 谢谢回复，我主存储有问题，换了一个主存储就好了。 -- 原始邮件 -- 发件人: Shane Wayne;zx0...@gmail.com; 发送时间: 2014年4月3日(星期四) 下午4:59 收件人: users-cnusers-cn@cloudstack.apache.org; 主题: Re: 回复: 回复： 求助无法创建虚拟机 日志里面有这一条。 ISO-202-2-d3beb14a-c693-3825-b20c-f41493d06114 as they are not HVM enabled 2014年4月3日 下午4:55于 ganglin_lan ganglin_...@tcloudcomputing.com写道： FirstFitRoutingAllocator) Not considering hosts: [Host[-1-Routing]] to deploy template: Tmpl[202-ISO-202-2-d3beb14a-c693-3825-b20c-f41493d06114 as they are not HVM enabled 虚拟化没开还是不支持？ ganglin_lan From: 虚无缥缈 Date: 2014-04-03 16:48 To: users-cn Subject: 回复： 求助无法创建虚拟机 系统虚拟机，上边还没有跑vm呢，刚建的系统，主机cpu绝对够。 -- 原始邮件 -- 发件人: Shane Wayne;zx0...@gmail.com; 发送时间: 2014年4月3日(星期四) 下午4:39 收件人: users-cnusers-cn@cloudstack.apache.org; 主题: Re: 求助无法创建虚拟机 检查是不是你的offering主频超过了处理器核心频率。 2014年4月3日 下午3:33于 史丽丽 shi...@neusoft.com写道： 虚拟化管理程序是xenserver 创建虚拟机的时候日志反复提示下边这段代码，虚拟机创建失败 2014-04-03 15:19:13,649 DEBUG [cloud.deploy.DeploymentPlanningManagerImpl] (Job-Executor-2:job-9 = [ c62429cd-cfd8-439b-82bb-6bc6e4568764 ]) No suitable hosts found 2014-04-03 15:19:13,649 DEBUG [cloud.deploy.DeploymentPlanningManagerImpl] (Job-Executor-2:job-9 = [ c62429cd-cfd8-439b-82bb-6bc6e4568764 ]) No suitable hosts found under this Cluster: 1 2014-04-03 15:19:13,653 DEBUG [cloud.deploy.DeploymentPlanningManagerImpl] (Job-Executor-2:job-9 = [ c62429cd-cfd8-439b-82bb-6bc6e4568764 ]) Could not find suitable Deployment Destination for this VM under any clusters, returning. 2014-04-03 15:19:13,653 DEBUG [cloud.deploy.FirstFitPlanner] (Job-Executor-2:job-9 = [ c62429cd-cfd8-439b-82bb-6bc6e4568764 ]) Searching all possible resources under this Zone: 1 2014-04-03 15:19:13,654 DEBUG [cloud.deploy.FirstFitPlanner] (Job-Executor-2:job-9 = [ c62429cd-cfd8-439b-82bb-6bc6e4568764 ]) Listing clusters in order of aggregate capacity, that have (atleast one host with) enough CPU and RAM capacity under this Zone: 1 2014-04-03 15:19:13,666 DEBUG [cloud.deploy.DeploymentPlanningManagerImpl] (Job-Executor-2:job-9 = [ c62429cd-cfd8-439b-82bb-6bc6e4568764 ]) Checking resources in Cluster: 1 under Pod: 1 2014-04-03 15:19:13,666 DEBUG [allocator.impl.FirstFitAllocator] (Job-Executor-2:job-9 = [ c62429cd-cfd8-439b-82bb-6bc6e4568764 ] FirstFitRoutingAllocator) Looking for hosts in dc: 1 pod:1 cluster:1 2014-04-03 15:19:13,669 DEBUG [allocator.impl.FirstFitAllocator] (Job-Executor-2:job-9 = [ c62429cd-cfd8-439b-82bb-6bc6e4568764 ] FirstFitRoutingAllocator) FirstFitAllocator has 1 hosts to check for allocation: [Host[-1-Routing]] 2014-04-03 15:19:13,672 DEBUG [allocator.impl.FirstFitAllocator] (Job-Executor-2:job-9 = [ c62429cd-cfd8-439b-82bb-6bc6e4568764 ] FirstFitRoutingAllocator) Not considering hosts: [Host[-1-Routing]] to deploy template: Tmpl[202-ISO-202-2-d3beb14a-c693-3825-b20c-f41493d06114 as they are not HVM enabled 2014-04-03 15:19:13,672 DEBUG [allocator.impl.FirstFitAllocator] (Job-Executor-2:job-9 = [ c62429cd-cfd8-439b-82bb-6bc6e4568764 ] FirstFitRoutingAllocator) Found 0 hosts for allocation after prioritization: [] 2014-04-03 15:19:13,672 DEBUG [allocator.impl.FirstFitAllocator] (Job-Executor-2:job-9 = [ c62429cd-cfd8-439b-82bb-6bc6e4568764 ] FirstFitRoutingAllocator) Looking for speed=1000Mhz, Ram=1024 2014-04-03 15:19:13,672 DEBUG [allocator.impl.FirstFitAllocator] (Job-Executor-2:job-9 = [ c62429cd-cfd8-439b-82bb-6bc6e4568764 ] FirstFitRoutingAllocator) Host Allocator returning 0 suitable hosts --- Confidentiality Notice: The information contained in this e-mail and any accompanying attachment(s) is intended only for the use of the intended recipient and may be confidential and/or privileged of Neusoft Corporation, its subsidiaries and/or its affiliates. If any reader of this communication is not the intended recipient, unauthorized use, forwarding, printing, storing, disclosure or copying is strictly prohibited, and may be unlawful.If you have received this communication in error,please immediately notify the sender by return e-mail, and delete the original message and all copies from your system. Thank you. ---
Re: 回复: 咨询虚拟机CPU的使用问题
这么测CPU使用性能还是有些片面，得出的数据也没有多大参考价值，得了解CPU有哪些性能指标，例如虚拟化和物理环境下CPU的浮点运算能力、整数运算能力等，还跟不同CPU型号，不同CPU厂商有关，做一个全面的对比，所以要得到虚拟机使用CPU的性能问题还是挺复杂的。个人见解，请多指教。
ganglin_lan
发件人： cui6522123
发送时间： 2014-03-31 13:54
收件人： cloud
主题： 回复: Re: 咨询虚拟机CPU的使用问题
麻烦一下 发下你的结果 图片我都没收到。
这段代码主要是测试CPU单线程满负荷情况下的计算能力 你可在运行命令后查看top后按1命令 单个线程的CPU利用率达到了100%。
另外请问一下你的虚拟机是几线程？
如果你的线程是8线程的话，建议你起8个java命令 让它后台执行看看最后的值能稳定在什么情况下。
cui6522123
发件人： Shane Wayne发送时间： 2014-03-31 13:44收件人： users-cn主题： Re: Re:
咨询虚拟机CPU的使用问题今天中午已经测试完成，发现了很多的东西：1、KVM使用频率限制CPU资源在这个测试上面并不能体现出性能的区别；2、Intel使用的CPU(本测试中使用了E7-4820)在虚拟化之后会比AMD的CPU未经过虚拟化性能还好。
上半部分是Intel处理器的测试结果，下半部分是未经虚拟化的AMD服务器跑出的结果。
AMD的Java JDK环境：
但运行环境稍有区别，Intel虚拟化后的OpenJDK：
如果需要我还可以用AMD上进行OpenJDK的测试。
在这里我还有个特别的疑问：就是你的代码为什么能够测试单线程的性能？有没有什么根据？
在 2014年3月31日 上午10:31，cui6522123 cui6522...@gmail.com写道：
我给你贴一下代码吧，你拷贝到服务器上，命名成Test.java即可
import java.util.Random;
public class Test {
public static void main(String[] args) {
Random rand = new Random();
while (true) {
long start = System.currentTimeMillis();
int init = 0;
for (int i = 0; i 1000; i++) {
init ^= rand.nextInt();
}
long end = System.currentTimeMillis();
long used = end - start;
long rate = 1000L * 1000L / used;
System.out.println(rate);
}
}
}
cui6522123
发件人： Shane Wayne发送时间： 2014-03-31 10:18收件人： users-cn主题： Re: Re:
咨询虚拟机CPU的使用问题没有找到你的附件，可否发我私人邮箱一份。
在 2014年3月31日 上午9:35，cui6522123 cui6522...@gmail.com写道：
附件里有一个Test.java文件，主要测试CPU的计算能力。你创建一个虚拟机2线程即可，因为这个java程序是测试单线程的运算，分别在物理机和虚拟机上都跑一下试试，看一下得到的值
首先保证你的虚拟机上有java环境
运行之前得编译一下
$JAVA_HOME/bin/javac Test.java
然后执行 java Test 即可
--
cui6522123
*发件人：* Shane Wayne zx0...@gmail.com
*发送时间：* 2014-03-31 09:08
*收件人：* users-cn users-cn@cloudstack.apache.org
*主题：* Re: 回复: Re: 咨询虚拟机CPU的使用问题
本来CloudStack的资源池概念就让我觉得很奇怪，原先KVM貌似没有这个形式的划分概念，你单线程性能怎么测试的？我在我这边KVM上给你测试一下。
--
http://www.avast.com/
此电子邮件不含病毒和恶意软件，因为 avast! 杀毒软件 http://www.avast.com/ 保护处于活动状态。
--
ZHANG Xiao
The Institute of Computer Software Engineering and Theory in Xi'an Jiaotong
University
Master-and-Doctoral Program Student
ACM Student Member
CCF Student Member
IEEE Computer Society Sister Society Associate Member
Xi'an Jiaotong University
Bachelor of Engineering in Computer Science and Technology
The Chinese University of Hong Kong
International Asia Study Program in CS/CE/EE/IE
---
此电子邮件没有病毒和恶意软件，因为 avast! 防病毒保护处于活动状态。
http://www.avast.com
--
ZHANG Xiao
The Institute of Computer Software Engineering and Theory in Xi'an Jiaotong
University
Master-and-Doctoral Program Student
ACM Student MemberCCF Student MemberIEEE Computer Society Sister Society
Associate Member
Xi'an Jiaotong UniversityBachelor of Engineering in Computer Science and
Technology
The Chinese University of Hong KongInternational Asia Study Program in
CS/CE/EE/IE
---
此电子邮件没有病毒和恶意软件，因为 avast! 防病毒保护处于活动状态。
http://www.avast.com
Re: 添加ISCSI存储的虚拟机出现闪退
现象是看不出问题的，得看本质，说好的log呢？ ganglin_lan 发件人： 许叁征 发送时间： 2014-03-31 16:36 收件人： users-cn@cloudstack.apache.org 主题： 添加ISCSI存储的虚拟机出现闪退 HI ALL 最近新上两个节点XENserver，添加节点各项正常，同时也添加了ISCSI存储。 启动虚拟机发现无法启动，资源 也够，检查二级存储发现是0.0KB 但是使用SSVM也启动正常，通过原有模板创建的也能正常创建。 问题来了，虚拟机创建一直不能成功，指定了ISCSI存储和新增的节点标签，发现在ISCSI的存储上，虚拟机启动出现一闪而过，在ISCSI存储发现它创建了文件，而后又删除掉了。 虚拟机就失败掉了。 这是怎么回事，问题要如何解决，谢谢
回复: 服务启动不成功
先把这个问题解决了吧 2:) Detected that another management node with the same IP 192.168.131.141 is considered as running in DB, however it is not pingable, we will continue cluster initialization with this management server node ganglin_lan 发件人： 史丽丽 发送时间： 2014-03-26 17:14 收件人： users-cn@cloudstack.apache.org 主题： 服务启动不成功 您好，我这边做一个cloudstack的部署，目前是在一台虚拟机上装cloudstack，数据库安装成功，操作系统是rhel cs版本为4.2，到初始化cloudstack管理程序步骤，执行如下命令cloudstack-setup-management 参看日志为：/var/log/cloudstack/management/catalina.out cs启动报错如下：服务启动不成功，望您给予解答，谢谢。 maxElementsOnDisk = 0 memoryStoreEvictionPolicy = LRU timeToLiveSeconds = 600 timeToIdleSeconds = 300 diskPersistent = false diskExpiryThreadIntervalSeconds = 120 cacheEventListeners: hitCount = 0 memoryStoreHitCount = 0 diskStoreHitCount = 0 missCountNotFound = 0 missCountExpired = 0 ] INFO [utils.component.ComponentContext] (Timer-2:) Configuring com.cloud.upgrade.DatabaseIntegrityChecker_EnhancerByCloudStack_ead01e13 INFO [utils.component.ComponentContext] (Timer-2:) Configuring com.cloud.server.ConfigurationServerImpl_EnhancerByCloudStack_a685eed4 INFO [cloud.server.ConfigurationServerImpl] (Timer-2:) Processing updateSSLKeyStore INFO [cloud.server.ConfigurationServerImpl] (Timer-2:) SSL keystore located at /etc/cloudstack/management/cloud.keystore WARN [cloud.server.ConfigurationServerImpl] (Timer-2:) Would use fail-safe keystore to continue. java.io.IOException: Fail to generate certificate!: sudo: keytool: command not found at com.cloud.server.ConfigurationServerImpl.generateDefaultKeystore(ConfigurationServerImpl.java:496) at com.cloud.server.ConfigurationServerImpl.updateSSLKeystore(ConfigurationServerImpl.java:517) at com.cloud.server.ConfigurationServerImpl.persistDefaultValues(ConfigurationServerImpl.java:289) at com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125) at com.cloud.server.ConfigurationServerImpl.configure(ConfigurationServerImpl.java:157) at com.cloud.utils.component.ComponentContext.initComponentsLifeCycle(ComponentContext.java:111) at com.cloud.servlet.CloudStartupServlet$1.run(CloudStartupServlet.java:54) at java.util.TimerThread.mainLoop(Timer.java:512) at java.util.TimerThread.run(Timer.java:462) INFO [cloud.server.ConfigurationServerImpl] (Timer-2:) Processing updateKeyPairs INFO [cloud.server.ConfigurationServerImpl] (Timer-2:) Keypairs already in database, updating local copy INFO [cloud.server.ConfigurationServerImpl] (Timer-2:) Going to update systemvm iso with generated keypairs if needed 2014-3-26 13:57:40 org.springframework.web.context.ContextLoader initWebApplicationContext 信息: Root WebApplicationContext: initialization completed in 3871 ms 2014-3-26 13:57:40 org.springframework.beans.factory.annotation.AutowiredAnnotationBeanPostProcessor init 信息: JSR-330 'javax.inject.Inject' annotation found and supported for autowiring INFO [utils.component.ComponentContext] (Timer-2:) Configuring com.cloud.utils.crypt.EncryptionSecretKeyChecker_EnhancerByCloudStack_375384cc INFO [utils.component.ComponentContext] (Timer-2:) Configuring com.cloud.cluster.ManagementServerNode_EnhancerByCloudStack_ab03d7d2 INFO [utils.component.ComponentContext] (Timer-2:) Configuring com.cloud.cluster.ClusterManagerImpl_EnhancerByCloudStack_5702e15 INFO [cloud.cluster.ClusterManagerImpl] (Timer-2:) Start configuring cluster manager : ClusterManagerImpl_EnhancerByCloudStack_5702e15 INFO [cloud.cluster.ClusterManagerImpl] (Timer-2:) Cluster node IP : 192.168.131.141 INFO [utils.db.Merovingian2] (Timer-2:) Cleaning up locks for 86530476470110 INFO [utils.db.Merovingian2] (Timer-2:) Released 0 locks for 86530476470110 INFO [cloud.cluster.ClusterManagerImpl] (Timer-2:) register cluster listener class com.cloud.cluster.LockMasterListener INFO [cloud.cluster.ClusterManagerImpl] (Timer-2:) Trying to connect to 192.168.131.141 ERROR [cloud.cluster.ClusterManagerImpl] (Timer-2:) Unable to ping management server at 192.168.131.141:9090 due to ConnectException java.net.ConnectException: Connection refused at sun.nio.ch.Net.connect(Native Method) at sun.nio.ch.SocketChannelImpl.connect(SocketChannelImpl.java:500) at com.cloud.cluster.ClusterManagerImpl.pingManagementNode(ClusterManagerImpl.java:1405) at com.cloud.cluster.ClusterManagerImpl.pingManagementNode(ClusterManagerImpl.java:1384) at com.cloud.cluster.ClusterManagerImpl.checkConflicts(ClusterManagerImpl.java:1461) at com.cloud.cluster.ClusterManagerImpl.configure(ClusterManagerImpl.java:1347) at com.cloud.utils.component.ComponentContext.initComponentsLifeCycle(ComponentContext.java:111) at com.cloud.servlet.CloudStartupServlet$1.run(CloudStartupServlet.java:54) at java.util.TimerThread.mainLoop(Timer.java:512) at java.util.TimerThread.run(Timer.java:462) INFO [cloud.cluster.ClusterManagerImpl] (Timer-2:) Detected that another management node with the same IP 192.168.131.141 is considered
回复: cloudstack平台无法打开
cloudstack的日志给的不全，mysql的日志只显示到昨晚八点？ ganglin_lan 发件人： 许叁征 发送时间： 2014-03-26 11:42 收件人： users-cn@cloudstack.apache.org 主题： cloudstack平台无法打开 HI ALL 昨天虚拟机平台机器宕机后，重启发现平台无法打开，cloudstack 4.0.1 以及 mysql日志报错如下： 请教 这个要如何处理，谢谢！ [root@manager ~]# tailf /usr/share/cloud/management/logs/management-server. log at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:443) at org.apache.catalina.core.StandardService.start(StandardService.java:516) at org.apache.catalina.core.StandardServer.start(StandardServer.java:710) at org.apache.catalina.startup.Catalina.start(Catalina.java:593) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57 ) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl .java:43) at java.lang.reflect.Method.invoke(Method.java:616) at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:289) at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:414) 2014-03-26 10:56:26,367 INFO [utils.component.ComponentLocator] (main:null) Config file found at /etc/cloud/management/components.xml. Configuring system-integrity-checker 2014-03-26 10:56:26,372 DEBUG [utils.component.ComponentLocator] (main:null) Looking for class com.cloud.cluster.ManagementServerNode 2014-03-26 10:56:26,391 INFO [utils.component.ComponentLocator] (main:null) Found component: com.cloud.utils.component.SystemIntegrityChecker in com.cloud.cluster.ManagementServerNode - ManagementServerNode 2014-03-26 10:56:26,391 INFO [utils.component.ComponentLocator] (main:null) Adding system integrity checker: ManagementServerNode 2014-03-26 10:56:26,391 DEBUG [utils.component.ComponentLocator] (main:null) Looking for class com.cloud.utils.crypt.EncryptionSecretKeyChecker 2014-03-26 10:56:26,400 INFO [utils.component.ComponentLocator] (main:null) Found component: com.cloud.utils.component.SystemIntegrityChecker in com.cloud.utils.crypt.EncryptionSecretKeyChecker - EncryptionSecretKeyChecker 2014-03-26 10:56:26,400 INFO [utils.component.ComponentLocator] (main:null) Adding system integrity checker: EncryptionSecretKeyChecker 2014-03-26 10:56:26,400 DEBUG [utils.component.ComponentLocator] (main:null) Looking for class com.cloud.upgrade.DatabaseIntegrityChecker 2014-03-26 10:56:26,401 INFO [utils.component.ComponentLocator] (main:null) Found component: com.cloud.utils.component.SystemIntegrityChecker in com.cloud.upgrade.DatabaseIntegrityChecker - DatabaseIntegrityChecker 2014-03-26 10:56:26,402 INFO [utils.component.ComponentLocator] (main:null) Adding system integrity checker: DatabaseIntegrityChecker 2014-03-26 10:56:26,402 DEBUG [utils.component.ComponentLocator] (main:null) Looking for class com.cloud.upgrade.PremiumDatabaseUpgradeChecker 2014-03-26 10:56:26,403 INFO [utils.component.ComponentLocator] (main:null) Found component: com.cloud.utils.component.SystemIntegrityChecker in com.cloud.upgrade.PremiumDatabaseUpgradeChecker - DatabaseUpgradeChecker 2014-03-26 10:56:26,403 INFO [utils.component.ComponentLocator] (main:null) Adding system integrity checker: DatabaseUpgradeChecker 2014-03-26 10:56:26,474 DEBUG [utils.crypt.EncryptionSecretKeyChecker] (main:null) Encryption Type: file 2014-03-26 10:56:26,557 INFO [cloud.upgrade.DatabaseIntegrityChecker] (main:null) Grabbing lock to check for database integrity. 2014-03-26 10:56:30,774 ERROR [db.Transaction.Transaction] (main:null) Unexpected exception: com.mysql.jdbc.exceptions.jdbc4.MySQLNonTransientConnectionException: Could not create connection to database server. Attempted reconnect 3 times. Giving up. at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAcces sorImpl.java:57) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstruc torAccessorImpl.java:45) at java.lang.reflect.Constructor.newInstance(Constructor.java:532) at com.mysql.jdbc.Util.handleNewInstance(Util.java:411) at com.mysql.jdbc.Util.getInstance(Util.java:386) at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:1013) at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:987) at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:982) at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:927) at com.mysql.jdbc.ConnectionImpl.connectWithRetries(ConnectionImpl.java:2238) at com.mysql.jdbc.ConnectionImpl.createNewIO(ConnectionImpl.java:2159) at com.mysql.jdbc.ConnectionImpl.init(ConnectionImpl.java:792) at com.mysql.jdbc.JDBC4Connection.init(JDBC4Connection.java:49) at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAcces sorImpl.java:57) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstruc torAccessorImpl.java:45) at java.lang.reflect.Constructor.newInstance(Constructor.java:532
回复: 回复: 添加实例不成功
重启VR试试
ganglin_lan
发件人： yhz...@pipgame.com
发送时间： 2014-03-25 13:00
收件人： cloudstackusers...@cloudstack.apache.org
主题： 回复: 回复: 添加实例不成功
我这是4.2.0的环境。。VR在线上运行着。。新添加实例的时候报的这个错误，主机的资源还很充足
4.2.1有这问题么
赵元海
平台MIS部
9095
yhz...@pipgame.com
*
发件人： brito.w...@gmail.com
发送时间： 2014-03-25 12:39
收件人： users-cn
抄送：
主题： 回复: 添加实例不成功
我不知道你哪儿是cloudstack几点几的环境，你查看一下是不是v-router启动不起来?我记得cloudstack某一个版本中有关创建系统虚拟机有一个Bug,系统虚拟机在一种特别情况下会尝试在无效的主机或集群上创建，你先检查一下集群和主机的情况，把无效的禁用掉或者删除掉，看看能否把VM创建起来。
brito.w...@gmail.com
?发件人：?yhz...@pipgame.com发送时间：?2014-03-25?09:47收件人：?cloudstackusers...@cloudstack.apache.org主题：?添加实例不成功HI
大家帮我看一下。。创建实例不成功
?
2014-03-25 09:34:44,843 DEBUG [agent.transport.Request] (Job-Executor-7:job-237
= [ 05aec4e1-6b33-48f4-94d8-647c3ce1c791 ]) Seq 1-2085489885: Executing:? { Cmd
, MgmtId: 264018885718825, via: 1, Ver: v1, Flags: 100111,
[{com.cloud.agent.api.routing.SavePasswordCommand:{password:fnirq_cnffjbeq,vmIpAddress:10.10.30.66,vmName:pipProxy2,executeInSequence:true,accessDetails:{router.guest.ip:10.10.30.1,zone.network.type:Advanced,router.ip:169.254.1.159,router.name:r-4-VM},wait:0}},{com.cloud.agent.api.routing.VmDataCommand:{vmIpAddress:10.10.30.66,vmName:pipProxy2,executeInSequence:true,accessDetails:{router.guest.ip:10.10.30.1,zone.network.type:Advanced,router.ip:169.254.1.159,router.name:r-4-VM},wait:0}}]
}
2014-03-25 09:34:44,843 DEBUG [agent.manager.DirectAgentAttache]
(DirectAgent-330:null) Seq 1-2085489885: Executing request
2014-03-25 09:34:45,658 DEBUG [agent.manager.AgentManagerImpl]
(AgentManager-Handler-13:null) SeqA 2-934780: Processing Seq 2-934780:? { Cmd ,
MgmtId: -1, via: 2, Ver: v1, Flags: 11,
[{com.cloud.agent.api.ConsoleProxyLoadReportCommand:{_proxyVmId:2,_loadInfo:{\n?
\connections\: []\n},wait:0}}] }
2014-03-25 09:34:45,661 DEBUG [agent.manager.AgentManagerImpl]
(AgentManager-Handler-13:null) SeqA 2-934780: Sending Seq 2-934780:? { Ans: ,
MgmtId: 264018885718825, via: 2, Ver: v1, Flags: 100010,
[{com.cloud.agent.api.AgentControlAnswer:{result:true,wait:0}}] }
2014-03-25 09:34:46,047 DEBUG [cloud.server.StatsCollector]
(StatsCollector-3:null) HostStatsCollector is running...
2014-03-25 09:34:46,059 DEBUG [agent.manager.DirectAgentAttache]
(DirectAgent-134:null) Seq 1-2085489886: Executing request
2014-03-25 09:34:46,277 DEBUG [cloud.api.ApiServlet] (catalina-exec-1:null)
===START===? 114.251.179.130 -- GET?
command=queryAsyncJobResultjobId=05aec4e1-6b33-48f4-94d8-647c3ce1c791response=jsonsessionkey=a%2BkjTa8gW%2FA6qVlgpPRlO%2BFdNMs%3D_=1395711258453
2014-03-25 09:34:46,299 DEBUG [cloud.api.ApiServlet] (catalina-exec-1:null)
===END===? 114.251.179.130 -- GET?
command=queryAsyncJobResultjobId=05aec4e1-6b33-48f4-94d8-647c3ce1c791response=jsonsessionkey=a%2BkjTa8gW%2FA6qVlgpPRlO%2BFdNMs%3D_=1395711258453
2014-03-25 09:34:46,435 DEBUG [agent.manager.DirectAgentAttache]
(DirectAgent-330:null) Seq 1-2085489885: Response Received:
2014-03-25 09:34:46,436 DEBUG [agent.transport.Request] (DirectAgent-330:null)
Seq 1-2085489885: Processing:? { Ans: , MgmtId: 264018885718825, via: 1, Ver:
v1, Flags: 110,
[{com.cloud.agent.api.Answer:{result:true,wait:0}},{com.cloud.agent.api.Answer:{result:false,details:vm_data
failed,wait:0}}] }
2014-03-25 09:34:46,436 DEBUG [agent.manager.AgentAttache]
(DirectAgent-330:null) Seq 1-2085489885: No more commands found
2014-03-25 09:34:46,436 DEBUG [agent.transport.Request] (Job-Executor-7:job-237
= [ 05aec4e1-6b33-48f4-94d8-647c3ce1c791 ]) Seq 1-2085489885: Received:? { Ans:
, MgmtId: 264018885718825, via: 1, Ver: v1, Flags: 110, { Answer, Answer } }
2014-03-25 09:34:46,436 INFO? [cloud.vm.VirtualMachineManagerImpl]
(Job-Executor-7:job-237 = [ 05aec4e1-6b33-48f4-94d8-647c3ce1c791 ]) Unable to
contact resource.
com.cloud.exception.ResourceUnavailableException: Resource [DataCenter:1] is
unreachable: Unable to apply userdata and password entry on router
??? at
com.cloud.network.router.VirtualNetworkApplianceManagerImpl.applyRules(VirtualNetworkApplianceManagerImpl.java:3808)
??? at
com.cloud.network.router.VirtualNetworkApplianceManagerImpl.applyUserData(VirtualNetworkApplianceManagerImpl.java:2993)
??? at
com.cloud.network.element.VirtualRouterElement.addPasswordAndUserdata(VirtualRouterElement.java:926)
??? at
com.cloud.network.NetworkManagerImpl.prepareElement(NetworkManagerImpl.java:2076)
at
com.cloud.network.NetworkManagerImpl.prepareElement(NetworkManagerImpl.java:2076)
??? at
com.cloud.network.NetworkManagerImpl.prepareNic(NetworkManagerImpl.java:2191)
??? at
com.cloud.network.NetworkManagerImpl.prepare(NetworkManagerImpl.java:2127)
??? at
com.cloud.vm.VirtualMachineManagerImpl.advanceStart(VirtualMachineManagerImpl.java:887)
??? at
com.cloud.vm.VirtualMachineManagerImpl.start(VirtualMachineManagerImpl.java:578)
??? at
org.apache.cloudstack.engine.cloud.entity.api.VMEntityManagerImpl.deployVirtualMachine
Re: Re: [求助] v4.2.1 启动报错
cloudstack 全局设置中的host 参数设置成management-server IP，management.network.cidr 设置成相应的值了吗 ganglin_lan 发件人： 风南 发送时间： 2014-03-22 15:30 收件人： users-cn 主题： Re: [求助] v4.2.1 启动报错 补充一些信息： [root@cs-manager ~]# netstat -antp| grep 9090 tcp0 0 :::9090 :::* LISTEN 4282/java [root@cs-manager ~]# ps -ef | grep java| grep 4282 cloud 4282 1 4 22:45 ?00:01:52 /usr/lib/jvm/java/bin/java -Djava.awt.headless=true -Dcom.sun.management.jmxremote.port=45219 -Dcom.sun.management.jmxremote.authenticate=false -Dcom.sun.management.jmxremote.ssl=false -Xmx2g -XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=/var/log/cloudstack/management/ -XX:PermSize=512M -XX:MaxPermSize=800m -classpath :::/etc/cloudstack/management:/usr/share/cloudstack-management/setup:/usr/share/cloudstack-management/bin/bootstrap.jar:/usr/share/cloudstack-management/bin/tomcat-juli.jar:/usr/share/java/commons-daemon.jar -Dcatalina.base=/usr/share/cloudstack-management -Dcatalina.home=/usr/share/cloudstack-management -Djava.endorsed.dirs= -Djava.io.tmpdir=/usr/share/cloudstack-management/temp -Djava.util.logging.config.file=/usr/share/cloudstack-management/conf/logging.properties -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager org.apache.catalina.startup.Bootstrap start 2014-03-22 15:23 GMT+08:00 风南 winnery...@gmail.com: 各位好。 不好意思，刚才Gmail的快捷键误发了和一个没有写完的邮件，请管理员删除。 安装的4.2.1一直都没有启动成功过，请各位高手帮忙，非常感谢。 环境如下： management-server: 运行在vmware workstation的虚拟机中，网络桥接模式。 物理宿主机为windows7，IP：192.168.11.30 配置： CPU:：Intel(R) Core(TM) i7-4770 CPU @ 3.40GHz 两个 内存：2GB 磁盘：80GB IP： 192.168.11.61 GW: 192.168.11.1 Host： 运行在另一台物理主机，XenServer6.1.0 配置： CPU:：Intel(R) Core(TM) i7-4770 CPU @ 3.40GHz 内存：8GB 磁盘：2TB IP： 192.168.11.40 GW: 192.168.11.1 一级存储和二级存储使用NFS模式，NFS服务端：management-server（192.168.11.61） 中： primary: /export/primary secondary: /export/secondary 在Host中挂载NFS读写都没有问题 management-server iptables: [root@cs-manager management]# cat /etc/sysconfig/iptables # Generated by iptables-save v1.4.7 on Mon Mar 17 06:02:02 2014 *filter :INPUT ACCEPT [0:0] :FORWARD ACCEPT [0:0] :OUTPUT ACCEPT [999012:2307279867] -A INPUT -p tcp -m tcp --dport 9090 -j ACCEPT -A INPUT -p tcp -m tcp --dport 8250 -j ACCEPT -A INPUT -p tcp -m tcp --dport 7080 -j ACCEPT -A INPUT -p tcp -m tcp --dport 8080 -j ACCEPT -A INPUT -p tcp -m tcp --dport 111 -j ACCEPT -A INPUT -p udp -m udp --dport 111 -j ACCEPT -A INPUT -p tcp -m tcp --dport 2049 -j ACCEPT -A INPUT -p tcp -m tcp --dport 32803 -j ACCEPT -A INPUT -p udp -m udp --dport 32769 -j ACCEPT -A INPUT -p tcp -m tcp --dport 892 -j ACCEPT -A INPUT -p udp -m udp --dport 892 -j ACCEPT -A INPUT -p tcp -m tcp --dport 875 -j ACCEPT -A INPUT -p udp -m udp --dport 875 -j ACCEPT -A INPUT -p tcp -m tcp --dport 662 -j ACCEPT -A INPUT -p udp -m udp --dport 662 -j ACCEPT -A INPUT -m state --state RELATED,ESTABLISHED -j ACCEPT -A INPUT -p icmp -j ACCEPT -A INPUT -i lo -j ACCEPT -A INPUT -p tcp -m state --state NEW -m tcp --dport 22 -j ACCEPT -A INPUT -j REJECT --reject-with icmp-host-prohibited -A FORWARD -j REJECT --reject-with icmp-host-prohibited COMMIT # Completed on Mon Mar 17 06:02:02 2014 完整日志文件请见：http://hctysoft.com/management-server.log 从日志中分析来看在启动Console Proxy VM的报错，下面是我截取的一些关键的management-server日志片段： catalina.out: INFO [cloud.cluster.ClusterManagerImpl] (Timer-2:) register cluster listener class com.cloud.cluster.LockMasterListener INFO [cloud.cluster.ClusterManagerImpl] (Timer-2:) Trying to connect to 192.168.11.61 ERROR [cloud.cluster.ClusterManagerImpl] (Timer-2:) Unable to ping management server at 192.168.11.61:9090 due to ConnectException java.net.ConnectException: Connection refused at sun.nio.ch.Net.connect0(Native Method) at sun.nio.ch.Net.connect(Net.java:465) at sun.nio.ch.Net.connect(Net.java:457) at sun.nio.ch.SocketChannelImpl.connect(SocketChannelImpl.java:670) at com.cloud.cluster.ClusterManagerImpl.pingManagementNode(ClusterManagerImpl.java:1405) at com.cloud.cluster.ClusterManagerImpl.pingManagementNode(ClusterManagerImpl.java:1384) at com.cloud.cluster.ClusterManagerImpl.checkConflicts(ClusterManagerImpl.java:1461) at com.cloud.cluster.ClusterManagerImpl.configure(ClusterManagerImpl.java:1347) at com.cloud.utils.component.ComponentContext.initComponentsLifeCycle(ComponentContext.java:111) at com.cloud.servlet.CloudStartupServlet$1.run(CloudStartupServlet.java:54) at java.util.TimerThread.mainLoop(Timer.java:555) at java.util.TimerThread.run(Timer.java:505) management-server.log 2014-03-22 22:45:57,912 INFO [cloud.cluster.ClusterManagerImpl] (Timer-2:null) Cluster node IP : 192.168.11.61 2014-03-22 22:45:57,959 DEBUG [utils.db.ConnectionConcierge] (Timer-2:null) Registering a database connection for LockMaster1 2014-03-22 22:45:57,959 INFO [utils.db.Merovingian2] (Timer-2:null) Cleaning up
Re: Re: [求助] v4.2.1 启动报错
先把iptables stop 了试试呢？ ganglin_lan 发件人： 风南 发送时间： 2014-03-22 20:05 收件人： users-cn; ganglin_lan 主题： Re: Re: [求助] v4.2.1 启动报错 设置过了，值如下： host = 192.168.11.61 management.network.cidr = 192.168.11.0/24 2014-03-22 19:13 GMT+08:00 ganglin_lan ganglin_...@tcloudcomputing.com: cloudstack 全局设置中的host 参数设置成management-server IP，management.network.cidr 设置成相应的值了吗 ganglin_lan 发件人： 风南 发送时间： 2014-03-22 15:30 收件人： users-cn 主题： Re: [求助] v4.2.1 启动报错 补充一些信息： [root@cs-manager ~]# netstat -antp| grep 9090 tcp0 0 :::9090 :::* LISTEN 4282/java [root@cs-manager ~]# ps -ef | grep java| grep 4282 cloud 4282 1 4 22:45 ?00:01:52 /usr/lib/jvm/java/bin/java -Djava.awt.headless=true -Dcom.sun.management.jmxremote.port=45219 -Dcom.sun.management.jmxremote.authenticate=false -Dcom.sun.management.jmxremote.ssl=false -Xmx2g -XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=/var/log/cloudstack/management/ -XX:PermSize=512M -XX:MaxPermSize=800m -classpath :::/etc/cloudstack/management:/usr/share/cloudstack-management/setup:/usr/share/cloudstack-management/bin/bootstrap.jar:/usr/share/cloudstack-management/bin/tomcat-juli.jar:/usr/share/java/commons-daemon.jar -Dcatalina.base=/usr/share/cloudstack-management -Dcatalina.home=/usr/share/cloudstack-management -Djava.endorsed.dirs= -Djava.io.tmpdir=/usr/share/cloudstack-management/temp -Djava.util.logging.config.file=/usr/share/cloudstack-management/conf/logging.properties -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager org.apache.catalina.startup.Bootstrap start 2014-03-22 15:23 GMT+08:00 风南 winnery...@gmail.com: 各位好。 不好意思，刚才Gmail的快捷键误发了和一个没有写完的邮件，请管理员删除。 安装的4.2.1一直都没有启动成功过，请各位高手帮忙，非常感谢。 环境如下： management-server: 运行在vmware workstation的虚拟机中，网络桥接模式。 物理宿主机为windows7，IP：192.168.11.30 配置： CPU:：Intel(R) Core(TM) i7-4770 CPU @ 3.40GHz 两个 内存：2GB 磁盘：80GB IP： 192.168.11.61 GW: 192.168.11.1 Host： 运行在另一台物理主机，XenServer6.1.0 配置： CPU:：Intel(R) Core(TM) i7-4770 CPU @ 3.40GHz 内存：8GB 磁盘：2TB IP： 192.168.11.40 GW: 192.168.11.1 一级存储和二级存储使用NFS模式，NFS服务端：management-server（192.168.11.61） 中： primary: /export/primary secondary: /export/secondary 在Host中挂载NFS读写都没有问题 management-server iptables: [root@cs-manager management]# cat /etc/sysconfig/iptables # Generated by iptables-save v1.4.7 on Mon Mar 17 06:02:02 2014 *filter :INPUT ACCEPT [0:0] :FORWARD ACCEPT [0:0] :OUTPUT ACCEPT [999012:2307279867] -A INPUT -p tcp -m tcp --dport 9090 -j ACCEPT -A INPUT -p tcp -m tcp --dport 8250 -j ACCEPT -A INPUT -p tcp -m tcp --dport 7080 -j ACCEPT -A INPUT -p tcp -m tcp --dport 8080 -j ACCEPT -A INPUT -p tcp -m tcp --dport 111 -j ACCEPT -A INPUT -p udp -m udp --dport 111 -j ACCEPT -A INPUT -p tcp -m tcp --dport 2049 -j ACCEPT -A INPUT -p tcp -m tcp --dport 32803 -j ACCEPT -A INPUT -p udp -m udp --dport 32769 -j ACCEPT -A INPUT -p tcp -m tcp --dport 892 -j ACCEPT -A INPUT -p udp -m udp --dport 892 -j ACCEPT -A INPUT -p tcp -m tcp --dport 875 -j ACCEPT -A INPUT -p udp -m udp --dport 875 -j ACCEPT -A INPUT -p tcp -m tcp --dport 662 -j ACCEPT -A INPUT -p udp -m udp --dport 662 -j ACCEPT -A INPUT -m state --state RELATED,ESTABLISHED -j ACCEPT -A INPUT -p icmp -j ACCEPT -A INPUT -i lo -j ACCEPT -A INPUT -p tcp -m state --state NEW -m tcp --dport 22 -j ACCEPT -A INPUT -j REJECT --reject-with icmp-host-prohibited -A FORWARD -j REJECT --reject-with icmp-host-prohibited COMMIT # Completed on Mon Mar 17 06:02:02 2014 完整日志文件请见：http://hctysoft.com/management-server.log 从日志中分析来看在启动Console Proxy VM的报错，下面是我截取的一些关键的management-server日志片段： catalina.out: INFO [cloud.cluster.ClusterManagerImpl] (Timer-2:) register cluster listener class com.cloud.cluster.LockMasterListener INFO [cloud.cluster.ClusterManagerImpl] (Timer-2:) Trying to connect to 192.168.11.61 ERROR [cloud.cluster.ClusterManagerImpl] (Timer-2:) Unable to ping management server at 192.168.11.61:9090 due to ConnectException java.net.ConnectException: Connection refused at sun.nio.ch.Net.connect0(Native Method) at sun.nio.ch.Net.connect(Net.java:465) at sun.nio.ch.Net.connect(Net.java:457) at sun.nio.ch.SocketChannelImpl.connect(SocketChannelImpl.java:670) at com.cloud.cluster.ClusterManagerImpl.pingManagementNode(ClusterManagerImpl.java:1405) at com.cloud.cluster.ClusterManagerImpl.pingManagementNode(ClusterManagerImpl.java:1384) at com.cloud.cluster.ClusterManagerImpl.checkConflicts(ClusterManagerImpl.java:1461) at com.cloud.cluster.ClusterManagerImpl.configure(ClusterManagerImpl.java:1347) at com.cloud.utils.component.ComponentContext.initComponentsLifeCycle(ComponentContext.java:111) at com.cloud.servlet.CloudStartupServlet$1.run(CloudStartupServlet.java:54) at java.util.TimerThread.mainLoop(Timer.java:555) at java.util.TimerThread.run(Timer.java:505) management-server.log 2014-03-22 22:45:57,912 INFO
Re: Re: [求助] v4.2.1 启动报错
根据你提供的日志信息，你的DB里面已经存在了host = 192.168.11.61 的management server配置，你是不是重装cloudstack没有初始化DB呢，如果是新装环境，建议你做以下步奏： 1、停止cloudstack-management 服务 2、初始化mysql数据库，使用 cloudstack-setup-databases cloud:set cloud user passwd@localhost --deploy-as=root:mysql root user password 3、 cloudstack-setup-management 然后再配置试试 ganglin_lan 发件人： 风南 发送时间： 2014-03-22 23:17 收件人： ganglin_lan 主题： Re: Re: [求助] v4.2.1 启动报错 iptables关了貌似还是一样的问题，截了一段异常日志： 2014-03-23 07:14:52,069 DEBUG [allocator.impl.FirstFitAllocator] (secstorage-1:FirstFitRoutingAllocator) Looking for hosts in dc: 1 pod:1 cluster:1 2014-03-23 07:14:52,071 DEBUG [allocator.impl.FirstFitAllocator] (secstorage-1:FirstFitRoutingAllocator) FirstFitAllocator has 1 hosts to check for allocation: [Host[-1-Routing]] 2014-03-23 07:14:52,073 DEBUG [allocator.impl.FirstFitAllocator] (secstorage-1:FirstFitRoutingAllocator) Found 1 hosts for allocation after prioritization: [Host[-1-Routing]] 2014-03-23 07:14:52,073 DEBUG [allocator.impl.FirstFitAllocator] (secstorage-1:FirstFitRoutingAllocator) Looking for speed=500Mhz, Ram=256 2014-03-23 07:14:52,076 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-03-23 07:14:52,078 DEBUG [cloud.capacity.CapacityManagerImpl] (secstorage-1:FirstFitRoutingAllocator) Hosts's actual total CPU: 27744 and CPU after applying overprovisioning: 27744 2014-03-23 07:14:52,078 DEBUG [cloud.capacity.CapacityManagerImpl] (secstorage-1:FirstFitRoutingAllocator) Free CPU: 27744 , Requested CPU: 500 2014-03-23 07:14:52,078 DEBUG [cloud.capacity.CapacityManagerImpl] (secstorage-1:FirstFitRoutingAllocator) Free RAM: 3773286656 , Requested RAM: 268435456 2014-03-23 07:14:52,078 DEBUG [cloud.capacity.CapacityManagerImpl] (secstorage-1:FirstFitRoutingAllocator) Host has enough CPU and RAM available 2014-03-23 07:14:52,078 DEBUG [cloud.capacity.CapacityManagerImpl] (secstorage-1:FirstFitRoutingAllocator) STATS: Can alloc CPU from host: 1, used: 0, reserved: 0, actual total: 27744, total with overprovisioning: 27744; requested cpu:500,alloc_from_last_host?:false ,considerReservedCapacity?: true 2014-03-23 07:14:52,078 DEBUG [cloud.capacity.CapacityManagerImpl] (secstorage-1:FirstFitRoutingAllocator) STATS: Can alloc MEM from host: 1, used: 0, reserved: 0, total: 3773286656; requested mem: 268435456,alloc_from_last_host?:false ,considerReservedCapacity?: true 2014-03-23 07:14:52,078 DEBUG [allocator.impl.FirstFitAllocator] (secstorage-1:FirstFitRoutingAllocator) Found a suitable host, adding to list: 1 2014-03-23 07:14:52,078 DEBUG [allocator.impl.FirstFitAllocator] (secstorage-1:FirstFitRoutingAllocator) Host Allocator returning 1 suitable hosts 2014-03-23 07:14:52,079 DEBUG [cloud.deploy.DeploymentPlanningManagerImpl] (secstorage-1:null) Checking suitable pools for volume (Id, Type): (296,ROOT) 2014-03-23 07:14:52,079 DEBUG [cloud.deploy.DeploymentPlanningManagerImpl] (secstorage-1:null) We need to allocate new storagepool for this volume 2014-03-23 07:14:52,079 DEBUG [cloud.deploy.DeploymentPlanningManagerImpl] (secstorage-1:null) Calling StoragePoolAllocators to find suitable pools 2014-03-23 07:14:52,080 DEBUG [storage.allocator.LocalStoragePoolAllocator] (secstorage-1:null) LocalStoragePoolAllocator trying to find storage pool to fit the vm 2014-03-23 07:14:52,081 DEBUG [storage.allocator.LocalStoragePoolAllocator] (secstorage-1:null) LocalStoragePoolAllocator returning 0 suitable storage pools 2014-03-23 07:14:52,082 DEBUG [storage.allocator.ClusterScopeStoragePoolAllocator] (secstorage-1:null) ClusterScopeStoragePoolAllocator looking for storage pool 2014-03-23 07:14:52,082 DEBUG [storage.allocator.ZoneWideStoragePoolAllocator] (secstorage-1:null) ZoneWideStoragePoolAllocator to find storage pool 2014-03-23 07:14:52,082 DEBUG [cloud.deploy.DeploymentPlanningManagerImpl] (secstorage-1:null) No suitable pools found for volume: Vol[296|vm=295|ROOT] under cluster: 1 2014-03-23 07:14:52,082 DEBUG [cloud.deploy.DeploymentPlanningManagerImpl] (secstorage-1:null) No suitable pools found 2014-03-23 07:14:52,082 DEBUG [cloud.deploy.DeploymentPlanningManagerImpl] (secstorage-1:null) No suitable storagePools found under this Cluster: 1 2014-03-23 07:14:52,083 DEBUG [cloud.deploy.DeploymentPlanningManagerImpl] (secstorage-1:null) Could not find suitable Deployment Destination for this VM under any clusters, returning. 2014-03-23 07:14:52,083 DEBUG [cloud.deploy.FirstFitPlanner] (secstorage-1:null) Searching all possible resources under this Zone: 1 2014-03-23 07:14:52,084 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-03-23 07:14:52,086 DEBUG [cloud.deploy.FirstFitPlanner] (secstorage-1:null) Removing from the clusterId list
Re: 答复: 物理主机上能做NFS共享吗
幸好你有lvm元数据备份文件，也许还能恢复。我曾经恢复过lvm卷，lvm卷信息丢失情况各不一样，我后来做实验模拟手工删除lvm一个卷，重启之后就lvm就报错了，详细的恢复过程请看我当时记录的文章http://blog.chinaunix.net/uid-26230811-id-3267323.html ，另外可以参考这篇：http://blog.chinaunix.net/uid-26230811-id-3268366.html ganglin_lan 发件人： 许叁征 发送时间： 2014-03-21 14:46 收件人： users-cn@cloudstack.apache.org; 'xushy1' 主题： 答复: Re: 物理主机上能做NFS共享吗 好，大家一起来解决问题，不过我现在发现是ISCSI服务端发布的存储存在问题，主机找不到虚拟机磁盘组，一直是I/O错误 ，。 Mar 20 15:21:07 localhost tgtd: bs_rdwr_request(126) io error 0x150483c0 28 -1 4096 167480688640, Input/output error Mar 20 15:21:07 localhost tgtd: bs_rdwr_request(126) io error 0x150483c0 28 -1 512 1151535746560, Input/output error Mar 20 15:21:07 localhost tgtd: bs_rdwr_request(126) io error 0xafa1500 28 -1 512 1151539949056, Input/output error Mar 20 15:21:07 localhost tgtd: bs_rdwr_request(126) io error 0x150483c0 28 -1 512 1151535746560, Input/output error Mar 20 15:21:07 localhost tgtd: bs_rdwr_request(126) io error 0x150483c0 28 -1 4096 166025674752, Input/output error Mar 20 15:21:07 localhost tgtd: bs_rdwr_request(126) io error 0x150483c0 28 -1 4096 166025674752, Input/output error Mar 20 15:21:07 localhost kernel: scsi 1:2:1:0: rejecting I/O to dead device Mar 20 15:21:08 localhost last message repeated 5 times Mar 20 15:21:08 localhost tgtd: bs_rdwr_request(126) io error 0x150483c0 28 -1 4096 167480688640, Input/output error Mar 20 15:21:08 localhost tgtd: bs_rdwr_request(126) io error 0x150483c0 28 -1 512 1151535746560, Input/output error 后面重启了tgtd的主机，发现机器找不到逻辑卷vg (sdc 实际上有17TB左右，是提供给虚拟化的存储使用) 奇怪的是，它为什么找不到虚拟磁盘组，vg1 各位大神有什么办法 能恢复逻辑卷吗？ VG #PV #LV #SN Attr VSize VFree vg 1 10 0 wz--n- 21.83T 14.70T [root@localhost ~]# blkid /dev/sda1: LABEL=/boot UUID=600c84c5-cd60-4896-9a0f-56f70f585bec TYPE=ext3 /dev/sda2: TYPE=swap LABEL=SWAP-sda2 /dev/sda3: LABEL=/ UUID=51146b28-b3c5-44c4-94bc-6a216a35604d TYPE=ext3 /dev/sdb1: UUID=pTXddZ-O0pw-weQr-MXqs-ExLo-sUAc-CsECL6 TYPE=lvm2pv [root@localhost ~]# fdisk -l Disk /dev/sda: 299.4 GB, 299439751168 bytes 255 heads, 63 sectors/track, 36404 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start End Blocks Id System /dev/sda1 * 1 25 200781 83 Linux /dev/sda2 26818465537167+ 82 Linux swap / Solaris /dev/sda38185 36404 226677150 83 Linux WARNING: GPT (GUID Partition Table) detected on '/dev/sdb'! The util fdisk doesn't support GPT. Use GNU Parted. WARNING: The size of this disk is 24.0 TB (24000277250048 bytes). DOS partition table format can not be used on drives for volumes larger than 2.2 TB (2199023255040 bytes). Use parted(1) and GUID partition table format (GPT). Disk /dev/sdb: 24000.2 GB, 24000277250048 bytes 255 heads, 63 sectors/track, 2917867 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start End Blocks Id System /dev/sdb1 1 267350 2147483647+ ee EFI GPT WARNING: GPT (GUID Partition Table) detected on '/dev/sdc'! The util fdisk doesn't support GPT. Use GNU Parted. Disk /dev/sdc: 18000.2 GB, 18000207937536 bytes 255 heads, 63 sectors/track, 2188400 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Disk /dev/sdc doesn't contain a valid partition table [root@localhost ~]# vgcfgrestore --file /etc/lvm/backup/vg1 vg1 Couldn't find device with uuid KyGefy-Vctk-GjiG-OTMr-jF8W-JQ2A-Qmcila. Cannot restore Volume Group vg1 with 1 PVs marked as missing. Restore failed. 许叁征 网宿科技股份有限公司 厦门分公司 运营技术支持部 Tel:13860125907 E-mail:x...@chinanetcenter.com http://www.chinanetcenter.com 分公司：北京-上海-广州-深圳 免费咨询热线:800-820-0001 网宿科技 --卓越的互联网业务平台提供商 -邮件原件- 发件人: users-cn-return-3276-xusz=chinanetcenter@cloudstack.apache.org [mailto:users-cn-return-3276-xusz=chinanetcenter@cloudstack.apache.org] 代表 網勁科技 黃奕璽 / Carl Huang 发送时间: 2014年3月21日星期五 10:56 收件人: users-cn@cloudstack.apache.org; xushy1 主题: Re: Re: 物理主机上能做NFS共享吗 可以 2014-03-19 18:28 GMT+08:00 徐诗云 xus...@yonyou.com: 我是没存储空间了，想拿主机上的空间做一级 二级存储 发件人： linux...@gmail.com 发送时间： 2014-03-19 17:36 收件人： users-cn; xushy1 主题： Re: 物理主机上能做NFS共享吗 请具体描述下你的问题 一般情况下物理主机是可以做NFS共享 2014-03-19 17:25 GMT+08:00 徐诗云 xus...@yonyou.com: -- 白清杰 (Born Bai) 北京开源愿景信息技术有限公司 Mail: linux...@gmail.com -- eDynamics 網勁科技 總管理處 主任 黃奕璽 Carl Huang 電話：+886-2-8797-6373 分機：6302 傳真：+886-2-8797-6272 E-Mail：carl_hu...@edyna.com 台北總公司：台北市內湖區瑞光路 513 巷 28 號 7 樓 來寶島 www.laibaodao.com oBuy全買網 www.obuy.tw 荷包網 www.joinbao.com CityTalk城市通 www.citytalk.tw
Re: 答复: 取消维护ISCSI存储提示错误
这应该不是cloudstack的问题，存储出问题了
ganglin_lan
发件人： 许叁征
发送时间： 2014-03-21 16:27
收件人： users-cn@cloudstack.apache.org
主题： 答复: 取消维护ISCSI存储提示错误
贴一下详细的日志，供大家分析下
Task failed! Task record: uuid:
513c8151-9139-7a39-6b24-0dedd5def7db
nameLabel: Async.VM.start_on
nameDescription:
allowedOperations: []
currentOperations: {}
created: Fri Mar 21 16:26:32 CST 2014
finished: Fri Mar 21 16:26:32 CST 2014
status: FAILURE
residentOn: com.xensource.xenapi.Host@c363ddd0
progress: 1.0
type: none/
result:
errorInfo: [VM_REQUIRES_SR,
OpaqueRef:bd805ae5-0a58-f2f7-7637-9f1d98409861,
OpaqueRef:1ac71e7e-ca08-710d-4a0d-ea5f85764413]
otherConfig: {}
subtaskOf: com.xensource.xenapi.Task@aaf13f6f
subtasks: []
at
com.cloud.hypervisor.xen.resource.CitrixResourceBase.checkForSuccess(CitrixResourceBase.java:3142)
at
com.cloud.hypervisor.xen.resource.CitrixResourceBase.startVM(CitrixResourceBase.java:3254)
at
com.cloud.hypervisor.xen.resource.CitrixResourceBase.execute(CitrixResourceBase.java:1292)
at
com.cloud.hypervisor.xen.resource.CitrixResourceBase.executeRequest(CitrixResourceBase.java:497)
at
com.cloud.hypervisor.xen.resource.XenServer56Resource.executeRequest(XenServer56Resource.java:73)
at
com.cloud.agent.manager.DirectAgentAttache$Task.run(DirectAgentAttache.java:191)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
at java.util.concurrent.FutureTask.run(FutureTask.java:166)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:165)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:266)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:679)
2014-03-21 16:25:12,910 WARN [xen.resource.CitrixResourceBase]
(DirectAgent-193:null) Catch Exception: class
com.cloud.utils.exception.CloudRuntimeException due to
com.cloud.utils.exception.CloudRuntimeException: Unable to start
VM(i-2-64691-VM) on host(ea339c35-2574-4813-b873-35c24f47e5e1) due to Task
failed! Task record: uuid: 513c8151-9139-7a39-6b24-0dedd5def7db
nameLabel: Async.VM.start_on
nameDescription:
allowedOperations: []
currentOperations: {}
created: Fri Mar 21 16:26:32 CST 2014
finished: Fri Mar 21 16:26:32 CST 2014
status: FAILURE
residentOn: com.xensource.xenapi.Host@c363ddd0
progress: 1.0
type: none/
result:
errorInfo: [VM_REQUIRES_SR,
OpaqueRef:bd805ae5-0a58-f2f7-7637-9f1d98409861,
OpaqueRef:1ac71e7e-ca08-710d-4a0d-ea5f85764413]
otherConfig: {}
subtaskOf: com.xensource.xenapi.Task@aaf13f6f
subtasks: []
com.cloud.utils.exception.CloudRuntimeException: Unable to start
VM(i-2-64691-VM) on host(ea339c35-2574-4813-b873-35c24f47e5e1) due to Task
failed! Task record: uuid: 513c8151-9139-7a39-6b24-0dedd5def7db
nameLabel: Async.VM.start_on
nameDescription:
allowedOperations: []
currentOperations: {}
created: Fri Mar 21 16:26:32 CST 2014
finished: Fri Mar 21 16:26:32 CST 2014
status: FAILURE
residentOn: com.xensource.xenapi.Host@c363ddd0
progress: 1.0
type: none/
result:
errorInfo: [VM_REQUIRES_SR,
OpaqueRef:bd805ae5-0a58-f2f7-7637-9f1d98409861,
OpaqueRef:1ac71e7e-ca08-710d-4a0d-ea5f85764413]
otherConfig: {}
subtaskOf: com.xensource.xenapi.Task@aaf13f6f
subtasks: []
at
com.cloud.hypervisor.xen.resource.CitrixResourceBase.startVM(CitrixResourceBase.java:3265)
at
com.cloud.hypervisor.xen.resource.CitrixResourceBase.execute(CitrixResourceBase.java:1292)
at
com.cloud.hypervisor.xen.resource.CitrixResourceBase.executeRequest(CitrixResourceBase.java:497)
at
com.cloud.hypervisor.xen.resource.XenServer56Resource.executeRequest(XenServer56Resource.java:73)
at
com.cloud.agent.manager.DirectAgentAttache$Task.run(DirectAgentAttache.java:191)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
at java.util.concurrent.FutureTask.run(FutureTask.java:166)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:165)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:266)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110
Re: 答复: 取消维护ISCSI存储提示错误
试试 xe pbd-plug uuid=4e2cc197-fdec-5688-131a-746e0fc16262 ?
ganglin_lan
发件人： 许叁征
发送时间： 2014-03-21 19:50
收件人： users-cn@cloudstack.apache.org; 'ganglin_lan'
主题： 答复: 答复: 取消维护ISCSI存储提示错误
是的，存储出问题， 不过存储问题已解决。之前把xenserver
的ISCSI不小心给forget掉了，现在找不到这个磁盘，重新通过XENserver面板添加的ISCSI可以显示name
35510305-6f6f-3ca0-90ae-797b47b29ae3
但是UUID却不能变成原来XENserver“4e2cc197-fdec-5688-131a-746e0fc16262”
尝试以下办法 添加 提示出错，有什么办法 可以恢复cloudstack正常连接xenserver上的iscsi, ？让原来的使用iscsi存储启动起来。
[root@xen122 ~]# xe pbd-create sr-uuid=4e2cc197-fdec-5688-131a-746e0fc16262
host-uuid=ea339c35-2574-4813-b873-35c24f47e5e1
device-config:target=192.168.0.28
device-config:targetIQN=iqn.2014-01.net.xsz:iscsi.disk0-target
device-config:SCSIlid=35510305-6f6f-3ca0-90ae-797b47b29ae3
The uuid you supplied was invalid.
type: SR
uuid: 4e2cc197-fdec-5688-131a-746e0fc16262
许叁征
网宿科技股份有限公司 厦门分公司 运营技术支持部
Tel:13860125907
E-mail:x...@chinanetcenter.com
http://www.chinanetcenter.com
分公司：北京-上海-广州-深圳
免费咨询热线:800-820-0001
网宿科技 --卓越的互联网业务平台提供商
-邮件原件-
发件人: users-cn-return-3281-xusz=chinanetcenter@cloudstack.apache.org
[mailto:users-cn-return-3281-xusz=chinanetcenter@cloudstack.apache.org] 代表
ganglin_lan
发送时间: 2014年3月21日星期五 16:46
收件人: users-cn
主题: Re: 答复: 取消维护ISCSI存储提示错误
这应该不是cloudstack的问题，存储出问题了
ganglin_lan
发件人： 许叁征
发送时间： 2014-03-21 16:27
收件人： users-cn@cloudstack.apache.org
主题： 答复: 取消维护ISCSI存储提示错误
贴一下详细的日志，供大家分析下
Task failed! Task record: uuid:
513c8151-9139-7a39-6b24-0dedd5def7db
nameLabel: Async.VM.start_on
nameDescription:
allowedOperations: []
currentOperations: {}
created: Fri Mar 21 16:26:32 CST 2014
finished: Fri Mar 21 16:26:32 CST 2014
status: FAILURE
residentOn: com.xensource.xenapi.Host@c363ddd0
progress: 1.0
type: none/
result:
errorInfo: [VM_REQUIRES_SR,
OpaqueRef:bd805ae5-0a58-f2f7-7637-9f1d98409861,
OpaqueRef:1ac71e7e-ca08-710d-4a0d-ea5f85764413]
otherConfig: {}
subtaskOf: com.xensource.xenapi.Task@aaf13f6f
subtasks: []
at
com.cloud.hypervisor.xen.resource.CitrixResourceBase.checkForSuccess(CitrixResourceBase.java:3142)
at
com.cloud.hypervisor.xen.resource.CitrixResourceBase.startVM(CitrixResourceBase.java:3254)
at
com.cloud.hypervisor.xen.resource.CitrixResourceBase.execute(CitrixResourceBase.java:1292)
at
com.cloud.hypervisor.xen.resource.CitrixResourceBase.executeRequest(CitrixResourceBase.java:497)
at
com.cloud.hypervisor.xen.resource.XenServer56Resource.executeRequest(XenServer56Resource.java:73)
at
com.cloud.agent.manager.DirectAgentAttache$Task.run(DirectAgentAttache.java:191)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
at java.util.concurrent.FutureTask.run(FutureTask.java:166)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:165)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:266)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:679)
2014-03-21 16:25:12,910 WARN [xen.resource.CitrixResourceBase]
(DirectAgent-193:null) Catch Exception: class
com.cloud.utils.exception.CloudRuntimeException due to
com.cloud.utils.exception.CloudRuntimeException: Unable to start
VM(i-2-64691-VM) on host(ea339c35-2574-4813-b873-35c24f47e5e1) due to Task
failed! Task record: uuid: 513c8151-9139-7a39-6b24-0dedd5def7db
nameLabel: Async.VM.start_on
nameDescription:
allowedOperations: []
currentOperations: {}
created: Fri Mar 21 16:26:32 CST 2014
finished: Fri Mar 21 16:26:32 CST 2014
status: FAILURE
residentOn: com.xensource.xenapi.Host@c363ddd0
progress: 1.0
type: none/
result:
errorInfo: [VM_REQUIRES_SR,
OpaqueRef:bd805ae5-0a58-f2f7-7637-9f1d98409861,
OpaqueRef:1ac71e7e-ca08-710d-4a0d-ea5f85764413]
otherConfig: {}
subtaskOf: com.xensource.xenapi.Task@aaf13f6f
subtasks: []
com.cloud.utils.exception.CloudRuntimeException: Unable to start
VM(i-2-64691-VM) on host(ea339c35-2574-4813-b873-35c24f47e5e1) due to Task
failed! Task record: uuid: 513c8151-9139-7a39-6b24-0dedd5def7db
nameLabel: Async.VM.start_on
nameDescription:
allowedOperations: []
currentOperations: {}
created: Fri Mar 21 16:26:32 CST 2014
finished: Fri Mar 21 16:26:32 CST 2014
status: FAILURE
residentOn: com.xensource.xenapi.Host@c363ddd0
progress: 1.0
type: none/
result
回复: Re: 执行cloud-setup-agent,报不能启动agent错误，请大家帮忙分析分析，谢谢
find 一下cloud-agent 的pid文件是否存在，如果存在删除再试试
ganglin_lan
发件人： linux...@gmail.com
发送时间： 2014-03-20 17:34
收件人： users-cn
主题： Re: 执行cloud-setup-agent,报不能启动agent错误，请大家帮忙分析分析，谢谢
你检查下kvm的cgroup配置文件是不是修改过
2014-03-19 19:27 GMT+08:00 淡看浮华 360736...@qq.com:
我是在vmware workstation8中的一台虚拟机里同时安装了cloudstack4.0.2的管理节点和agent,操作系统为ubuntu12.04
在添加域的过程中,添加主机这一步始终失败,agent.log日志里报错，说不能启动agent
执行cloud-setup-agent,也是报错说不能启动agent
**
具体agent.log日志内容如下：
***
2014-03-19 04:07:51,649 ERROR [cloud.agent.AgentShell] (main:null) Unable to
start agent:
com.cloud.utils.exception.CloudRuntimeException: Cannot recv data: Connection
reset by peer
at
com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.configure(LibvirtComputingResource.java:654)
at com.cloud.agent.Agent.init(Agent.java:163)
at com.cloud.agent.AgentShell.launchAgent(AgentShell.java:559)
at com.cloud.agent.AgentShell.launchAgentFromClassInfo(AgentShell.java:514)
at com.cloud.agent.AgentShell.launchAgent(AgentShell.java:431)
at com.cloud.agent.AgentShell.start(AgentShell.java:589)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:616)
at
org.apache.commons.daemon.support.DaemonLoader.start(DaemonLoader.java:243)
2014-03-19 04:08:22,946 INFO [utils.component.ComponentLocator] (main:null)
Unable to find components.xml
2014-03-19 04:08:22,949 INFO [utils.component.ComponentLocator] (main:null)
Skipping configuration using components.xml
2014-03-19 04:08:22,949 INFO [cloud.agent.AgentShell] (main:null)
Implementation Version is 4.0.2.20130501180711
2014-03-19 04:08:22,950 INFO [cloud.agent.AgentShell] (main:null)
agent.properties found at /etc/cloud/agent/agent.properties
2014-03-19 04:08:22,952 INFO [cloud.agent.AgentShell] (main:null) Defaulting
to using properties file for storage
2014-03-19 04:08:22,958 INFO [cloud.agent.AgentShell] (main:null) Defaulting
to the constant time backoff algorithm
2014-03-19 04:08:23,076 INFO [cloud.agent.Agent] (main:null) id is
2014-03-19 04:08:23,164 INFO
[resource.virtualnetwork.VirtualRoutingResource] (main:null)
VirtualRoutingResource _scriptDir to use: scripts/network/domr/kvm
*
setup.log日志内容如下：
*
DEBUG:root:execute:route -n|awk '/^0.0.0.0/ {print $2,$8}'
DEBUG:root:execute:ifconfig cloudbr0
DEBUG:root:Found default network device:cloudbr0
DEBUG:root:execute:uname -r
DEBUG:root:execute:uname -m
DEBUG:root:execute:hostname -f
DEBUG:root:execute:kvm-ok
DEBUG:root:execute:service apparmor status
DEBUG:root:execute:apparmor_status |grep libvirt
DEBUG:root:Failed to execute:
DEBUG:root:execute:sudo /usr/sbin/service network-manager status
DEBUG:root:Failed to execute:network-manager: unrecognized service
DEBUG:root:execute:route -n|awk '/^0.0.0.0/ {print $2,$8}'
DEBUG:root:execute:ifconfig cloudbr0
DEBUG:root:Found default network device:cloudbr0
DEBUG:root:execute:ifconfig eth0
DEBUG:root:cloudbr0:eth0 already configured
DEBUG:root:execute:sudo /usr/sbin/service network-manager status
DEBUG:root:Failed to execute:network-manager: unrecognized service
DEBUG:root:execute:sudo /usr/sbin/service network-manager stop
DEBUG:root:Failed to execute:network-manager: unrecognized service
DEBUG:root:execute:sudo /usr/sbin/service network-manager status
DEBUG:root:Failed to execute:network-manager: unrecognized service
DEBUG:root:execute:sudo /usr/sbin/service network-manager stop
DEBUG:root:Failed to execute:network-manager: unrecognized service
DEBUG:root:execute:sudo update-rc.d -f network-manager remove
DEBUG:root:execute:ifup cloudbr0
DEBUG:root:execute:sudo /usr/sbin/service libvirt-bin status
DEBUG:root:execute:sudo /usr/sbin/service libvirt-bin stop
DEBUG:root:execute:sudo update-rc.d -f libvirt-bin remove
DEBUG:root:execute:sudo update-rc.d -f libvirt-bin defaults
DEBUG:root:execute:sudo /usr/sbin/service libvirt-bin status
DEBUG:root:execute:sudo /usr/sbin/service libvirt-bin start
DEBUG:root:execute:ufw allow 22
DEBUG:root:execute:ufw allow 1798
DEBUG:root:execute:ufw allow 16509
DEBUG:root:execute:ufw allow proto tcp from any to any port 5900:6100
DEBUG:root:execute:ufw allow proto tcp from any to any port 49152:49216
DEBUG:root:execute:sudo /usr/sbin/service ufw status
DEBUG:root:execute:sudo /usr/sbin/service ufw stop
DEBUG:root:execute:sudo /usr/sbin/service ufw status
DEBUG:root:execute:sudo /usr/sbin/service ufw start
DEBUG:root:execute:sudo /usr/sbin/service cloud-agent status
回复: Re: 请问CloudStack是否支持Mysql之外的其他数据库？比如Oracle？
oracle用的好可以提供很高的性能，用的不好还不如mysql ganglin_lan 发件人： linux...@gmail.com 发送时间： 2014-03-12 11:42 收件人： users-cn 主题： Re: 请问CloudStack是否支持Mysql之外的其他数据库？比如Oracle？ 有免费的为什么还要使用oracle呢？ mysql的性能也是很好的，几百万的访问没有问题 在 2014年3月11日 下午9:18，dong xie xiedon...@gmail.com 写道： 请问CloudStack是否支持Mysql之外的其他数据库？比如Oracle？通过修改其配置或源码是否有这种可能性？谢谢 -- 白清杰 (Born Bai) 北京开源愿景信息技术有限公司 Mail: linux...@gmail.com
