similar to: Callback on Shutdown

hi guys I have just two guest after which libvirt looks and when I shutdown those guests: $ virsh shutdown $_dom that domain takes little time to power down, as expected one would say(~20sec) But! I reboot the hosts and I have in my: /etc/sysconfig/libvirt-guests : ON_SHUTDOWN=shutdown PARALLEL_SHUTDOWN=1 SHUTDOWN_TIMEOUT=300 I see libvirtd service shut down takes minutes, a few good

hi guys I have just two guest after which libvirt looks and when I shutdown those guests: $ virsh shutdown $_dom that domain takes little time to power down, as expected one would say(~20sec) But! I reboot the hosts and I have in my: /etc/sysconfig/libvirt-guests : ON_SHUTDOWN=shutdown PARALLEL_SHUTDOWN=1 SHUTDOWN_TIMEOUT=300 I see libvirtd service shut down takes minutes, a few good

Bernd wrote: > > > > What's the LIBVIRTD_KVM_SHUTDOWN value (on my system it's in > > /etc/conf.d/libvirtd)? You want it to be 'shutdown'. > > > > Michal > > > > Hi Michal, > > i have neither this variable nor that file. > But i have /etc/syconfig/libvirt-guests: > > ========================================================

Michal wrote: > -----Original Message----- > From: Michal Privoznik [mailto:mprivozn@redhat.com] > Sent: Wednesday, July 10, 2013 12:45 PM > To: Lentes, Bernd > Cc: libvirt-ML (libvirt-users@redhat.com) > Subject: Re: [libvirt-users] guests not shutting down when > host shuts down > > On 10.07.2013 11:37, Lentes, Bernd wrote: > > Hi, > > > > i have a

On 9/5/20 7:47 AM, Eric Blake wrote: > I noticed while reading the code that we have a documentation hole that > may cause memory leaks for clients that are unaware, in relation to > completion callbacks. > > The situation arises as follows: for all commands with a completion > callback, I checked that the code has clean semantics: either > nbd_aio_FOO() returns -1 and we

just a followup with more information: The approach I have tried is to update /etc/sysconfig/libvirt-guests as follows: # URIs to check for running guests # example: URIS='default xen:/// vbox+tcp://host/system lxc:///' #URIS=default # action taken on host boot # - start all guests which were running on shutdown are started on boot # regardless on their autostart settings #

A deeper problem I think is that it's ill-specified what is supposed to happen when nbdkit receives a termination signal. We don't specify (for example) that plugin callbacks could or could not be killed in the middle. Killing them in the middle of a callback could be bad for some plugins. Going back to the original problem, perhaps we could have fixed it instead by acquiring a lock

I noticed while reading the code that we have a documentation hole that may cause memory leaks for clients that are unaware, in relation to completion callbacks. The situation arises as follows: for all commands with a completion callback, I checked that the code has clean semantics: either nbd_aio_FOO() returns -1 and we never call the callback cleanup, or nbd_aio_FOO() returns a cookie and

Hi, I'm unable to start a lxc domain again after shutting it down. Something doesn't seem to "clean up" the socket file (and probably more), as the error message says "Unable to start Domain: Failed to connect socket to '/var/run/libvirt/lxc/test.sock': Connection refused." I can create a domain with the same config as the one thats shutted down, but with

Previously the .free function of a callback was not called if the .callback field was NULL, because the callback as a whole would be considered to be "null". This change allows you to register callbacks where the .callback field is NULL, but the .free field is != NULL, meaning that the callback is freed after the last time it would have been used. This is mainly convenient for language

On 03/13/2018 01:41 PM, Christian Borntraeger wrote: > Gerd, > > another thing with virtio-gpu. > > I can successfully do suspend/resume (echo disk > /sys/power/state) on my system. As soon as I have a > virtio-gpu the system hangs on reboot/shutdown: > > e.g. > > crash> bt 1 > PID: 1 TASK: 6bef0000 CPU: 4 COMMAND: "systemd" >

On Sun, Jul 16, 2023 at 04:39:18PM +0000, Tage Johansson wrote: > > @@ -194,7 +198,10 @@ calls. The cookie is unique (per libnbd handle) and E<ge> 1. > > > > You may register a function which is called when the command > > completes, see L</Completion callbacks> below. In this case we have > > -specified a null completion callback. > >

On 7/14/2023 4:13 PM, Eric Blake wrote: > On Fri, Jul 14, 2023 at 09:13:42AM +0200, Laszlo Ersek wrote: >> On 7/13/23 21:29, Eric Blake wrote: >>> The documentation has claimed since commit 6f4dcdab that any >>> completion callback will be called exactly once; but this is not >>> consistent with the code: if nbd_aio_* itself returns an error, then >>>

On 8/13/19 5:36 PM, Richard W.M. Jones wrote: > The definition of functions that take a callback is changed so that > the callback and user_data are combined into a single structure, eg: > > int64_t nbd_aio_pread (struct nbd_handle *h, > void *buf, size_t count, uint64_t offset, > - int (*completion_callback) (/*..*/), void *user_data, > +

On Mon, Sep 30, 2013 at 04:42:18PM +0200, Florian Klink wrote: > Hi, > > I'm unable to start a lxc domain again after shutting it down. > > Something doesn't seem to "clean up" the socket file (and probably > more), as the error message says > > "Unable to start Domain: Failed to connect socket to > '/var/run/libvirt/lxc/test.sock':

Some callers of nbd_aio_pread_structured_callback or nbd_aio_block_status_callback share the same opaque pointer to both calls, with the intent to only free the pointer on the completion callback. Although our documentation does not explicitly specify the order in which callbacks are made, allowing the callback(FREE) to occur prior to the read(FREE) puts a burden on the client to not dereference

On Wed, May 17, 2017 at 03:08:23PM +0200, Daniel Kučera wrote: > Hi all, > > I'm using libvirt-go and I following code to listen for lifecycle events: > > func event_listen() { > log.Printf("event_listen %s", conf.Libvirt.LocalUrl) > hv, err := libvirt.NewConnect(conf.Libvirt.LocalUrl) > > lifecycleCallback := func(c *libvirt.Connect, d

On Tue, Aug 13, 2019 at 10:06:06PM -0500, Eric Blake wrote: > On 8/13/19 5:36 PM, Richard W.M. Jones wrote: > > The definition of functions that take a callback is changed so that > > the callback and user_data are combined into a single structure, eg: > > > > int64_t nbd_aio_pread (struct nbd_handle *h, > > void *buf, size_t count, uint64_t offset,

Hi, I was looking around a bit and couldn''t find any callbacks that executed before before_validation The current problem with using before_validation is that it won''t fire if I''m not using validations with #save(:validate => false) - which makes sense. Before_save won''t suffice because I want these callbacks to fire before validation on the occasions that

Hi Sumeeth, I'm not sure I understand what your new mechanism is supposed to add. You can already call functions defined in the host program from generated code. The Kaleidoscope tutorial does this. If the function you want to call is defined in a module that is dynamically loaded and you are using the default memory manager all you need to do is declare a prototype for the function in