similar to: libvirt guests graceful shutdown upon hosts powerdown/reboot

should have mentioned, apologies, suspend is the graceful shutdown of the guest I was thinking of. Guest is win2k8, why would it not suspend? On 22/10/14 10:58, lejeczek wrote: > hi everybody > > by an assumption I expected VM guests to be shut down/off > gracefully when the host is being powered down or > rebooted, but this does not seem to be the case so I wonder.. > Am I

Hi All, I''ve been looking through the code and list archives but haven''t found this yet... From dom0, how do you cause a virtual domain to gracefully shutdown? It seems like the machinery is there somewhere, because the hypervisor can do it to dom0... For reference, in UML you do this by putting this in /etc/inittab: ca:12345:ctrlaltdel:/sbin/shutdown -h now ...and then

My Gurus! I'm still playing with asterisk in the lab here. There is a feature that I need in a production asterisk system. I was wondering if it already exists in asterisk. When we want to shutdown a production asterisk system, we would like the shutdown to happen after there are no more calls being processed. In other words, a shutdown command that does the following: - block asterisk

Hello Everyone, I am using GlusterFS 9.4, and whenever we use the systemctl command to stop the Gluster server, it leaves many Gluster processes running. So, I just want to check how to shut down the Gluster server in a graceful manner. Is there any specific sequence or trick I need to follow? Currently, I am using the following command: [root at master2 ~]# systemctl stop glusterd.service

Hi, I've got a task to have a small number of laptops netboot Linux over WiFi. The kernel is loaded off the USB stick of cource, it's off topic for now. The WPA-supplicant daemon is started early by dracut off initrd. It works. Mostly. The problem is that upon shutdown systemd terminates all the processes FIRST and unmounts filesystems NEXT. Guess what? Upon termination,

Hi all, I just bought a Trust 1000VA PW-4105 UPS. I installed the UPS on FreeBSD 6.1, and installed NUT 2.0.3 via the FreeBSD port. I had no problems installing and configuring nut and the UPS to run with the PowerMust driver. My problem however is when I test the powerdown function by issuing the command: 'upsmon -c fsd' The UPS is cutting the power before the shutdown procedure

Hello all, I am running Dovecot v1alpha4 on Fedora 4 from the command line (as opposed to deamon). Is there a recommended way to shut it down gracefully? Or do I just use killall -9 dovecot? I'm not using the included version, so I can't do SERVICE DOVECOT STOP. Thanks, Cliff

Hello * Trying to get above serial UPS to work gives my some troubles. With upstype=21 [CP=RTS] [OL=CTS] [LB=-DCD] [SD=RTS+DTR] and/or upstype=4 [CP=RTS] [OL=CTS] [LB=-DCD] [SD=-RTS] I do get OL OB LB ok, but shutting down the UPS does not work. Direct call w/ command genericups ... -k and from lowbatt/ initscripts doesnt do. The UPS claims to be capable of and the software shipped (RUPS2000)

Just wanted to let anyone know that might have checked out the generator before and couldn''t use it b/c you''re project required graceful degredation. Well its in there now. Thanks everyone and enjoy. Demo: http://ajaxscaffold.height1percent.com Release Notes: http://www.height1percent.com/articles/2006/03/04/ajaxscaffold-2-2-0-released-with-graceful-js-degredation -- Richard

Hi Anant, why would you need to shutdown a brick to expand it ? This is an online operation. Best Regards, Strahil Nikolov

I think the service that shutdowns the bricks on EL systems is something like this - right now I don't have access to my systems to check but you can extract the rpms and see it: https://bugzilla.redhat.com/show_bug.cgi?id=1022542#c4 Best Regards,Strahil Nikolov On Wed, Feb 7, 2024 at 19:51, Ronny Adsetts<ronny.adsetts at amazinginternet.com> wrote: ________ Community Meeting

Hi Strahil, In our setup, the Gluster brick comes from an iSCSI SAN storage and is then used as a brick on the Gluster server. To extend the brick, we stop the Gluster server, extend the logical volume (LV) on the SAN server, resize it on the host, mount the brick with the extended size, and finally start the Gluster server. Please let me know if this process can be optimized, I will be happy to

No. If the script is used to update the GlusterFS packages in the node, then we need to stop the client processes as well (Fuse client is `glusterfs` process. `ps ax | grep glusterfs`). The default behaviour can't be changed, but the script can be enhanced by adding a new option `--skip-clients` so that it can skip stopping the client processes. -- Aravinda Kadalu Technologies

How do I "enable" qemu-ga on a guest to be able to (I think this means have a success-response:true) for: guest-suspend-hybrid; guest-suspend-ram; guest-suspend-disk; and guest-shutdown? At least I think that's my question. http://wiki.stoney-cloud.org/wiki/Qemu_Guest_Agent_Integration shows these same 4 as false, so I'm not sure if they're always supposed to be that way.

Dear all, I am currently implementing an experimental key exchange (KEX) algorithm. Unlike current algorithms like DH, mine needs to be able to fail gracefully, and in case of failure, continue with whatever algorithm would have been negotiated if mine was not selected. My strategy for graceful failure is to remove my KEX algorithm from myproposal[KEX_DEFAULT_KEX] and to initiate a new key

Hi Anant, Do you use the fuse client in the container ?Wouldn't it be more reasonable to mount the fuse and then use bind mount to provide access to the container ? Best Regards,Strahil Nikolov On Fri, Feb 16, 2024 at 15:02, Anant Saraswat<anant.saraswat at techblue.co.uk> wrote: Okay, I understand. Yes, it would be beneficial to include an option for skipping the client

Hello Everyone, We are mounting this external Gluster volume (dc.local:/docker_config) for docker configuration on one of the Gluster servers. When I ran the stop-all-gluster-processes.sh script, I wanted to stop all gluster server-related processes on the server, but not to unmount the external gluster volume mounted on the server. However, running stop-all-gluster-processes.sh unmounted the

Well, you prepare the host for shutdown, right ? So why don't you setup systemd to start the container and shut it down before the bricks ? Best Regards, Strahil Nikolov ? ?????, 16 ???????? 2024 ?. ? 18:48:36 ?. ???????+2, Anant Saraswat <anant.saraswat at techblue.co.uk> ??????: Hi Strahil, Yes, we mount the fuse to the physical host and then use bind mount to

Okay, I understand. Yes, it would be beneficial to include an option for skipping the client processes. This way, we could utilize the 'stop-all-gluster-processes.sh' script with that option to stop the gluster server process while retaining the fuse mounts. ________________________________ From: Aravinda <aravinda at kadalu.tech> Sent: 16 February 2024 12:36 PM To: Anant Saraswat

Hi Strahil, Yes, we mount the fuse to the physical host and then use bind mount to provide access to the container. The same physical host also runs the gluster server. Therefore, when we stop gluster using 'stop-all-gluster-processes.sh' on the physical host, it kills the fuse mount and impacts containers accessing this volume via bind. Thanks, Anant ________________________________