Date: Mon, 29 Apr 2019 10:13:44 +0200 From: Andrea Venturoli <ml@netfence.it> To: freebsd-virtualization@freebsd.org Subject: Re: [vm-bhyve] shutting down VMs and kern.init_shutdown_timeout Message-ID: <306069c2-1e7c-9f95-107d-adb0724d5e0e@netfence.it> In-Reply-To: <1DE7A90B-E3AB-4F1E-9A3A-981B18751F8E@punkt.de> References: <20190428044118.GA46284@admin.sibptus.ru> <1DE7A90B-E3AB-4F1E-9A3A-981B18751F8E@punkt.de>
index | next in thread | previous in thread | raw e-mail
On 2019-04-29 09:45, Patrick M. Hausen wrote: > What’s keeping you from increasing that timeout for your > particular requirements? IMHO 2 minutes are a reasonable > default for a system that does not run hypervisor VMs - > which is probably the vast majority. > > Anyone with the knowledge to implement a virtualized > environment can simply set that to a more suitable value, > can’t he/she? The problem is: what is a reasonable value? Shutting down Windows can take literally hours if there are pending updates; that's of course unacceptable if you are running other services and need them up again in a reasonable time. Solution, of course, is not shutting down VMs, but suspending them. IIRC that is coming in bhyve in the future. bye av.home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?306069c2-1e7c-9f95-107d-adb0724d5e0e>