1. 01 4月, 2018 2 次提交
  2. 26 3月, 2018 1 次提交
  3. 24 3月, 2018 5 次提交
  4. 23 3月, 2018 7 次提交
  5. 20 3月, 2018 1 次提交
    • J
      qemu: Don't assign alias to disabled balloon device · 1554eafb
      Jiri Denemark 提交于
      <memballoon model='none'/> is the only way to disable balloon driver
      since libvirt will add one automatically if the memballoon element is
      missing. In other words, there's no balloon device if model is 'none'
      and generating an alias for it makes no sense. The alias will be ignored
      when parsing the XML and it will disappear once libvirtd is restarted.
      Signed-off-by: NJiri Denemark <jdenemar@redhat.com>
      1554eafb
  6. 19 3月, 2018 1 次提交
    • E
      qemu: hostdev: Fix the error on VM start with an mdev when IOMMU is off · e02d102b
      Erik Skultety 提交于
      Commit b4c2ac8d made a false assumption that IOMMU support necessary
      for an mdev device to be assigned to a VM. Unlike direct PCI assignment,
      IOMMU support is not needed for mediated devices, as the physical parent
      device provides the isolation, therefore, simply checking for VFIO
      presence is enough to successfully start a VM.
      
      Luckily, this issue is not serious, since as of yet, libvirt mandates
      mdevs to be pre-created prior to a domain's launch - if it is,
      everything does work smoothly even with IOMMU disabled, because the
      parent device will ensure the iommu groups we try to access exist.
      However, if there are *no* IOMMU groups yet, thus no mdev exists yet, one
      would see the following error:
      
      "unsupported configuration: Mediated host device assignment requires VFIO
      support"
      
      The error msg above is simply wrong and doesn't even reflect the IOMMU
      reality, so after applying this patch one would rather see the following
      error in such case instead:
      
      "device not found: mediated device '<UUID>' not found"
      Signed-off-by: NErik Skultety <eskultet@redhat.com>
      e02d102b
  7. 18 3月, 2018 1 次提交
  8. 16 3月, 2018 4 次提交
  9. 15 3月, 2018 4 次提交
  10. 14 3月, 2018 1 次提交
    • D
      qemu: avoid denial of service reading from QEMU guest agent (CVE-2018-1064) · fbf31e1a
      Daniel P. Berrangé 提交于
      We read from the agent until seeing a \r\n pair to indicate a completed
      reply or event. To avoid memory denial-of-service though, we must have a
      size limit on amount of data we buffer. 10 MB is large enough that it
      ought to cope with normal agent replies, and small enough that we're not
      consuming unreasonable mem.
      
      This is identical to the flaw we had reading from the QEMU monitor
      as CVE-2018-5748, so rather embarrassing that we forgot to fix
      the agent code at the same time.
      Signed-off-by: NDaniel P. Berrangé <berrange@redhat.com>
      fbf31e1a
  11. 13 3月, 2018 7 次提交
  12. 12 3月, 2018 3 次提交
  13. 09 3月, 2018 3 次提交