1. 27 7月, 2017 2 次提交
  2. 04 4月, 2017 1 次提交
  3. 28 3月, 2017 1 次提交
  4. 14 6月, 2016 1 次提交
    • J
      xenconfig: support bios=ovmf xl.cfg · 53d98cce
      Jim Fehlig 提交于
      Add support to xenconfig for conversion of xl.cfg(5) bios config
      to/from libvirt domXml <loader> config. SeaBIOS is the default
      for HVM guests using upstream QEMU. ROMBIOS is the default when
      using the old qemu-dm. This patch allows specifying OVMF as an
      alternate firmware.
      
      Example xl.cfg:
        bios = "ovmf"
      
      Example domXML:
        <os>
          ...
          <loader readonly='yes' type='pflash'>/usr/lib/xen/boot/ovmf.bin</loader>
        </os>
      
      Note that currently Xen does not support a separate nvram for
      non-volatile variables.
      Signed-off-by: NJim Fehlig <jfehlig@suse.com>
      53d98cce
  5. 08 6月, 2016 15 次提交
  6. 20 5月, 2016 1 次提交
  7. 14 5月, 2016 1 次提交
    • M
      virtestmock: Print invalid file accesses into a file · 6326865e
      Michal Privoznik 提交于
      All the accesses to files outside our build or source directories
      are now identified and appended into a file for later processing.
      The location of the file that contains all the records can be
      controlled via VIR_TEST_FILE_ACCESS env variable and defaults to
      abs_builddir "/test_file_access.txt".
      
      The script that will process the access file is to be added in
      next commit.
      Signed-off-by: NMichal Privoznik <mprivozn@redhat.com>
      6326865e
  8. 05 5月, 2016 1 次提交
  9. 15 4月, 2016 1 次提交
  10. 25 3月, 2016 1 次提交
  11. 26 2月, 2016 1 次提交
  12. 18 2月, 2016 1 次提交
  13. 10 2月, 2016 1 次提交
  14. 09 1月, 2016 1 次提交
  15. 08 1月, 2016 2 次提交
  16. 06 10月, 2015 1 次提交
    • C
      testutils: Drop virtTestResult · bb5fc5c7
      Cole Robinson 提交于
      virtTestResult is suboptimal for a few reasons:
      
      - It poorly duplicates virtTestRun pass/fail reporting logic
      - It doesn't have virtTestRun's alloc testing support
      - It only reports the test name _after_ the test has run.
      - It doesn't follow the standard virtTestRun pattern that most other
        tests use.
      
      There's no users left, so drop it. If any other async tests like eventtest
      spring up that don't cleanly fit the virtTestRun pattern, I suggest they
      just open code the support for it around virtTestRun
      bb5fc5c7
  17. 24 4月, 2015 2 次提交
  18. 31 1月, 2015 1 次提交
    • P
      test: utils: Add helpers for automatic numbering of test cases · d793aeed
      Peter Krempa 提交于
      Adding or reordering test cases is usually a pain due to static test
      case names that are then passed to virtTestRun(). To ease the numbering
      of test cases, this patch adds two simple helpers that generate the test
      names according to the order they are run. The test name can be
      configured via the reset function.
      
      This will allow us to freely add test cases in middle of test groups
      without the need to re-number the rest of test cases.
      d793aeed
  19. 21 11月, 2014 1 次提交
    • P
      test: xml2xml: Print full filenames if xml2xml test fails · c5942a9f
      Peter Krempa 提交于
      To simplify looking for a problem instrument the XML comparator function
      with possibility to print the filename of the failed/expected XML
      output.
      
      This is necessary as the VIR_TEST_DIFFERENT macro possibly tests two XML
      files for the inactive/active state and the resulting error may not be
      obvious.
      c5942a9f
  20. 25 4月, 2014 1 次提交
  21. 10 3月, 2014 1 次提交
  22. 20 2月, 2014 2 次提交
    • D
      Rename virDomainGetRootFilesystem to virDomainGetFilesystemForTarget · 432a3fee
      Daniel P. Berrange 提交于
      The virDomainGetRootFilesystem method can be generalized to allow
      any filesystem path to be obtained.
      
      While doing this, start a new test case for purpose of testing various
      helper methods in the domain_conf.{c,h} files, such as this one.
      Signed-off-by: NDaniel P. Berrange <berrange@redhat.com>
      432a3fee
    • D
      Introduce new OOM testing support · 590029f6
      Daniel P. Berrange 提交于
      The previous OOM testing support would re-run the entire "main"
      method each iteration, failing a different malloc each time.
      When a test suite has 'n' allocations, the number of repeats
      requires is  (n * (n + 1) ) / 2.  This gets very large, very
      quickly.
      
      This new OOM testing support instead integrates at the
      virtTestRun level, so each individual test case gets repeated,
      instead of the entire test suite. This means the values of
      'n' are orders of magnitude smaller.
      
      The simple usage is
      
         $ VIR_TEST_OOM=1 ./qemuxml2argvtest
         ...
         29) QEMU XML-2-ARGV clock-utc                                         ... OK
             Test OOM for nalloc=36 .................................... OK
         30) QEMU XML-2-ARGV clock-localtime                                   ... OK
             Test OOM for nalloc=36 .................................... OK
         31) QEMU XML-2-ARGV clock-france                                      ... OK
             Test OOM for nalloc=38 ...................................... OK
         ...
      
      the second lines reports how many mallocs have to be failed, and thus
      how many repeats of the test will be run.
      
      If it crashes, then running under valgrind will often show the problem
      
        $ VIR_TEST_OOM=1 ../run valgrind ./qemuxml2argvtest
      
      When debugging problems it is also helpful to select an individual
      test case
      
        $ VIR_TEST_RANGE=30 VIR_TEST_OOM=1 ../run valgrind ./qemuxml2argvtest
      
      When things get really tricky, it is possible to request that just
      specific allocs are failed. eg to fail allocs 5 -> 12, use
      
        $ VIR_TEST_RANGE=30 VIR_TEST_OOM=1:5-12 ../run valgrind ./qemuxml2argvtest
      
      In the worse case, you might want to know the stack trace of the
      alloc which was failed then VIR_TEST_OOM_TRACE can be set. If it
      is set to 1 then it will only print if it thinks a mistake happened.
      This is often not reliable, so setting it to 2 will make it print
      the stack trace for every alloc that is failed.
      
        $ VIR_TEST_OOM_TRACE=2 VIR_TEST_RANGE=30 VIR_TEST_OOM=1:5-5 ../run valgrind ./qemuxml2argvtest
        30) QEMU XML-2-ARGV clock-localtime                                   ... OK
            Test OOM for nalloc=36 !virAllocN
        /home/berrange/src/virt/libvirt/src/util/viralloc.c:180
        virHashCreateFull
        /home/berrange/src/virt/libvirt/src/util/virhash.c:144
        virDomainDefParseXML
        /home/berrange/src/virt/libvirt/src/conf/domain_conf.c:11745
        virDomainDefParseNode
        /home/berrange/src/virt/libvirt/src/conf/domain_conf.c:12646
        virDomainDefParse
        /home/berrange/src/virt/libvirt/src/conf/domain_conf.c:12590
        testCompareXMLToArgvFiles
        /home/berrange/src/virt/libvirt/tests/qemuxml2argvtest.c:106
        virtTestRun
        /home/berrange/src/virt/libvirt/tests/testutils.c:250
        mymain
        /home/berrange/src/virt/libvirt/tests/qemuxml2argvtest.c:418 (discriminator 2)
        virtTestMain
        /home/berrange/src/virt/libvirt/tests/testutils.c:750
        ??
        ??:0
        _start
        ??:?
         FAILED
      Signed-off-by: NDaniel P. Berrange <berrange@redhat.com>
      590029f6