[libvirt] wrong warning flags for clang

Appears that configure doesn't properly detect the case when clang is used instead of gcc: CC=clang ./configure runs fine, but produces a long list of warning flags that clang doesn't support: configure: Warning Flags: -W -Waddress -Wall -Warray-bounds -Wattributes -Wbad-function-cast ... tr

Re: [libvirt] [PATCH] portability: fix virNetDevSetMAC and virNetDevExists on BSD

Eric Blake wrote: > On 05/03/2013 07:35 AM, Roman Bogorodskiy wrote: > > - provide virNetDevSetMAC() implementation based on SIOCSIFLLADDR > > ioctl. > > - adjust virNetDevExists() to check for ENXIO error because > > FreeBSD throws it when device doesn't exist > > --- > > configure.ac

Re: [libvirt] BSD gcrypt warnings [was: [PATCH] build: mark conditionally unused variables]

Eric Blake wrote: > On 05/02/2013 09:32 PM, Roman Bogorodskiy wrote: > >>> > >>> Can you actually compile it successfully without '--disable-werror'? > >> > >> Looks like I skipped a few files: > >> > >> $ ./config.status --version | head -n3 > >> libvirt config.status 1.0.5 > >> configured by .

[libvirt] latency between LIFECYCLE event and notification generation

Hi, I want to know following about LIFECYCLE events of libvirt. 1. about the the latency of these events happening and notification generation. e.g. suppose a VM goes down. How much time it takes to realize that the particular VM has gone down(going to say, DEFINED state) and then notification i