1. 15 10月, 2019 1 次提交
  2. 27 9月, 2019 2 次提交
  3. 22 8月, 2019 3 次提交
  4. 21 8月, 2019 6 次提交
  5. 16 8月, 2019 1 次提交
  6. 15 8月, 2019 2 次提交
  7. 12 8月, 2019 2 次提交
  8. 09 8月, 2019 3 次提交
  9. 07 8月, 2019 3 次提交
  10. 06 8月, 2019 8 次提交
  11. 29 7月, 2019 2 次提交
  12. 27 7月, 2019 1 次提交
  13. 26 7月, 2019 2 次提交
  14. 25 7月, 2019 2 次提交
    • E
      test_driver: Fix testDomainSetMemoryFlags' behaviour on config change · a1c04c27
      Erik Skultety 提交于
      When commit 6ac402c4 added the API whenever VIR_DOMAIN_MEM_MAXIMUM
      was passed the code always checked whether the domain was active and
      therefore failed with an error even though only a config change was
      requested. Fix the issue by replacing virDomainObjGetOneDef with
      virDomainObjGetOneDefState which tells us what definition we're
      performing the change on.
      Signed-off-by: NErik Skultety <eskultet@redhat.com>
      Reviewed-by: NJán Tomko <jtomko@redhat.com>
      Acked-by: NPeter Krempa <pkrempa@redhat.com>
      a1c04c27
    • E
      snapshot: Don't leak moment obj list metaroot to callers · ceb10192
      Eric Blake 提交于
      virDomainSnapshotFindByName(list, NULL) should return NULL, rather
      than the internal-use-only metaroot.  Most existing callers pass in a
      non-NULL name; the few external callers that don't are immediately
      calling virDomainMomentSetParent (which indeed needs the metaroot
      rather than NULL if the parent name is NULL); but as the leaky
      abstraction is ugly, it is worth instead making
      virDomainMomentSetParent static and adding a new function for
      resolving the parent link of a brand new moment within its list.  The
      existing external uses of virDomainMomentSetParent always succeed
      (either the new moment has parent_name of NULL to become a new root,
      or has parent_name set to a strdup of the previous current moment);
      hence, our new function does not need a return value (but it still has
      a VIR_WARN in case future uses break our assumptions about failure
      being impossible).
      
      Missed when commit 02c4e24d refactored things to attempt to remove
      direct metaroot manipulations out of the qemu and test drivers into
      internal-only details, and made more obvious when commit dc8d3dc6
      factored it out into a separate file.
      Signed-off-by: NEric Blake <eblake@redhat.com>
      Reviewed-by: NDaniel P. Berrangé <berrange@redhat.com>
      ceb10192
  15. 24 7月, 2019 2 次提交