1. 20 12月, 2019 2 次提交
  2. 17 12月, 2019 1 次提交
  3. 16 12月, 2019 1 次提交
    • M
      configure: Provide OpenRC scripts for sub-daemons · 49c6fe62
      Michal Privoznik 提交于
      There is plenty of distributions that haven't switched to
      systemd nor they force their users to (Gentoo, Alpine Linux to
      name a few). With the daemon split merged their only option is to
      still use the monolithic daemon which will go away eventually.
      Provide init scripts for these distros too.
      
      For now, I'm not introducing config files which would correspond
      to the init files except for libvirtd and virtproxyd init scripts
      where it might be desirable to tweak the command line of
      corresponding daemons.
      Signed-off-by: NMichal Privoznik <mprivozn@redhat.com>
      Reviewed-by: NDaniel P. Berrangé <berrange@redhat.com>
      49c6fe62
  4. 14 12月, 2019 2 次提交
  5. 11 12月, 2019 1 次提交
  6. 10 12月, 2019 2 次提交
  7. 29 11月, 2019 1 次提交
    • M
      remote_daemon_stream: Hold an extra reference to stream in daemonStreamFilter · 5e9bdccd
      Michal Privoznik 提交于
      In v5.9.0-273-g8ecab214 I've tried to fix a lock ordering
      problem, but introduced a crasher. Problem is that because the
      client lock is unlocked (in order to honour lock ordering) the
      stream we are currently checking in daemonStreamFilter() might be
      freed and thus stream->priv might not even exist when the control
      get to virMutexLock() call.
      
      To resolve this, grab an extra reference to the stream and handle
      its cleanup should the refcounter reach zero after the deref.
      If that's the case and we are the only ones holding a reference
      to the stream, we MUST return a positive value to make
      virNetServerClientDispatchRead() break its loop where it iterates
      over filters. The problem is, if we did not do so, then
      "filter = filter->next" line will read from a memory that was
      just freed (freeing a stream also unregisters its filter).
      Signed-off-by: NMichal Privoznik <mprivozn@redhat.com>
      Reviewed-by: NJán Tomko <jtomko@redhat.com>
      5e9bdccd
  8. 19 11月, 2019 1 次提交
  9. 15 11月, 2019 1 次提交
    • J
      Add API to change qemu agent response timeout · 95f5ac9a
      Jonathon Jongsma 提交于
      Some layered products such as oVirt have requested a way to avoid being
      blocked by guest agent commands when querying a loaded vm. For example,
      many guest agent commands are polled periodically to monitor changes,
      and rather than blocking the calling process, they'd prefer to simply
      time out when an agent query is taking too long.
      
      This patch adds a way for the user to specify a custom agent timeout
      that is applied to all agent commands.
      
      One special case to note here is the 'guest-sync' command. 'guest-sync'
      is issued internally prior to calling any other command. (For example,
      when libvirt wants to call 'guest-get-fsinfo', we first call
      'guest-sync' and then call 'guest-get-fsinfo').
      
      Previously, the 'guest-sync' command used a 5-second timeout
      (VIR_DOMAIN_QEMU_AGENT_COMMAND_DEFAULT), whereas the actual command that
      followed always blocked indefinitely
      (VIR_DOMAIN_QEMU_AGENT_COMMAND_BLOCK). As part of this patch, if a
      custom timeout is specified that is shorter than
      5 seconds,  this new timeout is also used for 'guest-sync'. If there is
      no custom timeout or if the custom timeout is longer than 5 seconds, we
      will continue to use the 5-second timeout.
      Signed-off-by: NJonathon Jongsma <jjongsma@redhat.com>
      Signed-off-by: NMichal Privoznik <mprivozn@redhat.com>
      Reviewed-by: NMichal Privoznik <mprivozn@redhat.com>
      95f5ac9a
  10. 14 11月, 2019 1 次提交
  11. 13 11月, 2019 1 次提交
  12. 12 11月, 2019 2 次提交
  13. 11 11月, 2019 1 次提交
  14. 09 11月, 2019 5 次提交
  15. 25 10月, 2019 4 次提交
  16. 24 10月, 2019 1 次提交
    • M
      Drop needless ret variable · 3b4df5d3
      Michal Privoznik 提交于
      In few places we have the following code pattern:
      
        int ret;
        ... /* @ret is not accessed here */
        ret = f(...);
        return ret;
      
      This pattern can be written less verbose:
      
        ...
        return f(...);
      
      This patch was generated with following coccinelle spatch:
      
        @@
        type T;
        constant C;
        expression f;
        identifier ret;
        @@
        -T ret = C;
         ... when != ret
        -ret = f;
        -return ret;
        +return f;
      
      Afterwards I needed to fix a few places, e.g. comment in
      virDomainNetIPParseXML() was removed too because coccinelle
      thinks it refers to @ret while in fact it doesn't. Also in few
      places it replaced @ret declaration with a few spaces instead of
      removing the line. But nothing terribly wrong.
      Signed-off-by: NMichal Privoznik <mprivozn@redhat.com>
      Reviewed-by: NDaniel Henrique Barboza <danielhb413@gmail.com>
      3b4df5d3
  17. 23 10月, 2019 1 次提交
  18. 21 10月, 2019 2 次提交
  19. 18 10月, 2019 2 次提交
    • D
      util: drop support for stack traces with logging · 9b80e0c1
      Daniel P. Berrangé 提交于
      The log filters have supported the use of a "+" before the source match
      string to request that a stack trace be emitted for every log message:
      
        commit 54856395
        Author: Daniel P. Berrange <berrange@redhat.com>
        Date:   Wed May 9 15:18:56 2012 +0100
      
          Allow stack traces to be included with log messages
      
          Sometimes it is useful to see the callpath for log messages.
          This change enhances the log filter syntax so that stack traces
          can be show by setting '1:+NAME' instead of '1:NAME'.
      
      With the huge & ever increasing number of logging statements per file,
      this will be incredibly verbose and have a major performance penalty.
      This makes the feature impractical to use widely and as such it is not
      worth the code maint cost.
      
      Removing this seldom used feature allows us to drop the 'execinfo'
      module in gnulib which provides the backtrace() function which doesn't
      exist on non-Linux.
      
      Users who want to get stack traces of parts of libvirt can use GDB,
      or systemtap for live tracing with minimal perf impact.
      Reviewed-by: NJán Tomko <jtomko@redhat.com>
      Signed-off-by: NDaniel P. Berrangé <berrange@redhat.com>
      9b80e0c1
    • D
      build: fix use of $(AUG_GENTEST) as a dependency · b36b20a1
      Daniel P. Berrangé 提交于
      The use of $(AUG_GENTEST) as a dependency in the makefiles is
      a problem because this was assumed to be the filename of the
      script, but is in fact a full shell command line.
      
      Split it into two variables, so it can be correctly used for
      dependencies.
      Reviewed-by: NJán Tomko <jtomko@redhat.com>
      Signed-off-by: NDaniel P. Berrangé <berrange@redhat.com>
      b36b20a1
  20. 17 10月, 2019 1 次提交
  21. 16 10月, 2019 3 次提交
  22. 15 10月, 2019 4 次提交