1. 10 1月, 2020 1 次提交
  2. 03 1月, 2020 1 次提交
  3. 19 12月, 2019 1 次提交
  4. 10 12月, 2019 4 次提交
  5. 09 12月, 2019 1 次提交
  6. 03 12月, 2019 5 次提交
  7. 22 11月, 2019 1 次提交
  8. 15 11月, 2019 2 次提交
    • P
      replace use of gnulib snprintf by g_snprintf · 43b01ef2
      Pavel Hrdina 提交于
      Glib implementation follows the ISO C99 standard so it's safe to replace
      the gnulib implementation.
      Signed-off-by: NPavel Hrdina <phrdina@redhat.com>
      Reviewed-by: NPeter Krempa <pkrempa@redhat.com>
      43b01ef2
    • 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
  9. 13 11月, 2019 1 次提交
  10. 12 11月, 2019 1 次提交
  11. 25 10月, 2019 2 次提交
  12. 20 10月, 2019 5 次提交
  13. 16 10月, 2019 3 次提交
  14. 15 10月, 2019 3 次提交
  15. 14 10月, 2019 1 次提交
  16. 19 9月, 2019 4 次提交
  17. 03 9月, 2019 1 次提交
  18. 29 8月, 2019 1 次提交
  19. 28 8月, 2019 1 次提交
  20. 06 8月, 2019 1 次提交
    • M
      lib: Format PCI address differently · 9b332820
      Michal Privoznik 提交于
      Currently, the way we format PCI address is using printf-s
      precision, e.g. "%.4x". This works if we don't want to print any
      value outside of bounds (which is usually the case). However,
      turns out, PCI domain can be 0x10000 which doesn't work well with
      our format strings. However, if we change the format string to
      "%04x" then we still pad small values with zeroes but also we are
      able to print values that are larger than four digits. In fact,
      this format string used by kernel to print a PCI address:
      
        "%04x:%02x:%02x.%d"
      
      The other three format strings (for bus, device and function) are
      changed too, so that we use the same format string as kernel.
      Signed-off-by: NMichal Privoznik <mprivozn@redhat.com>
      Reviewed-by: NJán Tomko <jtomko@redhat.com>
      9b332820