Hello,
Suppose we have a VM that is stuck for a reason and won't respond to a shutdown command(for example, booted a live cd, guest agent not active, etc) - either issued manually via the UI or triggered when trying to shutdown the host.
If this was a manual shutdown, it can be easily fixed by either deleting the lock file and stopping it, or by directly killing the VM.
BUT, if it's during host shutdown process, it doesn't seem to kill a vm and the host just stays stuck - even with a monitor attached, the video is stopped, no networking, no console, no UI.
So I guess my question is, is there some sort of a hard timeout I haven't reached(5, 10, 30 mins?) on a host shutdown when everything is forcefully killed and the hardware actually stops? Because if shutdown depends on a VM's graceful shutdown, then every VM is a single point of failure where you'd have to physically cycle the host's power.
And if there is such a timeout, can it be configured somehow?
Suppose we have a VM that is stuck for a reason and won't respond to a shutdown command(for example, booted a live cd, guest agent not active, etc) - either issued manually via the UI or triggered when trying to shutdown the host.
If this was a manual shutdown, it can be easily fixed by either deleting the lock file and stopping it, or by directly killing the VM.
BUT, if it's during host shutdown process, it doesn't seem to kill a vm and the host just stays stuck - even with a monitor attached, the video is stopped, no networking, no console, no UI.
So I guess my question is, is there some sort of a hard timeout I haven't reached(5, 10, 30 mins?) on a host shutdown when everything is forcefully killed and the hardware actually stops? Because if shutdown depends on a VM's graceful shutdown, then every VM is a single point of failure where you'd have to physically cycle the host's power.
And if there is such a timeout, can it be configured somehow?