1. 12 3月, 2019 1 次提交
  2. 05 3月, 2019 6 次提交
  3. 08 2月, 2019 12 次提交
  4. 01 2月, 2019 1 次提交
  5. 25 1月, 2019 1 次提交
  6. 02 1月, 2019 3 次提交
  7. 12 12月, 2018 1 次提交
    • E
      conf: domain: gfx: Iterate over graphics devices when doing validation · dd45c271
      Erik Skultety 提交于
      The QEMU validation code for graphics has been in place for a while, but
      because it is only executed from virDomainDeviceInfoIterateInternal, it
      was never run, since the iterator expects the device to have boot info
      which graphics don't have. The unfortunate side effect of this whole mess
      was that a few capabilities were missing from the test suite (as commit
      d8266ebe demonstrated with graphics-spice-invalid-egl-headless test),
      which in turn meant that a few graphics tests which expected a failure
      happily accepted any failure the test runtime returned which made them
      succeed. The impact of this was that we then allowed to start a domain
      with multiple OpenGL-enabled graphics devices.
      
      This patch enables iteration over graphics devices. Unsurprisingly,
      a few tests started to fail as a result, so fix those too.
      Signed-off-by: NErik Skultety <eskultet@redhat.com>
      Reviewed-by: NJohn Ferlan <jferlan@redhat.com>
      dd45c271
  8. 06 12月, 2018 1 次提交
  9. 03 12月, 2018 1 次提交
  10. 28 11月, 2018 1 次提交
  11. 15 11月, 2018 2 次提交
  12. 21 9月, 2018 1 次提交
  13. 20 9月, 2018 2 次提交
  14. 12 9月, 2018 1 次提交
    • L
      conf: correct false boot order error during domain parse · 7ea73429
      Laine Stump 提交于
      virDomainDefCollectBootOrder() is called for every item on the list
      for each type of device. One of the checks it makes is to gather the
      order attributes from the <boot> element of all devices, and assure
      that no two devices have been given the same order.
      
      Since (internally to libvirt, *not* in the domain XML) an <interface
      type='hostdev'> is on both the list of hostdev devices and the list of
      network devices, it will be counted twice, and the code that checks
      for multiple devices with the same boot order will give a false
      positive.
      
      To remedy this, we make sure to return early for hostdev devices that
      have a parent.type != NONE.
      
      This was introduced in commit 5b75a4, which was first in libvirt-4.4.0.
      
      Resolves: https://bugzilla.redhat.com/1601318Signed-off-by: NLaine Stump <laine@laine.org>
      Reviewed-by: NJán Tomko <jtomko@redhat.com>
      7ea73429
  15. 06 9月, 2018 1 次提交
  16. 05 9月, 2018 1 次提交
  17. 24 8月, 2018 1 次提交
  18. 21 8月, 2018 1 次提交
  19. 13 8月, 2018 1 次提交
  20. 10 8月, 2018 1 次提交
    • P
      conf: Introduce virDomainDefPostParseMemtune · 0a476f15
      Pavel Hrdina 提交于
      Previously we were ignoring "nodeset" attribute for hugepage pages
      if there was no guest NUMA topology configured in the domain XML.
      Commit <fa6bdf6a> partially fixed
      that issue but it introduced a somehow valid regression.
      
      In case that there is no guest NUMA topology configured and the
      "nodeset" attribute is set to "0" it was accepted and was working
      properly even though it was not completely valid XML.
      
      This patch introduces a workaround that it will ignore the nodeset="0"
      only in case that there is no guest NUMA topology in order not to
      hit the validation error.
      
      After this commit the following XML configuration is valid:
      
        <memoryBacking>
          <hugepages>
            <page size='2048' unit='KiB' nodeset='0'/>
          </hugepages>
        </memoryBacking>
      
      but this configuration remains invalid:
      
        <memoryBacking>
          <hugepages>
            <page size='2048' unit='KiB' nodeset='0'/>
            <page size='1048576' unit='KiB'/>
          </hugepages>
        </memoryBacking>
      
      The issue with the second configuration is that it was originally
      working, however changing the order of the <page> elements resolved
      into using different page size for the guest.  The code is written
      in a way that it expect only one page configured and always uses only
      the first page in case that there is no guest NUMA topology configured.
      See qemuBuildMemPathStr() function for details.
      
      Resolves: https://bugzilla.redhat.com/show_bug.cgi?id=1591235Signed-off-by: NPavel Hrdina <phrdina@redhat.com>
      0a476f15