Hello Tzach,
Agree for a graceful shutdown there should be some steps ahead. Im
actually asking the question because the hardware we use has a high
failure rate on RAID controllers. The physical machine reacts with a
reboot, so its not controlable from our side. We dont want to delete the
ins
Hello Remo,
Exactly what I was looking for! If I could give you a rating it would be
the highest :)
Cheers,
Chris
On 2017-11-03 1:27, Remo Mattei wrote:
sorry forgot to paste the file location
/etc/sysconfig/libvirt-guests
On 11/2/17 11:21 AM, Remo Mattei wrote:
If you are using CentOS
>There is this nova option:
>resume_guests_state_on_host_boot=true
>
>But it doesn't delete or shutdown instances but rather turns them on
>automatically once compute host resumes.
>which might also work for you, probably not just mentioning it any way.
Note that you might want to check some thin
sorry forgot to paste the file location
/etc/sysconfig/libvirt-guests
On 11/2/17 11:21 AM, Remo Mattei wrote:
> If you are using CentOS / Red Hat you can modify this file:
>
> libvirt-guests:#ON_SHUTDOWN=suspend
>
>
>
> # action taken on host shutdown
> # - suspend all running guests are sus
If you are using CentOS / Red Hat you can modify this file:
libvirt-guests:#ON_SHUTDOWN=suspend
# action taken on host shutdown
# - suspend all running guests are suspended using virsh managedsave
# - shutdown all running guests are asked to shutdown. Please be
careful with
# th
On 11/02/2017 01:03 AM, Chris wrote:
Hello,
When we shut down a compute node the instances running on it get suspended. This
generates some difficulties with some applications like RabbitMQ dont like to be
suspended. Is there a way to change this behavior so that the running instances
gets kille
unt=30
while $( virsh list | grep $vmName >/dev/null ) && [ $count -gt 0 ]
do
sleep 1
let count=count-1
[ -n "$debug" ] && echo -n "."
done
# report current status
( virsh list | grep $vmName >/dev/nul
Hi,
A better Q would be why do you shutdown a compute node to begin with?
I mean if you need you should do so in an orderly fashion basically
excavate instances
or shut instances down manually, put the compute node in maintenance mode.
On rebooting compute node remove it from maintenance mode, tur
Hello,
When we shut down a compute node the instances running on it get
suspended. This generates some difficulties with some applications like
RabbitMQ dont like to be suspended. Is there a way to change this
behavior so that the running instances gets killed or shutdown instead?
Thanks in
