search for: msg01280

...elt cleaner. > > Also keep in mind that the hook scripts aren't an officially supported > part of the API, and are thus liable to change without warning. As an > example, danpb has proposed changing the network hook: > > https://www.redhat.com/archives/libvir-list/2019-March/msg01280.html > > Once this goes in, any network hook script that uses the plugged and > unplugged hooks will no longer work; you would instead need to use the > port-created and port-deleted hooks. That's good to know, thank you Laine. In that case perhaps adding this functionality to lib...

On Tue, Apr 9, 2019 at 5:10 PM Michal Privoznik <mprivozn@redhat.com> wrote: > > On 4/9/19 4:38 PM, Ruben Kerkhof wrote: > > Hi all, > > > > I have a hook script, /etc/libvirt/hooks/network, that doesn't seem to > > be called when I attach an interface with type 'ethernet' with this > > xml snippet: > > > > <interface

...n remote boxes. This bug report is for reference only as I already reported the issue upstream. See * http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1698 * http://lists.xensource.com/archives/html/xen-users/2010-12/msg00307.html * http://lists.xensource.com/archives/html/xen-devel/2010-12/msg01280.html There is no solution known, as workaround passing 'dom0_mem=max:4GB' works around the issue, although I'm unsure about potential side effects. -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86...

...that the hook scripts aren't an officially supported > > > part of the API, and are thus liable to change without warning. As an > > > example, danpb has proposed changing the network hook: > > > > > > https://www.redhat.com/archives/libvir-list/2019-March/msg01280.html > > > > > > Once this goes in, any network hook script that uses the plugged and > > > unplugged hooks will no longer work; you would instead need to use the > > > port-created and port-deleted hooks. > > > > That's good to know, thank you La...

...ll > interface events felt cleaner. Also keep in mind that the hook scripts aren't an officially supported part of the API, and are thus liable to change without warning. As an example, danpb has proposed changing the network hook: https://www.redhat.com/archives/libvir-list/2019-March/msg01280.html Once this goes in, any network hook script that uses the plugged and unplugged hooks will no longer work; you would instead need to use the port-created and port-deleted hooks.

...t; Also keep in mind that the hook scripts aren't an officially supported > > part of the API, and are thus liable to change without warning. As an > > example, danpb has proposed changing the network hook: > > > > https://www.redhat.com/archives/libvir-list/2019-March/msg01280.html > > > > Once this goes in, any network hook script that uses the plugged and > > unplugged hooks will no longer work; you would instead need to use the > > port-created and port-deleted hooks. > > That's good to know, thank you Laine. > > In that case pe...