Re: Re: Re: 我在创建完域以后启动SSVM出以下错误，请各位大拿帮忙看看啥情况。
是的 2013/9/18 toudsf 18600601...@163.com 4.5.3.3. Downloading vhd-util This procedure is required only for installations where XenServer is installed on the hypervisor hosts. Before setting up the Management Server, download vhd-util from vhd-util 2 . If the Management Server is RHEL or CentOS, copy vhd-util to /usr/share/cloudstack-common/scripts/ vm/hypervisor/xenserver. 是这个吗？ 2013-09-18 toudsf 发件人：Hongtu Zang zanghongtu2...@gmail.com 发送时间：2013-09-18 10:30 主题：Re: Re: 我在创建完域以后启动SSVM出以下错误，请各位大拿帮忙看看啥情况。 收件人：users-cnusers-cn@cloudstack.apache.org 抄送： 应该是缺少vhd-util文件 社区有下载链接的 2013/9/17 tanthalas tanthalas...@hotmail.com com.cloud.utils.exception.CloudRuntimeException: can not create vdi in sr cfe7b609-d80a-796b-852b-12882ab5c57d at com.cloud.hypervisor.xen.resource.CitrixResourceBase.copy_vhd_from_secondarystorage 没有办法吧二级存储上的系统虚拟机的模板考到主存储上。 刘宇超 Richard Liu 发件人： Wei ZHOU 发送时间： 2013-09-17 16:18:50 收件人： users-cn 抄送： 主题： Re: 我在创建完域以后启动SSVM出以下错误，请各位大拿帮忙看看啥情况。 没有vhd-util文件吧 2013/9/17 toudsf 18600601...@163.com WARN [xen.resource.CitrixResourceBase] (DirectAgent-61:) destoryVDIbyNameLabel failed due to there are 0 VDIs with name cloud-54f75385-8bc5-490b-bee7-7485a65ae1b8 WARN [xen.resource.CitrixResourceBase] (DirectAgent-61:) can not create vdi in sr cfe7b609-d80a-796b-852b-12882ab5c57d WARN [xen.resource.CitrixResourceBase] (DirectAgent-61:) Catch Exception com.cloud.utils.exception.CloudRuntimeException on host:1a331a5f-74be-443f-8c3a-39e622858044 for template: nfs:// 192.168.40.128/export/secondary/template/tmpl/1/1/ due to com.cloud.utils.exception.CloudRuntimeException: can not create vdi in sr cfe7b609-d80a-796b-852b-12882ab5c57d com.cloud.utils.exception.CloudRuntimeException: can not create vdi in sr cfe7b609-d80a-796b-852b-12882ab5c57d at com.cloud.hypervisor.xen.resource.CitrixResourceBase.copy_vhd_from_secondarystorage(CitrixResourceBase.java:2707) at com.cloud.hypervisor.xen.resource.CitrixResourceBase.execute(CitrixResourceBase.java:2729) at com.cloud.hypervisor.xen.resource.CitrixResourceBase.executeRequest(CitrixResourceBase.java:501) at com.cloud.hypervisor.xen.resource.XenServer56Resource.executeRequest(XenServer56Resource.java:73) at com.cloud.agent.manager.DirectAgentAttache$Task.run(DirectAgentAttache.java:186) 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) WARN [xen.resource.CitrixResourceBase] (DirectAgent-62:) destoryVDIbyNameLabel failed due to there are 0 VDIs with name cloud-46c29a05-7668-4585-9c47-25a548839b2b WARN [xen.resource.CitrixResourceBase] (DirectAgent-62:) can not create vdi in sr cfe7b609-d80a-796b-852b-12882ab5c57d WARN [xen.resource.CitrixResourceBase] (DirectAgent-62:) Catch Exception com.cloud.utils.exception.CloudRuntimeException on host:1a331a5f-74be-443f-8c3a-39e622858044 for template: nfs:// 192.168.40.128/export/secondary/template/tmpl/1/1/ due to com.cloud.utils.exception.CloudRuntimeException: can not create vdi in sr cfe7b609-d80a-796b-852b-12882ab5c57d com.cloud.utils.exception.CloudRuntimeException: can not create vdi in sr cfe7b609-d80a-796b-852b-12882ab5c57d at com.cloud.hypervisor.xen.resource.CitrixResourceBase.copy_vhd_from_secondarystorage(CitrixResourceBase.java:2707) at com.cloud.hypervisor.xen.resource.CitrixResourceBase.execute(CitrixResourceBase.java:2729) at com.cloud.hypervisor.xen.resource.CitrixResourceBase.executeRequest(CitrixResourceBase.java:501) at com.cloud.hypervisor.xen.resource.XenServer56Resource.executeRequest(XenServer56Resource.java:73) at com.cloud.agent.manager.DirectAgentAttache$Task.run(DirectAgentAttache.java:186) 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
Re: AWS interface in CloudStack 4.1.1 with Advanced Networking
On Sep 17, 2013, at 2:54 PM, Richard Chatterton richard.chatter...@contegix.com wrote: Howdy, CloudStack users! I'm wanting to set up the AWS interface in CloudStack 4.1.1 in an advanced networking zone. I noticed that section 11.1 of the CloudStack installation documents says the following about the AWS interface: Supported only in zones that use basic networking As I haven't yet gotten the AWS interface working, I'm curious if this is the reason, or if I just have it configured incorrectly. If this documentation is accurate, does anyone know of a workaround to get the AWS interface working in an advanced network zone in CloudStack 4.1.1, or is this a hard limitation in this version of CloudStack? Also, does anyone know if later versions of CloudStack are planned to support the AWS interface in advanced zones? Thanks for the help! Best, Rich Chatterton Rich, I believe that the AWS interface is broken in 4.1.1. A patch has been submitted and will be in the 4.1.2 release. It is working though in the 4.2 release (that should come out shortly). I don't know about advanced zone support, I only ever tested it in basic zones. -sebastien
Re: AWS interface in CloudStack 4.1.1 with Advanced Networking
I checked the documentation. AWS interface only supports basic zone. Sorry! On 18 September 2013 09:46, Sebastien Goasguen run...@gmail.com wrote: On Sep 17, 2013, at 2:54 PM, Richard Chatterton richard.chatter...@contegix.com wrote: Howdy, CloudStack users! I'm wanting to set up the AWS interface in CloudStack 4.1.1 in an advanced networking zone. I noticed that section 11.1 of the CloudStack installation documents says the following about the AWS interface: Supported only in zones that use basic networking As I haven't yet gotten the AWS interface working, I'm curious if this is the reason, or if I just have it configured incorrectly. If this documentation is accurate, does anyone know of a workaround to get the AWS interface working in an advanced network zone in CloudStack 4.1.1, or is this a hard limitation in this version of CloudStack? Also, does anyone know if later versions of CloudStack are planned to support the AWS interface in advanced zones? Thanks for the help! Best, Rich Chatterton Rich, I believe that the AWS interface is broken in 4.1.1. A patch has been submitted and will be in the 4.1.2 release. It is working though in the 4.2 release (that should come out shortly). I don't know about advanced zone support, I only ever tested it in basic zones. -sebastien
Cloudstack 4.1.1 + XCP 1.6 fresh install
Hello all,
Trying to install subj. several times I have decided to ask your
help. May be someone already faced the same problem? I did the configuration
according to “Installation guide” and always end up with the same problem: on
system VM creation I got repeated errors like this:
2013-09-18 16:49:21,605 DEBUG [cloud.storage.StorageManagerImpl]
(consoleproxy-1:null) Creating volume: Vol[2|vm=2|ROOT]
2013-09-18 16:49:21,605 DEBUG [cloud.storage.StorageManagerImpl]
(consoleproxy-1:null) Trying to create in Pool[200|NetworkFilesystem]
2013-09-18 16:49:23,381 WARN [xen.resource.CitrixResourceBase]
(DirectAgent-4:null) kill_copy_process failed
2013-09-18 16:49:23,381 WARN [xen.resource.CitrixResourceBase]
(DirectAgent-4:null) can not create vdi in sr
c6e55039-1fb0-5e5d-37d5-118a9ac3abb6
2013-09-18 16:49:23,382 WARN [xen.resource.CitrixResourceBase]
(DirectAgent-4:null) Catch Exception
com.cloud.utils.exception.CloudRuntimeException on
host:e6a339ee-521c-4c67-ac55-cbd256607150 for template:
nfs://192.168.107.142/export/secondary/template/tmpl/1/1/ due to
com.cloud.utils.exception.CloudRuntimeException: can not create vdi in sr
c6e55039-1fb0-5e5d-37d5-118a9ac3abb6
com.cloud.utils.exception.CloudRuntimeException: can not create vdi in sr
c6e55039-1fb0-5e5d-37d5-118a9ac3abb6
at
com.cloud.hypervisor.xen.resource.CitrixResourceBase.copy_vhd_from_secondarystorage(CitrixResourceBase.java:2707)
at
com.cloud.hypervisor.xen.resource.CitrixResourceBase.execute(CitrixResourceBase.java:2729)
at
com.cloud.hypervisor.xen.resource.CitrixResourceBase.executeRequest(CitrixResourceBase.java:501)
at
com.cloud.hypervisor.xen.resource.XcpServerResource.executeRequest(XcpServerResource.java:51)
at
com.cloud.agent.manager.DirectAgentAttache$Task.run(DirectAgentAttache.java:186)
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:1146)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:679)
2013-09-18 16:49:23,384 DEBUG [agent.manager.DirectAgentAttache]
(DirectAgent-4:null) Seq 1-1333067786: Response Received:
2013-09-18 16:49:23,385 DEBUG [agent.transport.Request] (DirectAgent-4:null)
Seq 1-1333067786: Processing: { Ans: , MgmtId: 8796752993784, via: 1, Ver: v1,
Flags: 110,
[{storage.PrimaryStorageDownloadAnswer:{templateSize:0,result:false,details:Catch
Exception com.cloud.utils.exception.CloudRuntimeException on
host:e6a339ee-521c-4c67-ac55-cbd256607150 for template:
nfs://192.168.107.142/export/secondary/template/tmpl/1/1/ due to
com.cloud.utils.exception.CloudRuntimeException: can not create vdi in sr
c6e55039-1fb0-5e5d-37d5-118a9ac3abb6,wait:0}}] }
2013-09-18 16:49:23,385 DEBUG [agent.transport.Request] (secstorage-1:null) Seq
1-1333067786: Received: { Ans: , MgmtId: 8796752993784, via: 1, Ver: v1,
Flags: 110, { PrimaryStorageDownloadAnswer } }
2013-09-18 16:49:23,385 DEBUG [agent.manager.AgentManagerImpl]
(secstorage-1:null) Details from executing class
com.cloud.agent.api.storage.PrimaryStorageDownloadCommand: Catch Exception
com.cloud.utils.exception.CloudRuntimeException on
host:e6a339ee-521c-4c67-ac55-cbd256607150 for template:
nfs://192.168.107.142/export/secondary/template/tmpl/1/1/ due to
com.cloud.utils.exception.CloudRuntimeException: can not create vdi in sr
c6e55039-1fb0-5e5d-37d5-118a9ac3abb6
2013-09-18 16:49:23,386 DEBUG [cloud.template.TemplateManagerImpl]
(secstorage-1:null) Template 1 download to pool 200 failed due to Catch
Exception com.cloud.utils.exception.CloudRuntimeException on
host:e6a339ee-521c-4c67-ac55-cbd256607150 for template:
nfs://192.168.107.142/export/secondary/template/tmpl/1/1/ due to
com.cloud.utils.exception.CloudRuntimeException: can not create vdi in sr
c6e55039-1fb0-5e5d-37d5-118a9ac3abb6
2013-09-18 16:49:23,386 DEBUG [cloud.template.TemplateManagerImpl]
(secstorage-1:null) Downloading 1 via 1
2013-09-18 16:49:23,394 DEBUG [agent.manager.AgentAttache] (DirectAgent-4:null)
Seq 1-1333067786: No more commands found
2013-09-18 16:49:23,411 DEBUG [agent.transport.Request] (secstorage-1:null) Seq
1-1333067787: Sending { Cmd , MgmtId: 8796752993784, via: 1, Ver: v1, Flags:
100111,
Re: Cloudstack 4.1.1 + XCP 1.6 fresh install
Did you copy over vhd-util to the correct folder and chmod +x it?
On 18 Sep 2013 15:13, Vadim Kimlaychuk vadim.kimlayc...@elion.ee wrote:
Hello all,
Trying to install subj. several times I have decided to ask
your help. May be someone already faced the same problem? I did the
configuration according to “Installation guide” and always end up with the
same problem: on system VM creation I got repeated errors like this:
2013-09-18 16:49:21,605 DEBUG [cloud.storage.StorageManagerImpl]
(consoleproxy-1:null) Creating volume: Vol[2|vm=2|ROOT]
2013-09-18 16:49:21,605 DEBUG [cloud.storage.StorageManagerImpl]
(consoleproxy-1:null) Trying to create in Pool[200|NetworkFilesystem]
2013-09-18 16:49:23,381 WARN [xen.resource.CitrixResourceBase]
(DirectAgent-4:null) kill_copy_process failed
2013-09-18 16:49:23,381 WARN [xen.resource.CitrixResourceBase]
(DirectAgent-4:null) can not create vdi in sr
c6e55039-1fb0-5e5d-37d5-118a9ac3abb6
2013-09-18 16:49:23,382 WARN [xen.resource.CitrixResourceBase]
(DirectAgent-4:null) Catch Exception
com.cloud.utils.exception.CloudRuntimeException on
host:e6a339ee-521c-4c67-ac55-cbd256607150 for template: nfs://
192.168.107.142/export/secondary/template/tmpl/1/1/ due to
com.cloud.utils.exception.CloudRuntimeException: can not create vdi in sr
c6e55039-1fb0-5e5d-37d5-118a9ac3abb6
com.cloud.utils.exception.CloudRuntimeException: can not create vdi in sr
c6e55039-1fb0-5e5d-37d5-118a9ac3abb6
at
com.cloud.hypervisor.xen.resource.CitrixResourceBase.copy_vhd_from_secondarystorage(CitrixResourceBase.java:2707)
at
com.cloud.hypervisor.xen.resource.CitrixResourceBase.execute(CitrixResourceBase.java:2729)
at
com.cloud.hypervisor.xen.resource.CitrixResourceBase.executeRequest(CitrixResourceBase.java:501)
at
com.cloud.hypervisor.xen.resource.XcpServerResource.executeRequest(XcpServerResource.java:51)
at
com.cloud.agent.manager.DirectAgentAttache$Task.run(DirectAgentAttache.java:186)
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:1146)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:679)
2013-09-18 16:49:23,384 DEBUG [agent.manager.DirectAgentAttache]
(DirectAgent-4:null) Seq 1-1333067786: Response Received:
2013-09-18 16:49:23,385 DEBUG [agent.transport.Request]
(DirectAgent-4:null) Seq 1-1333067786: Processing: { Ans: , MgmtId:
8796752993784, via: 1, Ver: v1, Flags: 110,
[{storage.PrimaryStorageDownloadAnswer:{templateSize:0,result:false,details:Catch
Exception com.cloud.utils.exception.CloudRuntimeException on
host:e6a339ee-521c-4c67-ac55-cbd256607150 for template: nfs://
192.168.107.142/export/secondary/template/tmpl/1/1/ due to
com.cloud.utils.exception.CloudRuntimeException: can not create vdi in sr
c6e55039-1fb0-5e5d-37d5-118a9ac3abb6,wait:0}}] }
2013-09-18 16:49:23,385 DEBUG [agent.transport.Request]
(secstorage-1:null) Seq 1-1333067786: Received: { Ans: , MgmtId:
8796752993784, via: 1, Ver: v1, Flags: 110, { PrimaryStorageDownloadAnswer
} }
2013-09-18 16:49:23,385 DEBUG [agent.manager.AgentManagerImpl]
(secstorage-1:null) Details from executing class
com.cloud.agent.api.storage.PrimaryStorageDownloadCommand: Catch Exception
com.cloud.utils.exception.CloudRuntimeException on
host:e6a339ee-521c-4c67-ac55-cbd256607150 for template: nfs://
192.168.107.142/export/secondary/template/tmpl/1/1/ due to
com.cloud.utils.exception.CloudRuntimeException: can not create vdi in sr
c6e55039-1fb0-5e5d-37d5-118a9ac3abb6
2013-09-18 16:49:23,386 DEBUG [cloud.template.TemplateManagerImpl]
(secstorage-1:null) Template 1 download to pool 200 failed due to Catch
Exception com.cloud.utils.exception.CloudRuntimeException on
host:e6a339ee-521c-4c67-ac55-cbd256607150 for template: nfs://
192.168.107.142/export/secondary/template/tmpl/1/1/ due to
com.cloud.utils.exception.CloudRuntimeException: can not create vdi in sr
c6e55039-1fb0-5e5d-37d5-118a9ac3abb6
2013-09-18 16:49:23,386 DEBUG [cloud.template.TemplateManagerImpl]
(secstorage-1:null) Downloading 1 via 1
2013-09-18 16:49:23,394 DEBUG [agent.manager.AgentAttache]
(DirectAgent-4:null) Seq 1-1333067786: No more commands found
2013-09-18 16:49:23,411 DEBUG [agent.transport.Request]
(secstorage-1:null) Seq 1-1333067787: Sending { Cmd , MgmtId:
8796752993784, via: 1, Ver: v1, Flags:
RE: Cloudstack 4.1.1 + XCP 1.6 fresh install
Yes, its over there (I have Ubuntu 12.04 LTS) :
root@mgmt4xcp:/home/vadim# ls -al
/usr/share/cloudstack-common/scripts/vm/hypervisor/xenserver/vh*
-rwxr-xr-x 1 root root 318977 Sep 18 15:55
/usr/share/cloudstack-common/scripts/vm/hypervisor/xenserver/vhd-util
Vadim
-Original Message-
From: Ian Duffy [mailto:i...@ianduffy.ie]
Sent: Wednesday, September 18, 2013 5:26 PM
To: users@cloudstack.apache.org
Subject: Re: Cloudstack 4.1.1 + XCP 1.6 fresh install
Did you copy over vhd-util to the correct folder and chmod +x it?
On 18 Sep 2013 15:13, Vadim Kimlaychuk vadim.kimlayc...@elion.ee wrote:
Hello all,
Trying to install subj. several times I have decided to
ask your help. May be someone already faced the same problem? I did
the configuration according to “Installation guide” and always end up
with the same problem: on system VM creation I got repeated errors like this:
2013-09-18 16:49:21,605 DEBUG [cloud.storage.StorageManagerImpl]
(consoleproxy-1:null) Creating volume: Vol[2|vm=2|ROOT]
2013-09-18 16:49:21,605 DEBUG [cloud.storage.StorageManagerImpl]
(consoleproxy-1:null) Trying to create in Pool[200|NetworkFilesystem]
2013-09-18 16:49:23,381 WARN [xen.resource.CitrixResourceBase]
(DirectAgent-4:null) kill_copy_process failed
2013-09-18 16:49:23,381 WARN [xen.resource.CitrixResourceBase]
(DirectAgent-4:null) can not create vdi in sr
c6e55039-1fb0-5e5d-37d5-118a9ac3abb6
2013-09-18 16:49:23,382 WARN [xen.resource.CitrixResourceBase]
(DirectAgent-4:null) Catch Exception
com.cloud.utils.exception.CloudRuntimeException on
host:e6a339ee-521c-4c67-ac55-cbd256607150 for template: nfs://
192.168.107.142/export/secondary/template/tmpl/1/1/ due to
com.cloud.utils.exception.CloudRuntimeException: can not create vdi in
sr
c6e55039-1fb0-5e5d-37d5-118a9ac3abb6
com.cloud.utils.exception.CloudRuntimeException: can not create vdi in
sr
c6e55039-1fb0-5e5d-37d5-118a9ac3abb6
at
com.cloud.hypervisor.xen.resource.CitrixResourceBase.copy_vhd_from_secondarystorage(CitrixResourceBase.java:2707)
at
com.cloud.hypervisor.xen.resource.CitrixResourceBase.execute(CitrixResourceBase.java:2729)
at
com.cloud.hypervisor.xen.resource.CitrixResourceBase.executeRequest(CitrixResourceBase.java:501)
at
com.cloud.hypervisor.xen.resource.XcpServerResource.executeRequest(XcpServerResource.java:51)
at
com.cloud.agent.manager.DirectAgentAttache$Task.run(DirectAgentAttache.java:186)
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:1146)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:679)
2013-09-18 16:49:23,384 DEBUG [agent.manager.DirectAgentAttache]
(DirectAgent-4:null) Seq 1-1333067786: Response Received:
2013-09-18 16:49:23,385 DEBUG [agent.transport.Request]
(DirectAgent-4:null) Seq 1-1333067786: Processing: { Ans: , MgmtId:
8796752993784, via: 1, Ver: v1, Flags: 110,
[{storage.PrimaryStorageDownloadAnswer:{templateSize:0,result:fa
lse,details:Catch Exception
com.cloud.utils.exception.CloudRuntimeException on
host:e6a339ee-521c-4c67-ac55-cbd256607150 for template: nfs://
192.168.107.142/export/secondary/template/tmpl/1/1/ due to
com.cloud.utils.exception.CloudRuntimeException: can not create vdi in
sr c6e55039-1fb0-5e5d-37d5-118a9ac3abb6,wait:0}}] }
2013-09-18 16:49:23,385 DEBUG [agent.transport.Request]
(secstorage-1:null) Seq 1-1333067786: Received: { Ans: , MgmtId:
8796752993784, via: 1, Ver: v1, Flags: 110, {
PrimaryStorageDownloadAnswer } }
2013-09-18 16:49:23,385 DEBUG [agent.manager.AgentManagerImpl]
(secstorage-1:null) Details from executing class
com.cloud.agent.api.storage.PrimaryStorageDownloadCommand: Catch
Exception com.cloud.utils.exception.CloudRuntimeException on
host:e6a339ee-521c-4c67-ac55-cbd256607150 for template: nfs://
192.168.107.142/export/secondary/template/tmpl/1/1/ due to
com.cloud.utils.exception.CloudRuntimeException: can not create vdi in
sr
c6e55039-1fb0-5e5d-37d5-118a9ac3abb6
2013-09-18 16:49:23,386 DEBUG [cloud.template.TemplateManagerImpl]
(secstorage-1:null) Template 1 download to pool 200 failed due to
Catch Exception com.cloud.utils.exception.CloudRuntimeException on
host:e6a339ee-521c-4c67-ac55-cbd256607150 for template: nfs://
192.168.107.142/export/secondary/template/tmpl/1/1/ due to
Re: Cloudstack 4.1.1 + XCP 1.6 fresh install
On a recent install of CS4.1.1 + XS6.1 I thought I had vhd-util in the right
place but it did not get copied to the hosts. It maybe a similar issue here.
Try to copy the vhd-util to the hosts and see if things start working. They did
for me.
On Sep 18, 2013, at 7:28 AM, Vadim Kimlaychuk vadim.kimlayc...@elion.ee wrote:
Yes, its over there (I have Ubuntu 12.04 LTS) :
root@mgmt4xcp:/home/vadim# ls -al
/usr/share/cloudstack-common/scripts/vm/hypervisor/xenserver/vh*
-rwxr-xr-x 1 root root 318977 Sep 18 15:55
/usr/share/cloudstack-common/scripts/vm/hypervisor/xenserver/vhd-util
Vadim
-Original Message-
From: Ian Duffy [mailto:i...@ianduffy.ie]
Sent: Wednesday, September 18, 2013 5:26 PM
To: users@cloudstack.apache.org
Subject: Re: Cloudstack 4.1.1 + XCP 1.6 fresh install
Did you copy over vhd-util to the correct folder and chmod +x it?
On 18 Sep 2013 15:13, Vadim Kimlaychuk vadim.kimlayc...@elion.ee wrote:
Hello all,
Trying to install subj. several times I have decided to
ask your help. May be someone already faced the same problem? I did
the configuration according to “Installation guide” and always end up
with the same problem: on system VM creation I got repeated errors like this:
2013-09-18 16:49:21,605 DEBUG [cloud.storage.StorageManagerImpl]
(consoleproxy-1:null) Creating volume: Vol[2|vm=2|ROOT]
2013-09-18 16:49:21,605 DEBUG [cloud.storage.StorageManagerImpl]
(consoleproxy-1:null) Trying to create in Pool[200|NetworkFilesystem]
2013-09-18 16:49:23,381 WARN [xen.resource.CitrixResourceBase]
(DirectAgent-4:null) kill_copy_process failed
2013-09-18 16:49:23,381 WARN [xen.resource.CitrixResourceBase]
(DirectAgent-4:null) can not create vdi in sr
c6e55039-1fb0-5e5d-37d5-118a9ac3abb6
2013-09-18 16:49:23,382 WARN [xen.resource.CitrixResourceBase]
(DirectAgent-4:null) Catch Exception
com.cloud.utils.exception.CloudRuntimeException on
host:e6a339ee-521c-4c67-ac55-cbd256607150 for template: nfs://
192.168.107.142/export/secondary/template/tmpl/1/1/ due to
com.cloud.utils.exception.CloudRuntimeException: can not create vdi in
sr
c6e55039-1fb0-5e5d-37d5-118a9ac3abb6
com.cloud.utils.exception.CloudRuntimeException: can not create vdi in
sr
c6e55039-1fb0-5e5d-37d5-118a9ac3abb6
at
com.cloud.hypervisor.xen.resource.CitrixResourceBase.copy_vhd_from_secondarystorage(CitrixResourceBase.java:2707)
at
com.cloud.hypervisor.xen.resource.CitrixResourceBase.execute(CitrixResourceBase.java:2729)
at
com.cloud.hypervisor.xen.resource.CitrixResourceBase.executeRequest(CitrixResourceBase.java:501)
at
com.cloud.hypervisor.xen.resource.XcpServerResource.executeRequest(XcpServerResource.java:51)
at
com.cloud.agent.manager.DirectAgentAttache$Task.run(DirectAgentAttache.java:186)
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:1146)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:679)
2013-09-18 16:49:23,384 DEBUG [agent.manager.DirectAgentAttache]
(DirectAgent-4:null) Seq 1-1333067786: Response Received:
2013-09-18 16:49:23,385 DEBUG [agent.transport.Request]
(DirectAgent-4:null) Seq 1-1333067786: Processing: { Ans: , MgmtId:
8796752993784, via: 1, Ver: v1, Flags: 110,
[{storage.PrimaryStorageDownloadAnswer:{templateSize:0,result:fa
lse,details:Catch Exception
com.cloud.utils.exception.CloudRuntimeException on
host:e6a339ee-521c-4c67-ac55-cbd256607150 for template: nfs://
192.168.107.142/export/secondary/template/tmpl/1/1/ due to
com.cloud.utils.exception.CloudRuntimeException: can not create vdi in
sr c6e55039-1fb0-5e5d-37d5-118a9ac3abb6,wait:0}}] }
2013-09-18 16:49:23,385 DEBUG [agent.transport.Request]
(secstorage-1:null) Seq 1-1333067786: Received: { Ans: , MgmtId:
8796752993784, via: 1, Ver: v1, Flags: 110, {
PrimaryStorageDownloadAnswer } }
2013-09-18 16:49:23,385 DEBUG [agent.manager.AgentManagerImpl]
(secstorage-1:null) Details from executing class
com.cloud.agent.api.storage.PrimaryStorageDownloadCommand: Catch
Exception com.cloud.utils.exception.CloudRuntimeException on
host:e6a339ee-521c-4c67-ac55-cbd256607150 for template: nfs://
192.168.107.142/export/secondary/template/tmpl/1/1/ due to
com.cloud.utils.exception.CloudRuntimeException: can not create vdi in
sr
c6e55039-1fb0-5e5d-37d5-118a9ac3abb6
RE: Cloudstack 4.1.1 + XCP 1.6 fresh install
Do you mean I have to copy vhd-util to the server where XCP is installed? What
should be the right path there?
Vadim
From: Carlos Reátegui [create...@gmail.com]
Sent: Wednesday, September 18, 2013 18:15
To: users@cloudstack.apache.org
Cc: users@cloudstack.apache.org
Subject: Re: Cloudstack 4.1.1 + XCP 1.6 fresh install
On a recent install of CS4.1.1 + XS6.1 I thought I had vhd-util in the right
place but it did not get copied to the hosts. It maybe a similar issue here.
Try to copy the vhd-util to the hosts and see if things start working. They did
for me.
On Sep 18, 2013, at 7:28 AM, Vadim Kimlaychuk vadim.kimlayc...@elion.ee wrote:
Yes, its over there (I have Ubuntu 12.04 LTS) :
root@mgmt4xcp:/home/vadim# ls -al
/usr/share/cloudstack-common/scripts/vm/hypervisor/xenserver/vh*
-rwxr-xr-x 1 root root 318977 Sep 18 15:55
/usr/share/cloudstack-common/scripts/vm/hypervisor/xenserver/vhd-util
Vadim
-Original Message-
From: Ian Duffy [mailto:i...@ianduffy.ie]
Sent: Wednesday, September 18, 2013 5:26 PM
To: users@cloudstack.apache.org
Subject: Re: Cloudstack 4.1.1 + XCP 1.6 fresh install
Did you copy over vhd-util to the correct folder and chmod +x it?
On 18 Sep 2013 15:13, Vadim Kimlaychuk vadim.kimlayc...@elion.ee wrote:
Hello all,
Trying to install subj. several times I have decided to
ask your help. May be someone already faced the same problem? I did
the configuration according to “Installation guide” and always end up
with the same problem: on system VM creation I got repeated errors like this:
2013-09-18 16:49:21,605 DEBUG [cloud.storage.StorageManagerImpl]
(consoleproxy-1:null) Creating volume: Vol[2|vm=2|ROOT]
2013-09-18 16:49:21,605 DEBUG [cloud.storage.StorageManagerImpl]
(consoleproxy-1:null) Trying to create in Pool[200|NetworkFilesystem]
2013-09-18 16:49:23,381 WARN [xen.resource.CitrixResourceBase]
(DirectAgent-4:null) kill_copy_process failed
2013-09-18 16:49:23,381 WARN [xen.resource.CitrixResourceBase]
(DirectAgent-4:null) can not create vdi in sr
c6e55039-1fb0-5e5d-37d5-118a9ac3abb6
2013-09-18 16:49:23,382 WARN [xen.resource.CitrixResourceBase]
(DirectAgent-4:null) Catch Exception
com.cloud.utils.exception.CloudRuntimeException on
host:e6a339ee-521c-4c67-ac55-cbd256607150 for template: nfs://
192.168.107.142/export/secondary/template/tmpl/1/1/ due to
com.cloud.utils.exception.CloudRuntimeException: can not create vdi in
sr
c6e55039-1fb0-5e5d-37d5-118a9ac3abb6
com.cloud.utils.exception.CloudRuntimeException: can not create vdi in
sr
c6e55039-1fb0-5e5d-37d5-118a9ac3abb6
at
com.cloud.hypervisor.xen.resource.CitrixResourceBase.copy_vhd_from_secondarystorage(CitrixResourceBase.java:2707)
at
com.cloud.hypervisor.xen.resource.CitrixResourceBase.execute(CitrixResourceBase.java:2729)
at
com.cloud.hypervisor.xen.resource.CitrixResourceBase.executeRequest(CitrixResourceBase.java:501)
at
com.cloud.hypervisor.xen.resource.XcpServerResource.executeRequest(XcpServerResource.java:51)
at
com.cloud.agent.manager.DirectAgentAttache$Task.run(DirectAgentAttache.java:186)
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:1146)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:679)
2013-09-18 16:49:23,384 DEBUG [agent.manager.DirectAgentAttache]
(DirectAgent-4:null) Seq 1-1333067786: Response Received:
2013-09-18 16:49:23,385 DEBUG [agent.transport.Request]
(DirectAgent-4:null) Seq 1-1333067786: Processing: { Ans: , MgmtId:
8796752993784, via: 1, Ver: v1, Flags: 110,
[{storage.PrimaryStorageDownloadAnswer:{templateSize:0,result:fa
lse,details:Catch Exception
com.cloud.utils.exception.CloudRuntimeException on
host:e6a339ee-521c-4c67-ac55-cbd256607150 for template: nfs://
192.168.107.142/export/secondary/template/tmpl/1/1/ due to
com.cloud.utils.exception.CloudRuntimeException: can not create vdi in
sr c6e55039-1fb0-5e5d-37d5-118a9ac3abb6,wait:0}}] }
2013-09-18 16:49:23,385 DEBUG [agent.transport.Request]
(secstorage-1:null) Seq 1-1333067786: Received: { Ans: , MgmtId:
8796752993784, via: 1, Ver: v1, Flags: 110, {
PrimaryStorageDownloadAnswer } }
2013-09-18 16:49:23,385 DEBUG [agent.manager.AgentManagerImpl]
(secstorage-1:null) Details from executing class
Re: Unable to start DomR CS 4.1 VMware esxi 5.1
I'll take a look at that. I am wondering if the problem is it is unable to pull
the systemvm template. I noticed that the permissions for the systemvm .ova
file on secondary storage have a different ownership then the rest of the files
on secondary storage. Second thing I noticed, the template on the vCenter side
has a network associated to it that is not be used by CloudStack and isn't
routable in the network at all... and I am not sure how that happened.
John Skinner
Senior Systems Administrator | Appcore - the business of cloud computing®
Office +1.800.735.7104
Direct +1.515.612.7783 | Mobile +1.515.745.0248
john.skin...@appcore.com | www.appcore.com
--
The information in this message is intended for the named recipients only. It
may contain information that is privileged, confidential or otherwise protected
from disclosure. If you are not the intended recipient, you are hereby notified
that any disclosure, copying, distribution, or the taking of any action in
reliance on the contents of this message is strictly prohibited. If you have
received this e-mail in error, do not print it or disseminate it or its
contents. In such event, please notify the sender by return e-mail and delete
the e-mail file immediately thereafter. Thank you.
- Original Message -
From: Kelven Yang kelven.y...@citrix.com
To: users@cloudstack.apache.org
Sent: Tuesday, September 17, 2013 5:13:54 PM
Subject: Re: Unable to start DomR CS 4.1 VMware esxi 5.1
It looks like that the disk image of the VM is corrupted. Do following,
1) Locate the datastore in vCenter on which the system VM is running
2) Open datastore-browse window
3) In the meantime, right click on the problem VM in vCenter (int host
view), chose Edit SettingsŠ to bring up VM configuration dialog
4) Find the VMDK location from the dialog in step 3
5) cross-check your findings about the VMDK in datastore, first check if
the file does exist on datastore
If it is a problem caused by disk corruption, you will need to destroy the
system and let CloudStack recreate it
Kelven
On 9/17/13 2:31 PM, John Skinner john.skin...@appcore.com wrote:
Yes, however on the console it just comes up with Operating System Not
Found error. This is really strange since this was all working fine last
week.
John Skinner
Senior Systems Administrator | Appcore - the business of cloud computing®
Office +1.800.735.7104
Direct +1.515.612.7783 | Mobile +1.515.745.0248
john.skin...@appcore.com | www.appcore.com
--
The information in this message is intended for the named recipients
only. It may contain information that is privileged, confidential or
otherwise protected from disclosure. If you are not the intended
recipient, you are hereby notified that any disclosure, copying,
distribution, or the taking of any action in reliance on the contents of
this message is strictly prohibited. If you have received this e-mail in
error, do not print it or disseminate it or its contents. In such event,
please notify the sender by return e-mail and delete the e-mail file
immediately thereafter. Thank you.
- Original Message -
From: Kelven Yang kelven.y...@citrix.com
To: users@cloudstack.apache.org
Sent: Tuesday, September 17, 2013 4:16:42 PM
Subject: Re: Unable to start DomR CS 4.1 VMware esxi 5.1
Yes, the last step is to configure VNC for the VM.
Are you able to start the VM in vCenter?
Kelven
On 9/17/13 1:50 PM, John Skinner john.skin...@appcore.com wrote:
Looking at the catalina.out log from the management server I see this
right before the error:
INFO [vmware.resource.VmwareResource] (DirectAgent-317:10.0.97.107)
Preparing NIC device on network cloud.public.2502.0.1-vSwitch2
INFO [vmware.resource.VmwareResource] (DirectAgent-317:10.0.97.107)
Configure VNC port for VM r-134-VM, port: 5927, host: 10.0.97.107
Fault {http://schemas.xmlsoap.org/soap/envelope/}Server.generalException
Message A specified parameter was not correct.
ERROR [vmware.mo.VirtualMachineMO] (DirectAgent-317:10.0.97.107) VMware
reconfigVM_Task failed due to A specified parameter was not correct.
com.vmware.vim25.InvalidArgument
WARN [vmware.resource.VmwareResource] (DirectAgent-317:10.0.97.107)
StartCommand failed due to Exception: java.lang.Exception
Message: Failed to configure VM before start. vmName: r-134-VM
java.lang.Exception: Failed to configure VM before start. vmName:
r-134-VM
at
com.cloud.hypervisor.vmware.resource.VmwareResource.execute(VmwareResourc
e
.java:2315)
at
com.cloud.hypervisor.vmware.resource.VmwareResource.executeRequest(Vmware
R
esource.java:419)
at
com.cloud.agent.manager.DirectAgentAttache$Task.run(DirectAgentAttache.ja
v
a:186)
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at
java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
at
who can explain cpu.overprovisioning.factor more detailed?
Hi, What is cpu.overprovisioning.factor use for? Who can explain it more detailed? Thank you. -- Steven Liang Linux System Admin Phone: 1.416.499.8009 ext. 2865 Cell Phone: 1.647.718.5292 Email: stevenli...@yesup.com www.yesup.com | account.yesup.com
Re: Unable to start DomR CS 4.1 VMware esxi 5.1
John,
Yes, the bottom of the disk chain for system VM lands to the template, if
for some reason it is not accessible, it will lead to corrupted disk
content and fail the VM bootstrap process
Kelven
On 9/18/13 9:19 AM, John Skinner john.skin...@appcore.com wrote:
I'll take a look at that. I am wondering if the problem is it is unable
to pull the systemvm template. I noticed that the permissions for the
systemvm .ova file on secondary storage have a different ownership then
the rest of the files on secondary storage. Second thing I noticed, the
template on the vCenter side has a network associated to it that is not
be used by CloudStack and isn't routable in the network at all... and I
am not sure how that happened.
John Skinner
Senior Systems Administrator | Appcore - the business of cloud computing(R)
Office +1.800.735.7104
Direct +1.515.612.7783 | Mobile +1.515.745.0248
john.skin...@appcore.com | www.appcore.com
--
The information in this message is intended for the named recipients
only. It may contain information that is privileged, confidential or
otherwise protected from disclosure. If you are not the intended
recipient, you are hereby notified that any disclosure, copying,
distribution, or the taking of any action in reliance on the contents of
this message is strictly prohibited. If you have received this e-mail in
error, do not print it or disseminate it or its contents. In such event,
please notify the sender by return e-mail and delete the e-mail file
immediately thereafter. Thank you.
- Original Message -
From: Kelven Yang kelven.y...@citrix.com
To: users@cloudstack.apache.org
Sent: Tuesday, September 17, 2013 5:13:54 PM
Subject: Re: Unable to start DomR CS 4.1 VMware esxi 5.1
It looks like that the disk image of the VM is corrupted. Do following,
1) Locate the datastore in vCenter on which the system VM is running
2) Open datastore-browse window
3) In the meantime, right click on the problem VM in vCenter (int host
view), chose Edit SettingsŠ to bring up VM configuration dialog
4) Find the VMDK location from the dialog in step 3
5) cross-check your findings about the VMDK in datastore, first check if
the file does exist on datastore
If it is a problem caused by disk corruption, you will need to destroy the
system and let CloudStack recreate it
Kelven
On 9/17/13 2:31 PM, John Skinner john.skin...@appcore.com wrote:
Yes, however on the console it just comes up with Operating System Not
Found error. This is really strange since this was all working fine last
week.
John Skinner
Senior Systems Administrator | Appcore - the business of cloud computing(R)
Office +1.800.735.7104
Direct +1.515.612.7783 | Mobile +1.515.745.0248
john.skin...@appcore.com | www.appcore.com
--
The information in this message is intended for the named recipients
only. It may contain information that is privileged, confidential or
otherwise protected from disclosure. If you are not the intended
recipient, you are hereby notified that any disclosure, copying,
distribution, or the taking of any action in reliance on the contents of
this message is strictly prohibited. If you have received this e-mail in
error, do not print it or disseminate it or its contents. In such event,
please notify the sender by return e-mail and delete the e-mail file
immediately thereafter. Thank you.
- Original Message -
From: Kelven Yang kelven.y...@citrix.com
To: users@cloudstack.apache.org
Sent: Tuesday, September 17, 2013 4:16:42 PM
Subject: Re: Unable to start DomR CS 4.1 VMware esxi 5.1
Yes, the last step is to configure VNC for the VM.
Are you able to start the VM in vCenter?
Kelven
On 9/17/13 1:50 PM, John Skinner john.skin...@appcore.com wrote:
Looking at the catalina.out log from the management server I see this
right before the error:
INFO [vmware.resource.VmwareResource] (DirectAgent-317:10.0.97.107)
Preparing NIC device on network cloud.public.2502.0.1-vSwitch2
INFO [vmware.resource.VmwareResource] (DirectAgent-317:10.0.97.107)
Configure VNC port for VM r-134-VM, port: 5927, host: 10.0.97.107
Fault {http://schemas.xmlsoap.org/soap/envelope/}Server.generalException
Message A specified parameter was not correct.
ERROR [vmware.mo.VirtualMachineMO] (DirectAgent-317:10.0.97.107) VMware
reconfigVM_Task failed due to A specified parameter was not correct.
com.vmware.vim25.InvalidArgument
WARN [vmware.resource.VmwareResource] (DirectAgent-317:10.0.97.107)
StartCommand failed due to Exception: java.lang.Exception
Message: Failed to configure VM before start. vmName: r-134-VM
java.lang.Exception: Failed to configure VM before start. vmName:
r-134-VM
at
com.cloud.hypervisor.vmware.resource.VmwareResource.execute(VmwareResour
c
e
.java:2315)
at
com.cloud.hypervisor.vmware.resource.VmwareResource.executeRequest(Vmwar
e
R
esource.java:419)
at
Re: who can explain cpu.overprovisioning.factor more detailed?
If you have 1G and a factor of 2, you van instantiate 2 machines with 1G. This is useful of you don't expect all machines top be running art the dame time. Regards, mobile biligual spell checker used Op 18 sep. 2013 17:54 schreef Steven Liang stevenli...@yesup.com het volgende: Hi, What is cpu.overprovisioning.factor use for? Who can explain it more detailed? Thank you. -- *Steven Liang* *Linux System Admin* *Phone*: 1.416.499.8009 ext. 2865 *Cell Phone*: 1.647.718.5292 *Email*: stevenli...@yesup.com www.yesup.com | account.yesup.com [image: Yesup]
Re: Cloudstack 4.1.1 + XCP 1.6 fresh install
Yes. vhd-util needs to be copied in the hypervisor host under /opt/xensource/bin
-Koushik
On 18-Sep-2013, at 8:55 PM, Vadim Kimlaychuk vadim.kimlayc...@elion.ee wrote:
Do you mean I have to copy vhd-util to the server where XCP is installed?
What should be the right path there?
Vadim
From: Carlos Reátegui [create...@gmail.com]
Sent: Wednesday, September 18, 2013 18:15
To: users@cloudstack.apache.org
Cc: users@cloudstack.apache.org
Subject: Re: Cloudstack 4.1.1 + XCP 1.6 fresh install
On a recent install of CS4.1.1 + XS6.1 I thought I had vhd-util in the right
place but it did not get copied to the hosts. It maybe a similar issue here.
Try to copy the vhd-util to the hosts and see if things start working. They
did for me.
On Sep 18, 2013, at 7:28 AM, Vadim Kimlaychuk vadim.kimlayc...@elion.ee
wrote:
Yes, its over there (I have Ubuntu 12.04 LTS) :
root@mgmt4xcp:/home/vadim# ls -al
/usr/share/cloudstack-common/scripts/vm/hypervisor/xenserver/vh*
-rwxr-xr-x 1 root root 318977 Sep 18 15:55
/usr/share/cloudstack-common/scripts/vm/hypervisor/xenserver/vhd-util
Vadim
-Original Message-
From: Ian Duffy [mailto:i...@ianduffy.ie]
Sent: Wednesday, September 18, 2013 5:26 PM
To: users@cloudstack.apache.org
Subject: Re: Cloudstack 4.1.1 + XCP 1.6 fresh install
Did you copy over vhd-util to the correct folder and chmod +x it?
On 18 Sep 2013 15:13, Vadim Kimlaychuk vadim.kimlayc...@elion.ee wrote:
Hello all,
Trying to install subj. several times I have decided to
ask your help. May be someone already faced the same problem? I did
the configuration according to “Installation guide” and always end up
with the same problem: on system VM creation I got repeated errors like
this:
2013-09-18 16:49:21,605 DEBUG [cloud.storage.StorageManagerImpl]
(consoleproxy-1:null) Creating volume: Vol[2|vm=2|ROOT]
2013-09-18 16:49:21,605 DEBUG [cloud.storage.StorageManagerImpl]
(consoleproxy-1:null) Trying to create in Pool[200|NetworkFilesystem]
2013-09-18 16:49:23,381 WARN [xen.resource.CitrixResourceBase]
(DirectAgent-4:null) kill_copy_process failed
2013-09-18 16:49:23,381 WARN [xen.resource.CitrixResourceBase]
(DirectAgent-4:null) can not create vdi in sr
c6e55039-1fb0-5e5d-37d5-118a9ac3abb6
2013-09-18 16:49:23,382 WARN [xen.resource.CitrixResourceBase]
(DirectAgent-4:null) Catch Exception
com.cloud.utils.exception.CloudRuntimeException on
host:e6a339ee-521c-4c67-ac55-cbd256607150 for template: nfs://
192.168.107.142/export/secondary/template/tmpl/1/1/ due to
com.cloud.utils.exception.CloudRuntimeException: can not create vdi in
sr
c6e55039-1fb0-5e5d-37d5-118a9ac3abb6
com.cloud.utils.exception.CloudRuntimeException: can not create vdi in
sr
c6e55039-1fb0-5e5d-37d5-118a9ac3abb6
at
com.cloud.hypervisor.xen.resource.CitrixResourceBase.copy_vhd_from_secondarystorage(CitrixResourceBase.java:2707)
at
com.cloud.hypervisor.xen.resource.CitrixResourceBase.execute(CitrixResourceBase.java:2729)
at
com.cloud.hypervisor.xen.resource.CitrixResourceBase.executeRequest(CitrixResourceBase.java:501)
at
com.cloud.hypervisor.xen.resource.XcpServerResource.executeRequest(XcpServerResource.java:51)
at
com.cloud.agent.manager.DirectAgentAttache$Task.run(DirectAgentAttache.java:186)
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:1146)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:679)
2013-09-18 16:49:23,384 DEBUG [agent.manager.DirectAgentAttache]
(DirectAgent-4:null) Seq 1-1333067786: Response Received:
2013-09-18 16:49:23,385 DEBUG [agent.transport.Request]
(DirectAgent-4:null) Seq 1-1333067786: Processing: { Ans: , MgmtId:
8796752993784, via: 1, Ver: v1, Flags: 110,
[{storage.PrimaryStorageDownloadAnswer:{templateSize:0,result:fa
lse,details:Catch Exception
com.cloud.utils.exception.CloudRuntimeException on
host:e6a339ee-521c-4c67-ac55-cbd256607150 for template: nfs://
192.168.107.142/export/secondary/template/tmpl/1/1/ due to
com.cloud.utils.exception.CloudRuntimeException: can not create vdi in
sr c6e55039-1fb0-5e5d-37d5-118a9ac3abb6,wait:0}}] }
2013-09-18 16:49:23,385 DEBUG [agent.transport.Request]
(secstorage-1:null) Seq 1-1333067786: Received: { Ans: , MgmtId:
8796752993784, via: 1, Ver: v1, Flags:
Re: Cloudstack 4.1.1 + XCP 1.6 fresh install
Hi Vadim,
As Kousik mentioned, please check /opt/xensource/bin/ to see that it got
copied there when the hosts were added to CS (along with several other CS
scripts). It should have been. If not, that is likely the problem.
On Wed, Sep 18, 2013 at 10:45 AM, Koushik Das koushik@citrix.comwrote:
Yes. vhd-util needs to be copied in the hypervisor host under
/opt/xensource/bin
-Koushik
On 18-Sep-2013, at 8:55 PM, Vadim Kimlaychuk vadim.kimlayc...@elion.ee
wrote:
Do you mean I have to copy vhd-util to the server where XCP is
installed? What should be the right path there?
Vadim
From: Carlos Reátegui [create...@gmail.com]
Sent: Wednesday, September 18, 2013 18:15
To: users@cloudstack.apache.org
Cc: users@cloudstack.apache.org
Subject: Re: Cloudstack 4.1.1 + XCP 1.6 fresh install
On a recent install of CS4.1.1 + XS6.1 I thought I had vhd-util in the
right place but it did not get copied to the hosts. It maybe a similar
issue here.
Try to copy the vhd-util to the hosts and see if things start working.
They did for me.
On Sep 18, 2013, at 7:28 AM, Vadim Kimlaychuk vadim.kimlayc...@elion.ee
wrote:
Yes, its over there (I have Ubuntu 12.04 LTS) :
root@mgmt4xcp:/home/vadim# ls -al
/usr/share/cloudstack-common/scripts/vm/hypervisor/xenserver/vh*
-rwxr-xr-x 1 root root 318977 Sep 18 15:55
/usr/share/cloudstack-common/scripts/vm/hypervisor/xenserver/vhd-util
Vadim
-Original Message-
From: Ian Duffy [mailto:i...@ianduffy.ie]
Sent: Wednesday, September 18, 2013 5:26 PM
To: users@cloudstack.apache.org
Subject: Re: Cloudstack 4.1.1 + XCP 1.6 fresh install
Did you copy over vhd-util to the correct folder and chmod +x it?
On 18 Sep 2013 15:13, Vadim Kimlaychuk vadim.kimlayc...@elion.ee
wrote:
Hello all,
Trying to install subj. several times I have decided to
ask your help. May be someone already faced the same problem? I did
the configuration according to “Installation guide” and always end up
with the same problem: on system VM creation I got repeated errors
like this:
2013-09-18 16:49:21,605 DEBUG [cloud.storage.StorageManagerImpl]
(consoleproxy-1:null) Creating volume: Vol[2|vm=2|ROOT]
2013-09-18 16:49:21,605 DEBUG [cloud.storage.StorageManagerImpl]
(consoleproxy-1:null) Trying to create in Pool[200|NetworkFilesystem]
2013-09-18 16:49:23,381 WARN [xen.resource.CitrixResourceBase]
(DirectAgent-4:null) kill_copy_process failed
2013-09-18 16:49:23,381 WARN [xen.resource.CitrixResourceBase]
(DirectAgent-4:null) can not create vdi in sr
c6e55039-1fb0-5e5d-37d5-118a9ac3abb6
2013-09-18 16:49:23,382 WARN [xen.resource.CitrixResourceBase]
(DirectAgent-4:null) Catch Exception
com.cloud.utils.exception.CloudRuntimeException on
host:e6a339ee-521c-4c67-ac55-cbd256607150 for template: nfs://
192.168.107.142/export/secondary/template/tmpl/1/1/ due to
com.cloud.utils.exception.CloudRuntimeException: can not create vdi in
sr
c6e55039-1fb0-5e5d-37d5-118a9ac3abb6
com.cloud.utils.exception.CloudRuntimeException: can not create vdi in
sr
c6e55039-1fb0-5e5d-37d5-118a9ac3abb6
at
com.cloud.hypervisor.xen.resource.CitrixResourceBase.copy_vhd_from_secondarystorage(CitrixResourceBase.java:2707)
at
com.cloud.hypervisor.xen.resource.CitrixResourceBase.execute(CitrixResourceBase.java:2729)
at
com.cloud.hypervisor.xen.resource.CitrixResourceBase.executeRequest(CitrixResourceBase.java:501)
at
com.cloud.hypervisor.xen.resource.XcpServerResource.executeRequest(XcpServerResource.java:51)
at
com.cloud.agent.manager.DirectAgentAttache$Task.run(DirectAgentAttache.java:186)
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:1146)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:679)
2013-09-18 16:49:23,384 DEBUG [agent.manager.DirectAgentAttache]
(DirectAgent-4:null) Seq 1-1333067786: Response Received:
2013-09-18 16:49:23,385 DEBUG [agent.transport.Request]
(DirectAgent-4:null) Seq 1-1333067786: Processing: { Ans: , MgmtId:
8796752993784, via: 1, Ver: v1, Flags: 110,
[{storage.PrimaryStorageDownloadAnswer:{templateSize:0,result:fa
lse,details:Catch Exception
com.cloud.utils.exception.CloudRuntimeException on
Re: who can explain cpu.overprovisioning.factor more detailed?
Thank you for replying. I have another question. If there are only 8 core cpu on every hosts, can I assign 10 cpu to a vm? On 09/18/2013 01:31 PM, Daan Hoogland wrote: If you have 1G and a factor of 2, you van instantiate 2 machines with 1G. This is useful of you don't expect all machines top be running art the dame time. Regards, mobile biligual spell checker used Op 18 sep. 2013 17:54 schreef "Steven Liang" stevenli...@yesup.com het volgende: Hi, What is cpu.overprovisioning.factor use for? Who can explain it more detailed? Thank you. -- Steven Liang Linux System Admin Phone: 1.416.499.8009 ext. 2865 Cell Phone: 1.647.718.5292 Email: stevenli...@yesup.com www.yesup.com | account.yesup.com -- Steven Liang Linux System Admin Phone: 1.416.499.8009 ext. 2865 Cell Phone: 1.647.718.5292 Email: stevenli...@yesup.com www.yesup.com | account.yesup.com
Re: Unable to start DomR CS 4.1 VMware esxi 5.1
Ok. So we stopped CloudStack management, changed the permissions on the .ova for the systemvm template, and removed the references from template_spool_ref to force CloudStack to send the template to vCenter again. We are still seeing this error when trying to start the Domain Router: 2013-09-18 13:59:29,732 ERROR [vmware.mo.VirtualMachineMO] (DirectAgent-42:10.0.97.105) VMware reconfigVM_Task failed due to A specified parameter was not correct. com.vmware.vim25.InvalidArgument - Original Message - From: Kelven Yang kelven.y...@citrix.com To: users@cloudstack.apache.org Sent: Wednesday, September 18, 2013 12:05:49 PM Subject: Re: Unable to start DomR CS 4.1 VMware esxi 5.1 John, Yes, the bottom of the disk chain for system VM lands to the template, if for some reason it is not accessible, it will lead to corrupted disk content and fail the VM bootstrap process Kelven On 9/18/13 9:19 AM, John Skinner john.skin...@appcore.com wrote: I'll take a look at that. I am wondering if the problem is it is unable to pull the systemvm template. I noticed that the permissions for the systemvm .ova file on secondary storage have a different ownership then the rest of the files on secondary storage. Second thing I noticed, the template on the vCenter side has a network associated to it that is not be used by CloudStack and isn't routable in the network at all... and I am not sure how that happened. John Skinner Senior Systems Administrator | Appcore - the business of cloud computing(R) Office +1.800.735.7104 Direct +1.515.612.7783 | Mobile +1.515.745.0248 john.skin...@appcore.com | www.appcore.com -- The information in this message is intended for the named recipients only. It may contain information that is privileged, confidential or otherwise protected from disclosure. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution, or the taking of any action in reliance on the contents of this message is strictly prohibited. If you have received this e-mail in error, do not print it or disseminate it or its contents. In such event, please notify the sender by return e-mail and delete the e-mail file immediately thereafter. Thank you. - Original Message - From: Kelven Yang kelven.y...@citrix.com To: users@cloudstack.apache.org Sent: Tuesday, September 17, 2013 5:13:54 PM Subject: Re: Unable to start DomR CS 4.1 VMware esxi 5.1 It looks like that the disk image of the VM is corrupted. Do following, 1) Locate the datastore in vCenter on which the system VM is running 2) Open datastore-browse window 3) In the meantime, right click on the problem VM in vCenter (int host view), chose Edit SettingsŠ to bring up VM configuration dialog 4) Find the VMDK location from the dialog in step 3 5) cross-check your findings about the VMDK in datastore, first check if the file does exist on datastore If it is a problem caused by disk corruption, you will need to destroy the system and let CloudStack recreate it Kelven On 9/17/13 2:31 PM, John Skinner john.skin...@appcore.com wrote: Yes, however on the console it just comes up with Operating System Not Found error. This is really strange since this was all working fine last week. John Skinner Senior Systems Administrator | Appcore - the business of cloud computing(R) Office +1.800.735.7104 Direct +1.515.612.7783 | Mobile +1.515.745.0248 john.skin...@appcore.com | www.appcore.com -- The information in this message is intended for the named recipients only. It may contain information that is privileged, confidential or otherwise protected from disclosure. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution, or the taking of any action in reliance on the contents of this message is strictly prohibited. If you have received this e-mail in error, do not print it or disseminate it or its contents. In such event, please notify the sender by return e-mail and delete the e-mail file immediately thereafter. Thank you. - Original Message - From: Kelven Yang kelven.y...@citrix.com To: users@cloudstack.apache.org Sent: Tuesday, September 17, 2013 4:16:42 PM Subject: Re: Unable to start DomR CS 4.1 VMware esxi 5.1 Yes, the last step is to configure VNC for the VM. Are you able to start the VM in vCenter? Kelven On 9/17/13 1:50 PM, John Skinner john.skin...@appcore.com wrote: Looking at the catalina.out log from the management server I see this right before the error: INFO [vmware.resource.VmwareResource] (DirectAgent-317:10.0.97.107) Preparing NIC device on network cloud.public.2502.0.1-vSwitch2 INFO [vmware.resource.VmwareResource] (DirectAgent-317:10.0.97.107) Configure VNC port for VM r-134-VM, port: 5927,
Re: who can explain cpu.overprovisioning.factor more detailed?
I'm guessing here; I think you can but you'll get an error deploying it. On Wed, Sep 18, 2013 at 9:03 PM, Steven Liang stevenli...@yesup.com wrote: Thank you for replying. I have another question. If there are only 8 core cpu on every hosts, can I assign 10 cpu to a vm? On 09/18/2013 01:31 PM, Daan Hoogland wrote: If you have 1G and a factor of 2, you van instantiate 2 machines with 1G. This is useful of you don't expect all machines top be running art the dame time. Regards, mobile biligual spell checker used Op 18 sep. 2013 17:54 schreef Steven Liang stevenli...@yesup.com het volgende: Hi, What is cpu.overprovisioning.factor use for? Who can explain it more detailed? Thank you. -- *Steven Liang* *Linux System Admin* *Phone*: 1.416.499.8009 ext. 2865 *Cell Phone*: 1.647.718.5292 *Email*: stevenli...@yesup.com www.yesup.com | account.yesup.com [image: Yesup] -- *Steven Liang* *Linux System Admin* *Phone*: 1.416.499.8009 ext. 2865 *Cell Phone*: 1.647.718.5292 *Email*: stevenli...@yesup.com www.yesup.com | account.yesup.com [image: Yesup]
Re: Unable to start DomR CS 4.1 VMware esxi 5.1
Ok so here is something interesting. I just destroyed the console proxy system VM, and it recreated successfully. However, Domain routers will not create. - Original Message - From: John Skinner john.skin...@appcore.com To: users@cloudstack.apache.org Sent: Wednesday, September 18, 2013 2:08:41 PM Subject: Re: Unable to start DomR CS 4.1 VMware esxi 5.1 Ok. So we stopped CloudStack management, changed the permissions on the .ova for the systemvm template, and removed the references from template_spool_ref to force CloudStack to send the template to vCenter again. We are still seeing this error when trying to start the Domain Router: 2013-09-18 13:59:29,732 ERROR [vmware.mo.VirtualMachineMO] (DirectAgent-42:10.0.97.105) VMware reconfigVM_Task failed due to A specified parameter was not correct. com.vmware.vim25.InvalidArgument - Original Message - From: Kelven Yang kelven.y...@citrix.com To: users@cloudstack.apache.org Sent: Wednesday, September 18, 2013 12:05:49 PM Subject: Re: Unable to start DomR CS 4.1 VMware esxi 5.1 John, Yes, the bottom of the disk chain for system VM lands to the template, if for some reason it is not accessible, it will lead to corrupted disk content and fail the VM bootstrap process Kelven On 9/18/13 9:19 AM, John Skinner john.skin...@appcore.com wrote: I'll take a look at that. I am wondering if the problem is it is unable to pull the systemvm template. I noticed that the permissions for the systemvm .ova file on secondary storage have a different ownership then the rest of the files on secondary storage. Second thing I noticed, the template on the vCenter side has a network associated to it that is not be used by CloudStack and isn't routable in the network at all... and I am not sure how that happened. John Skinner Senior Systems Administrator | Appcore - the business of cloud computing(R) Office +1.800.735.7104 Direct +1.515.612.7783 | Mobile +1.515.745.0248 john.skin...@appcore.com | www.appcore.com -- The information in this message is intended for the named recipients only. It may contain information that is privileged, confidential or otherwise protected from disclosure. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution, or the taking of any action in reliance on the contents of this message is strictly prohibited. If you have received this e-mail in error, do not print it or disseminate it or its contents. In such event, please notify the sender by return e-mail and delete the e-mail file immediately thereafter. Thank you. - Original Message - From: Kelven Yang kelven.y...@citrix.com To: users@cloudstack.apache.org Sent: Tuesday, September 17, 2013 5:13:54 PM Subject: Re: Unable to start DomR CS 4.1 VMware esxi 5.1 It looks like that the disk image of the VM is corrupted. Do following, 1) Locate the datastore in vCenter on which the system VM is running 2) Open datastore-browse window 3) In the meantime, right click on the problem VM in vCenter (int host view), chose Edit SettingsŠ to bring up VM configuration dialog 4) Find the VMDK location from the dialog in step 3 5) cross-check your findings about the VMDK in datastore, first check if the file does exist on datastore If it is a problem caused by disk corruption, you will need to destroy the system and let CloudStack recreate it Kelven On 9/17/13 2:31 PM, John Skinner john.skin...@appcore.com wrote: Yes, however on the console it just comes up with Operating System Not Found error. This is really strange since this was all working fine last week. John Skinner Senior Systems Administrator | Appcore - the business of cloud computing(R) Office +1.800.735.7104 Direct +1.515.612.7783 | Mobile +1.515.745.0248 john.skin...@appcore.com | www.appcore.com -- The information in this message is intended for the named recipients only. It may contain information that is privileged, confidential or otherwise protected from disclosure. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution, or the taking of any action in reliance on the contents of this message is strictly prohibited. If you have received this e-mail in error, do not print it or disseminate it or its contents. In such event, please notify the sender by return e-mail and delete the e-mail file immediately thereafter. Thank you. - Original Message - From: Kelven Yang kelven.y...@citrix.com To: users@cloudstack.apache.org Sent: Tuesday, September 17, 2013 4:16:42 PM Subject: Re: Unable to start DomR CS 4.1 VMware esxi 5.1 Yes, the last step is to configure VNC for the VM. Are you able to start the VM in vCenter? Kelven On 9/17/13 1:50 PM, John Skinner
Security Groups
Having troubles getting security groups to function My test environment is as follows: Cloudstack 4.1.1 on centos6.4Xen Server 6.0.2, CSP installed, iptables running...not sure if it needs to be but it is by default, all xen patches installed.Primary Storage = iscsiSecondary Storage = nfs on mgmt serverSystem VM's and router are running as expected.Network = flat 192.168.50.0/24 I then create 2 instances(vm's) based on the centos5.6 template provided and assign them to the default security group. The instances are able to ping each other, and I thought the expected behavior is that they should not be able to, since the default security group has 0 ingress rules which should block all inbound traffic. What could I be missing??
Re: Security Groups
Hi, Can you please share host 'iptables -L -nv' output on pastebin Thanks, Jayapal On 19-Sep-2013, at 8:04 AM, Michael Phillips mphilli7...@hotmail.com wrote: Having troubles getting security groups to function My test environment is as follows: Cloudstack 4.1.1 on centos6.4Xen Server 6.0.2, CSP installed, iptables running...not sure if it needs to be but it is by default, all xen patches installed.Primary Storage = iscsiSecondary Storage = nfs on mgmt serverSystem VM's and router are running as expected.Network = flat 192.168.50.0/24 I then create 2 instances(vm's) based on the centos5.6 template provided and assign them to the default security group. The instances are able to ping each other, and I thought the expected behavior is that they should not be able to, since the default security group has 0 ingress rules which should block all inbound traffic. What could I be missing??
RE: Security Groups
http://pastebin.com/xf9SBzVY From: jayapalreddy.ur...@citrix.com To: users@cloudstack.apache.org Subject: Re: Security Groups Date: Thu, 19 Sep 2013 03:54:51 + Hi, Can you please share host 'iptables -L -nv' output on pastebin Thanks, Jayapal On 19-Sep-2013, at 8:04 AM, Michael Phillips mphilli7...@hotmail.com wrote: Having troubles getting security groups to function My test environment is as follows: Cloudstack 4.1.1 on centos6.4Xen Server 6.0.2, CSP installed, iptables running...not sure if it needs to be but it is by default, all xen patches installed.Primary Storage = iscsiSecondary Storage = nfs on mgmt serverSystem VM's and router are running as expected.Network = flat 192.168.50.0/24 I then create 2 instances(vm's) based on the centos5.6 template provided and assign them to the default security group. The instances are able to ping each other, and I thought the expected behavior is that they should not be able to, since the default security group has 0 ingress rules which should block all inbound traffic. What could I be missing??
Re: Security Groups
There are no cloudstack configured iptables rules on your xen host. It seems iptables are stopped on the host ? Please check is CSP installed correctly not he host. Please try to force connect or host once. Thanks, Jayapal On 19-Sep-2013, at 9:50 AM, Michael Phillips mphilli7...@hotmail.com wrote: http://pastebin.com/xf9SBzVY From: jayapalreddy.ur...@citrix.com To: users@cloudstack.apache.org Subject: Re: Security Groups Date: Thu, 19 Sep 2013 03:54:51 + Hi, Can you please share host 'iptables -L -nv' output on pastebin Thanks, Jayapal On 19-Sep-2013, at 8:04 AM, Michael Phillips mphilli7...@hotmail.com wrote: Having troubles getting security groups to function My test environment is as follows: Cloudstack 4.1.1 on centos6.4Xen Server 6.0.2, CSP installed, iptables running...not sure if it needs to be but it is by default, all xen patches installed.Primary Storage = iscsiSecondary Storage = nfs on mgmt serverSystem VM's and router are running as expected.Network = flat 192.168.50.0/24 I then create 2 instances(vm's) based on the centos5.6 template provided and assign them to the default security group. The instances are able to ping each other, and I thought the expected behavior is that they should not be able to, since the default security group has 0 ingress rules which should block all inbound traffic. What could I be missing??
RE: Security Groups
Sorry posted the wrong thing...please view this. http://pastebin.com/NF28fpq7 From: jayapalreddy.ur...@citrix.com To: users@cloudstack.apache.org Subject: Re: Security Groups Date: Thu, 19 Sep 2013 04:40:14 + There are no cloudstack configured iptables rules on your xen host. It seems iptables are stopped on the host ? Please check is CSP installed correctly not he host. Please try to force connect or host once. Thanks, Jayapal On 19-Sep-2013, at 9:50 AM, Michael Phillips mphilli7...@hotmail.com wrote: http://pastebin.com/xf9SBzVY From: jayapalreddy.ur...@citrix.com To: users@cloudstack.apache.org Subject: Re: Security Groups Date: Thu, 19 Sep 2013 03:54:51 + Hi, Can you please share host 'iptables -L -nv' output on pastebin Thanks, Jayapal On 19-Sep-2013, at 8:04 AM, Michael Phillips mphilli7...@hotmail.com wrote: Having troubles getting security groups to function My test environment is as follows: Cloudstack 4.1.1 on centos6.4Xen Server 6.0.2, CSP installed, iptables running...not sure if it needs to be but it is by default, all xen patches installed.Primary Storage = iscsiSecondary Storage = nfs on mgmt serverSystem VM's and router are running as expected.Network = flat 192.168.50.0/24 I then create 2 instances(vm's) based on the centos5.6 template provided and assign them to the default security group. The instances are able to ping each other, and I thought the expected behavior is that they should not be able to, since the default security group has 0 ingress rules which should block all inbound traffic. What could I be missing??
