1. 07 6月, 2019 1 次提交
    • A
      gitdm: Add gitdm configuration · 18006c69
      Andrea Bolognani 提交于
      This configuration can be used by gitdm to generate reports about
      libvirt development.
      
      The goal I was working with was being able to generate a report
      for every single libvirt release and having zero "email address
      as company" entries; picking different commit ranges might result
      in some contributions not being accounted for.
      
      I had to make some judgement calls when the situation was not
      entirely clear-cut: when in doubt, and not finding any obvious
      signs of the opposite being true, I mostly ended up dumping
      people in the "unaffiliated contributions" bin. If I got it
      wrong, and companies want to get recognition for their sponsored
      contributions to libvirt, they can send patches.
      Signed-off-by: NAndrea Bolognani <abologna@redhat.com>
      Reviewed-by: NJán Tomko <jtomko@redhat.com>
      18006c69
  2. 04 6月, 2019 1 次提交
  3. 03 6月, 2019 4 次提交
  4. 31 5月, 2019 3 次提交
  5. 27 5月, 2019 2 次提交
  6. 23 5月, 2019 1 次提交
  7. 22 5月, 2019 3 次提交
  8. 13 5月, 2019 3 次提交
  9. 09 5月, 2019 1 次提交
  10. 06 5月, 2019 1 次提交
  11. 05 5月, 2019 2 次提交
  12. 30 4月, 2019 1 次提交
  13. 29 4月, 2019 1 次提交
  14. 17 4月, 2019 1 次提交
    • E
      snapshot: Don't expose testsuite-only state in snapshot XML · a007fcab
      Eric Blake 提交于
      None of the existing drivers actually use the 0-valued 'nostate'
      snapshot state; rather, it was a fluke of implementation. In fact,
      some drivers, like qemu, actively reject 'nostate' as invalid during a
      snapshot redefine. Normally, a driver computes the state post-parse
      from the current domain, and thus virDomainSnapshotGetXMLDesc() will
      never expose the state. However, since the testsuite lacks any
      associated domain to copy state from, and lacks post-parse processing
      that normal drivers have, the testsuite output had several spots with
      the state, coupled with a regex filter to ignore the oddity.
      
      It is better to follow the lead of other XML defaults, by not
      outputting anything during format if post-parse defaults have not been
      applied, and rejecting the default value during parsing. The testsuite
      needs a bit of an update, by adding another flag for when to simulate
      a post-parse action of setting a snapshot state, but none of the
      drivers are impacted other than rejecting XML that was previously
      already suspicious in nature.
      
      Similarly, don't expose creation time 0 (for now, only possible if a
      user redefined a snapshot to claim creation at the Epoch, but also
      happens once setting the creation time is deferred to a post-parse
      handler).
      
      This is also a step towards cleaning up snapshot_conf.c to separate
      its existing post-parse work (namely, setting the creationTime and
      default snapshot name) from the pure parsing work, so that we can get
      rid of the testsuite hack of regex filtering of the XML and instead
      have more accurate testing of our parser/formatter code.
      Signed-off-by: NEric Blake <eblake@redhat.com>
      Reviewed-by: NCole Robinson <crobinso@redhat.com>
      a007fcab
  15. 16 4月, 2019 6 次提交
  16. 15 4月, 2019 1 次提交
  17. 11 4月, 2019 3 次提交
  18. 10 4月, 2019 1 次提交
    • M
      domain capabilities: Expose firmware auto selection feature · 5b9819ee
      Michal Privoznik 提交于
      If a management application wants to use firmware auto selection
      feature it can't currently know if the libvirtd it's talking to
      support is or not. Moreover, it doesn't know which values that
      are accepted for the @firmware attribute of <os/> when parsing
      will allow successful start of the domain later, i.e. if the mgmt
      application wants to use 'bios' whether there exists a FW
      descriptor in the system that describes bios.
      
      This commit then adds 'firmware' enum to <os/> element in
      <domainCapabilities/> XML like this:
      
        <enum name='firmware'>
          <value>bios</value>
          <value>efi</value>
        </enum>
      
      We can see both 'bios' and 'efi' listed which means that there
      are descriptors for both found in the system (matched with the
      machine type and architecture reported in the domain capabilities
      earlier and not shown here).
      Signed-off-by: NMichal Privoznik <mprivozn@redhat.com>
      Acked-by: NLaszlo Ersek <lersek@redhat.com>
      5b9819ee
  19. 09 4月, 2019 1 次提交
  20. 05 4月, 2019 3 次提交