Ashley, I was just playing with this in my own lab... I'm currently running XenServer 6.2. From what I can tell, CloudStack relies on the underlying hypervisor to do HA. I'm thinking CloudStack uses the restart.retry.interval variable to test whether the host/vm is alive even if the underlying hypervisor has moved the vm. Coming from a background in ESXi and used to the single ping delay, I'm a bit confused on optimal settings in a work environment.
l variable, Sincerely, Eric Tykwinski TrueNet, Inc. P: 610-429-8300 F: 610-429-3222 On Oct 19, 2013, at 4:48 PM, CSG - Ashley Lester <ash...@computer-services.com.au> wrote: > Hello, > > I have a situation where CS has emailed a alert saying host 2 (was the pool > master) is down: > I have found the following : > > Checking finds XenServer Host 2 running but not accessible in the pool, its > console show "No VMs Running on this host" > CouldStack reports Host 2 down but also reports that some VMs are running on > this host > The VMs that CS reports as running on the host2 are still actually running on > host2, I can log into them and they are not present on any other host > > Asking CS to move the VM to another host fails. > > Can anyone help with some advise ? > > I was considering a toolstack reboot on the "failed host"
