1. 05 11月, 2018 1 次提交
    • H
      pci_devices: run "info qtree" after the guest boots up · a057c85f
      Huan Xiong 提交于
      QEMU "info qtree" output depends on information generated by guest
      firmware. One example is the bus number in PCI device address. QEMU
      retrieves it from the PCI configuration space of the bridge which
      creates the bus that a PCI device is attached to. So if test runs
      "info qtree" before firmware finishes initializing pci devices, its
      output can be incorrect.
      
      The current code works around this timing issue by sleeping 5 seconds.
      That is not reliable and doesn't work on my aarch64 system. So I'd
      suggest to change the test to not start until it verifies the guest
      has booted up. This will make the test execution time slightly longer
      but is reliable.
      Signed-off-by: NHuan Xiong <huan.xiong@hxt-semitech.com>
      a057c85f
  2. 08 8月, 2018 1 次提交
  3. 13 4月, 2018 1 次提交
  4. 12 4月, 2018 1 次提交
  5. 10 4月, 2018 1 次提交
  6. 20 1月, 2018 4 次提交
  7. 28 11月, 2017 1 次提交
  8. 21 9月, 2015 1 次提交
    • L
      tp-qemu: Import cleanups · 288ce897
      Lucas Meneghel Rodrigues 提交于
      Clean up imports across the board in tp-qemu. The criteria
      followed was:
      
      1) Remove unnecessary imports
      2) Turn multi imports from a single entry point to one
         import per line. This increases both patch and
         source code readability.
      3) Separate blocks of imports with a line:
         * Python standard library imports
         * Autotest imports
         * virttest imports
         * Internal tp-qemu imports
      4) Remove try/except blocks refering autotest libs and
         stick with the virttest.staging copy
      
      This paves the way for the future removal of autotest
      references, replacing those references with avocado ones.
      Signed-off-by: NLucas Meneghel Rodrigues <lmr@redhat.com>
      288ce897
  9. 19 12月, 2013 1 次提交
    • C
      virt: change test entry point method name · 6124219f
      Cleber Rosa 提交于
      There's no need to have the name of the "run_<name>" method (main
      test entry point) depend on the test name. So, for simplicity sake,
      let's just name the test entry point "run".
      
      I have decided to not fallback gracefully to the previous naming
      convention as I believe this can lead to confusion in the future.
      Signed-off-by: NCleber Rosa <crosa@redhat.com>
      6124219f
  10. 11 12月, 2013 3 次提交
  11. 07 12月, 2013 1 次提交
  12. 26 11月, 2013 3 次提交
  13. 20 11月, 2013 1 次提交
  14. 08 11月, 2013 1 次提交
  15. 06 11月, 2013 3 次提交
    • L
      qemu.tests.pci_devices: Fix the add_devices_all problem and login to VM · a8718f06
      Lukáš Doktor 提交于
      add_devices_all occupied all ports even when the bus was used for another
      buses. This caused problems with occupied ports. This patch increases
      the first_port number of the upper bus with each inserted bus thus the
      bus could be plugged there.
      
      The drawback is that buses which has some buses inside will have those
      buses on the first addresses and the testing devices would not start with
      addr=0x0. On the other hand missing bus would also test that the bus is
      incapable of handling the first slot correctly.
      
      Additionally this patch adds wait_for_login() in order to verify that
      the VM booted correctly.
      Signed-off-by: NLukáš Doktor <ldoktor@redhat.com>
      a8718f06
    • X
      Minor fix to unattended_install.cdrom.floppy_ks for legacy SLES · 75ff3f2e
      Xiaoqing Wei 提交于
      1) change dest_fname to "autoinst.xml", as most cfg used.
      2) change autoyast_param from floppy to 'autoyast=device://fd0/autoinst.xml'
          for old SLES OS compatibility.
      3) add kernel_params for all existing SLES
      Signed-off-by: NXiaoqing Wei <xwei@redhat.com>
      75ff3f2e
    • L
      qemu.tests.pci_devices: Add test of pci devices · c58efed4
      Lukáš Doktor 提交于
      This test boots VM with a define set of PCI devices and compares
      the qtree and internal representation.
      
      In the future this test should also check the operation system view
      of the devices (lspci or the windows equivalent)
      
      The testing setup is done via graphical representation of the setup.
      Note that the number of spaces is irelevant. The location is defined
      by the number of '->' characters. You can verify the setup in the test.
      Signed-off-by: NLukáš Doktor <ldoktor@redhat.com>
      c58efed4