Bug 1983684
| Summary: | Wrong socket address in qemu while using 'tight=on' | |||
|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 8 | Reporter: | liunana <nanliu> | |
| Component: | qemu-kvm | Assignee: | Marc-Andre Lureau <marcandre.lureau> | |
| qemu-kvm sub component: | General | QA Contact: | liunana <nanliu> | |
| Status: | CLOSED ERRATA | Docs Contact: | ||
| Severity: | medium | |||
| Priority: | high | CC: | berrange, ddepaula, marcandre.lureau, virt-maint, yfu | |
| Version: | 8.5 | Keywords: | Tracking, Triaged | |
| Target Milestone: | rc | |||
| Target Release: | 8.6 | |||
| Hardware: | x86_64 | |||
| OS: | Linux | |||
| Whiteboard: | ||||
| Fixed In Version: | qemu-kvm-6.1.0-2.module+el8.6.0+12861+13975d62 | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | ||
| Clone Of: | ||||
| : | 1983915 (view as bug list) | Environment: | ||
| Last Closed: | 2022-05-10 13:20:14 UTC | Type: | Epic | |
| Regression: | --- | Mount Type: | --- | |
| Documentation: | --- | CRM: | ||
| Verified Versions: | Category: | --- | ||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | ||
| Cloudforms Team: | --- | Target Upstream Version: | ||
| Embargoed: | ||||
| Bug Depends On: | 1997410 | |||
| Bug Blocks: | ||||
Moving this to 8.6.0, POST, and set DTM=5 since this can be tested with the weekly rebase. Decision is to not backport to AV 8.5.0. Set 'Verified:Tested,SanityOnly' as gating test with qemu-kvm-6.1.0-2.module+el8.6.0+12861+13975d62 pass. Test Env:
kernel-4.18.0-345.1.el8.x86_64
qemu-kvm-6.1.0-2.module+el8.6.0+12861+13975d62.x86_64
Test steps:
Lanuch QEMU with cmdline, can get the right socket path:
# /usr/libexec/qemu-kvm -monitor stdio -chardev socket,id=channel0,path=/tmp/port0,server=on,wait=off,abstract=on
(qemu) VNC server running on ::1:5900
info chardev
channel0: filename=disconnected:unix:/tmp/port0,abstract=on,tight=on,server=on
Move this bug to verified now, thanks.
Best regards
Liu Nana
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Moderate: virt:rhel and virt-devel:rhel security, bug fix, and enhancement update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2022:1759 |
Description of problem: Wrong socket address in qemu while using 'tight=on' Version-Release number of selected component (if applicable): 4.18.0-322.el8.x86_64 qemu-kvm-6.0.0-23.module+el8.5.0+11740+35571f13.x86_64 How reproducible: 100% Steps to Reproduce: 1. Lanuch QEMU with cmdline: # /usr/libexec/qemu-kvm -monitor stdio -chardev socket,id=channel0,path=/tmp/port0,server=on,wait=off,abstract=on 2. Check the chardev info, the socket address changed: (qemu)info chardev serial0: filename=vc compat_monitor0: filename=stdio channel0: filename=disconnected:unix:/tmp/port0U,abstract,tight,server=on 3. Connect the socket using the changed address, will fail. # socat abstract-connect:/tmp/port0U - 2021/07/19 09:38:18 socat[236167] E connect(5, AF=1 "\0/tmp/port0U", 14): Connection refused 4. Connect the socket using the original socket address, will success. # socat abstract-connect:/tmp/port0 - Actual results: socket address gets a wrong name in qemu Expected results: socket address shows right. Additional info: