The last host of this VM is in avoid set

2013-06-03 Thread Aditya
Hi, I am running CloudStack with XenServer 6.0.2. The setup was working fine till yesterday when I started getting this when trying to restart stopped instances. (The host is not overutilized and there is plenty of RAM/HDD space available - Local Storage 40% utilized, Memory 2GB/14.6GB

Re: The last host of this VM is in avoid set

2013-06-03 Thread Shanker Balan
On 03-Jun-2013, at 6:15 PM, Aditya adi...@savitr.commailto:adi...@savitr.com wrote: Hi, I am running CloudStack with XenServer 6.0.2. The setup was working fine till yesterday when I started getting this when trying to restart stopped instances. (The host is not overutilized and there is

RE: The last host of this VM is in avoid set

2013-06-03 Thread Aditya
Hi Shanker, We're running Cloudstack 4.0.1. Aditya From: Shanker Balan [mailto:shanker.ba...@shapeblue.com] Sent: Monday, June 03, 2013 6:28 PM To: users@cloudstack.apache.org Subject: Re: The last host of this VM is in avoid set On 03-Jun-2013, at 6:15 PM, Aditya

RE: The last host of this VM is in avoid set

2013-06-03 Thread Aditya
Hi, The host is up and there have been no changes to the host. Xsconsole on the host shows that the ip address is allocated as it should be. I am able to ping it and login. I'm not sure what else to check. Is there anyway to have cloudstack give me more information of what exactly is wrong?

Re: The last host of this VM is in avoid set

2013-06-03 Thread Shanker Balan
On 03-Jun-2013, at 7:37 PM, Aditya adi...@savitr.commailto:adi...@savitr.com wrote: Hi, The host is up and there have been no changes to the host. Xsconsole on the host shows that the ip address is allocated as it should be. I am able to ping it and login. I'm not sure what else to check. Is

Re: The last host of this VM is in avoid set

2013-06-03 Thread Kirk Kosinski
Is the host in Alert state in CloudStack? If so, here are some things to check: 1. CS mgmt server needs access to 22/tcp, 80/tcp, and 443/tcp of all XS hosts. 2. CS mgmt server must be able to ssh to all XS hosts using root user and password. 3. Did you recently install any patches on the XS