diff options
| author | Daniel P. Berrangé <berrange@redhat.com> | 2020-09-18 10:31:45 +0100 |
|---|---|---|
| committer | Daniel P. Berrangé <berrange@redhat.com> | 2020-10-29 09:57:37 +0000 |
| commit | dfc00eb7dea43bfb6d4a2ba38c4f6bc9745f3729 (patch) | |
| tree | e3a211dae650c740c2f46f0c163e892e08b40280 /scripts | |
| parent | 77b7829e755aec2f74601190a4521617b6dab49c (diff) | |
| download | qemu-dfc00eb7dea43bfb6d4a2ba38c4f6bc9745f3729.zip qemu-dfc00eb7dea43bfb6d4a2ba38c4f6bc9745f3729.tar.gz qemu-dfc00eb7dea43bfb6d4a2ba38c4f6bc9745f3729.tar.bz2 | |
util: include the target address in socket connect failures
Reporting "Failed to connect socket" is essentially useless for a user
attempting to diagnose failure. It needs to include the target address
details. Similarly when failing to create a socket we should include the
socket family info, so the user understands what particular feature was
missing in their kernel build (IPv6, VSock in particular).
Reviewed-by: Philippe Mathieu-Daudé <philmd@redhat.com>
Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
Diffstat (limited to 'scripts')
0 files changed, 0 insertions, 0 deletions