From my experience,
After adding memory or cpu onto hosts, it nomarlly works by putting into the
host maintenance mode and cancel it
Could you give it a try if you run into the same situation again
James.
Original message
Subject: RE: XenServer Memory Increase Problem
From
apache.org
Subject: RE: XenServer Memory Increase Problem
Thanks Nitin, I created Jira Bug:
https://issues.apache.org/jira/browse/CLOUDSTACK-4883
-Soheil
From: Nitin Mehta [nitin.me...@citrix.com]
Sent: Wednesday, October 16, 2013 12:15 PM
To: dev@cloudstack.
Thanks Nitin, I created Jira Bug:
https://issues.apache.org/jira/browse/CLOUDSTACK-4883
-Soheil
From: Nitin Mehta [nitin.me...@citrix.com]
Sent: Wednesday, October 16, 2013 12:15 PM
To: dev@cloudstack.apache.org
Subject: Re: XenServer Memory Increase
Soheil - I guess this is a bug that addition of new memory isn't detected.
File it if not already done.
I would suggest you to change the DB as of now. Right tables are host and
op_host_capacity (capacity_type=0).
You might have to keep in mind the over provisioning factors you have
kept. See if ch
I am running on CloudStack Master 4.3.
I had a use case where my XenServer ran out of memory and I could not create
any more instances on CloudStack.
I shutdown the XenServer and increased the memory on XenServer and brought up
the Management Server again, but the Management Server still sees th
