VM Shutdown Timeout - Remove the limitation for max. 300 seconds

Problem/Justification
In the configuration settings of a TrueNAS SCALE VM there is a “Shutdown Timeout” that can only be increased up to 300 seconds. If trying to increase the value further the error “[EINVAL] vm_create.shutdown_timeout: Should be between 5 and 300” is shown.

If a VM takes a while to properly shut-down this limitation becomes a problem. Please remove this “artificial” limitation of the shutdown timeout value and let the user decide how long the TrueNAS system might wait on a shutdown for the VM.
A TrueNAS administrator should be able to judge himself if a longer timeout is okay or not.

With the current limitation no virtual machines which have a longer shutdown time can be used properly with TrueNAS SCALE.

See also https://ixsystems.atlassian.net/browse/NAS-131657.

Impact
With the current limitation no virtual machines which have a longer shutdown time can be used properly with TrueNAS SCALE.

User Story

1 Like

Yes.

This can happen when the Vm itself has to deal with timing out services… and then TrueNAS will power the VM off, thus making a bad situation worse.

PS: @thomas-hn you should vote for your own feature.

1 Like

Is no one paying attention to this? I think this is a serious problem that affects usage!

I created a Windows 10 VM which takes more than 300 seconds to update the system, and every time it gets halfway through the update, my Windows VM is forced to shut down! This causes me to never complete the system update!

I understand why the developers set this option, but you guys don’t realize that some VMs will take over 300 seconds to system update.

This can be considered a wicked problem!

So I would like to allow us to turn off Shutdown Timeout!

Thank you very much!

Pretty much this. There are a lot of weird restrictions in TrueNAS that just don’t make sense, this being one of them.

Whats wrong with shutting down the Windows VM from within, and not initiated by TrueNAS? Your update will complete just fine that way since there would be no watchdog.

What’s wrong with just allowing the admin to set their own preferred timeout, tho?