1. 05 6月, 2018 9 次提交
  2. 29 5月, 2018 2 次提交
  3. 28 5月, 2018 1 次提交
  4. 23 5月, 2018 1 次提交
  5. 16 5月, 2018 3 次提交
  6. 15 5月, 2018 1 次提交
  7. 14 5月, 2018 2 次提交
  8. 11 5月, 2018 3 次提交
  9. 07 5月, 2018 1 次提交
  10. 04 5月, 2018 3 次提交
  11. 03 5月, 2018 1 次提交
  12. 23 4月, 2018 2 次提交
  13. 18 4月, 2018 1 次提交
  14. 17 4月, 2018 1 次提交
  15. 10 4月, 2018 1 次提交
  16. 06 4月, 2018 1 次提交
    • J
      util: introduce virSocketAddrParseAny · 412afdb8
      Jim Fehlig 提交于
      When preparing for migration, the libxl driver creates a new TCP listen
      socket for the incoming migration by calling virNetSocketNewListenTCP,
      passing the destination host name. virNetSocketNewListenTCP calls
      virSocketAddrParse to check if the host name is a wildcard address, in
      which case it avoids adding the AI_ADDRCONFIG flag to the hints passed to
      getaddrinfo. If the host name is not an IP address, virSocketAddrParse
      reports an error
      
      error : virSocketAddrParseInternal:121 : Cannot parse socket address
      'myhost.example.com': Name or service not known
      
      But virNetSocketNewListenTCP succeeds regardless and the overall migration
      operation succeeds.
      
      Introduce virSocketAddrParseAny and use it when simply testing if a host
      name/addr is parsable.
      Signed-off-by: NJim Fehlig <jfehlig@suse.com>
      Reviewed-by: NJohn Ferlan <jferlan@redhat.com>
      412afdb8
  17. 05 4月, 2018 1 次提交
  18. 03 4月, 2018 3 次提交
  19. 23 3月, 2018 1 次提交
  20. 15 3月, 2018 2 次提交