You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users-cn@cloudstack.apache.org by 俄看过 <12...@qq.com> on 2013/06/20 04:21:37 UTC
回复： 回复: 回复： 回复: 回复： 回复: 回复: CloudStack 4.0.2运行后，系统虚拟机无法启动，日志报错
非常感谢！！！ 我先试试。
------------------ 原始邮件 ------------------
发件人: "张晓飞"<zh...@oncloudit.com>;
发送时间: 2013年6月20日(星期四) 上午10:19
收件人: "users-cn"<us...@cloudstack.apache.org>;
主题: 回复: 回复： 回复: 回复： 回复: 回复: CloudStack 4.0.2运行后，系统虚拟机无法启动，日志报错
大概过程是这样的
/etc/init.d/cloudstack-management stop
mysql> drop database cloud;
mysql> drop database cloud_usage;
mysql> drop database cloudbridge;
cloudstack-setup-databases cloud:cloud@localhost --deploy-as=root:密码
/usr/share/cloudstack-common/scripts/storage/secondary/cloud-install-sys-tmplt -m /辅助存储路径 -u
http://download.cloud.com/templates/acton/acton-systemvm-02062012.qcow2.bz2 -h kvm -F
/etc/init.d/cloudstack-management start
2013-06-20
张晓飞
发件人："俄看过" <12...@qq.com>
发送时间：2013-06-20 10:14
主题：回复： 回复: 回复： 回复: 回复: CloudStack 4.0.2运行后，系统虚拟机无法启动，日志报错
收件人："users-cn"<us...@cloudstack.apache.org>
抄送：
我想问一下。
数据库清空是把整个数据库删除掉吗？我应该怎么操作
模版是系统虚拟机模版？
------------------ 原始邮件 ------------------
发件人: "zhang.xiaofei"<zh...@oncloudit.com>;
发送时间: 2013年6月20日(星期四) 上午10:05
收件人: "users-cn"<us...@cloudstack.apache.org>;
主题: 回复: 回复： 回复: 回复: CloudStack 4.0.2运行后，系统虚拟机无法启动，日志报错
我遇到这种情况 都是把数据库清空 模版给删掉 重新导入数据库 注册下模版 你要不也试试？
或者你是改过内存后 cloudstack-agent得重启下？
2013-06-20
zhang.xiaofei
发件人："俄看过" <12...@qq.com>
发送时间：2013-06-20 09:49
主题：回复： 回复: 回复: CloudStack 4.0.2运行后，系统虚拟机无法启动，日志报错
收件人："users-cn"<us...@cloudstack.apache.org>
抄送：
可以，我看网上好多人都这样做
------------------ 原始邮件 ------------------
发件人: "zhang.xiaofei"<zh...@oncloudit.com>;
发送时间: 2013年6月20日(星期四) 上午9:46
收件人: "users-cn"<us...@cloudstack.apache.org>;
主题: 回复: 回复: CloudStack 4.0.2运行后，系统虚拟机无法启动，日志报错
虚拟机下 还可以建虚拟机？
2013-06-20
zhang.xiaofei
发件人：evanitsharp <ev...@gmail.com>
发送时间：2013-06-20 09:16
主题：回复: CloudStack 4.0.2运行后，系统虚拟机无法启动，日志报错
收件人："CloudStack社区"<us...@cloudstack.apache.org>
抄送：
冰天雪地跪求帮忙看看。
evanitsharp
发件人： evanitsharp
发送时间： 2013-06-18 17:09
收件人： CloudStack社区
主题： CloudStack 4.0.2运行后，系统虚拟机无法启动，日志报错
CloudStack 4.0.2运行后，系统虚拟机无法启动，日志报错，如下，怎么解决。
之前认为是Hypervisor分配的内存太少，但是内存加到3G，这个问题仍然在，求大神给予指导。
我的环境是这样的：管理服务器、Hypervisor基础设施（XenServer）都装在VMware二次虚拟环境下。
2013-06-18 02:04:57,680 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-395-TEST]Scope=interface com.cloud.dc.DataCenter; id=1
at com.cloud.vm.VirtualMachineManagerImpl.advanceStart(VirtualMachineManagerImpl.java:734)
at com.cloud.vm.VirtualMachineManagerImpl.start(VirtualMachineManagerImpl.java:472)
at com.cloud.vm.VirtualMachineManagerImpl.start(VirtualMachineManagerImpl.java:465)
at com.cloud.storage.secondary.SecondaryStorageManagerImpl.startSecStorageVm(SecondaryStorageManagerImpl.java:257)
at com.cloud.storage.secondary.SecondaryStorageManagerImpl.allocCapacity(SecondaryStorageManagerImpl.java:684)
at com.cloud.storage.secondary.SecondaryStorageManagerImpl.expandPool(SecondaryStorageManagerImpl.java:1310)
at com.cloud.secstorage.PremiumSecondaryStorageManagerImpl.scanPool(PremiumSecondaryStorageManagerImpl.java:119)
at com.cloud.secstorage.PremiumSecondaryStorageManagerImpl.scanPool(PremiumSecondaryStorageManagerImpl.java:50)
at com.cloud.vm.SystemVmLoadScanner.loadScan(SystemVmLoadScanner.java:106)
at com.cloud.vm.SystemVmLoadScanner.access$100(SystemVmLoadScanner.java:34)
at com.cloud.vm.SystemVmLoadScanner$1.reallyRun(SystemVmLoadScanner.java:83)
at com.cloud.vm.SystemVmLoadScanner$1.run(SystemVmLoadScanner.java:73)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:351)
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:178)
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:722)
2013-06-18 02:04:57,682 INFO [storage.secondary.SecondaryStorageManagerImpl] (secstorage-1:null) Unable to start secondary storage vm for standby capacity, secStorageVm vm Id : 395, will recycle it and start a new one
2013-06-18 01:59:35,515 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-TEST]Scope=interface com.cloud.dc.DataCenter; id=1
at com.cloud.vm.VirtualMachineManagerImpl.advanceStart(VirtualMachineManagerImpl.java:734)
at com.cloud.vm.VirtualMachineManagerImpl.start(VirtualMachineManagerImpl.java:472)
at com.cloud.vm.VirtualMachineManagerImpl.start(VirtualMachineManagerImpl.java:465)
at com.cloud.consoleproxy.ConsoleProxyManagerImpl.startProxy(ConsoleProxyManagerImpl.java:627)
at com.cloud.consoleproxy.ConsoleProxyManagerImpl.allocCapacity(ConsoleProxyManagerImpl.java:1164)
at com.cloud.consoleproxy.ConsoleProxyManagerImpl.expandPool(ConsoleProxyManagerImpl.java:1981)
at com.cloud.consoleproxy.ConsoleProxyManagerImpl.expandPool(ConsoleProxyManagerImpl.java:173)
at com.cloud.vm.SystemVmLoadScanner.loadScan(SystemVmLoadScanner.java:113)
at com.cloud.vm.SystemVmLoadScanner.access$100(SystemVmLoadScanner.java:34)
at com.cloud.vm.SystemVmLoadScanner$1.reallyRun(SystemVmLoadScanner.java:83)
at com.cloud.vm.SystemVmLoadScanner$1.run(SystemVmLoadScanner.java:73)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:351)
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:178)
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:722)
evanitsharp
回复: 回复: CloudStack 4.0.2运行后，系统虚拟机无法启动，日志报错
Posted by evanitsharp <ev...@gmail.com>.
解决了，将准备系统虚拟机模板的命令由/usr/lib64/cloud/common/scripts/storage/secondary/cloud-install-sys-tmplt -m /export/secondary/ -u file:///zhanglei/install/acton-systemvm-02062012.vhd.bz2 -h xenserver -F
改成：
/usr/lib64/cloud/common/scripts/storage/secondary/cloud-install-sys-tmplt -m /export/secondary/ -u http://192.168.0.101:8080/acton-systemvm-02062012.vhd.bz2 -h xenserver -F
原来，不能以file:///的方式来上传模板。
但是以file:///的方式却给了提示：Successfully installed system VM template to....
真是误人子弟！！！
evanitsharp
From: 俄看过
Date: 2013-06-20 10:21
To: users-cn
Subject: 回复： 回复: 回复： 回复: 回复： 回复: 回复: CloudStack 4.0.2运行后，系统虚拟机无法启动，日志报错
非常感谢！！！ 我先试试。
------------------ 原始邮件 ------------------
发件人: "张晓飞"<zh...@oncloudit.com>;
发送时间: 2013年6月20日(星期四) 上午10:19
收件人: "users-cn"<us...@cloudstack.apache.org>;
主题: 回复: 回复： 回复: 回复： 回复: 回复: CloudStack 4.0.2运行后，系统虚拟机无法启动，日志报错
大概过程是这样的
/etc/init.d/cloudstack-management stop
mysql> drop database cloud;
mysql> drop database cloud_usage;
mysql> drop database cloudbridge;
cloudstack-setup-databases cloud:cloud@localhost --deploy-as=root:密码
/usr/share/cloudstack-common/scripts/storage/secondary/cloud-install-sys-tmplt -m /辅助存储路径 -u
http://download.cloud.com/templates/acton/acton-systemvm-02062012.qcow2.bz2 -h kvm -F
/etc/init.d/cloudstack-management start
2013-06-20
张晓飞
发件人："俄看过" <12...@qq.com>
发送时间：2013-06-20 10:14
主题：回复： 回复: 回复： 回复: 回复: CloudStack 4.0.2运行后，系统虚拟机无法启动，日志报错
收件人："users-cn"<us...@cloudstack.apache.org>
抄送：
我想问一下。
数据库清空是把整个数据库删除掉吗？我应该怎么操作
模版是系统虚拟机模版？
------------------ 原始邮件 ------------------
发件人: "zhang.xiaofei"<zh...@oncloudit.com>;
发送时间: 2013年6月20日(星期四) 上午10:05
收件人: "users-cn"<us...@cloudstack.apache.org>;
主题: 回复: 回复： 回复: 回复: CloudStack 4.0.2运行后，系统虚拟机无法启动，日志报错
我遇到这种情况 都是把数据库清空 模版给删掉 重新导入数据库 注册下模版 你要不也试试？
或者你是改过内存后 cloudstack-agent得重启下？
2013-06-20
zhang.xiaofei
发件人："俄看过" <12...@qq.com>
发送时间：2013-06-20 09:49
主题：回复： 回复: 回复: CloudStack 4.0.2运行后，系统虚拟机无法启动，日志报错
收件人："users-cn"<us...@cloudstack.apache.org>
抄送：
可以，我看网上好多人都这样做
------------------ 原始邮件 ------------------
发件人: "zhang.xiaofei"<zh...@oncloudit.com>;
发送时间: 2013年6月20日(星期四) 上午9:46
收件人: "users-cn"<us...@cloudstack.apache.org>;
主题: 回复: 回复: CloudStack 4.0.2运行后，系统虚拟机无法启动，日志报错
虚拟机下 还可以建虚拟机？
2013-06-20
zhang.xiaofei
发件人：evanitsharp <ev...@gmail.com>
发送时间：2013-06-20 09:16
主题：回复: CloudStack 4.0.2运行后，系统虚拟机无法启动，日志报错
收件人："CloudStack社区"<us...@cloudstack.apache.org>
抄送：
冰天雪地跪求帮忙看看。
evanitsharp
发件人： evanitsharp
发送时间： 2013-06-18 17:09
收件人： CloudStack社区
主题： CloudStack 4.0.2运行后，系统虚拟机无法启动，日志报错
CloudStack 4.0.2运行后，系统虚拟机无法启动，日志报错，如下，怎么解决。
之前认为是Hypervisor分配的内存太少，但是内存加到3G，这个问题仍然在，求大神给予指导。
我的环境是这样的：管理服务器、Hypervisor基础设施（XenServer）都装在VMware二次虚拟环境下。
2013-06-18 02:04:57,680 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-395-TEST]Scope=interface com.cloud.dc.DataCenter; id=1
at com.cloud.vm.VirtualMachineManagerImpl.advanceStart(VirtualMachineManagerImpl.java:734)
at com.cloud.vm.VirtualMachineManagerImpl.start(VirtualMachineManagerImpl.java:472)
at com.cloud.vm.VirtualMachineManagerImpl.start(VirtualMachineManagerImpl.java:465)
at com.cloud.storage.secondary.SecondaryStorageManagerImpl.startSecStorageVm(SecondaryStorageManagerImpl.java:257)
at com.cloud.storage.secondary.SecondaryStorageManagerImpl.allocCapacity(SecondaryStorageManagerImpl.java:684)
at com.cloud.storage.secondary.SecondaryStorageManagerImpl.expandPool(SecondaryStorageManagerImpl.java:1310)
at com.cloud.secstorage.PremiumSecondaryStorageManagerImpl.scanPool(PremiumSecondaryStorageManagerImpl.java:119)
at com.cloud.secstorage.PremiumSecondaryStorageManagerImpl.scanPool(PremiumSecondaryStorageManagerImpl.java:50)
at com.cloud.vm.SystemVmLoadScanner.loadScan(SystemVmLoadScanner.java:106)
at com.cloud.vm.SystemVmLoadScanner.access$100(SystemVmLoadScanner.java:34)
at com.cloud.vm.SystemVmLoadScanner$1.reallyRun(SystemVmLoadScanner.java:83)
at com.cloud.vm.SystemVmLoadScanner$1.run(SystemVmLoadScanner.java:73)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:351)
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:178)
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:722)
2013-06-18 02:04:57,682 INFO [storage.secondary.SecondaryStorageManagerImpl] (secstorage-1:null) Unable to start secondary storage vm for standby capacity, secStorageVm vm Id : 395, will recycle it and start a new one
2013-06-18 01:59:35,515 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-TEST]Scope=interface com.cloud.dc.DataCenter; id=1
at com.cloud.vm.VirtualMachineManagerImpl.advanceStart(VirtualMachineManagerImpl.java:734)
at com.cloud.vm.VirtualMachineManagerImpl.start(VirtualMachineManagerImpl.java:472)
at com.cloud.vm.VirtualMachineManagerImpl.start(VirtualMachineManagerImpl.java:465)
at com.cloud.consoleproxy.ConsoleProxyManagerImpl.startProxy(ConsoleProxyManagerImpl.java:627)
at com.cloud.consoleproxy.ConsoleProxyManagerImpl.allocCapacity(ConsoleProxyManagerImpl.java:1164)
at com.cloud.consoleproxy.ConsoleProxyManagerImpl.expandPool(ConsoleProxyManagerImpl.java:1981)
at com.cloud.consoleproxy.ConsoleProxyManagerImpl.expandPool(ConsoleProxyManagerImpl.java:173)
at com.cloud.vm.SystemVmLoadScanner.loadScan(SystemVmLoadScanner.java:113)
at com.cloud.vm.SystemVmLoadScanner.access$100(SystemVmLoadScanner.java:34)
at com.cloud.vm.SystemVmLoadScanner$1.reallyRun(SystemVmLoadScanner.java:83)
at com.cloud.vm.SystemVmLoadScanner$1.run(SystemVmLoadScanner.java:73)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:351)
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:178)
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:722)
evanitsharp