1. 24 6月, 2016 5 次提交
  2. 23 6月, 2016 3 次提交
  3. 22 6月, 2016 16 次提交
  4. 21 6月, 2016 6 次提交
    • J
      Mark virsh-optparse as expensive · a1e1679c
      Ján Tomko 提交于
      a1e1679c
    • J
      Drop virrandomtest · 031b477b
      Ján Tomko 提交于
      This test only checks if mocking of virRandomBytes works correctly.
      
      Drop it to avoid infinite recursion by testing the test suite.
      031b477b
    • J
      Remove virsh-synopsis · 79d3fc85
      Ján Tomko 提交于
      This tests checks that the first word after SYNOPSIS
      in virsh help ${command} output is ${command}.
      
      This was only good to check that the command option structures
      are valid, which is now served by 'virsh self-test'.
      79d3fc85
    • J
      Introduce virsh self-test · 920ab8bd
      Ján Tomko 提交于
      A new hidden command for virsh that will iterate over
      all command groups and commands and print help for every single one.
      
      This involves running vshCmddefOptParse so we can get an error if
      one of the command's option structure is invalid.
      920ab8bd
    • J
      tests: mock gnutls_dh_params_generate2 · 743bda06
      Ján Tomko 提交于
      This function generates some big random numbers.
      
      Cache the result and supply it to any subsequent generate2 calls.
      743bda06
    • J
      Remove virsh-all · 9f95593d
      Ján Tomko 提交于
      Since e8ac4a79 this test wastes some CPU cycles by blindly trying to
      run almost every virsh command, blindly throwing away the output
      and the return value and returning success if 'virsh help' successfully
      returned at least one command.
      
      Drop it completely.
      9f95593d
  5. 20 6月, 2016 5 次提交
  6. 18 6月, 2016 2 次提交
    • J
      libxl: add USB to hostdev domcapabilities · 8bab1e7c
      Jim Fehlig 提交于
      Commit 2a58ed0b added support for creating guests with USB
      hostdevs. Commit fc21d106 later added support for hotplut of
      USB hostdevs. Advertise support for USB hostdevs in the
      domcapabilities.
      
      In addition add the appropriate caps for USB support on
      domaincapstest when libvirt is built on a Xen with
      LIBXL_HAVE_PVUSB. Otherwise domaincapstest would fail i.e.
      testing the wrong domain capabilities.
      Signed-off-by: NJim Fehlig <jfehlig@suse.com>
      Signed-off-by: NJoao Martins <joao.m.martins@oracle.com>
      8bab1e7c
    • A
      qemu: Permit PCI-free aarch64 mach-virt guests · 86a68bdb
      Andrea Bolognani 提交于
      There has been some progress lately in enabling virtio-pci on
      aarch64 guests; however, guest OS support is still spotty at best,
      so most guests are going to be using virtio-mmio instead.
      
      Currently, mach-virt guests are closely modeled after q35 guests,
      and that includes always adding a dmi-to-pci-bridge that's just
      impossible to get rid of. While that's acceptable (if suboptimal)
      for q35, where you will always need some kind of PCI device anyway,
      mach-virt guests should be allowed to avoid it.
      86a68bdb
  7. 17 6月, 2016 3 次提交
    • P
      tests: schema: Remove useless perf schema data · 95f4328e
      Peter Krempa 提交于
      We have a test case that excercises the parser and formatter now which
      takes part in schema checking so remove the schema-only test.
      95f4328e
    • J
      cpu_x86: Use signature in CPU detection code · 5a9221b9
      Jiri Denemark 提交于
      Our current detection code uses just the number of CPU features which
      need to be added/removed from the CPU model to fully describe the CPUID
      data. The smallest number wins. But this may sometimes generate wrong
      results as one can see from the fixed test cases. This patch modifies
      the algorithm to prefer the CPU model with matching signature even if
      this model results in a longer list of additional features.
      Signed-off-by: NJiri Denemark <jdenemar@redhat.com>
      5a9221b9
    • J
      cpu: Add Skylake-Client x86 CPU model · 2f3ccdf0
      Jiri Denemark 提交于
      The CPU model was implemented in QEMU by commit f6f949e929.
      
      The change to i7-5600U is wrong since it's a 5th generation CPU, i.e.,
      Broadwell rather than Skylake, but that's just the result of our CPU
      detection code (which is fixed by the following commit).
      Signed-off-by: NJiri Denemark <jdenemar@redhat.com>
      2f3ccdf0