RE: 请问cloudstack的两个system vm 为什么不能启动？
查看cloudstack-management日志，很有可能是二级存储的网络有问题。 Date: Mon, 11 Nov 2013 02:54:08 -0500 From: liulin0...@ufl.edu To: users-cn@cloudstack.apache.org Subject: 请问cloudstack的两个system vm 为什么不能启动？ 请问cloudstack的两个system vm 为什么不能启动？ SSVM 和 console poxy 的 status 总是starting. 请问我应该怎么办？ 多谢多谢
Re: not HVM enabled?
Xen HVM是Xen在服务器CPU支持某些虚拟化技术（例如intel VT）的前提下的虚拟化产品，Xen能够使用Qemu来模拟PC的硬件情况，包括BIOS，IDE磁盘、VGA、USB、网络等。在使用Xen HVM虚拟化技术的情况下，服务器无需安装特定的内核即可运行。 检查HVM是否启用 [root@xm xen]# xm dmesg | grep -i hvm (XEN) HVM: VMX enabled 2013/11/10 Du Jun dj199...@gmail.com: When I try to deploy an instance with my template onto a LXC hypervisor host,I get the error message: 2013-11-10 20:30:11,319 DEBUG [allocator.impl.FirstFitAllocator] (Job-Executor-5:job-19 = [ d070b5ba-f342-4252-9137-4d2c1b19eca6 ] FirstFitRoutingAllocator) Not considering hosts: [Host[-4-Routing]] to deploy template: Tmpl[201-TAR-201-2-7444dd2e-2fe3-347b-a9cc-97ba7bdca211 as they are not HVM enabled what does that mean?Any suggestion will be appreciated! - Best regards, Frank -- 白清杰 (Born Bai) 北京开源愿景信息技术有限公司 Mail: linux...@gmail.com
Re: not HVM enabled?
OR you can just update database vm_template set hvm=0 and try to start a new vm again 2013/11/12 linux...@gmail.com linux...@gmail.com Xen HVM是Xen在服务器CPU支持某些虚拟化技术（例如intel VT）的前提下的虚拟化产品，Xen能够使用Qemu来模拟PC的硬件情况，包括BIOS，IDE磁盘、VGA、USB、网络等。在使用Xen HVM虚拟化技术的情况下，服务器无需安装特定的内核即可运行。 检查HVM是否启用 [root@xm xen]# xm dmesg | grep -i hvm (XEN) HVM: VMX enabled 2013/11/10 Du Jun dj199...@gmail.com: When I try to deploy an instance with my template onto a LXC hypervisor host,I get the error message: 2013-11-10 20:30:11,319 DEBUG [allocator.impl.FirstFitAllocator] (Job-Executor-5:job-19 = [ d070b5ba-f342-4252-9137-4d2c1b19eca6 ] FirstFitRoutingAllocator) Not considering hosts: [Host[-4-Routing]] to deploy template: Tmpl[201-TAR-201-2-7444dd2e-2fe3-347b-a9cc-97ba7bdca211 as they are not HVM enabled what does that mean?Any suggestion will be appreciated! - Best regards, Frank -- 白清杰 (Born Bai) 北京开源愿景信息技术有限公司 Mail: linux...@gmail.com
Re: kvm+qemu VM自动停止
不会自动被kill的，cloudstack没有此类设置 你可以看看是否有vm设置了 间隔N分钟待机等等，如果待机可能也会导致cloudstack认为vm状态异常 在 2013年11月11日下午6:26，Wei ZHOU ustcweiz...@gmail.com写道： 你看看/var/log/libvirt/libvirtd.log里面有什么提示 在 2013年11月11日上午2:24，王耀锋 wilc...@hotmail.com写道： hi， 在cloudstack4.2中kvm+qemu的VM自动停止， 出现过好几次这种情况了。我自己的一些分析： 可能是因为单个节点host上VM运行数量过多，导致memory不够分配，于是有些VM的进程自动被kill。 如果我的分析没错，那为什么不自动迁移到别的主机上去？有人遇到过吗，怎么解决？ thanks
”CS从root-volume或者快照启动实例的特性“什么时候出来
hello：
Re: ”CS从root-volume或者快照启动实例的特性“什么时候出来
hi： 目前CS对于从快照恢复用户系统和用户系统的导入/导出场景没有很好的支持。 典型的，当需要把用户的系统做一个备份，然后再恢复用户系统场景中，需要把用户的root盘做成模板，然后从模板再创建实例，不仅操作很麻烦，而且逻辑有问题，因为模板具有被复制和传播的特性，而用户的系统是私有的，不能被传播。 在把已有的xencenter环境迁往cloudstack时，原有的VM可以被导出为.xva或者.ovf的虚拟机格式，但CS不支持导入.xva或者.ovf的格式，就算提取出可启动的.vhd盘，上传到CS后，也不支持启动，需要做成模板，同样遇到逻辑上的尴尬。 如果CS支持从root盘启动，能很好解决这方面的问题。 目前不知道openstack是否支持这个特性，之前G版本好像是不支持。 On Tue, Nov 12, 2013 at 3:14 PM, sunko2014 sunko2...@gmail.com wrote: hello：
Re: F5: Failed to create VLAN
Hi Sanjeev,
The F5 was added after I installed cloudstack
This vlan was not existing at 1.1 before I added the F5 to cloudstack but I
will try it again, just to be sure
Bjoern
On Sunday, November 10, 2013, Sanjeev Neelarapu wrote:
Hi Bjoern,
From the log it looks like you are using 1.1 as the guest (private)
interface and vlan 651 is already configured on the network.
Please remove F5 from CS, clean the interface 1.1 before adding F5 to CS
and add F5.
Now create network with F5 and deploy vms in it. I don't think it is a bug.
Thanks,
Sanjeev
-Original Message-
From: BJO ERN [mailto:bjoern.tei...@gmail.com javascript:;]
Sent: Sunday, November 10, 2013 12:34 PM
To: users@cloudstack.apache.org javascript:;
Subject: F5: Failed to create VLAN
Guys, I hope that there is someone who can help me.
After investing days now to get F5 loadbalancer and Cloudstack (4.2.1
build from sources) I'm pretty much stuck, mostly due to lack of
information and documentation.
I got to a point now where Cloudstack wants to provision a VLAN to spin up
the first VR but it just bails out, what ever I do. Even worse it makes no
sense, the VLAN is created on the F5 so I guess there is just a bug going
on :
*Error Message cloudstack :*
2013-11-09 22:03:49,041 DEBUG [agent.transport.Request]
(Job-Executor-25:job-71 = [ 081a9bd4-6d4d-40d2-9868-48f6aca0116e ]) Seq
7-671875076: Sending { Cmd , MgmtId: 110493122496, via: 7, Ver: v1, Flags:
100011, [{com.cloud.agent.api.ro
uting.IpAssocCommand:{ipAddresses:[{accountId:1,sourceNat:true,add:true,oneToOneNat:false,firstIP:false,vlanId:651,vlanGateway:10.161.2.168,vlanNetmask:255.255.254.0,networkRate:200}],accessDetails:{},wait:
0}}] }
2013-11-09 22:03:49,041 DEBUG [agent.transport.Request]
(Job-Executor-25:job-71 = [ 081a9bd4-6d4d-40d2-9868-48f6aca0116e ]) Seq
7-671875076: Executing: { Cmd , MgmtId: 110493122496, via: 7, Ver: v1,
Flags: 100011, [{com.cloud.agent.api
.routing.IpAssocCommand:{ipAddresses:[{accountId:1,sourceNat:true,add:true,oneToOneNat:false,firstIP:false,vlanId:651,vlanGateway:10.161.2.168,vlanNetmask:255.255.254.0,networkRate:200}],accessDetails:{},wai
t:0}}] }
2013-11-09 22:03:49,042 DEBUG [agent.manager.DirectAgentAttache]
(DirectAgent-220:null) Seq 7-671875076: Executing request
2013-11-09 22:03:49,316 DEBUG [network.resource.F5BigIpResource]
(DirectAgent-220:null) Creating a guest VLAN with tag 651
2013-11-09 22:03:49,398 ERROR [network.resource.F5BigIpResource]
(DirectAgent-220:null) *Failed to execute IPAssocCommand due to
com.cloud.utils.exception.ExecutionException: Failed to create vlan with
tag 651*
2013-11-09 22:03:49,467 ERROR [network.resource.F5BigIpResource]
(DirectAgent-220:null) Retrying IpAssocCommand. Number of retries
remaining: 1
2013-11-09 22:03:49,662 DEBUG [network.resource.F5BigIpResource]
(DirectAgent-220:null) Creating a guest VLAN with tag 651
2013-11-09 22:03:49,685 ERROR [network.resource.F5BigIpResource]
(DirectAgent-220:null) Exception caught in
Networking::urn:iControl:Networking/VLAN::create()
Exception: Common::OperationFailed
primary_error_code : 16908390 (0x01020066)
secondary_error_code : 0
error_string : 01020066:3: The requested VLAN
(/Common/vlan-651) already exists in partition Common.
2013-11-09 22:03:49,685 ERROR [network.resource.F5BigIpResource]
(DirectAgent-220:null) Failed to execute IPAssocCommand due to
com.cloud.utils.exception.ExecutionException: Exception caught in
Networking::urn:iControl:Networking/VLAN::c
reate()
Exception: Common::OperationFailed
primary_error_code : 16908390 (0x01020066)
secondary_error_code : 0
error_string : 01020066:3: The requested VLAN
(/Common/vlan-651) already exists in partition Common.
2013-11-09 22:03:49,701 DEBUG
[storage.secondary.SecondaryStorageManagerImpl] (secstorage-1:null) Zone 1
is ready to launch secondary storage VM
2013-11-09 22:03:49,765 ERROR [network.resource.F5BigIpResource]
(DirectAgent-220:null) Retrying IpAssocCommand. Number of retries
remaining: 0
2013-11-09 22:03:49,910 DEBUG [cloud.consoleproxy.ConsoleProxyManagerImpl]
(consoleproxy-1:null) Zone 1 is ready to launch console proxy
2013-11-09 22:03:49,956 DEBUG [network.resource.F5BigIpResource]
(DirectAgent-220:null) Creating a guest VLAN with tag 651
2013-11-09 22:03:49,976 ERROR [network.resource.F5BigIpResource]
(DirectAgent-220:null) Exception caught in
Networking::urn:iControl:Networking/VLAN::create()
Exception: Common::OperationFailed
primary_error_code : 16908390 (0x01020066)
secondary_error_code : 0
error_string : 01020066:3: The requested VLAN
(/Common/vlan-651) already exists in partition Common.
2013-11-09 22:03:49,977 ERROR [network.resource.F5BigIpResource]
(DirectAgent-220:null) Failed to execute IPAssocCommand due to
com.cloud.utils.exception.ExecutionException: Exception caught in
Reg:Basic Zone csp package install issue
Hi, In basiczone setup, i installed csp in xenserver 6.2 (64bit). Let i know xenserver 6.2 contain inbuilt csp packge. I received following error: [root@xen1 ~]# tar xf xenserver-cloud-supp.tgz [root@xen1 ~]# xe-install-supplemental-pack xenserver-cloud-supp.iso Error: unsatisfied dependency xs:main eq 6.0.2 Do you want to continue? (Y/N) Y Installing 'XenServer Cloud Supp Pack'... error: Failed dependencies: kernel-xen = 2.6.32.12-0.7.1.xs6.0.2.542.170665 is needed by ipset-modul es-xen-2.6.32.12-0.7.1.xs6.0.2.542.170665-4.5-1.xs32.i686 kernel-xen = 2.6.32.12-0.7.1.xs6.0.2.542.170665 is needed by ipset-modul es-kdump-2.6.32.12-0.7.1.xs6.0.2.542.170665-4.5-1.xs32.i686 ./install.sh: line 308: /etc/firstboot.d/99-XenServer-CSP-setup: No such file or directory FATAL: packages failed to install steps followed: = To enable security groups, elastic load balancing, and elastic IP on XenServer, download and install the CloudStack XenServer Support Package (CSP). After installing XenServer, perform the following additional steps on each XenServer host. 1. Download the CSP software onto the XenServer host from one of the following links: For XenServer 6.0.2: http://download.cloud.com/releases/3.0.1/XS-6.0.2/xenserver-cloud-supp.tgz For XenServer 5.6 SP2: http://download.cloud.com/releases/2.2.0/xenserver-cloud-supp.tgz For XenServer 6.0: http://download.cloud.com/releases/3.0/xenserver-cloud-supp.tgz 2. Extract the file: # tar xf xenserver-cloud-supp.tgz 3. Run the following script: # xe-install-supplemental-pack xenserver-cloud-supp.iso 4. If the XenServer host is part of a zone that uses basic networking, disable Open vSwitch (OVS): # xe-switch-network-backend bridge Restart the host machine when prompted. The XenServer host is now ready to be added to CloudStack. Regards, Prakash.M
RE: Reg:Basic Zone csp package install issue
Hi Prakash, XenServer6.2 comes with CSP inbuilt. If you want to use it for basic zone just change the switch network backend to bridge mode. Thanks, Sanjeev -Original Message- From: prak...@assistanz.com [mailto:prak...@assistanz.com] Sent: Monday, November 11, 2013 3:34 PM To: users@cloudstack.apache.org Subject: Reg:Basic Zone csp package install issue Hi, In basiczone setup, i installed csp in xenserver 6.2 (64bit). Let i know xenserver 6.2 contain inbuilt csp packge. I received following error: [root@xen1 ~]# tar xf xenserver-cloud-supp.tgz [root@xen1 ~]# xe-install-supplemental-pack xenserver-cloud-supp.iso Error: unsatisfied dependency xs:main eq 6.0.2 Do you want to continue? (Y/N) Y Installing 'XenServer Cloud Supp Pack'... error: Failed dependencies: kernel-xen = 2.6.32.12-0.7.1.xs6.0.2.542.170665 is needed by ipset-modul es-xen-2.6.32.12-0.7.1.xs6.0.2.542.170665-4.5-1.xs32.i686 kernel-xen = 2.6.32.12-0.7.1.xs6.0.2.542.170665 is needed by ipset-modul es-kdump-2.6.32.12-0.7.1.xs6.0.2.542.170665-4.5-1.xs32.i686 ./install.sh: line 308: /etc/firstboot.d/99-XenServer-CSP-setup: No such file or directory FATAL: packages failed to install steps followed: = To enable security groups, elastic load balancing, and elastic IP on XenServer, download and install the CloudStack XenServer Support Package (CSP). After installing XenServer, perform the following additional steps on each XenServer host. 1. Download the CSP software onto the XenServer host from one of the following links: For XenServer 6.0.2: http://download.cloud.com/releases/3.0.1/XS-6.0.2/xenserver-cloud-supp.tgz For XenServer 5.6 SP2: http://download.cloud.com/releases/2.2.0/xenserver-cloud-supp.tgz For XenServer 6.0: http://download.cloud.com/releases/3.0/xenserver-cloud-supp.tgz 2. Extract the file: # tar xf xenserver-cloud-supp.tgz 3. Run the following script: # xe-install-supplemental-pack xenserver-cloud-supp.iso 4. If the XenServer host is part of a zone that uses basic networking, disable Open vSwitch (OVS): # xe-switch-network-backend bridge Restart the host machine when prompted. The XenServer host is now ready to be added to CloudStack. Regards, Prakash.M
Re: fail to start system vm in cloudstack with lxc
Hi, How do you create instance?As the concept of LXC is different from kvm,and it never use the template that contains a complete OS.So,I think we should change the way we usually think.You can reference this: https://cwiki.apache.org/confluence/display/CLOUDSTACK/LXC+Support+in+Cloudstack# -- Best regards Frank 2013/11/11, 池原 治 ikeh...@joes.co.jp: hi, Unable to find suitable host yes, same situation. 2013-11-09 09:26:17,330 DEBUG [allocator.impl.FirstFitAllocator] (Job-Executor-12:job-12 = [ a2bb39de-bb23-40b1-b06c-3868a45715ff ] FirstFitRoutingAllocator) Not considering hosts: [Host[-4-Routing]] to deploy template: Tmpl[203-ISO-203-2-bfeb7b85-13c7-3b11-a273-c92c4431becf as they are not HVM enabled cloudstack is trying to deploy container as HVM? On 2013/11/10, at 18:42, Du Jun dj199...@gmail.com wrote: Hi, I occur the same problem.Do you get the error message that Unable to find suitable host when you create instance? -- Best regards, Frank 2013/11/9, 池原 治 ikeh...@joes.co.jp: Hi, I met same situation. I found info from dev-ml, On 10/24/2013, 7:00 PM, Chiradeep Vittal wrote: So here's what should work Create zone Add a KVM cluster - add a KVM host - wait for systemvms to start Add a LXC cluster - add a LXC host it seems to be work about systemvm. but I am now stacking to create instance. Regards, O.Ikehara Joe's Cloud Computing On 2013/11/09, at 10:21, Du Jun dj199...@gmail.com wrote: LXC is not a real hypervisor?As the cloudstack4.2 installation guide says,I download the system vm template,why cloudstack can't start system vm through it? If I need KVM to turn them on,would you please tell me more details? --- Best regards, Frank 2013/11/9 Francois Gaudreault fgaudrea...@cloudops.com The SSVM and CPVM won't start on LXC, you need a real hypervisor to run those. (i.e KVM). Then, it will work. Francois On 11/8/2013, 9:51 AM, Du Jun wrote: Hi,all I can add host with lxc hypervisor to cloudstack management server,however I fail to start system vm.Is there any one can provide some clues? -- Francois Gaudreault Architecte de Solution Cloud | Cloud Solutions Architect fgaudrea...@cloudops.com 514-629-6775 - - - CloudOps 420 rue Guy Montréal QC H3J 1S6 www.cloudops.com @CloudOps_
Re: ACS4.2: Unable to add Primary Storage
Hello,
Did you add the primary as a preconfigured ?
Or choosing the NFS as a primary storage ?
Also find this words
KVM supports Shared Mountpoint storage. A shared mountpoint is a file
system path local to each server in a given cluster. The path must be the
same across all Hosts in the cluster, for example /mnt/primary1. This
shared mountpoint is assumed to be a clustered filesystem such as OCFS2.
In this case the CloudStack does not attempt to mount or unmount the
storage as is done with NFS. The CloudStack requires that the
administrator insure that the storage is available
Regards
VM
On 11/11/13 13:16, CK cloudw...@gmail.com wrote:
Hi,
I have just installed ACS 4.2 on Centos 6.4 using the repo:
http://cloudstack.apt-get.eu/rhel/4.2/ for POC purposes (like the DevCloud
but on Centos)
On first startup, I am using the Launch wizard to setup a Basic Zone with
a
KVM host (both KVM and NFS running on management server). The wizard
setups
everything until it gets to the Primary Storage, where I get following
message:
Failed to delete storage pool on host and the wizard stops there. If I
try to add the Primary Storage via Infrastructure Primary Storage Add
Primary Storage I still get the same message. But I can add Secondary
Storage without problem.
I have double checked the NFS and it mounts ok outside of CloudStack.
Note:
both Primary and Secondary mount points are not mounted before running the
wizard.
Can anyone help?
Thanks
The log extract for the Primary Storage is as follows:
2013-11-11 01:52:38,517 DEBUG [cloud.api.ApiServlet]
(catalina-exec-22:null) ===END=== 192.168.2.20 -- POST
command=addHostresponse=jsonsessionkey=FOSFGSl%2BMFut7z2dyOA%2BDiqrZ60%3
D
2013-11-11 01:52:38,546 DEBUG [cloud.api.ApiServlet]
(catalina-exec-17:null) ===START=== 192.168.2.20 -- GET
command=createStoragePoolzoneid=303b03d1-507b-457d-b991-ab019745ef01podI
d=a45a5bde-aa8b-458c-9d48-8338acddb514clusterid=52340bd7-2ab0-43c1-ab44-9
09df68fe788name=Primary1scope=clusterurl=nfs%3A%2F%2F192.168.2.40%2Fmou
nt%2Fprimaryresponse=jsonsessionkey=FOSFGSl%2BMFut7z2dyOA%2BDiqrZ60%3D_
=1384048344807
2013-11-11 01:52:38,644 DEBUG
[datastore.lifecycle.CloudStackPrimaryDataStoreLifeCycleImpl]
(catalina-exec-17:null) createPool Params @ scheme - nfs storageHost -
192.168.2.40 hostPath - /mount/primary port - -1
2013-11-11 01:52:38,696 DEBUG
[datastore.lifecycle.CloudStackPrimaryDataStoreLifeCycleImpl]
(catalina-exec-17:null) creating pool null on host 1
2013-11-11 01:52:38,708 DEBUG [agent.transport.Request]
(catalina-exec-17:null) Seq 1-249364488: Sending { Cmd , MgmtId:
253719053137455, via: 1, Ver: v1, Flags: 100011,
[{com.cloud.agent.api.CreateStoragePoolCommand:{add:true,pool:{id:
1,uuid:a7649155-eede-3007-9c9c-f1e054e7256f,host:192.168.2.40,pat
h:/mount/primary,port:2049,type:NetworkFilesystem},localPath:/
mnt//a7649155-eede-3007-9c9c-f1e054e7256f,wait:0}}]
}
2013-11-11 01:52:38,731 DEBUG [agent.transport.Request]
(AgentManager-Handler-2:null) Seq 1-249364488: Processing: { Ans: ,
MgmtId: 253719053137455, via: 1, Ver: v1, Flags: 10,
[{com.cloud.agent.api.Answer:{result:true,details:success,wait:0
}}]
}
2013-11-11 01:52:38,731 DEBUG [agent.transport.Request]
(catalina-exec-17:null) Seq 1-249364488: Received: { Ans: , MgmtId:
253719053137455, via: 1, Ver: v1, Flags: 10, { Answer } }
2013-11-11 01:52:38,731 DEBUG [agent.manager.AgentManagerImpl]
(catalina-exec-17:null) Details from executing class
com.cloud.agent.api.CreateStoragePoolCommand: success
2013-11-11 01:52:38,732 DEBUG
[datastore.lifecycle.CloudStackPrimaryDataStoreLifeCycleImpl]
(catalina-exec-17:null) In createPool Adding the pool to each of the hosts
2013-11-11 01:52:38,735 DEBUG [cloud.storage.StorageManagerImpl]
(catalina-exec-17:null) Adding pool null to host 1
2013-11-11 01:52:38,743 DEBUG [agent.transport.Request]
(catalina-exec-17:null) Seq 1-249364489: Sending { Cmd , MgmtId:
253719053137455, via: 1, Ver: v1, Flags: 100011,
[{com.cloud.agent.api.ModifyStoragePoolCommand:{add:true,pool:{id:
1,uuid:a7649155-eede-3007-9c9c-f1e054e7256f,host:192.168.2.40,pat
h:/mount/primary,port:2049,type:NetworkFilesystem},localPath:/
mnt//a7649155-eede-3007-9c9c-f1e054e7256f,wait:0}}]
}
2013-11-11 01:52:38,880 DEBUG [agent.transport.Request]
(AgentManager-Handler-3:null) Seq 1-249364489: Processing: { Ans: ,
MgmtId: 253719053137455, via: 1, Ver: v1, Flags: 10,
[{com.cloud.agent.api.Answer:{result:false,details:com.cloud.utils.
exception.CloudRuntimeException:
org.libvirt.LibvirtException: cannot open path
'/mnt/a7649155-eede-3007-9c9c-f1e054e7256f': No such file or
directory\n\tat
com.cloud.hypervisor.kvm.storage.LibvirtStorageAdaptor.createStoragePool(L
ibvirtStorageAdaptor.java:526)\n\tat
com.cloud.hypervisor.kvm.storage.KVMStoragePoolManager.createStoragePool(K
VMStoragePoolManager.java:185)\n\tat
com.cloud.hypervisor.kvm.storage.KVMStoragePoolManager.createStoragePool(K
VMStoragePoolManager.java:177)\n\tat
Re: listUsageRecords fails after deleting an account
Nikolay,
Getting back to this, did you file a bug for it ?
http://issues.apache.org select the CLOUDSTACK project
that way we can track it and make sure it's indeed a bug and that it gets fixed.
thanks,
-sebastien
On Oct 11, 2013, at 11:02 AM, Nikolay Kabadjov niki...@yahoo.com wrote:
Short update:
It turned out that deleted security groups ware in charge instead of deleted
users.
We've managed to overcome by fixing the following codebase:
com.cloud.api.ApiResponseHelper.createUsageResponse
3259 } else if(usageRecord.getUsageType() ==
UsageTypes.SECURITY_GROUP){
3260 //Security Group Id
3261 SecurityGroupVO sg =
_entityMgr.findByIdIncludingRemoved(SecurityGroupVO.class,
usageRecord.getUsageId().toString());
3262 usageRecResponse.setUsageId(sg.getUuid());
3263 }
with
3259 } else if(usageRecord.getUsageType() ==
UsageTypes.SECURITY_GROUP){
3260 //Security Group Id
3261 SecurityGroupVO sg =
_entityMgr.findByIdIncludingRemoved(SecurityGroupVO.class,
usageRecord.getUsageId().toString());
3262 usageRecResponse.setUsageId( (sg!=null)?
sg.getUuid(): missing_security_group_ + usageRecord.getUsageId().toString()
);
3263 }
Regards,
Niki
On Thursday, October 10, 2013 8:01 PM, Nikolay Kabadjov niki...@yahoo.com
wrote:
Nope!
no stack trace
On Thursday, October 10, 2013 7:58 PM, Alena Prokharchyk
alena.prokharc...@citrix.com wrote:
On 10/10/13 9:31 AM, Nikolay Kabadjov niki...@yahoo.com wrote:
The only
meaningfull line in the log is:
2013-10-10 18:29:06,063 ERROR [cloud.api.ApiServer] (ApiServer-3:null)
unhandled exception executing api command: listUsageRecords
java.lang.NullPointerException
On Thursday, October 10, 2013 6:46 PM, Nikolay Kabadjov
niki...@yahoo.com wrote:
I've got the following response with no further explanation and no
exceptions in the management-server.log related to the issue
{
listusagerecordsresponse: {
errorcode: 530,
cserrorcode:
}
}
Any idea?
How could I overcome this peculiar situation?
Thanks,
Niki
Niki, is there a stack trace for the NPE? Without the line number its hard
to tell where it fails.
Re: Domain Admin can't create accounts, how to handle reselling?
I'll put in a ticket now. :) On 11/9/13, 7:48 AM, Daan Hoogland wrote: Hey David, Andrija, Did you guys make an jira ticket for this? It sounds like something Schuberg Philis wants as well. Let's discuss further. Daan On Thu, Nov 7, 2013 at 9:52 PM, Andrija Panic andrija.pa...@gmail.com wrote: Also having the same issue / dilemma... Sent from Google Nexus 4 On Nov 7, 2013 7:25 PM, David Matteson dmatte...@a2hosting.com wrote: Hey everybody, We're trying to figure out the logistics of how a Reseller accounts might work under CloudStack. Initially we thought Domain Admins would be perfect for this, but they cannot create accounts within their domain (or even, apparently, users) so this makes that not feasible. Obviously giving ROOT Admin access to a Reseller is not ideal either. Has anyone else come up with a solution for this? Right now the only option seems to be some kind of wrapper around CloudStack that provide the Reseller ability to create accounts only under their own domain, which is highly sub-optimal. Thanks.
Re: F5: Failed to create VLAN
Yes I verified it and it happens still.
Can't add Vlans to an 11.4 LTM device, same error.
Bjoern
On Monday, November 11, 2013, BJO ERN wrote:
Hi Sanjeev,
The F5 was added after I installed cloudstack
This vlan was not existing at 1.1 before I added the F5 to cloudstack but
I will try it again, just to be sure
Bjoern
On Sunday, November 10, 2013, Sanjeev Neelarapu wrote:
Hi Bjoern,
From the log it looks like you are using 1.1 as the guest (private)
interface and vlan 651 is already configured on the network.
Please remove F5 from CS, clean the interface 1.1 before adding F5 to CS
and add F5.
Now create network with F5 and deploy vms in it. I don't think it is a bug.
Thanks,
Sanjeev
-Original Message-
From: BJO ERN [mailto:bjoern.tei...@gmail.com]
Sent: Sunday, November 10, 2013 12:34 PM
To: users@cloudstack.apache.org
Subject: F5: Failed to create VLAN
Guys, I hope that there is someone who can help me.
After investing days now to get F5 loadbalancer and Cloudstack (4.2.1
build from sources) I'm pretty much stuck, mostly due to lack of
information and documentation.
I got to a point now where Cloudstack wants to provision a VLAN to spin up
the first VR but it just bails out, what ever I do. Even worse it makes no
sense, the VLAN is created on the F5 so I guess there is just a bug going
on :
*Error Message cloudstack :*
2013-11-09 22:03:49,041 DEBUG [agent.transport.Request]
(Job-Executor-25:job-71 = [ 081a9bd4-6d4d-40d2-9868-48f6aca0116e ]) Seq
7-671875076: Sending { Cmd , MgmtId: 110493122496, via: 7, Ver: v1, Flags:
100011, [{com.cloud.agent.api.ro
uting.IpAssocCommand:{ipAddresses:[{accountId:1,sourceNat:true,add:true,oneToOneNat:false,firstIP:false,vlanId:651,vlanGateway:10.161.2.168,vlanNetmask:255.255.254.0,networkRate:200}],accessDetails:{},wait:
0}}] }
2013-11-09 22:03:49,041 DEBUG [agent.transport.Request]
(Job-Executor-25:job-71 = [ 081a9bd4-6d4d-40d2-9868-48f6aca0116e ]) Seq
7-671875076: Executing: { Cmd , MgmtId: 110493122496, via: 7, Ver: v1,
Flags: 100011, [{com.cloud.agent.api
.routing.IpAssocCommand:{ipAddresses:[{accountId:1,sourceNat:true,add:true,oneToOneNat:false,firstIP:false,vlanId:651,vlanGateway:10.161.2.168,vlanNetmask:255.255.254.0,networkRate:200}],accessDetails:{},wai
t:0}}] }
2013-11-09 22:03:49,042 DEBUG [agent.manager.DirectAgentAttache]
(DirectAgent-220:null) Seq 7-671875076: Executing request
2013-11-09 22:03:49,316 DEBUG [network.resource.F5BigIpResource]
(DirectAgent-220:null) Creating a guest VLAN with tag 651
2013-11-09 22:03:49,398 ERROR [network.resource.F5BigIpResource]
(DirectAgent-220:null) *Failed to execute IPAssocCommand due to
com.cloud.utils.exception.ExecutionException: Failed to create vlan with
tag 651*
2013-11-09 22:03:49,467 ERROR [network.resource.F5BigIpResource]
(DirectAgent-220:null) Retrying IpAssocCommand. Number of retries
remaining: 1
2013-11-09 22:03:49,662 DEBUG [network.resource.F5BigIpResource]
(DirectAgent-220:null) Creating a guest VLAN with tag 651
2013-11-09 22:03:49,685 ERROR [network.resource.F5BigIpResource]
(DirectAgent-220:null) Exception caught in
Networking::urn:iControl:Networking/VLAN::create()
Exception: Common::OperationFailed
primary_error_code : 16908390 (0x01020066)
secondary_error_code : 0
error_string : 01020066:3: The requested VLAN
(/Common/vlan-651) already exists in partition Common.
2013-11-09 22:03:49,685 ERROR [network.resource.F5BigIpResource]
(DirectAgent-220:null) Failed to execute IPAssocCommand due to
com.cloud.utils.exception.ExecutionException: Exception caught in
Networking::urn:iControl:Networking/VLAN::c
reate()
Exception: Common::OperationFailed
primary_error_code : 16908390 (0x01020066)
secondary_error_code : 0
error_string : 01020066:3: The requested VLAN
(/Common/vlan-651) already exists in partition Common.
2013-11-09 22:03:49,701 DEBUG
[storage.secondary.SecondaryStorageManagerImpl] (secstorage-1:null) Zone 1
is ready to launch secondary storage VM
2013-11-09 22:03:49,765 ERROR [network.resource.F5BigIpResource]
(DirectAgent-220:null) Retrying IpAssocCommand. Number of retries
remaining: 0
2013-11-09 22:03:49,910 DEBUG [cloud.consoleproxy.ConsoleProxyManagerImpl]
(consoleproxy-1:null) Zone 1 is ready to launch console proxy
2013-11-09 22:03:49,956 DEBUG [network.resource.F5BigIpResource]
(DirectAgent-220:null) Creating a g
Re: agent not running in ssvm
Hello, I was wondering if anyone else is experiencing this issue? I am having identical problem with Ubuntu 12.04 kvm host and ACS 4.2.0. Basically, I've got two clusters, cluster1 and cluster2. Cluster1 is using centos 6.4 as kvm host and cluster2 uses ubuntu 12.04. I am planning to decommission cluster1 and I am having a bunch of issues doing that. One of the problems is with ssvm. If I destroy ssvm it always starts on cluster1. I can't make it to start on cluster2. So, what i've tried is i've stopped ssvm and migrated its disk volume over to the storage pool available on cluster2. I've manually updated db entries including host_id, last_host_id and pool_id. The SSVM starts just fine, but the agent is always show as Disconnected even though the same procedure works just fine with CPVM - it's agent is up and running. What i've noticed while running ssvm-check script is it is incorrectly lists the nfs server. Like this: - root@s-825-VM:/var/log/cloud# /usr/local/cloud/systemvm/ssvm-check.sh First DNS server is 192.168.169.254 PING 192.168.169.254 (192.168.169.254): 56 data bytes 64 bytes from 192.168.169.254: icmp_seq=0 ttl=64 time=0.304 ms 64 bytes from 192.168.169.254: icmp_seq=1 ttl=64 time=0.309 ms --- 192.168.169.254 ping statistics --- 2 packets transmitted, 2 packets received, 0% packet loss round-trip min/avg/max/stddev = 0.304/0.306/0.309/0.000 ms Good: Can ping DNS server Good: DNS resolves download.cloud.com ERROR: NFS is not currently mounted Try manually mounting from inside the VM NFS server is eth2 ping: unknown host WARNING: cannot ping NFS server routing table follows Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 0.0.0.0 82.*.*.* 0.0.0.0 UG 0 0 0 eth2 82.*.*.* 0.0.0.0 255.255.255.192 U 0 0 0 eth2 169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth0 192.168.169.0 0.0.0.0 255.255.255.0 U 0 0 0 eth1 192.168.169.0 0.0.0.0 255.255.255.0 U 0 0 0 eth3 Management server is 192.168.169.250. Checking connectivity. Good: Can connect to management server port 8250 ERROR: Java process not running. Try restarting the SSVM. - Two things from the above look odd. First, the NFS server is not eth2! My nfs server is 192.168.169.202, it's not eth2. The ACS gui shows the secondary storage server as nfs://192.168.169.202:/secondary. I can mount this path within the ssvm. The second strange thing is that its got both eth1 and eth3 configured in the same management range - 192.168.169.0/24. Not sure if this is meant to be like this or something is broken. Restarting the agent produces the following log entries: - 15:46:59,916 INFO AgentShell:403 - Agent started log4j:ERROR No output stream or file set for the appender named [FILE3]. 15:46:59,920 INFO AgentShell:411 - Implementation Version is 4.2.0 15:46:59,920 INFO AgentShell:267 - agent.properties found at /usr/local/cloud/systemvm/conf/agent.properties Invalid Parameter: internaldns2= 15:46:59,924 INFO AgentShell:423 - Defaulting to using properties file for storage 15:46:59,930 INFO AgentShell:434 - Defaulting to the constant time backoff algorithm 15:46:59,936 INFO LogUtils:31 - log4j configuration found at /usr/local/cloud/systemvm/conf/log4j-cloud.xml log4j:WARN No such property [maxFileSize] in org.apache.log4j.rolling.RollingFileAppender. log4j:WARN No such property [maxBackupIndex] in org.apache.log4j.rolling.RollingFileAppender. log4j:WARN Please set a rolling policy for the RollingFileAppender named 'FILE3' log4j:ERROR No output stream or file set for the appender named [FILE3]. 15:46:59,990 ERROR AgentShell:549 - Unable to start agent: Resource class not found: com.cloud.storage.resource.PremiumSecondaryStorageResource due to: java.lang.ClassNotFoundException: com.cloud.storage.resource.PremiumSecondaryStorageResource Unable to start agent: Resource class not found: com.cloud.storage.resource.PremiumSecondaryStorageResource due to: java.lang.ClassNotFoundException: com.cloud.storage.resource.PremiumSecondaryStorageResource ./run.sh: line 29: ./_run.sh: No such file or directory 2013-11-11 15:46:59,916 INFO [cloud.agent.AgentShell] (main:null) Agent started 2013-11-11 15:46:59,920 INFO [cloud.agent.AgentShell] (main:null) Implementation Version is 4.2.0 2013-11-11 15:46:59,920 INFO [cloud.agent.AgentShell] (main:null) agent.properties found at /usr/local/cloud/systemvm/conf/agent.properties 2013-11-11 15:46:59,923 DEBUG [cloud.agent.AgentShell] (main:null) Found property: instance 2013-11-11 15:46:59,924 DEBUG [cloud.agent.AgentShell] (main:null) Found property: resource 2013-11-11 15:46:59,924 INFO [cloud.agent.AgentShell] (main:null)
Wondering KVM
Hello All , Sorry for this stupid question but i really wonder why KVM is used or trying to use as a hypervisor option. (Sorry for out of scope of this list) but try to learn people understandings, also i do not want to say do not use it :D Mostly third party supported hypervisor is vmware XenServer and Hyper-v is i guess mostly third party supported hypervisors Then i can see the KVM , because of mostly IBM focus on it My point of view ; Using iscsi, FC is a problem because need shared mount point No internal DRS or WLB or kind of distributing algorithm. Backup , no any 3th party software i know support KVM If we start to talk about Disaster Recovery finding solution should be very hard If its free Citrix XenServer is free I¹m confusing when i think all , i don¹t know any performance pluses then the other hypervisors but i don¹t know how to compare it with all such parameters Of course every people have their own ideas but could you pls share it to understand better. Regards VM
Re: Networking issues when vRouter is on different host
Jake, what network card are you using? Is it a broadcom chip by any chance? Andrei - Original Message - From: Jake G. dj_dark_jungl...@yahoo.com To: users@cloudstack.apache.org Sent: Monday, 11 November, 2013 4:44:16 AM Subject: Networking issues when vRouter is on different host Hi All, I'm running Cloudstack 4.2 on CentOS 6.4 with 2 KVM hosts using advanced networking. I have 3 networks on 2 physical NICs. eth0 - Management, Storage traffic eth0.900 - Guest Network VLAN 900 on the physical NIC, but a Guest VM vlan range of 600-699 handled by the CS vRouter. eth1 - Internet, public traffic I am able to deploy Guest VMs in the cluster containing the 2 KVM hosts. I can also ping the vRouter and other Guest VMs located on the other host of the cluster. Lastly, I can receive Guest IPs from the vRouter`s DHCP service no problem. My problem is, I am unable to connect to the internet and/or the internet is extremely slow (200bytes/sec) from a Guest VM that is located on a different host than the vRouter. Guest machines that are located on the same host of the vRouter work fine. Could this possibly be a MTU issue? As far as I know everything should be the default MTU 1500. Thank you very much!
Re: Domain Admin can't create accounts, how to handle reselling?
Hi, I guess there is no need to to open a ticket. http://markmail.org/message/ucxsapyannat2z6b https://issues.apache.org/jira/browse/CLOUDSTACK-4830 2013/11/11 David Matteson dmatte...@a2hosting.com I'll put in a ticket now. :) On 11/9/13, 7:48 AM, Daan Hoogland wrote: Hey David, Andrija, Did you guys make an jira ticket for this? It sounds like something Schuberg Philis wants as well. Let's discuss further. Daan On Thu, Nov 7, 2013 at 9:52 PM, Andrija Panic andrija.pa...@gmail.com wrote: Also having the same issue / dilemma... Sent from Google Nexus 4 On Nov 7, 2013 7:25 PM, David Matteson dmatte...@a2hosting.com wrote: Hey everybody, We're trying to figure out the logistics of how a Reseller accounts might work under CloudStack. Initially we thought Domain Admins would be perfect for this, but they cannot create accounts within their domain (or even, apparently, users) so this makes that not feasible. Obviously giving ROOT Admin access to a Reseller is not ideal either. Has anyone else come up with a solution for this? Right now the only option seems to be some kind of wrapper around CloudStack that provide the Reseller ability to create accounts only under their own domain, which is highly sub-optimal. Thanks. -- Rafael Weingärtner
Re: Wondering KVM
On 11.11.2013 16:24, Vahric Muhtaryan wrote: Hello All , Sorry for this stupid question but i really wonder why KVM is used or trying to use as a hypervisor option. (Sorry for out of scope of this list) but try to learn people understandings, also i do not want to say do not use it :D Mostly third party supported hypervisor is vmware XenServer and Hyper-v is i guess mostly third party supported hypervisors Then i can see the KVM , because of mostly IBM focus on it My point of view ; Using iscsi, FC is a problem because need shared mount point No internal DRS or WLB or kind of distributing algorithm. Backup , no any 3th party software i know support KVM If we start to talk about Disaster Recovery finding solution should be very hard If its free Citrix XenServer is free I¹m confusing when i think all , i don¹t know any performance pluses then the other hypervisors but i don¹t know how to compare it with all such parameters Of course every people have their own ideas but could you pls share it to understand better. Regards VM There are many advantages to using KVM. Think of it like the Linux of the virtualisation world. Start learning it, fast. :) The main reason I like it is that it comes bundled with the linux kernel, as such I can just keep running my favourite linux distro that I know and trust and which can do more than a minimal management layer. Need to run a VM on the same box with a CPanel? Done,just yum install it. Need to test something in a VM on your PXE deployment box? Done, yum install it. On an ARM server? Done. Need to run NFS server, cloudstack management server, mysql server and hypervisor on the same box? Done. :) It's very flexible, geeky and it's a bit DIY, most sysadmins I know love this part of it and it has turned out a great success. It's simple, it doesn't try to do too much, it's a hypervisor and that's what it does, the rest is done by hand or through libvirt. It has no Windows management interfaces (so IT managers stay away), though Cloudstack helps in this case. :) It's free and open source, which is amazing really. It comes with a nice VNC replacement (http://www.spice-space.org/) that is also free and open source (and supported in other stacks). It can talk to a lot of block device stuff (CEPH, GlusterFS, iSCSI, Sheepdog etc etc) and I bet it will be the first to support whatever new (open source) technology comes along. It's from RedHat (yeah, I know) which has a really good karma considering. etc etc -- Sent from the Delta quadrant using Borg technology! Nux! www.nux.ro
RE: agent not running in ssvm
See, if this is of any help for you: https://cwiki.apache.org/confluence/display/CLOUDSTACK/SSVM%2C+templates%2C+Secondary+storage+troubleshooting --Sanjay -Original Message- From: Andrei Mikhailovsky [mailto:and...@arhont.com] Sent: Monday, November 11, 2013 9:47 PM To: users@cloudstack.apache.org Subject: Re: agent not running in ssvm Hello, I was wondering if anyone else is experiencing this issue? I am having identical problem with Ubuntu 12.04 kvm host and ACS 4.2.0. Basically, I've got two clusters, cluster1 and cluster2. Cluster1 is using centos 6.4 as kvm host and cluster2 uses ubuntu 12.04. I am planning to decommission cluster1 and I am having a bunch of issues doing that. One of the problems is with ssvm. If I destroy ssvm it always starts on cluster1. I can't make it to start on cluster2. So, what i've tried is i've stopped ssvm and migrated its disk volume over to the storage pool available on cluster2. I've manually updated db entries including host_id, last_host_id and pool_id. The SSVM starts just fine, but the agent is always show as Disconnected even though the same procedure works just fine with CPVM - it's agent is up and running. What i've noticed while running ssvm-check script is it is incorrectly lists the nfs server. Like this: - root@s-825-VM:/var/log/cloud# /usr/local/cloud/systemvm/ssvm-check.sh First DNS server is 192.168.169.254 PING 192.168.169.254 (192.168.169.254): 56 data bytes 64 bytes from 192.168.169.254: icmp_seq=0 ttl=64 time=0.304 ms 64 bytes from 192.168.169.254: icmp_seq=1 ttl=64 time=0.309 ms --- 192.168.169.254 ping statistics --- 2 packets transmitted, 2 packets received, 0% packet loss round-trip min/avg/max/stddev = 0.304/0.306/0.309/0.000 ms Good: Can ping DNS server Good: DNS resolves download.cloud.com ERROR: NFS is not currently mounted Try manually mounting from inside the VM NFS server is eth2 ping: unknown host WARNING: cannot ping NFS server routing table follows Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 0.0.0.0 82.*.*.* 0.0.0.0 UG 0 0 0 eth2 82.*.*.* 0.0.0.0 255.255.255.192 U 0 0 0 eth2 169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth0 192.168.169.0 0.0.0.0 255.255.255.0 U 0 0 0 eth1 192.168.169.0 0.0.0.0 255.255.255.0 U 0 0 0 eth3 Management server is 192.168.169.250. Checking connectivity. Good: Can connect to management server port 8250 ERROR: Java process not running. Try restarting the SSVM. - Two things from the above look odd. First, the NFS server is not eth2! My nfs server is 192.168.169.202, it's not eth2. The ACS gui shows the secondary storage server as nfs://192.168.169.202:/secondary. I can mount this path within the ssvm. The second strange thing is that its got both eth1 and eth3 configured in the same management range - 192.168.169.0/24. Not sure if this is meant to be like this or something is broken. Restarting the agent produces the following log entries: - 15:46:59,916 INFO AgentShell:403 - Agent started log4j:ERROR No output stream or file set for the appender named [FILE3]. 15:46:59,920 INFO AgentShell:411 - Implementation Version is 4.2.0 15:46:59,920 INFO AgentShell:267 - agent.properties found at /usr/local/cloud/systemvm/conf/agent.properties Invalid Parameter: internaldns2= 15:46:59,924 INFO AgentShell:423 - Defaulting to using properties file for storage 15:46:59,930 INFO AgentShell:434 - Defaulting to the constant time backoff algorithm 15:46:59,936 INFO LogUtils:31 - log4j configuration found at /usr/local/cloud/systemvm/conf/log4j-cloud.xml log4j:WARN No such property [maxFileSize] in org.apache.log4j.rolling.RollingFileAppender. log4j:WARN No such property [maxBackupIndex] in org.apache.log4j.rolling.RollingFileAppender. log4j:WARN Please set a rolling policy for the RollingFileAppender named 'FILE3' log4j:ERROR No output stream or file set for the appender named [FILE3]. 15:46:59,990 ERROR AgentShell:549 - Unable to start agent: Resource class not found: com.cloud.storage.resource.PremiumSecondaryStorageResource due to: java.lang.ClassNotFoundException: com.cloud.storage.resource.PremiumSecondaryStorageResource Unable to start agent: Resource class not found: com.cloud.storage.resource.PremiumSecondaryStorageResource due to: java.lang.ClassNotFoundException: com.cloud.storage.resource.PremiumSecondaryStorageResource ./run.sh: line 29: ./_run.sh: No such file or directory 2013-11-11 15:46:59,916 INFO [cloud.agent.AgentShell] (main:null) Agent started 2013-11-11 15:46:59,920 INFO [cloud.agent.AgentShell] (main:null) Implementation Version is 4.2.0 2013-11-11
Re: Wondering KVM
I can only speak for me why we are moving to KVM. It starts with license costs which will be an issue once you have several hundred hosts like I have. Going on we were a big Citrix Xen shop but after issues with Citrix Xenserver 6 (XCP variant) like openvswitch performance issues, XAPI communication issues between VMs and hypervisor we decided to switch. Overall important is stability above features and another big plus for KVM is you can easily roll out bare metal via Kickstart and Puppet/Chef a option we only discovered recently for xenserver. Now is xenserver free but there were still enough issues in the past for us to even consider it again. On Mon, Nov 11, 2013 at 8:24 AM, Vahric Muhtaryan vah...@doruk.net.trwrote: Hello All , Sorry for this stupid question but i really wonder why KVM is used or trying to use as a hypervisor option. (Sorry for out of scope of this list) but try to learn people understandings, also i do not want to say do not use it :D Mostly third party supported hypervisor is vmware XenServer and Hyper-v is i guess mostly third party supported hypervisors Then i can see the KVM , because of mostly IBM focus on it My point of view ; Using iscsi, FC is a problem because need shared mount point No internal DRS or WLB or kind of distributing algorithm. Backup , no any 3th party software i know support KVM If we start to talk about Disaster Recovery finding solution should be very hard If its free Citrix XenServer is free I¹m confusing when i think all , i don¹t know any performance pluses then the other hypervisors but i don¹t know how to compare it with all such parameters Of course every people have their own ideas but could you pls share it to understand better. Regards VM
RE: Problems with Secondary Storage on Cloudstack 4.2
Secondary storage is managed by system VM. Try to read this guide and follow the advices given for every possible problem: https://cwiki.apache.org/confluence/display/CLOUDSTACK/SSVM,+templates,+Secondary+storage+troubleshooting In my case ssvm-check.sh shows that everything is correct, but SSVM itself could not resolve the hostname where NFS storage was mounted to. So in my case I fixed the problem by adding storage IP to hosts file. In your case may be there is no route to host where NFS is (your management and storage are in different subnets) or something else. Try to log in into SSVM and troubleshoot from the console. Vadim. -Original Message- From: Vahric Muhtaryan [mailto:vah...@doruk.net.tr] Sent: Saturday, November 09, 2013 5:06 PM To: CloudStack SupportMailingList; sugandh.sinha.dbst_irdst...@dbst.iitd.ac.in Subject: Re: Problems with Secondary Storage on Cloudstack 4.2 Hi Sugandh , Nothing mounted to system you can not fallow it like that but via file system activity you can find it Also pls check the logs On nodes for example i have Xen and under /var/run, there are directories named with GUIDs , mounts are happening there Regards Vahric Muhtaryan On 09/11/13 15:18, Daan Hoogland daan.hoogl...@gmail.com wrote: Sugandh, Is this a problem, or are you wondering how come? It seams to me that secondary storage does not have to be mounted all the time only when templates or snapshots need copying over. regards, Daan On Fri, Nov 8, 2013 at 11:01 AM, Sugandh sugandh.s.dbst_irdst...@dbst.iitd.ac.in wrote: Hello, I am having some issues with Secondary storage on Cloudstack 4.2. My setup is as follows: 1) Both the management server and hypervisor host are on the same system, which is running Ubuntu 12.04, and is assigned an IP 10.208.67.86. 2) Another system which is also running Ubuntu 12.04 is serving as both primary storage and secondary storage and has an IP 10.208.66.162. My problem is that when I run mount on management server, I can only see my primary storage mounted. I'd really appreciate any help. Thanks ahead, Sugandh
replace host best practice
Hey! I use CS 4.2 and XenServer 6.2 I have had this issue several times: If the host fails, Cloudstack does not take notice. It thinks the host and the system VMs are still running. Cloudstack ignoring a complete host failure does concern me in the long run but no that much for now. The problem is cloudstack neither lets me delete the System VMs, the primary storage nor the host. Isn't there a better way than fiddling directly with the database and probably messing up the installation? I managed to delete the host but I have still the System VMs and the storage volumes. I think deletion fails because cloudstack can for obvious reasons not reach the host. What is best practice for this use case? Thanks! Lisa
Create primary storage entry via API
Hey! I use CS 4.2 and XenServer 6.2 This is about primary local storage on the XS host. CS deletes the Local Storage SR and creates a new one in its place with the UUID as the name. That is fine but I still have to look up the SR UUID/name in XenCenter and create the primary storage manually via the CS GUI. If CS creates this SR why does it not create the corresponding primary storage entry right away? Anyway, is there a way to get the UUID/name of the XS SR via the Cloudstack API so I can automate the process of adding the primary storage? Thank you, Lisa
Basic Zone Virtual Router Issues
I have a couple issues with the current setup involving the virtual router. 1. I'm not using the VR for port forwarding / VPN / routing or anything traffic related so it would seem to me to be relatively trivial to have a secondary virtual router that just provides DNS, userdata metadata. This would be sufficient for all my failover requirements. 2. It would also be useful to be able to set DNS options in a basic zone. Timeout, attempts etc. Timeout on linux is set to 5 seconds which is an eternity in case of failure. Are people comfortable with a single VR in a basic zone, and what mitigations can be put in place to avoid any fallout from failures?
Re: agent not running in ssvm
nfs://192.168.169.202:/secondary is not a valid nfs address. You may have better luck with nfs://192.168.169.202/secondary On 11 November 2013 10:17, Andrei Mikhailovsky and...@arhont.com wrote: Hello, I was wondering if anyone else is experiencing this issue? I am having identical problem with Ubuntu 12.04 kvm host and ACS 4.2.0. Basically, I've got two clusters, cluster1 and cluster2. Cluster1 is using centos 6.4 as kvm host and cluster2 uses ubuntu 12.04. I am planning to decommission cluster1 and I am having a bunch of issues doing that. One of the problems is with ssvm. If I destroy ssvm it always starts on cluster1. I can't make it to start on cluster2. So, what i've tried is i've stopped ssvm and migrated its disk volume over to the storage pool available on cluster2. I've manually updated db entries including host_id, last_host_id and pool_id. The SSVM starts just fine, but the agent is always show as Disconnected even though the same procedure works just fine with CPVM - it's agent is up and running. What i've noticed while running ssvm-check script is it is incorrectly lists the nfs server. Like this: - root@s-825-VM:/var/log/cloud# /usr/local/cloud/systemvm/ssvm-check.sh First DNS server is 192.168.169.254 PING 192.168.169.254 (192.168.169.254): 56 data bytes 64 bytes from 192.168.169.254: icmp_seq=0 ttl=64 time=0.304 ms 64 bytes from 192.168.169.254: icmp_seq=1 ttl=64 time=0.309 ms --- 192.168.169.254 ping statistics --- 2 packets transmitted, 2 packets received, 0% packet loss round-trip min/avg/max/stddev = 0.304/0.306/0.309/0.000 ms Good: Can ping DNS server Good: DNS resolves download.cloud.com ERROR: NFS is not currently mounted Try manually mounting from inside the VM NFS server is eth2 ping: unknown host WARNING: cannot ping NFS server routing table follows Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 0.0.0.0 82.*.*.* 0.0.0.0 UG 0 0 0 eth2 82.*.*.* 0.0.0.0 255.255.255.192 U 0 0 0 eth2 169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth0 192.168.169.0 0.0.0.0 255.255.255.0 U 0 0 0 eth1 192.168.169.0 0.0.0.0 255.255.255.0 U 0 0 0 eth3 Management server is 192.168.169.250. Checking connectivity. Good: Can connect to management server port 8250 ERROR: Java process not running. Try restarting the SSVM. - Two things from the above look odd. First, the NFS server is not eth2! My nfs server is 192.168.169.202, it's not eth2. The ACS gui shows the secondary storage server as nfs://192.168.169.202:/secondary. I can mount this path within the ssvm. The second strange thing is that its got both eth1 and eth3 configured in the same management range - 192.168.169.0/24. Not sure if this is meant to be like this or something is broken. Restarting the agent produces the following log entries: - 15:46:59,916 INFO AgentShell:403 - Agent started log4j:ERROR No output stream or file set for the appender named [FILE3]. 15:46:59,920 INFO AgentShell:411 - Implementation Version is 4.2.0 15:46:59,920 INFO AgentShell:267 - agent.properties found at /usr/local/cloud/systemvm/conf/agent.properties Invalid Parameter: internaldns2= 15:46:59,924 INFO AgentShell:423 - Defaulting to using properties file for storage 15:46:59,930 INFO AgentShell:434 - Defaulting to the constant time backoff algorithm 15:46:59,936 INFO LogUtils:31 - log4j configuration found at /usr/local/cloud/systemvm/conf/log4j-cloud.xml log4j:WARN No such property [maxFileSize] in org.apache.log4j.rolling.RollingFileAppender. log4j:WARN No such property [maxBackupIndex] in org.apache.log4j.rolling.RollingFileAppender. log4j:WARN Please set a rolling policy for the RollingFileAppender named 'FILE3' log4j:ERROR No output stream or file set for the appender named [FILE3]. 15:46:59,990 ERROR AgentShell:549 - Unable to start agent: Resource class not found: com.cloud.storage.resource.PremiumSecondaryStorageResource due to: java.lang.ClassNotFoundException: com.cloud.storage.resource.PremiumSecondaryStorageResource Unable to start agent: Resource class not found: com.cloud.storage.resource.PremiumSecondaryStorageResource due to: java.lang.ClassNotFoundException: com.cloud.storage.resource.PremiumSecondaryStorageResource ./run.sh: line 29: ./_run.sh: No such file or directory 2013-11-11 15:46:59,916 INFO [cloud.agent.AgentShell] (main:null) Agent started 2013-11-11 15:46:59,920 INFO [cloud.agent.AgentShell] (main:null) Implementation Version is 4.2.0 2013-11-11 15:46:59,920 INFO [cloud.agent.AgentShell] (main:null) agent.properties found at /usr/local/cloud/systemvm/conf/agent.properties 2013-11-11 15:46:59,923 DEBUG [cloud.agent.AgentShell]
Re: Basic Zone Virtual Router Issues
Op 12 november 2013 om 0:07 schreef Nick Wales n...@nickwales.co.uk: I have a couple issues with the current setup involving the virtual router. 1. I'm not using the VR for port forwarding / VPN / routing or anything traffic related so it would seem to me to be relatively trivial to have a secondary virtual router that just provides DNS, userdata metadata. This would be sufficient for all my failover requirements. 2. It would also be useful to be able to set DNS options in a basic zone. Timeout, attempts etc. Timeout on linux is set to 5 seconds which is an eternity in case of failure. Are people comfortable with a single VR in a basic zone, and what mitigations can be put in place to avoid any fallout from failures? Hi Nick, When the VR is down, you could run into some issues especially when you are recovering from hardware failure. In this case the instances that are down will not start until you fixed the router. This is quite logical cause they need DHCP for example. The router startup was quite slow in the past. We run about 400 VMs per pod, and you will not be very happy when it takes about 1 hour to reconfigure all DHCP entries. Luckily, the VR startup time has been improved a lot lately, and for us the same process takes about 15 minutes but still, it could be faster in the future. So when the VR doesn't boot you cannot boot your other VMs which could be problematic even if it takes only 15 minutes. Because of this we are planning to move SSVMs (including the VR) to a seperate cluster so it doesn't run next to instances of our clients so both cannot (or shouldn't) be offline at the same time. Anyway, if you plan to run like up to 50 instances in a pod (using the same VR), this will won't be a problem for you cause VR startup time will probably be acceptable. When you recreate the VR (which you should be able to do whenever you want), it will likely receive a new IP and you VMs need to renew their DHCP lease to receive the new IP adres for DNS. This is why we have chosen not to use the DNS server of the VR. Hope this helps! Met vriendelijke groet / Kind regards, Lennert den Teuling Tel direct: +31 (0)118 700 210
Re: ACS4.2: Unable to add Primary Storage
Hi,
When using the Launch Wizard it only gives the option of NFS for primary
storage - Shared Mountpoint is not offered. So I used NFS for primary
storage which results in the error above.
However, I can add Primary Storage using Shared Mountpoint from the
Infrastructure screen, but NFS fails. So the question is why can I not add
Primary Storage using NFS in ACS 4.2?
Btw what do you mean by Did you add the primary as a preconfigured ?
Thanks
On 11 November 2013 12:52, Vahric Muhtaryan vah...@doruk.net.tr wrote:
Hello,
Did you add the primary as a preconfigured ?
Or choosing the NFS as a primary storage ?
Also find this words
KVM supports Shared Mountpoint storage. A shared mountpoint is a file
system path local to each server in a given cluster. The path must be the
same across all Hosts in the cluster, for example /mnt/primary1. This
shared mountpoint is assumed to be a clustered filesystem such as OCFS2.
In this case the CloudStack does not attempt to mount or unmount the
storage as is done with NFS. The CloudStack requires that the
administrator insure that the storage is available
Regards
VM
On 11/11/13 13:16, CK cloudw...@gmail.com wrote:
Hi,
I have just installed ACS 4.2 on Centos 6.4 using the repo:
http://cloudstack.apt-get.eu/rhel/4.2/ for POC purposes (like the
DevCloud
but on Centos)
On first startup, I am using the Launch wizard to setup a Basic Zone with
a
KVM host (both KVM and NFS running on management server). The wizard
setups
everything until it gets to the Primary Storage, where I get following
message:
Failed to delete storage pool on host and the wizard stops there. If I
try to add the Primary Storage via Infrastructure Primary Storage Add
Primary Storage I still get the same message. But I can add Secondary
Storage without problem.
I have double checked the NFS and it mounts ok outside of CloudStack.
Note:
both Primary and Secondary mount points are not mounted before running the
wizard.
Can anyone help?
Thanks
The log extract for the Primary Storage is as follows:
2013-11-11 01:52:38,517 DEBUG [cloud.api.ApiServlet]
(catalina-exec-22:null) ===END=== 192.168.2.20 -- POST
command=addHostresponse=jsonsessionkey=FOSFGSl%2BMFut7z2dyOA%2BDiqrZ60%3
D
2013-11-11 01:52:38,546 DEBUG [cloud.api.ApiServlet]
(catalina-exec-17:null) ===START=== 192.168.2.20 -- GET
command=createStoragePoolzoneid=303b03d1-507b-457d-b991-ab019745ef01podI
d=a45a5bde-aa8b-458c-9d48-8338acddb514clusterid=52340bd7-2ab0-43c1-ab44-9
09df68fe788name=Primary1scope=clusterurl=nfs%3A%2F%2F192.168.2.40%2Fmou
nt%2Fprimaryresponse=jsonsessionkey=FOSFGSl%2BMFut7z2dyOA%2BDiqrZ60%3D_
=1384048344807
2013-11-11 01:52:38,644 DEBUG
[datastore.lifecycle.CloudStackPrimaryDataStoreLifeCycleImpl]
(catalina-exec-17:null) createPool Params @ scheme - nfs storageHost -
192.168.2.40 hostPath - /mount/primary port - -1
2013-11-11 01:52:38,696 DEBUG
[datastore.lifecycle.CloudStackPrimaryDataStoreLifeCycleImpl]
(catalina-exec-17:null) creating pool null on host 1
2013-11-11 01:52:38,708 DEBUG [agent.transport.Request]
(catalina-exec-17:null) Seq 1-249364488: Sending { Cmd , MgmtId:
253719053137455, via: 1, Ver: v1, Flags: 100011,
[{com.cloud.agent.api.CreateStoragePoolCommand:{add:true,pool:{id:
1,uuid:a7649155-eede-3007-9c9c-f1e054e7256f,host:192.168.2.40,pat
h:/mount/primary,port:2049,type:NetworkFilesystem},localPath:/
mnt//a7649155-eede-3007-9c9c-f1e054e7256f,wait:0}}]
}
2013-11-11 01:52:38,731 DEBUG [agent.transport.Request]
(AgentManager-Handler-2:null) Seq 1-249364488: Processing: { Ans: ,
MgmtId: 253719053137455, via: 1, Ver: v1, Flags: 10,
[{com.cloud.agent.api.Answer:{result:true,details:success,wait:0
}}]
}
2013-11-11 01:52:38,731 DEBUG [agent.transport.Request]
(catalina-exec-17:null) Seq 1-249364488: Received: { Ans: , MgmtId:
253719053137455, via: 1, Ver: v1, Flags: 10, { Answer } }
2013-11-11 01:52:38,731 DEBUG [agent.manager.AgentManagerImpl]
(catalina-exec-17:null) Details from executing class
com.cloud.agent.api.CreateStoragePoolCommand: success
2013-11-11 01:52:38,732 DEBUG
[datastore.lifecycle.CloudStackPrimaryDataStoreLifeCycleImpl]
(catalina-exec-17:null) In createPool Adding the pool to each of the hosts
2013-11-11 01:52:38,735 DEBUG [cloud.storage.StorageManagerImpl]
(catalina-exec-17:null) Adding pool null to host 1
2013-11-11 01:52:38,743 DEBUG [agent.transport.Request]
(catalina-exec-17:null) Seq 1-249364489: Sending { Cmd , MgmtId:
253719053137455, via: 1, Ver: v1, Flags: 100011,
[{com.cloud.agent.api.ModifyStoragePoolCommand:{add:true,pool:{id:
1,uuid:a7649155-eede-3007-9c9c-f1e054e7256f,host:192.168.2.40,pat
h:/mount/primary,port:2049,type:NetworkFilesystem},localPath:/
mnt//a7649155-eede-3007-9c9c-f1e054e7256f,wait:0}}]
}
2013-11-11 01:52:38,880 DEBUG [agent.transport.Request]
(AgentManager-Handler-3:null) Seq 1-249364489: Processing: { Ans: ,
MgmtId: 253719053137455, via: 1, Ver: v1,
Re: Basic Zone Virtual Router Issues
Thanks Lennert. My issue isn't around the state of the VR as such, we've destroyed and brought back plenty with no issue, more so the impact it going down will have on my instances. We're looking at consolidation ratios of 40 to 1 so Pods will have a large number of instances. We have been trying to work out the best way to use external DNS servers my main issue there has been that puppet requires the FQDN of the instance which they won't get until the external DNS servers respond appropriately which slows things down. We have been testing scripts to push DNS entries from the instances at start up which seems to work ok. How do you approach this problem? Nick On 11 November 2013 17:44, Lennert den Teuling lenn...@pcextreme.nl wrote: Op 12 november 2013 om 0:07 schreef Nick Wales n...@nickwales.co.uk: I have a couple issues with the current setup involving the virtual router. 1. I'm not using the VR for port forwarding / VPN / routing or anything traffic related so it would seem to me to be relatively trivial to have a secondary virtual router that just provides DNS, userdata metadata. This would be sufficient for all my failover requirements. 2. It would also be useful to be able to set DNS options in a basic zone. Timeout, attempts etc. Timeout on linux is set to 5 seconds which is an eternity in case of failure. Are people comfortable with a single VR in a basic zone, and what mitigations can be put in place to avoid any fallout from failures? Hi Nick, When the VR is down, you could run into some issues especially when you are recovering from hardware failure. In this case the instances that are down will not start until you fixed the router. This is quite logical cause they need DHCP for example. The router startup was quite slow in the past. We run about 400 VMs per pod, and you will not be very happy when it takes about 1 hour to reconfigure all DHCP entries. Luckily, the VR startup time has been improved a lot lately, and for us the same process takes about 15 minutes but still, it could be faster in the future. So when the VR doesn't boot you cannot boot your other VMs which could be problematic even if it takes only 15 minutes. Because of this we are planning to move SSVMs (including the VR) to a seperate cluster so it doesn't run next to instances of our clients so both cannot (or shouldn't) be offline at the same time. Anyway, if you plan to run like up to 50 instances in a pod (using the same VR), this will won't be a problem for you cause VR startup time will probably be acceptable. When you recreate the VR (which you should be able to do whenever you want), it will likely receive a new IP and you VMs need to renew their DHCP lease to receive the new IP adres for DNS. This is why we have chosen not to use the DNS server of the VR. Hope this helps! Met vriendelijke groet / Kind regards, Lennert den Teuling Tel direct: +31 (0)118 700 210
Re: agent not running in ssvm
It was my mistype in the email. ACS has the right values and i've checked that i can mount it from within the ssvm. Any other ideas? - Original Message - From: Nick Wales n...@nickwales.co.uk To: users@cloudstack.apache.org Sent: Monday, 11 November, 2013 11:12:34 PM Subject: Re: agent not running in ssvm nfs://192.168.169.202:/secondary is not a valid nfs address. You may have better luck with nfs://192.168.169.202/secondary On 11 November 2013 10:17, Andrei Mikhailovsky and...@arhont.com wrote: Hello, I was wondering if anyone else is experiencing this issue? I am having identical problem with Ubuntu 12.04 kvm host and ACS 4.2.0. Basically, I've got two clusters, cluster1 and cluster2. Cluster1 is using centos 6.4 as kvm host and cluster2 uses ubuntu 12.04. I am planning to decommission cluster1 and I am having a bunch of issues doing that. One of the problems is with ssvm. If I destroy ssvm it always starts on cluster1. I can't make it to start on cluster2. So, what i've tried is i've stopped ssvm and migrated its disk volume over to the storage pool available on cluster2. I've manually updated db entries including host_id, last_host_id and pool_id. The SSVM starts just fine, but the agent is always show as Disconnected even though the same procedure works just fine with CPVM - it's agent is up and running. What i've noticed while running ssvm-check script is it is incorrectly lists the nfs server. Like this: - root@s-825-VM:/var/log/cloud# /usr/local/cloud/systemvm/ssvm-check.sh First DNS server is 192.168.169.254 PING 192.168.169.254 (192.168.169.254): 56 data bytes 64 bytes from 192.168.169.254: icmp_seq=0 ttl=64 time=0.304 ms 64 bytes from 192.168.169.254: icmp_seq=1 ttl=64 time=0.309 ms --- 192.168.169.254 ping statistics --- 2 packets transmitted, 2 packets received, 0% packet loss round-trip min/avg/max/stddev = 0.304/0.306/0.309/0.000 ms Good: Can ping DNS server Good: DNS resolves download.cloud.com ERROR: NFS is not currently mounted Try manually mounting from inside the VM NFS server is eth2 ping: unknown host WARNING: cannot ping NFS server routing table follows Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 0.0.0.0 82.*.*.* 0.0.0.0 UG 0 0 0 eth2 82.*.*.* 0.0.0.0 255.255.255.192 U 0 0 0 eth2 169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth0 192.168.169.0 0.0.0.0 255.255.255.0 U 0 0 0 eth1 192.168.169.0 0.0.0.0 255.255.255.0 U 0 0 0 eth3 Management server is 192.168.169.250. Checking connectivity. Good: Can connect to management server port 8250 ERROR: Java process not running. Try restarting the SSVM. - Two things from the above look odd. First, the NFS server is not eth2! My nfs server is 192.168.169.202, it's not eth2. The ACS gui shows the secondary storage server as nfs://192.168.169.202:/secondary. I can mount this path within the ssvm. The second strange thing is that its got both eth1 and eth3 configured in the same management range - 192.168.169.0/24. Not sure if this is meant to be like this or something is broken. Restarting the agent produces the following log entries: - 15:46:59,916 INFO AgentShell:403 - Agent started log4j:ERROR No output stream or file set for the appender named [FILE3]. 15:46:59,920 INFO AgentShell:411 - Implementation Version is 4.2.0 15:46:59,920 INFO AgentShell:267 - agent.properties found at /usr/local/cloud/systemvm/conf/agent.properties Invalid Parameter: internaldns2= 15:46:59,924 INFO AgentShell:423 - Defaulting to using properties file for storage 15:46:59,930 INFO AgentShell:434 - Defaulting to the constant time backoff algorithm 15:46:59,936 INFO LogUtils:31 - log4j configuration found at /usr/local/cloud/systemvm/conf/log4j-cloud.xml log4j:WARN No such property [maxFileSize] in org.apache.log4j.rolling.RollingFileAppender. log4j:WARN No such property [maxBackupIndex] in org.apache.log4j.rolling.RollingFileAppender. log4j:WARN Please set a rolling policy for the RollingFileAppender named 'FILE3' log4j:ERROR No output stream or file set for the appender named [FILE3]. 15:46:59,990 ERROR AgentShell:549 - Unable to start agent: Resource class not found: com.cloud.storage.resource.PremiumSecondaryStorageResource due to: java.lang.ClassNotFoundException: com.cloud.storage.resource.PremiumSecondaryStorageResource Unable to start agent: Resource class not found: com.cloud.storage.resource.PremiumSecondaryStorageResource due to: java.lang.ClassNotFoundException: com.cloud.storage.resource.PremiumSecondaryStorageResource
Re: Networking issues when vRouter is on different host
Hi! So i figured out that it was due to MTU settings. In order for the guest traffic on host`s physical NIC eth0.900 to traverse the switch I had to reduce the MTU on the guest VM to 1496. My guess is because the vlan tag 900 adds 4 bytes to the packets sent out the host`s NIC eth0.900. My switch is not configured for fragmentation so the packets where being dropped. On Tuesday, November 12, 2013 1:35 AM, Andrei Mikhailovsky and...@arhont.com wrote: Jake, what network card are you using? Is it a broadcom chip by any chance? Andrei - Original Message - From: Jake G. dj_dark_jungl...@yahoo.com To: users@cloudstack.apache.org Sent: Monday, 11 November, 2013 4:44:16 AM Subject: Networking issues when vRouter is on different host Hi All, I'm running Cloudstack 4.2 on CentOS 6.4 with 2 KVM hosts using advanced networking. I have 3 networks on 2 physical NICs. eth0 - Management, Storage traffic eth0.900 - Guest Network VLAN 900 on the physical NIC, but a Guest VM vlan range of 600-699 handled by the CS vRouter. eth1 - Internet, public traffic I am able to deploy Guest VMs in the cluster containing the 2 KVM hosts. I can also ping the vRouter and other Guest VMs located on the other host of the cluster. Lastly, I can receive Guest IPs from the vRouter`s DHCP service no problem. My problem is, I am unable to connect to the internet and/or the internet is extremely slow (200bytes/sec) from a Guest VM that is located on a different host than the vRouter. Guest machines that are located on the same host of the vRouter work fine. Could this possibly be a MTU issue? As far as I know everything should be the default MTU 1500. Thank you very much!
Unable to take Snapshots with KVM
Hi, CS 4.2 on CentOS 6.4 with KVM. I get the following error when trying to take a snapshot of a instance. Is this function not available with KVM? KVM Snapshot is not supported: 1 Thank you
Re: Unable to take Snapshots with KVM
Bjoern, That worked! Thank you On Tuesday, November 12, 2013 1:18 PM, BJO ERN bjoern.tei...@gmail.com wrote: First you need to set kvm.snapshot.enabled to true After that you can make snapshots from volumes not the whole VM like ths vm snapshot button would do (It does disk + memory which is not support in KVM). Just navigate to your volumes and use that snapshot function Bye, Bjoern On Mon, Nov 11, 2013 at 6:25 PM, Jake G. dj_dark_jungl...@yahoo.com wrote: Hi, CS 4.2 on CentOS 6.4 with KVM. I get the following error when trying to take a snapshot of a instance. Is this function not available with KVM? KVM Snapshot is not supported: 1 Thank you
Re: F5: Failed to create VLAN
FYI.
So it turn out it might be a bug in the F5 virtual edition.
When I did a test with a older physical F5 I was at least able to install
the VLAN..
So far I think the Ethernet media detection in the VE edition is a problem.
At least it's documented as known bug; a error is logged which might be
reported up to the icontrol client and causing cloudstack to fail.
If I get more info I'll let you know.
Thanks,
Bjoern
On Mon, Nov 11, 2013 at 8:16 AM, BJO ERN bjoern.tei...@gmail.com wrote:
Yes I verified it and it happens still.
Can't add Vlans to an 11.4 LTM device, same error.
Bjoern
On Monday, November 11, 2013, BJO ERN wrote:
Hi Sanjeev,
The F5 was added after I installed cloudstack
This vlan was not existing at 1.1 before I added the F5 to cloudstack but
I will try it again, just to be sure
Bjoern
On Sunday, November 10, 2013, Sanjeev Neelarapu wrote:
Hi Bjoern,
From the log it looks like you are using 1.1 as the guest (private)
interface and vlan 651 is already configured on the network.
Please remove F5 from CS, clean the interface 1.1 before adding F5 to CS
and add F5.
Now create network with F5 and deploy vms in it. I don't think it is a
bug.
Thanks,
Sanjeev
-Original Message-
From: BJO ERN [mailto:bjoern.tei...@gmail.com]
Sent: Sunday, November 10, 2013 12:34 PM
To: users@cloudstack.apache.org
Subject: F5: Failed to create VLAN
Guys, I hope that there is someone who can help me.
After investing days now to get F5 loadbalancer and Cloudstack (4.2.1
build from sources) I'm pretty much stuck, mostly due to lack of
information and documentation.
I got to a point now where Cloudstack wants to provision a VLAN to spin
up the first VR but it just bails out, what ever I do. Even worse it makes
no sense, the VLAN is created on the F5 so I guess there is just a bug
going on :
*Error Message cloudstack :*
2013-11-09 22:03:49,041 DEBUG [agent.transport.Request]
(Job-Executor-25:job-71 = [ 081a9bd4-6d4d-40d2-9868-48f6aca0116e ]) Seq
7-671875076: Sending { Cmd , MgmtId: 110493122496, via: 7, Ver: v1,
Flags:
100011, [{com.cloud.agent.api.ro
uting.IpAssocCommand:{ipAddresses:[{accountId:1,sourceNat:true,add:true,oneToOneNat:false,firstIP:false,vlanId:651,vlanGateway:10.161.2.168,vlanNetmask:255.255.254.0,networkRate:200}],accessDetails:{},wait:
0}}] }
2013-11-09 22:03:49,041 DEBUG [agent.transport.Request]
(Job-Executor-25:job-71 = [ 081a9bd4-6d4d-40d2-9868-48f6aca0116e ]) Seq
7-671875076: Executing: { Cmd , MgmtId: 110493122496, via: 7, Ver: v1,
Flags: 100011, [{com.cloud.agent.api
.routing.IpAssocCommand:{ipAddresses:[{accountId:1,sourceNat:true,add:true,oneToOneNat:false,firstIP:false,vlanId:651,vlanGateway:10.161.2.168,vlanNetmask:255.255.254.0,networkRate:200}],accessDetails:{},wai
t:0}}] }
2013-11-09 22:03:49,042 DEBUG [agent.manager.DirectAgentAttache]
(DirectAgent-220:null) Seq 7-671875076: Executing request
2013-11-09 22:03:49,316 DEBUG [network.resource.F5BigIpResource]
(DirectAgent-220:null) Creating a guest VLAN with tag 651
2013-11-09 22:03:49,398 ERROR [network.resource.F5BigIpResource]
(DirectAgent-220:null) *Failed to execute IPAssocCommand due to
com.cloud.utils.exception.ExecutionException: Failed to create vlan with
tag 651*
2013-11-09 22:03:49,467 ERROR [network.resource.F5BigIpResource]
(DirectAgent-220:null) Retrying IpAssocCommand. Number of retries
remaining: 1
2013-11-09 22:03:49,662 DEBUG [network.resource.F5BigIpResource]
(DirectAgent-220:null) Creating a guest VLAN with tag 651
2013-11-09 22:03:49,685 ERROR [network.resource.F5BigIpResource]
(DirectAgent-220:null) Exception caught in
Networking::urn:iControl:Networking/VLAN::create()
Exception: Common::OperationFailed
primary_error_code : 16908390 (0x01020066)
secondary_error_code : 0
error_string : 01020066:3: The requested VLAN
(/Common/vlan-651) already exists in partition Common.
2013-11-09 22:03:49,685 ERROR [network.resource.F5BigIpResource]
(DirectAgent-220:null) Failed to execute IPAssocCommand due to
com.cloud.utils.exception.ExecutionException: Exception caught in
Networking::urn:iControl:Networking/VLAN::c
reate()
Exception: Common::OperationFailed
primary_error_code : 16908390 (0x01020066)
secondary_error_code : 0
error_string : 01020066:3: The requested VLAN
(/Common/vlan-651) already exists in partition Common.
2013-11-09 22:03:49,701 DEBUG
[storage.secondary.SecondaryStorageManagerImpl] (secstorage-1:null) Zone
1 is ready to launch secondary storage VM
2013-11-09 22:03:49,765 ERROR [network.resource.F5BigIpResource]
(DirectAgent-220:null) Retrying IpAssocCommand. Number of retries
remaining: 0
2013-11-09 22:03:49,910 DEBUG [cloud.consoleproxy.ConsoleProxyManagerImpl]
(consoleproxy-1:null) Zone 1 is ready to launch console proxy
2013-11-09 22:03:49,956 DEBUG [network.resource.F5BigIpResource]
(DirectAgent-220:null) Creating a g
Advanced Networking with CloudStack
Apologies if this is a repeat, I couldn't find this in the archives and I previously wasn't subscribed to this list. Hello guys, I have a special client request that I'm not quite certain the most secure way to fulfil. Client wants to host a virtual office environment of Windows VMs on the cloud but needs the VMs to be connected to an onsite print/scan/fax. Access to all VMs must be available at this same onsite office via thinclients but some VMs must also be able to be RDPed in from a remote location. My first instinct would be to install a virtual router with a single static IP (maybe 2) but I'm not sure if there will be any negative implications of such a setup. Onsite, there would be a VPN compatible router that would talk to the virtual router to establish the VPN so that the onsite thinclients can connect to the VMs via RDP to their internal IPs. Since the printer is plugged to the same VPN router, this would allow all VMs connect to the printer directly. Regarding the issue about external RDP, the virtual router would forward specific ports to specific computers. Targets will be identified via the port being connected to - i.e. x.x.x.x:1 redirects to VM1:3389, 2 to VM2:3389 etc. I understand that I can modify the listen port on RDP but these VMs will be created from template so a common port would be the least troublesome. Alternatively, the virtual router could authenticate the redirections via MAC address but I think this would be an administrative nightmare. So after reading my wall of text, my questions would be: 1. Any VPN routers that work well with CloudStack? 2. Can someone point me to some links on how to setup the virtual router based on the above requirements? 3. Do advise if not having a particular static IP for the VPN router (means the virtual router would have to listen to traffic from all global traffic) would be opening a can of worms. Thank you in advance. Regards, Joshua
