1. 17 5月, 2016 3 次提交
    • A
      qemu: Drop QEMU_CAPS_VIRTIO_BLK_SG_IO · 0e8a72a5
      Andrea Bolognani 提交于
      The only QEMU versions that don't have such capability are <0.11,
      which we no longer support anyway
      0e8a72a5
    • A
      qemu: Drop QEMU_CAPS_CPU_HOST · 859743c2
      Andrea Bolognani 提交于
      The only QEMU versions that don't have such capability are <0.11,
      which we no longer support anyway
      859743c2
    • A
      qemu: Drop QEMU_CAPS_PCI_ROMBAR · 8531b85b
      Andrea Bolognani 提交于
      The only QEMU versions that don't have such capability are <0.12,
      which we no longer support anyway.
      
      Additionally, this solves the issue of some QEMU binaries being
      reported as not having such capability just because they lacked
      the {kvm-}pci-assign QMP object.
      8531b85b
  2. 15 4月, 2016 1 次提交
  3. 10 11月, 2015 13 次提交
  4. 10 9月, 2015 3 次提交
  5. 10 8月, 2015 3 次提交
    • L
      qemu: add capabilities bit for device xio3130-downstream · ad1748a1
      Laine Stump 提交于
      The downstream ports of an x3130-upstream switch can each have one of
      these plugged into them (and that is the only place they can be
      connected). Each xio3130-downstream provides a single PCIe port that
      can have PCI or PCIe devices hotplugged into it. Apparently an entire
      set of x3130-upstream + several xio3130-downstreams can be hotplugged
      as a unit, but it's not clear to me yet how that would be done, since
      qemu only allows attaching a single device at a time.
      
      This device will be used to implement the
      "pcie-switch-downstream-port" model of pci controller.
      ad1748a1
    • L
      qemu: add capabilities bit for device x3130-upstream · 4cde7588
      Laine Stump 提交于
      This is the upstream part of a PCIe switch. It connects to a PCIe port
      (but not PCI) on the upstream side, and can have up to 31
      xio3130-downstream controllers (but no other types of devices)
      connected to its downstream side.
      
      This device will be used to implement the "pcie-switch-upstream-port"
      model of pci controller.
      4cde7588
    • L
      qemu: add capabilities bit for device ioh3420 · 408b100a
      Laine Stump 提交于
      This is a PCIE "root port". It connects only to a port of the
      integrated pcie.0 bus of a Q35 machine (can't be hotplugged), and
      provides a single PCIe port that can have PCI or PCIe devices
      hotplugged into it.
      
      This device will be used to implement the "pcie-root-port" model of
      pci controller.
      408b100a
  6. 24 4月, 2015 1 次提交
  7. 05 12月, 2014 1 次提交
    • D
      Report original error when QMP probing fails with new QEMU · 25bf888a
      Daniel P. Berrange 提交于
      If probing capabilities via QMP fails, we now have a check
      that prevents us falling back to -help parsing. Unfortunately
      the error message
      
        "Failed to probe capabilities for /usr/bin/qemu-kvm:
         unsupported configuration: QEMU 2.1.2 is too new for help parsing"
      
      is proving rather unhelpful to the user. We need to be telling
      them why QMP failed (the root cause), rather than they can't
      use -help (the side effect).
      
      To do this we should capture stderr during QMP probing, and
      if -help parsing then sees a new QEMU version, we know that
      QMP should have worked, and so we can show the messages from
      stderr. The message thus becomes
      
        "Failed to probe capabilities for /usr/bin/qemu-kvm:
         internal error: QEMU / QMP failed: Could not access
         KVM kernel module: No such file or directory
         failed to initialize KVM: No such file or directory"
      25bf888a
  8. 14 11月, 2014 1 次提交
  9. 04 10月, 2014 1 次提交
  10. 25 8月, 2014 1 次提交
  11. 08 8月, 2014 1 次提交
  12. 06 5月, 2014 1 次提交
    • L
      qemu: add host-pci-multidomain capability · 17133e37
      Laine Stump 提交于
      Quite a long time ago, (apparently between qemu 0.12 and 0.13) qemu
      quietly began supporting the optional specification of a domain in the
      host-side address of all pci passthrough commands (by simply
      prepending it to the bus:slot.function format, as
      "dddd:bb:ss.f"). Since machines with multiple PCI domains are very
      rare, this never came up in practice, so libvirt was never updated to
      support it.
      
      This patch takes the first step to supporting specification of a non-0
      domain in the host-side address of PCI devices being assigned to a
      domain, by adding a capability bit to indicate support
      "QEMU_CAPS_HOST_PCI_MULTIDOMAIN", and detect it. Since this support
      was added in a version prior to the minimum version required for
      QMP-style capabilities detection, the capability is always enabled for
      any qemu that uses QMP for capabilities detection. For older qemus,
      the only clue that a domain can be specified in the host pci address
      is the presence of the string "[seg:]" in the help string for
      -pcidevice. (Ironically, libvirt will not be modified to support
      specification of domain for -pcidevice, since any qemu new enough for
      us to care about also supports "-device pci-assign" or "-device
      vfio-pci", which are greatly preferred).
      17133e37
  13. 25 3月, 2014 1 次提交
  14. 19 2月, 2014 1 次提交
  15. 08 10月, 2013 1 次提交
  16. 02 9月, 2013 2 次提交
  17. 29 7月, 2013 1 次提交
  18. 11 7月, 2013 1 次提交
  19. 10 7月, 2013 1 次提交
    • M
      Introduce OOM reporting to virAsprintf · dc6f2dad
      Michal Privoznik 提交于
      Actually, I'm turning this function into a macro as filename,
      function name and line number needs to be passed. The new
      function virAsprintfInternal is introduced with the extended set
      of arguments.
      dc6f2dad
  20. 06 6月, 2013 1 次提交
  21. 22 5月, 2013 1 次提交