1. 22 2月, 2018 1 次提交
  2. 16 8月, 2017 1 次提交
  3. 08 8月, 2017 1 次提交
    • J
      introduce virConfReadString · e9f32227
      Ján Tomko 提交于
      Rewrite virConfReadMem to take a null-terminated string.
      All the callers were calling strlen on it anyway.
      e9f32227
  4. 09 2月, 2017 1 次提交
  5. 12 7月, 2016 1 次提交
  6. 08 6月, 2016 1 次提交
  7. 03 5月, 2016 1 次提交
  8. 02 3月, 2016 1 次提交
    • J
      Libvirt: Add missing default value for config option max_queued_clients · b3a4b176
      Jason J. Herne 提交于
      Commit 1199edb1 added config option max_queued_clients and documented the
      default value as 1000 but never actually set that value. This patch sets the
      default value.
      
      This addresses an issue whereby the following error message is reported if too
      many migrations are started simultaneously:
      
      error: End of file while reading data: Ncat: Invalid argument.: Input/output error
      
      The problem is that too many ncat processes are spawned on the destination
      system. They all attempt to connect to the libvirt socket. Because the
      destination libvirtd cannot respond to the connect requests quickly enough we
      overrun the socket's pending connections queue.
      Signed-off-by: NJason J. Herne <jjherne@linux.vnet.ibm.com>
      Reviewed-by: NBoris Fiuczynski <fiuczy@linux.vnet.ibm.com>
      b3a4b176
  9. 10 8月, 2015 1 次提交
    • M
      rpc: Remove keepalive_required option · a8743c39
      Martin Kletzander 提交于
      Since its introduction in 2011 (particularly in commit f4324e32),
      the option doesn't work.  It just effectively disables all incoming
      connections.  That's because the client private data that contain the
      'keepalive_supported' boolean, are initialized to zeroes so the bool is
      false and the only other place where the bool is used is when checking
      whether the client supports keepalive.  Thus, according to the server,
      no client supports keepalive.
      
      Removing this instead of fixing it is better because a) apparently
      nobody ever tried it since 2011 (4 years without one month) and b) we
      cannot know whether the client supports keepalive until we get a ping or
      pong keepalive packet.  And that won't happen until after we dispatched
      the ConnectOpen call.
      
      Another two reasons would be c) the keepalive_required was tracked on
      the server level, but keepalive_supported was in private data of the
      client as well as the check that was made in the remote layer, thus
      making all other instances of virNetServer miss this feature unless they
      all implemented it for themselves and d) we can always add it back in
      case there is a request and a use-case for it.
      Signed-off-by: NMartin Kletzander <mkletzan@redhat.com>
      a8743c39
  10. 16 6月, 2015 1 次提交
  11. 15 12月, 2014 2 次提交
  12. 25 3月, 2014 1 次提交
  13. 21 3月, 2014 1 次提交
  14. 18 3月, 2014 3 次提交
  15. 10 3月, 2014 1 次提交
  16. 05 8月, 2013 1 次提交
    • M
      Introduce max_queued_clients · 1199edb1
      Michal Privoznik 提交于
      This configuration knob lets user to set the length of queue of
      connection requests waiting to be accept()-ed by the daemon. IOW, it
      just controls the @backlog passed to listen:
      
        int listen(int sockfd, int backlog);
      1199edb1
  17. 10 7月, 2013 2 次提交
  18. 29 6月, 2013 1 次提交
    • J
      Resolve valgrind error in remoteConfigGetStringList() · ba6e187f
      John Ferlan 提交于
      Commit id 'ed3bac71' introduced the following:
      
      TEST: libvirtdconftest
            ........................................ 40  OK
      ==25875== 690 (480 direct, 210 indirect) bytes in 30 blocks are definitely lost in loss record 18 of 24
      ==25875==    at 0x4A06B6F: calloc (vg_replace_malloc.c:593)
      ==25875==    by 0x4C737DF: virAllocN (viralloc.c:152)
      ==25875==    by 0x403BC8: remoteConfigGetStringList (libvirtd-config.c:74)
      ==25875==    by 0x4042CF: daemonConfigLoadOptions (libvirtd-config.c:382)
      ==25875==    by 0x4052F5: daemonConfigLoadData (libvirtd-config.c:479)
      ==25875==    by 0x40222C: testCorrupt (libvirtdconftest.c:112)
      ==25875==    by 0x40321F: virtTestRun (testutils.c:158)
      ==25875==    by 0x401FEE: mymain (libvirtdconftest.c:228)
      ==25875==    by 0x40385A: virtTestMain (testutils.c:722)
      ==25875==    by 0x37C1021A04: (below main) (libc-start.c:225)
      ==25875==
      PASS: libvirtdconftest
      ba6e187f
  19. 24 6月, 2013 1 次提交
  20. 07 6月, 2013 1 次提交
  21. 21 5月, 2013 1 次提交
  22. 08 5月, 2013 1 次提交
    • D
      Separate virGetHostname() API contract from driver APIs · ead63031
      Daniel P. Berrange 提交于
      Currently the virGetHostname() API has a bogus virConnectPtr
      parameter. This is because virtualization drivers directly
      reference this API in their virDriverPtr tables, tieing its
      API design to the public virConnectGetHostname API design.
      
      This also causes problems for access control checks since
      these must only be done for invocations from the public
      API, not internal invocation.
      
      Remove the bogus virConnectPtr parameter, and make each
      hypervisor driver provide a dedicated function for the
      driver API impl. This will allow access control checks
      to be easily inserted later.
      Signed-off-by: NDaniel P. Berrange <berrange@redhat.com>
      ead63031
  23. 05 5月, 2013 1 次提交
  24. 02 5月, 2013 1 次提交
    • M
      virutil: Move string related functions to virstring.c · 7c9a2d88
      Michal Privoznik 提交于
      The source code base needs to be adapted as well. Some files
      include virutil.h just for the string related functions (here,
      the include is substituted to match the new file), some include
      virutil.h without any need (here, the include is removed), and
      some require both.
      7c9a2d88
  25. 14 1月, 2013 1 次提交
  26. 11 1月, 2013 1 次提交
  27. 21 12月, 2012 4 次提交
  28. 02 11月, 2012 1 次提交
  29. 21 9月, 2012 1 次提交
  30. 23 7月, 2012 1 次提交
    • O
      Desert the FSF address in copyright · f9ce7dad
      Osier Yang 提交于
      Per the FSF address could be changed from time to time, and GNU
      recommends the following now: (http://www.gnu.org/licenses/gpl-howto.html)
      
        You should have received a copy of the GNU General Public License
        along with Foobar.  If not, see <http://www.gnu.org/licenses/>.
      
      This patch removes the explicit FSF address, and uses above instead
      (of course, with inserting 'Lesser' before 'General').
      
      Except a bunch of files for security driver, all others are changed
      automatically, the copyright for securify files are not complete,
      that's why to do it manually:
      
        src/security/security_selinux.h
        src/security/security_driver.h
        src/security/security_selinux.c
        src/security/security_apparmor.h
        src/security/security_apparmor.c
        src/security/security_driver.c
      f9ce7dad
  31. 20 7月, 2012 1 次提交
  32. 28 5月, 2012 1 次提交
  33. 14 5月, 2012 1 次提交
    • W
      Use XDG Base Directories instead of storing in home directory · 32a9aac2
      William Jon McCann 提交于
      As defined in:
      http://standards.freedesktop.org/basedir-spec/basedir-spec-latest.html
      
      This offers a number of advantages:
       * Allows sharing a home directory between different machines, or
      sessions (eg. using NFS)
       * Cleanly separates cache, runtime (eg. sockets), or app data from
      user settings
       * Supports performing smart or selective migration of settings
      between different OS versions
       * Supports reseting settings without breaking things
       * Makes it possible to clear cache data to make room when the disk
      is filling up
       * Allows us to write a robust and efficient backup solution
       * Allows an admin flexibility to change where data and settings are stored
       * Dramatically reduces the complexity and incoherence of the
      system for administrators
      32a9aac2