1. 18 1月, 2019 6 次提交
  2. 17 1月, 2019 4 次提交
  3. 16 1月, 2019 4 次提交
  4. 15 1月, 2019 4 次提交
  5. 14 1月, 2019 2 次提交
  6. 12 1月, 2019 1 次提交
  7. 11 1月, 2019 4 次提交
  8. 10 1月, 2019 12 次提交
  9. 09 1月, 2019 3 次提交
    • D
      lxc: allow empty path in URI for historical compatibility · c10a6d50
      Daniel P. Berrangé 提交于
      The use of 'lxc://' was mistakenly broken in:
      
        commit 4c8574c8
        Author: Daniel P. Berrangé <berrange@redhat.com>
        Date:   Wed Mar 28 12:49:29 2018 +0100
      
          driver: ensure NULL URI isn't passed to drivers with whitelisted URIs
      
      Allow it again for historical compatibility.
      Signed-off-by: NDaniel P. Berrangé <berrange@redhat.com>
      c10a6d50
    • M
      qemu: Use ULL instead of uint64_t for RDMA GID event · f8862714
      Michal Privoznik 提交于
      In the previous commit we are using uint64_t for storing subnet
      prefix and interface id that qemu reports in
      RDMA_GID_STATUS_CHANGED event. We also report them in some debug
      messages. This poses a problem because uint64_t can be UL or ULL
      depending on the host architecture and hence we wouldn't know
      which format to use. Switch to ULL which is big enough and
      doesn't suffer from the issue.
      Signed-off-by: NMichal Privoznik <mprivozn@redhat.com>
      f8862714
    • Y
      qemu: Process RDMA GID state change event · ed357cef
      Yuval Shaia 提交于
      This event is emitted on the monitor when a GID table in pvrdma device
      is modified and the change needs to be propagate to the backend RDMA
      device's GID table.
      
      The control over the RDMA device's GID table is done by updating the
      device's Ethernet function addresses.
      Usually the first GID entry is determine by the MAC address, the second
      by the first IPv6 address and the third by the IPv4 address. Other
      entries can be added by adding more IP addresses. The opposite is the
      same, i.e. whenever an address is removed, the corresponding GID entry
      is removed.
      
      The process is done by the network and RDMA stacks. Whenever an address
      is added the ib_core driver is notified and calls the device driver's
      add_gid function which in turn update the device.
      
      To support this in pvrdma device we need to hook into the create_bind
      and destroy_bind HW commands triggered by pvrdma driver in guest.
      Whenever a changed is made to the pvrdma device's GID table a special
      QMP messages is sent to be processed by libvirt to update the address of
      the backend Ethernet device.
      Signed-off-by: NYuval Shaia <yuval.shaia@oracle.com>
      Signed-off-by: NMichal Privoznik <mprivozn@redhat.com>
      ed357cef