1. 25 7月, 2019 1 次提交
  2. 19 7月, 2019 1 次提交
    • J
      virsh migrate: Properly check for --parallel-connections · 88ce7bac
      Jiri Denemark 提交于
      Ever since --parallel-connections option for virsh migrate was
      introduced we did not properly check the return value of
      vshCommandOptInt. We would set VIR_MIGRATE_PARAM_PARALLEL_CONNECTIONS
      parameter even if vshCommandOptInt returned 0 (which means
      --parallel-connections was not specified) when another int option which
      was checked earlier was specified with a nonzero value.
      
      Specifically, running virsh migrate with either
      --auto-converge-increment, --auto-converge-initial, --comp-mt-dthreads,
      --comp-mt-threads, or --comp-mt-level would set
      VIR_MIGRATE_PARAM_PARALLEL_CONNECTIONS parameter and if --parallel
      option was not used, libvirt would complain
      
          error: invalid argument: Turn parallel migration on to tune it
      
      even though --parallel-connections option was not used at all.
      
      https://bugzilla.redhat.com/show_bug.cgi?id=1726643Signed-off-by: NJiri Denemark <jdenemar@redhat.com>
      Reviewed-by: NMichal Privoznik <mprivozn@redhat.com>
      88ce7bac
  3. 18 7月, 2019 2 次提交
  4. 15 7月, 2019 5 次提交
  5. 13 7月, 2019 2 次提交
  6. 11 7月, 2019 1 次提交
    • E
      snapshot: Add VIR_DOMAIN_SNAPSHOT_CREATE_VALIDATE flag · 95f8e323
      Eric Blake 提交于
      We've been doing a terrible job of performing XML validation in our
      various API that parse XML with a corresponding schema (we started
      with domains back in commit dd69a14f, v1.2.12, but didn't catch all
      domain-related APIs, didn't document the use of the flag, and didn't
      cover other XML). New APIs (like checkpoints) should do the validation
      unconditionally, but it doesn't hurt to continue retrofitting existing
      APIs to at least allow the option.
      
      While there are many APIs that could be improved, this patch focuses
      on wiring up a new snapshot XML creation flag through all the
      hypervisors that support snapshots, as well as exposing it in 'virsh
      snapshot-create'.  For 'virsh snapshot-create-as', we blindly set the
      flag without a command-line option, since the XML we create from the
      command line should generally always comply (note that validation
      might cause failures where it used to succeed, such as if we tighten
      the RNG to reject a name of '../\n'); but blindly passing the flag
      means we also have to add in fallback code to disable validation if
      the server is too old to understand the flag.
      Signed-off-by: NEric Blake <eblake@redhat.com>
      Acked-by: NPeter Krempa <pkrempa@redhat.com>
      95f8e323
  7. 09 7月, 2019 1 次提交
    • L
      virsh: support block device storage type in virshParseSnapshotDiskspec · 7ca81e6f
      Liu Dayu 提交于
      virsh snapshot-create-as supports 'file' storage type in --diskspec by default.
      But it doesn't support 'block' storage type in the virshParseSnapshotDiskspec().
      So if a snapshot on a block device (e.g. LV) was created, the type of
      current running storage source in dumpxml is inconsistent with the actual
      backend storage source. It will check file-system type mismatch failed
      and return an error message of 'Migration without shared storage is unsafe'
      when VM performs a live migration after this snapshot.
      
      Considering virsh has to be able to work remotely that recognizing a block device
      by prefix /dev/ or by stat() may be not suitable, so adding a "stype" field
      for the --diskspec string which will be either "file" or "block".
      e.g. --diskspec vda,snapshot=external,driver=qcow2,stype=block,file=/dev/xxx.
      Signed-off-by: NLiu Dayu <liu.dayu@zte.com.cn>
      Signed-off-by: NPeter Krempa <pkrempa@redhat.com>
      7ca81e6f
  8. 03 7月, 2019 1 次提交
  9. 01 7月, 2019 1 次提交
  10. 20 6月, 2019 1 次提交
  11. 19 6月, 2019 1 次提交
  12. 17 6月, 2019 1 次提交
  13. 10 6月, 2019 1 次提交
  14. 06 6月, 2019 3 次提交
  15. 20 5月, 2019 1 次提交
    • H
      qemu: Add entry for balloon stats stat-htlb-pgalloc and stat-htlb-pgfail · a699b19f
      Han Han 提交于
      Qemu added reporting of virtio balloon new statistics stat-htlb-pgalloc and
      stat-htlb-pgfail since qemu-3.0 commit b7b12644297. The value of
      stat-htlb-pgalloc represents the number of successful hugetlb page allocations
      while stat-htlb-pgfail represents the number of failed ones. Add this
      statistics reporting to libvirt.
      
      To enable this feature for vm, guest kenel >= 4.17 is required because
      the exporting hugetlb page allocation for virtio balloon is introduced
      since 6c64fe7f.
      Signed-off-by: NHan Han <hhan@redhat.com>
      Signed-off-by: NMichal Privoznik <mprivozn@redhat.com>
      a699b19f
  16. 13 5月, 2019 1 次提交
    • M
      virsh: Don't leak disk targets in cmdDomBlkError · d55be922
      Michal Privoznik 提交于
      The virDomainGetDiskErrors() API copies disk targets into @disks
      array that we allocate. But we forgot to free it:
      
      ==140828== 16 bytes in 4 blocks are definitely lost in loss record 41 of 242
      ==140828==    at 0x4C2F08F: malloc (vg_replace_malloc.c:299)
      ==140828==    by 0x8C406D9: strdup (in /lib64/libc-2.28.so)
      ==140828==    by 0x5377DD3: virStrdup (virstring.c:966)
      ==140828==    by 0x54C112F: testDomainGetDiskErrors (test_driver.c:3068)
      ==140828==    by 0x55C863D: virDomainGetDiskErrors (libvirt-domain.c:10988)
      ==140828==    by 0x15D1FA: cmdDomBlkError (virsh-domain-monitor.c:1215)
      ==140828==    by 0x17F1A8: vshCommandRun (vsh.c:1335)
      ==140828==    by 0x13489E: main (virsh.c:920)
      Signed-off-by: NMichal Privoznik <mprivozn@redhat.com>
      d55be922
  17. 30 4月, 2019 1 次提交
  18. 26 4月, 2019 1 次提交
  19. 16 4月, 2019 1 次提交
  20. 15 4月, 2019 2 次提交
  21. 12 4月, 2019 2 次提交
  22. 11 4月, 2019 1 次提交
  23. 10 4月, 2019 1 次提交
  24. 04 4月, 2019 6 次提交
  25. 03 4月, 2019 1 次提交