1. 21 8月, 2018 1 次提交
  2. 20 8月, 2018 1 次提交
    • E
      tests: sev: Test launch-security with specific QEMU version · 6c50cef8
      Erik Skultety 提交于
      In order to test SEV we need real QEMU capabilities. Ideally, this would
      be tested with -latest capabilities, however, our capabilities are
      currently tied to Intel HW, even the 2.12.0 containing SEV were edited by
      hand, so we can only use that one for now, as splitting the capabilities
      according to the vendor is a refactor for another day. The need for real
      capabilities comes from the extended SEV platform data (PDH, cbitpos,
      etc.) we'll need to cache/parse.
      Signed-off-by: NErik Skultety <eskultet@redhat.com>
      Acked-by: NPeter Krempa <pkrempa@redhat.com>
      6c50cef8
  3. 15 8月, 2018 1 次提交
    • M
      qemuxml2argvtest: Set more fake drivers · 5c9277b6
      Michal Privoznik 提交于
      So far we are setting only fake secret and storage drivers.
      Therefore if the code wants to call a public NWFilter API (like
      qemuBuildInterfaceCommandLine() and qemuBuildNetCommandLine() are
      doing) the virGetConnectNWFilter() function will try to actually
      spawn session daemon because there's no connection object set to
      handle NWFilter driver.
      
      Even though I haven't experienced the same problem with the rest
      of the drivers (interface, network and node dev), the reasoning
      above can be applied to them as well.
      Signed-off-by: NMichal Privoznik <mprivozn@redhat.com>
      Reviewed-by: NJohn Ferlan <jferlan@redhat.com>
      5c9277b6
  4. 13 8月, 2018 1 次提交
  5. 10 8月, 2018 18 次提交
  6. 09 8月, 2018 3 次提交
  7. 08 8月, 2018 1 次提交
  8. 07 8月, 2018 2 次提交
  9. 26 7月, 2018 2 次提交
  10. 23 7月, 2018 10 次提交