1. 29 1月, 2018 6 次提交
  2. 26 1月, 2018 16 次提交
  3. 25 1月, 2018 7 次提交
  4. 24 1月, 2018 9 次提交
  5. 23 1月, 2018 1 次提交
  6. 22 1月, 2018 1 次提交
    • M
      libvirtd: Explicit dependency on systemd-machined · 1b0c42ff
      Michal Koutný 提交于
      The libvirtd daemon uses systemd-machined D-Bus API when manipulating
      domains. The systemd-machined is D-Bus activated on demand.
      
      However, during system shutdown systemd-machined is stopped concurrently
      with libvirtd and virsh users also doing their final cleanup may
      transitively fail due to unavailability of systemd-machined. Example
      error message
      
      > libvirtd[1390]: 2017-12-20 18:55:56.182+0000: 32700: error : virSystemdTerminateMachine:503 : Refusing activation, D-Bus is shutting down.
      
      To circumvent this we need to explicitly specify both ordering and
      requirement dependency (to avoid late D-Bus activation) on
      systemd-machined. See [1] for the dependency debate.
      
      [1] https://lists.freedesktop.org/archives/systemd-devel/2018-January/040095.html
      1b0c42ff