1. 26 6月, 2020 1 次提交
  2. 19 6月, 2020 7 次提交
  3. 22 4月, 2020 3 次提交
  4. 20 4月, 2020 1 次提交
    • M
      node_device_udev: handle move events · abbd3a31
      Mark Asselstine 提交于
      It is possible and common to rename some devices, this is especially
      true for ethernet devices such as veth pairs.
      
      In the udevEventHandleThread() we will be notified of this change but
      currently we only process "add", "change" and "remove"
      events. Renaming a device such as above results in a "move" event, not
      a "remove" followed by and "add" or vise versa. This change will add
      the new/destination device to our records but unfortunately there is
      no usable mechanism to identify the old/source device to remove it
      from the records. So this is admittedly only a partial fix.
      Signed-off-by: NMark Asselstine <mark.asselstine@windriver.com>
      Reviewed-by: NMartin Kletzander <mkletzan@redhat.com>
      Reviewed-by: NMichal Privoznik <mprivozn@redhat.com>
      abbd3a31
  5. 03 4月, 2020 2 次提交
  6. 17 3月, 2020 1 次提交
    • D
      nodedev: fix race in API usage vs initial device enumeration · 008abeb0
      Daniel P. Berrangé 提交于
      During startup the udev node device driver impl uses a background thread
      to populate the list of devices to avoid blocking the daemon startup
      entirely. There is no synchronization to the public APIs, so it is
      possible for an application to start calling APIs before the device
      initialization is complete.
      
      This was not a problem in the old approach where libvirtd was started
      on boot, as initialization would easily complete before any APIs were
      called.
      
      With the use of socket activation, however, APIs are invoked from the
      very moment the daemon starts. This is easily seen by doing a
      
        'virsh -c nodedev:///system list'
      
      the first time it runs it will only show one or two devices. The second
      time it runs it will show all devices. The solution is to introduce a
      flag and condition variable for APIs to synchronize against before
      returning any data.
      Reviewed-by: NMichal Privoznik <mprivozn@redhat.com>
      Signed-off-by: NDaniel P. Berrangé <berrange@redhat.com>
      008abeb0
  7. 05 3月, 2020 1 次提交
  8. 25 2月, 2020 2 次提交
  9. 07 2月, 2020 1 次提交
  10. 27 1月, 2020 1 次提交
    • D
      libvirt: pass a directory path into drivers for embedded usage · 207709a0
      Daniel P. Berrangé 提交于
      The intent here is to allow the virt drivers to be run directly embedded
      in an arbitrary process without interfering with libvirtd. To achieve
      this they need to store all their configuration & state in a separate
      directory tree from the main system or session libvirtd instances.
      
      This can be useful for doing testing of the virt drivers in "make check"
      without interfering with the user's own libvirtd instances.
      
      It can also be used for applications using KVM/QEMU as a piece of
      infrastructure to build an service, rather than for general purpose
      OS hosting. A long standing example is libguestfs, which would prefer
      if its temporary VMs did show up in the main libvirtd VM list, because
      this confuses apps such as OpenStack Nova. A more recent example would
      be Kata which is using KVM as a technology to build containers.
      Reviewed-by: NMichal Privoznik <mprivozn@redhat.com>
      Reviewed-by: NCole Robinson <crobinso@redhat.com>
      Signed-off-by: NDaniel P. Berrangé <berrange@redhat.com>
      207709a0
  11. 23 1月, 2020 1 次提交
  12. 07 1月, 2020 1 次提交
  13. 03 1月, 2020 1 次提交
  14. 20 12月, 2019 1 次提交
  15. 16 12月, 2019 1 次提交
    • M
      configure: Provide OpenRC scripts for sub-daemons · 49c6fe62
      Michal Privoznik 提交于
      There is plenty of distributions that haven't switched to
      systemd nor they force their users to (Gentoo, Alpine Linux to
      name a few). With the daemon split merged their only option is to
      still use the monolithic daemon which will go away eventually.
      Provide init scripts for these distros too.
      
      For now, I'm not introducing config files which would correspond
      to the init files except for libvirtd and virtproxyd init scripts
      where it might be desirable to tweak the command line of
      corresponding daemons.
      Signed-off-by: NMichal Privoznik <mprivozn@redhat.com>
      Reviewed-by: NDaniel P. Berrangé <berrange@redhat.com>
      49c6fe62
  16. 10 12月, 2019 1 次提交
  17. 13 11月, 2019 1 次提交
  18. 12 11月, 2019 3 次提交
  19. 09 11月, 2019 2 次提交
  20. 25 10月, 2019 1 次提交
  21. 21 10月, 2019 3 次提交
  22. 18 10月, 2019 1 次提交
  23. 16 10月, 2019 1 次提交
  24. 15 10月, 2019 2 次提交