1. 08 6月, 2016 1 次提交
  2. 07 6月, 2016 2 次提交
  3. 03 6月, 2016 1 次提交
    • M
      Fix building with -Og · 3470cd86
      Martin Kletzander 提交于
      When building using -Og, gcc sees that some variables can be used
      uninitialized  It can be debatable whether it is possible with our
      codeflow, but functions should be self-contained and initializations are
      always good.  The return instead of goto is due to actualType being used
      in the cleanup.
      Signed-off-by: NMartin Kletzander <mkletzan@redhat.com>
      3470cd86
  4. 27 5月, 2016 1 次提交
  5. 25 5月, 2016 2 次提交
    • J
      lxc: Fix lxcDomainDestroyFlags endjob processing · cb0159df
      John Ferlan 提交于
      Commit id '15ccb0db' added job functions for the lxc driver; however,
      for shutdown and nonpersistent path, the vm was removed from the domain
      object list and the vm pointer cleared before the endjob.
      
      Adjust the code to perform the endjob first and then perform the
      ObjListRemove as long as the vm wasn't NULL. This follows more closely
      models from qemu and libxl
      
      Found by Coverity (FORWARD_NULL)
      cb0159df
    • L
      lxc: support <interface type='ethernet'> · 002b7704
      Laine Stump 提交于
      This is identical to type='bridge', but without the "connect to a
      bridge" part, so it can be handled by using the same functions (and
      often even the same cases in switch statements), after renaming
      virLXCProcessSetupInterfaceBridged() to virLXCProcessInterfaceTap()
      and enhancing it to skip bridge-related items when brname == NULL.
      
      To be truly useful, we need to support setting the ip address on the
      host side veth as well as guest side veth (already supported for
      type='bridge'), as well as setting the peer address for both.
      
      The <script> element (supported by type='ethernet' in qemu) isn't
      supported in this patch. An error is logged at domain start time if it
      is encountered. This may be changed in a later patch.
      002b7704
  6. 24 5月, 2016 2 次提交
  7. 20 5月, 2016 7 次提交
  8. 09 5月, 2016 1 次提交
    • P
      lxc: Fix wrong error message on disk hotplug · 5e9d56f8
      Peter Krempa 提交于
      Commit 36025c55 tried to improve error reporting for <disk type="lun">
      but reused the code in LXC which doesn't care about the actual disk
      type. The error messages would then contain a bogous hint that the
      config for the 'lun' device is invalid which might not be the case.
      
      Re-do the relevant portion of the commit with the original message.
      5e9d56f8
  9. 19 4月, 2016 1 次提交
  10. 04 3月, 2016 1 次提交
  11. 17 2月, 2016 1 次提交
    • P
      util: cgroup: Allow ignoring EACCES in virCgroup(Allow|Deny)DevicePath · cf113e8d
      Peter Krempa 提交于
      When adding disk images to ACL we may call those functions on NFS
      shares. In that case we might get an EACCES, which isn't really relevant
      since NFS would not hold a block device. This patch adds a flag that
      allows to stop reporting an error on EACCES to avoid spaming logs.
      
      Currently there's no functional change.
      cf113e8d
  12. 08 2月, 2016 1 次提交
  13. 05 2月, 2016 1 次提交
  14. 04 2月, 2016 2 次提交
  15. 26 1月, 2016 1 次提交
  16. 09 12月, 2015 2 次提交
  17. 07 10月, 2015 1 次提交
  18. 24 9月, 2015 2 次提交
  19. 22 9月, 2015 1 次提交
  20. 15 9月, 2015 1 次提交
  21. 28 8月, 2015 1 次提交
  22. 19 8月, 2015 1 次提交
  23. 04 8月, 2015 1 次提交
    • J
      conf: Allow error reporting in virDomainDiskSourceIsBlockType · 36025c55
      John Ferlan 提交于
      Rather than provide a somewhat generic error message when the API
      returns false, allow the caller to supply a "report = true" option
      in order to cause virReportError's to describe which of the 3 paths
      that can cause failure.
      
      Some callers don't care about what caused the failure, they just want
      to have a true/false - for those, calling with report = false should
      be sufficient.
      36025c55
  24. 14 7月, 2015 3 次提交
  25. 24 6月, 2015 1 次提交
    • L
      Improve some errors for openconsole/channel · 898e76f0
      Luyao Huang 提交于
      Functions like virDomainOpenConsole() and virDomainOpenChannel() accept
      NULL as a dev_name parameter.  Try using alias for the error message if
      dev_name is not specified.
      
      Before:
        error: internal error: character device <null> is not using a PTY
      
      After:
        error: internal error: character device serial0 is not using a PTY
      Signed-off-by: NLuyao Huang <lhuang@redhat.com>
      898e76f0
  26. 21 5月, 2015 1 次提交