1. 05 3月, 2019 1 次提交
    • C
      conf: Add <disk model='virtio-{non-}transitional'/> · 25d05051
      Cole Robinson 提交于
      <disk> devices lack the model= attribute which is used by
      most other device types. bus= mostly acts as one, but it
      serves other purposes too like determing what target=
      prefix to use, and for matching against controller type=
      values.
      
      Extending bus= to handle additional virtio transitional
      devices will complicate apps lives, and it isn't a clean
      mapping anyways. So let's bite the bullet and add a new
      <disk model=X/> attribute, and wire up common handling
      for virtio and virtio-{non-}transitional
      Reviewed-by: NAndrea Bolognani <abologna@redhat.com>
      Signed-off-by: NCole Robinson <crobinso@redhat.com>
      25d05051
  2. 04 3月, 2019 9 次提交
  3. 25 2月, 2019 1 次提交
  4. 24 2月, 2019 1 次提交
  5. 21 2月, 2019 1 次提交
  6. 20 2月, 2019 1 次提交
    • E
      domain: Fix unknown flags diagnosis in virDomainGetXMLDesc · 27c8fd74
      Eric Blake 提交于
      Many drivers had a comment that they did not validate the incoming
      'flags' to virDomainGetXMLDesc() because they were relying on
      virDomainDefFormat() to do it instead. This used to be the case
      (at least since 461e0f1a and friends in 0.9.4 added unknown flag
      checking in general), but regressed in commit 0ecd6851 (1.2.12),
      when all of the drivers were changed to pass 'flags' through the
      new helper virDomainDefFormatConvertXMLFlags(). Since this helper
      silently ignores unknown flags, we need to implement flag checking
      in each driver instead.
      
      Annoyingly, this means that any new flag values added will silently
      be ignored when targeting an older libvirt, rather than our usual
      practice of loudly diagnosing an unsupported flag.  Add comments
      in domain_conf.[ch] to remind us to be extra vigilant about the
      impact when adding flags (a new flag to add data is safe if the
      older server omitting the requested data doesn't break things in
      the newer client; a new flag to suppress data rather than enhancing
      the existing VIR_DOMAIN_XML_SECURE may form a data leak or even a
      security hole).
      
      In the qemu driver, there are multiple callers all funnelling to
      qemuDomainDefFormatBufInternal(); many of them already validated
      flags (and often only a subset of the full set of possible flags),
      but for ease of maintenance, we can also check flags at the common
      helper function.
      Signed-off-by: NEric Blake <eblake@redhat.com>
      Reviewed-by: NJohn Ferlan <jferlan@redhat.com>
      27c8fd74
  7. 19 2月, 2019 1 次提交
  8. 18 2月, 2019 3 次提交
  9. 15 2月, 2019 7 次提交
  10. 13 2月, 2019 2 次提交
  11. 12 2月, 2019 3 次提交
  12. 07 2月, 2019 1 次提交
  13. 04 2月, 2019 3 次提交
  14. 31 1月, 2019 2 次提交
  15. 28 1月, 2019 1 次提交
    • M
      lib: Use more of VIR_STEAL_PTR() · 5772885d
      Michal Privoznik 提交于
      We have this very handy macro called VIR_STEAL_PTR() which steals
      one pointer into the other and sets the other to NULL. The
      following coccinelle patch was used to create this commit:
      
        @ rule1 @
        identifier a, b;
        @@
      
        - b = a;
          ...
        - a = NULL;
        + VIR_STEAL_PTR(b, a);
      
      Some places were clean up afterwards to make syntax-check happy
      (e.g. some curly braces were removed where the body become a one
      liner).
      Signed-off-by: NMichal Privoznik <mprivozn@redhat.com>
      Reviewed-by: NErik Skultety <eskultet@redhat.com>
      5772885d
  16. 25 1月, 2019 3 次提交