Victor Sudakov wrote:
>
> I've noticed that it takes too long for Windows 2012 and 2016 servers
> guests to shutdown when I issue "vm stopall," several minutes even.
>
> Does vm-bhyve provide a way to power them off ungracefully if they would
> not stop within a predefined time?
>
> Or is there
> On Apr 22, 2019, at 21:13, Victor Sudakov wrote:
>
> Paul Vixie wrote:
>>
>> Victor Sudakov wrote on 2019-04-22 19:43:
>> ...
And the implementation is pretty brutal:
# 'vm stopall'
# stop all bhyve instances
# note this will also stop instances not started by vm-bhyve
Victor Sudakov wrote on 2019-04-22 21:13:
...
sleep 1
...
i think this is worse than brutal, it's wrong. consider freebsd's own
work flow when trying to comply with the first soft shutdown it got:
https://github.com/freebsd/freebsd/blob/master/sbin/reboot/reboot.c#L220
this has
[ Charset UTF-8 unsupported, converting... ]
> Hi!
>
> > Am 21.04.2019 um 19:01 schrieb Bjoern A. Zeeb
> > :
> > Do we support this? Has anyone worked on this? How do people deal with
> > these problems?
>
> I?m actually surprised this is supported for some configurations - thanks
> for
Victor Sudakov wrote on 2019-04-22 19:43:
...
>> And the implementation is pretty brutal:
>> # 'vm stopall'
>> # stop all bhyve instances
>> # note this will also stop instances not started by vm-bhyve #
>> core::stopall(){
>> local _pids=$(pgrep -f 'bhyve:')
>>
>> echo "Shutting down
Hi!
> Am 21.04.2019 um 19:01 schrieb Bjoern A. Zeeb
> :
> Do we support this? Has anyone worked on this? How do people deal with
> these problems?
I’m actually surprised this is supported for some configurations - thanks
for starting the thread. As for how others deal with this - e.g. VMware
