Re: can't delete zone

mysql> SELECT * FROM cloud.image_store where name = "vmware00"; ++--+-+--+++---+---+--++-+-+++ | id | n

Re: can't delete zone

Backup your db Try SELECT * FROM cloud.image_store; Note the store_id (assume x) SELECT * FROM cloud.template_store_ref where store_id=x; What do you get? On 7/8/15 2:03 PM, Bernhard Dübi wrote: Hi, we have a CloudStack installation with lots of XenServer. Now I tried to configure VMware. U

Re: KVM Node running out of RAM

Please see response in-line On 7/8/15 7:51 AM, Logan Barfield wrote: We've run into this a few times as well. As I understand it the "cut off threshold" applies to a cluster, not an individual hypervisor. So a KVM hypervisor can get filled up regardless (overcommit "1" still means "100%", and

can't delete zone

Hi, we have a CloudStack installation with lots of XenServer. Now I tried to configure VMware. Unfortunatelly something was not working and I decided to delete everything and start over. Now my problem is that I can't delete the secondary storage and the zone. When I try to delete the secondary s

Re: cloudmonkey - account name with spaces

Hi Marco, Are you using the latest version, CloudMonkey 5.3.1? Can you try using double quotes? Like: assign virtualmachine account=“string1 string2” (CloudMonkey using shlex, fyi) The account parameter for the API should be provided as is (in case you were trying to do wild card search using

Unable to spawn new System VMs after server restarted

Hi All, Recently my Server started from backup and last I checked all my Management IPs were full and hence Cloudstack was not able to spawn new System Vms. Trying to solv the issue i cleared all the allocated management ips from op_dc_ip_address_alloc table in database. But now I am getting this

Re: KVM Node running out of RAM

We've run into this a few times as well. As I understand it the "cut off threshold" applies to a cluster, not an individual hypervisor. So a KVM hypervisor can get filled up regardless (overcommit "1" still means "100%", and a hypervisor can fill up while a cluster is still < 85% full). Right no

RE: Deployment failed on XenServer due to capacity miscalculation

Hi Martin, Thanks for the information. From the details below, I understand that your Cluster will not allow additional VMs to be created if 85% of the memory is consumed. This value is important as you also need to factor in what amount of memory is required by the Hypervisor (XenServer) to r

Re: cloudmonkey - account name with spaces

Hi after a deeper investigation I think the issue is in the cloudmonkey.py in the following function as it is using space as delimiter for the options of the command. I will install a cloudmonkey in my test environment and I'll see if I'm right and able to fix it. def default(self, args):

AW: Deployment failed on XenServer due to capacity miscalculation

Hi! The config options are on their default value: mem.overprovisioning.factor = 1 cluster.memory.allocated.capacity.disablethreshold = 0.85 (Would affect the whole cluster capacity, not that of a single host) So nothing strange here. I un- and remanaged the cluster, but no change in numbers :

RE: Deployment failed on XenServer due to capacity miscalculation

Hi Martin, I have seen this before with our CXS environment too. Could of things to check: 1. What is the mem.overprovisioning.factor field set to? 2. What is the cluster.memory.allocated.capacity.disablethreshold field set to? Also, try unmanage the XS Cluster, wait a couple of minutes and re-

AW: Deployment failed on XenServer due to capacity miscalculation

Hi! I tried that ("force reconnect"). But no improvement: Via cloudmonkey, memorytotal-memoryallocated == 4302535168, that's 4103MB. Via XenServer, the host has only 1667 MB free memory. Restarting the management server does not solve it, either. I see this: 2015-07-08 12:03:40,612 DEBUG [c.c.

Re: Deployment failed on XenServer due to capacity miscalculation

hi martin, Make sure that you reconnect server On Tue, Jul 7, 2015 at 4:33 AM, Martin Emrich wrote: > Hi! > > > > I try to create an instance on my ACS (4.4.3, XenServer 6.2 SP1). The > deployment fails on the first host in the cluster, as its memory is nearly > full. > > > > I see this message

AW: ACS does shutdown some VMs

Hello Patrick, good news. One more reason for upgrade. Thanks and regards, Ingo -Ursprüngliche Nachricht- Von: Patrick Chevalley [mailto:patrick.cheval...@b-i.com] Gesendet: Mittwoch, 8. Juli 2015 10:01 An: users@cloudstack.apache.org Betreff: RE: ACS does shutdown some VMs Hello Ingo

Cloudstack 4.5.1 - Upgrade Xenserver 6.1 to 6.2

Hi All, Is there a guide I can follow to upgrade Xenserver from 6.1 to 6.2 on Cloudstack 4.5.1? I'd rather wait for any issues with 6.5 to be completely ironed out before moving to it, 6.2 has been out for a while now. Cheers!

RE: ACS does shutdown some VMs

Hello Ingo, Wrong manipulation, sorry for the previous email. Ran into a similar problem, where my management log was displaying: Unexpected exception when trying to execute queue item, com.cloud.utils.exception.CloudRuntimeException: DB Exception on: com.mysql.jdbc.PreparedStatement@6d36a3e5: D

RE: ACS does shutdown some VMs

-Original Message- From: Jochim, Ingo [mailto:ingo.joc...@bautzen-it.de] Sent: jeudi 25 juin 2015 08:15 To: 'users@cloudstack.apache.org' Subject: AW: ACS does shutdown some VMs Hello all, any idea how to cleanup the job table? Thanks and regards, Ingo -Ursprüngliche Nachricht---

Re: Basic networking issue

Hello, Main issue is when any user in basic networking zone can use any IP from zone's subnet, without any isolation and CS wouldn't know that. On 2015.07.08. 10:09, Sanjeev N wrote: If you want CS not to allocate these IPs to any other vm, you can mark Allocated field in user_ip_address tabl

Re: Basic networking issue

If you want CS not to allocate these IPs to any other vm, you can mark Allocated field in user_ip_address table for all the IPs you want to assign to guest vms manually. On Mon, Jul 6, 2015 at 12:17 PM, Mārtiņš Jakubovičs wrote: > Hello, > > In Basic Networking IP address acquisition is not a ma