回复: Re: 两个系统VM在web ui中看到一直在创建-启动-删除，一直不停的循环
删除后依旧。 zb1019095...@163.com 发件人： hand...@126.com 发送时间： 2015-03-25 10:07 收件人： users-cn@cloudstack.apache.org 主题： Re: 两个系统VM在web ui中看到一直在创建-启动-删除，一直不停的循环 cpvm删掉，重新创建一下 On Mar 25, 2015, at 10:05 AM, zb1019095...@163.com zb1019095...@163.com wrote: 两个系统VM能看到正常启动，但是在web ui中vnc无法连接查看，提示超时，有什么原因导致呢？ libvirt和qemu的配置已经照着官网文档的确认过几次配置无误了。 iptables里也尝试过删除所有规则，允许所有流量通过了。 日志里看不出原因。 搭建环境：Centos6.5+cloudstack4.4.2,高级网络模式 管理端和agent端在同一台电脑上，有两张网卡，管理流量和guest流量走cloudbr0，公共流量走cloudbr1。cloudbr0和cloudbr1所在交换机端口均设置为trunk型，cloudbr0允许guest范围内的vlan id通过， cloudbr1允许公共流量vlan id 10通过。 在管理端上能ping通两个系统VM。
hyper-v 虚拟机控制台无法打开
大家好！！ 我在win2012 r2上 cp vm运行正常，公用IP和专用IP可正常ping通，但是在CS上，虚拟机控制台无法正常打开。 错误：Access is denied for the console session. Please close the window and retry again hyper-v agent的版本是4.4.3 CS版本是4.4.2 此问题可有解，辛苦了！！ -- name: 程少锋 phone:13925096693 E-mail:shaofeng.cheng 用心合作，真诚沟通
两个系统VM在web ui中看到一直在创建-启动-删除，一直不停的循环
两个系统VM能看到正常启动，但是在web ui中vnc无法连接查看，提示超时，有什么原因导致呢？ libvirt和qemu的配置已经照着官网文档的确认过几次配置无误了。 iptables里也尝试过删除所有规则，允许所有流量通过了。 日志里看不出原因。 搭建环境：Centos6.5+cloudstack4.4.2,高级网络模式 管理端和agent端在同一台电脑上，有两张网卡，管理流量和guest流量走cloudbr0，公共流量走cloudbr1。cloudbr0和cloudbr1所在交换机端口均设置为trunk型，cloudbr0允许guest范围内的vlan id通过， cloudbr1允许公共流量vlan id 10通过。 在管理端上能ping通两个系统VM。
Re: 两个系统VM在web ui中看到一直在创建-启动-删除，一直不停的循环
cpvm删掉，重新创建一下 On Mar 25, 2015, at 10:05 AM, zb1019095...@163.com zb1019095...@163.com wrote: 两个系统VM能看到正常启动，但是在web ui中vnc无法连接查看，提示超时，有什么原因导致呢？ libvirt和qemu的配置已经照着官网文档的确认过几次配置无误了。 iptables里也尝试过删除所有规则，允许所有流量通过了。 日志里看不出原因。 搭建环境：Centos6.5+cloudstack4.4.2,高级网络模式 管理端和agent端在同一台电脑上，有两张网卡，管理流量和guest流量走cloudbr0，公共流量走cloudbr1。cloudbr0和cloudbr1所在交换机端口均设置为trunk型，cloudbr0允许guest范围内的vlan id通过， cloudbr1允许公共流量vlan id 10通过。 在管理端上能ping通两个系统VM。
Re: Re: 两个系统VM在web ui中看到一直在创建-启动-删除，一直不停的循环
底层用的什么虚拟化平台，看起来是主机Agent没连上。
Alex
中航信华东数据中心有限责任公司
Mail:evanitsh...@gmail.com
发件人： Wei ZHOU
发送时间： 2015-03-24 15:30
收件人： users-cn
主题： Re: 两个系统VM在web ui中看到一直在创建-启动-删除，一直不停的循环
下载template了吗？
2015-03-24 8:17 GMT+01:00 zb1019095...@163.com zb1019095...@163.com:
两个系统VM在web ui中看到一直在创建-启动-删除，一直不停的循环，日志如下，求解如何解决。
2015-03-24 15:14:57,720 ERROR [c.c.v.VmWorkJobDispatcher]
(Work-Job-Executor-11:ctx-585af7eb job-43/job-220) Unable to complete
AsyncJobVO {id:220, userId: 1, accountId: 1, instanceType: null,
instanceId: null, cmd: com.cloud.vm.VmWorkStart, cmdInfo:
rO0ABXNyABhjb20uY2xvdWQudm0uVm1Xb3JrU3RhcnR9cMGsvxz73gIAC0oABGRjSWRMAAZhdm9pZHN0ADBMY29tL2Nsb3VkL2RlcGxveS9EZXBsb3ltZW50UGxhbm5lciRFeGNsdWRlTGlzdDtMAAljbHVzdGVySWR0ABBMamF2YS9sYW5nL0xvbmc7TAAGaG9zdElkcQB-AAJMAAtqb3VybmFsTmFtZXQAEkxqYXZhL2xhbmcvU3RyaW5nO0wAEXBoeXNpY2FsTmV0d29ya0lkcQB-AAJMAAdwbGFubmVycQB-AANMAAVwb2RJZHEAfgACTAAGcG9vbElkcQB-AAJMAAlyYXdQYXJhbXN0AA9MamF2YS91dGlsL01hcDtMAA1yZXNlcnZhdGlvbklkcQB-AAN4cgATY29tLmNsb3VkLnZtLlZtV29ya5-ZtlbwJWdrAgAESgAJYWNjb3VudElkSgAGdXNlcklkSgAEdm1JZEwAC2hhbmRsZXJOYW1lcQB-AAN4cAABAAEAAnQAGVZpcnR1YWxNYWNoaW5lTWFuYWdlckltcGwAAHBwcHBwcHBwcHA,
cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0,
result: null, initMsid: 156420888991411, completeMsid: null, lastUpdated:
null, lastPolled: null, created: Tue Mar 24 15:14:54 CST 2015}, job
origin:43
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.orchestrateStart(VirtualMachineManagerImpl.java:947)
at
com.cloud.vm.VirtualMachineManagerImpl.orchestrateStart(VirtualMachineManagerImpl.java:5195)
at sun.reflect.GeneratedMethodAccessor209.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at
com.cloud.vm.VmWorkJobHandlerProxy.handleVmWorkJob(VmWorkJobHandlerProxy.java:107)
at
com.cloud.vm.VirtualMachineManagerImpl.handleVmWorkJob(VirtualMachineManagerImpl.java:5340)
at com.cloud.vm.VmWorkJobDispatcher.runJob(VmWorkJobDispatcher.java:102)
at
org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.runInContext(AsyncJobManagerImpl.java:503)
at
org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:49)
at
org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56)
at
org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103)
at
org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53)
at
org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:46)
at
org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.run(AsyncJobManagerImpl.java:460)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask.run(FutureTask.java:262)
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:745)
2015-03-24 15:14:57,723 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
(Work-Job-Executor-11:ctx-585af7eb job-43/job-220) Complete async job-220,
jobStatus: FAILED, resultCode: 0, result:
答复: 系统虚拟机agent state一直为空
Hi, 请问你是使用基础网络，还是高级网络？ 如果你要使用高级网络，按照规范你要
配置在xenserver上面配置两个网络：管理网络和guset/public网络，前者access mode
后者trunk mode。
Best Regards,
Star Guo
-邮件原件-
发件人: 姜卫东 [mailto:jiang.weid...@foxmail.com]
发送时间: 2015年3月23日 19:01
收件人: users-cn
主题: 系统虚拟机agent state一直为空
看到邮件的朋友你们好：
我在安装测试cloudstack和xenserver的时候遇到了一些问题，希望有朋友能帮我
分析一下原因。
如下问题：
系统虚拟机启动之后agent state状态一直为空。日志提示 ：Ping timeout for
host 1
我的系统配置如下：
交换机：三个区域
1.一个公网 vlan 20，access
2.一个管理vlan 10 ，10.10.10.0/24,access
3.一个管理和来宾的公用区域, vlan 10,vlan30-50,trunk,默认vlan10
对管理网络做了vlanif,ip 10.10.10.1，
可上网的上层交换机连接到vlan20,网关：192.169.2.253，255.255.0.0.
管理机cloudstack4.2：ubuntu12.04,mysql,ntpd
eth0：10.10.10.2，255.255.255.0,网关：10.10.10.1，dns:10.10.10.3
eth1: 192.169.77.2,255.255.0.0,网关：192.169.2.253，dns：192.169.2.253
nfs: ubuntu12.04,nfs,dns
eth0:10.10.10.3,255.255.255.0,网关：10.10.10.1，dns:10.10.10.3
计算节点xenserver6.2:
eth0:10.10.10.11,网关：10.10.10.1，dns:10.10.10.3，标签network0
eth1:啥都没配，标签network1
下边是错误日志：一直循环出现下边的日志情况
2015-03-23 18:36:48,381 DEBUG [c.c.c.ConsoleProxyManagerImpl]
(consoleproxy-1:ctx-30a758f4) Zone 1 is ready to launch console proxy
2015-03-23 18:36:48,518 DEBUG [o.a.c.s.SecondaryStorageManagerImpl]
(secstorage-1:ctx-4613b985) Zone 1 is ready to launch secondary storage VM
2015-03-23 18:36:54,540 DEBUG [c.c.s.StatsCollector]
(StatsCollector-4:ctx-dc70f3fd) AutoScaling Monitor is running...
2015-03-23 18:36:54,572 DEBUG [c.c.s.StatsCollector]
(StatsCollector-1:ctx-cd4ca6c9) VmStatsCollector is running...
2015-03-23 18:36:55,061 DEBUG [c.c.s.StatsCollector]
(StatsCollector-2:ctx-f2ba1db3) HostStatsCollector is running...
2015-03-23 18:36:55,069 DEBUG [c.c.a.m.DirectAgentAttache]
(DirectAgent-14:ctx-7cb5c18e) Seq 1-67272519433846836: Executing request
2015-03-23 18:36:55,094 DEBUG [c.c.a.m.DirectAgentAttache]
(DirectAgent-14:ctx-7cb5c18e) Seq 1-67272519433846836: Response Received:
2015-03-23 18:36:55,095 DEBUG [c.c.a.t.Request]
(StatsCollector-2:ctx-f2ba1db3) Seq 1-67272519433846836: Received: { Ans: ,
MgmtId: 92378953757938, via: 1, Ver: v1, Flags: 10, { GetHostStatsAnswer } }
2015-03-23 18:37:00,042 WARN [c.c.a.m.DirectAgentAttache]
(DirectAgentCronJob-12:ctx-fec36132) Unable to get current status on 1(xs11.
cs.com)
2015-03-23 18:37:00,115 DEBUG [c.c.s.StatsCollector]
(StatsCollector-3:ctx-f4732348) StorageCollector is running...
2015-03-23 18:37:00,119 DEBUG [c.c.s.StatsCollector]
(StatsCollector-3:ctx-f4732348) There is no secondary storage VM for
secondary storage host secondary1
2015-03-23 18:37:00,122 DEBUG [c.c.a.m.DirectAgentAttache]
(DirectAgent-27:ctx-eb12616b) Seq 1-67272519433846837: Executing request
2015-03-23 18:37:00,451 DEBUG [c.c.a.m.DirectAgentAttache]
(DirectAgent-27:ctx-eb12616b) Seq 1-67272519433846837: Response Received:
2015-03-23 18:37:00,451 DEBUG [c.c.a.t.Request]
(StatsCollector-3:ctx-f4732348) Seq 1-67272519433846837: Received: { Ans: ,
MgmtId: 92378953757938, via: 1, Ver: v1, Flags: 10, { GetStorageStatsAnswer
} }
2015-03-23 18:37:09,560 DEBUG [c.c.n.r.VirtualNetworkApplianceManagerImpl]
(RouterStatusMonitor-1:ctx-409a1826) Found 0 routers to update status.
2015-03-23 18:37:09,561 DEBUG [c.c.n.r.VirtualNetworkApplianceManagerImpl]
(RouterStatusMonitor-1:ctx-409a1826) Found 0 networks to update RvR status.
2015-03-23 18:37:18,381 DEBUG [c.c.c.ConsoleProxyManagerImpl]
(consoleproxy-1:ctx-8efc34c1) Zone 1 is ready to launch console proxy
2015-03-23 18:37:18,518 DEBUG [o.a.c.s.SecondaryStorageManagerImpl]
(secstorage-1:ctx-43e9f234) Zone 1 is ready to launch secondary storage VM
2015-03-23 18:37:39,515 DEBUG [c.c.n.ExternalDeviceUsageManagerImpl]
(ExternalNetworkMonitor-1:ctx-55964f6a) External devices stats collector is
running...
2015-03-23 18:37:39,559 DEBUG [c.c.s.s.SnapshotSchedulerImpl]
(SnapshotPollTask:ctx-5b25e4fe) Snapshot scheduler.poll is being called at
2015-03-23 10:37:39 GMT
2015-03-23 18:37:39,559 DEBUG [c.c.n.r.VirtualNetworkApplianceManagerImpl]
(RouterMonitor-1:ctx-424c44e3) Found 0 running routers.
2015-03-23 18:37:39,560 DEBUG [c.c.n.r.VirtualNetworkApplianceManagerImpl]
(RouterStatusMonitor-1:ctx-52d7fa48) Found 0 routers to update status.
2015-03-23 18:37:39,561 DEBUG [c.c.s.s.SnapshotSchedulerImpl]
(SnapshotPollTask:ctx-5b25e4fe) Got 0 snapshots to be executed at 2015-03-23
10:37:39 GMT
2015-03-23 18:37:39,561 DEBUG [c.c.n.r.VirtualNetworkApplianceManagerImpl]
(RouterStatusMonitor-1:ctx-52d7fa48) Found 0 networks to update RvR status.
2015-03-23 18:37:39,645 INFO [c.c.a.m.AgentManagerImpl]
(AgentMonitor-1:ctx-c7abd581) Found the following agents behind on ping: [1]
2015-03-23 18:37:39,646 DEBUG [c.c.h.Status] (AgentMonitor-1:ctx-c7abd581)
Ping timeout for host 1, do invstigation
2015-03-23 18:37:39,649 INFO [c.c.a.m.AgentManagerImpl]
(AgentTaskPool-12:ctx-08432615) Investigating why host 1 has disconnected
with event PingTimeout
2015-03-23 18:37:39,649 DEBUG [c.c.a.m.AgentManagerImpl]
(AgentTaskPool-12:ctx-08432615) checking if agent (1)
Re: 两个系统VM在web ui中看到一直在创建-启动-删除，一直不停的循环
下载template了吗？
2015-03-24 8:17 GMT+01:00 zb1019095...@163.com zb1019095...@163.com:
两个系统VM在web ui中看到一直在创建-启动-删除，一直不停的循环，日志如下，求解如何解决。
2015-03-24 15:14:57,720 ERROR [c.c.v.VmWorkJobDispatcher]
(Work-Job-Executor-11:ctx-585af7eb job-43/job-220) Unable to complete
AsyncJobVO {id:220, userId: 1, accountId: 1, instanceType: null,
instanceId: null, cmd: com.cloud.vm.VmWorkStart, cmdInfo:
rO0ABXNyABhjb20uY2xvdWQudm0uVm1Xb3JrU3RhcnR9cMGsvxz73gIAC0oABGRjSWRMAAZhdm9pZHN0ADBMY29tL2Nsb3VkL2RlcGxveS9EZXBsb3ltZW50UGxhbm5lciRFeGNsdWRlTGlzdDtMAAljbHVzdGVySWR0ABBMamF2YS9sYW5nL0xvbmc7TAAGaG9zdElkcQB-AAJMAAtqb3VybmFsTmFtZXQAEkxqYXZhL2xhbmcvU3RyaW5nO0wAEXBoeXNpY2FsTmV0d29ya0lkcQB-AAJMAAdwbGFubmVycQB-AANMAAVwb2RJZHEAfgACTAAGcG9vbElkcQB-AAJMAAlyYXdQYXJhbXN0AA9MamF2YS91dGlsL01hcDtMAA1yZXNlcnZhdGlvbklkcQB-AAN4cgATY29tLmNsb3VkLnZtLlZtV29ya5-ZtlbwJWdrAgAESgAJYWNjb3VudElkSgAGdXNlcklkSgAEdm1JZEwAC2hhbmRsZXJOYW1lcQB-AAN4cAABAAEAAnQAGVZpcnR1YWxNYWNoaW5lTWFuYWdlckltcGwAAHBwcHBwcHBwcHA,
cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0,
result: null, initMsid: 156420888991411, completeMsid: null, lastUpdated:
null, lastPolled: null, created: Tue Mar 24 15:14:54 CST 2015}, job
origin:43
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.orchestrateStart(VirtualMachineManagerImpl.java:947)
at
com.cloud.vm.VirtualMachineManagerImpl.orchestrateStart(VirtualMachineManagerImpl.java:5195)
at sun.reflect.GeneratedMethodAccessor209.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at
com.cloud.vm.VmWorkJobHandlerProxy.handleVmWorkJob(VmWorkJobHandlerProxy.java:107)
at
com.cloud.vm.VirtualMachineManagerImpl.handleVmWorkJob(VirtualMachineManagerImpl.java:5340)
at com.cloud.vm.VmWorkJobDispatcher.runJob(VmWorkJobDispatcher.java:102)
at
org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.runInContext(AsyncJobManagerImpl.java:503)
at
org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:49)
at
org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56)
at
org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103)
at
org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53)
at
org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:46)
at
org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.run(AsyncJobManagerImpl.java:460)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask.run(FutureTask.java:262)
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:745)
2015-03-24 15:14:57,723 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
(Work-Job-Executor-11:ctx-585af7eb job-43/job-220) Complete async job-220,
jobStatus: FAILED, resultCode: 0, result:
