Bug 1220252
Summary: | qemu-kvm aborts with -chardev udp,... | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
Product: | Red Hat Enterprise Linux 7 | Reporter: | zhenfeng wang <zhwang> | ||||||||
Component: | qemu-kvm-rhev | Assignee: | Amit Shah <amit.shah> | ||||||||
Status: | CLOSED ERRATA | QA Contact: | Min Deng <mdeng> | ||||||||
Severity: | unspecified | Docs Contact: | |||||||||
Priority: | unspecified | ||||||||||
Version: | 7.2 | CC: | chayang, dyuan, fjin, gsun, harald, hhuang, huding, juzhang, mrezanin, mzhan, pkrempa, qzhang, rbalakri, tzheng, virt-maint, xfu | ||||||||
Target Milestone: | rc | ||||||||||
Target Release: | --- | ||||||||||
Hardware: | Unspecified | ||||||||||
OS: | Unspecified | ||||||||||
Whiteboard: | |||||||||||
Fixed In Version: | qemu-2.4 | Doc Type: | Bug Fix | ||||||||
Doc Text: | Story Points: | --- | |||||||||
Clone Of: | Environment: | ||||||||||
Last Closed: | 2016-11-07 20:23:46 UTC | Type: | Bug | ||||||||
Regression: | --- | Mount Type: | --- | ||||||||
Documentation: | --- | CRM: | |||||||||
Verified Versions: | Category: | --- | |||||||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||
Cloudforms Team: | --- | Target Upstream Version: | |||||||||
Embargoed: | |||||||||||
Attachments: |
|
Description
zhenfeng wang
2015-05-11 05:46:19 UTC
Could you please attach the full domain XML and the contents of '/var/log/libvirt/qemu/rhel7.log' The reported error message is only a warning from qemu and it's usually ignored so there must be a different error that hinders qemu from starting. Created attachment 1024837 [details]
The guest's xml
Created attachment 1024838 [details]
qemu log about guest
Created attachment 1024839 [details]
libvirtd's log
I traced the problem to few recent changes in qemu-kvm. The minimal reproducer case for qemu is: $ qemu-system-x86_64 -chardev udp,id=charrng0,host=127.0.0.1,port=1234,localaddr=,localport=1234 qemu-system-x86_64: - ,id=charrng0,host=127.0.0.1,port=1234,localaddr=,localport=1234: Invalid parameter 'localaddr' Aborted (core dumped) Since qemu commit f43e47dbf6de24db20ec9b588bb6cc762093dd69 the error is treated as fatal. Previously the warning was printed but the error was ignored. The main problem is that the QemuOptsList socket_optslist structure does not contain the localaddr and localport fields and thus the parsing of the commandline fails. Since this is an internal programming mistake in qemu I'm reassigning the bug. I've posted a patch to qemu-devel that fixes the issue: http://lists.gnu.org/archive/html/qemu-devel/2015-05/msg02604.html Additionally, I also encounter the same problem on the following packages: qemu-kvm-1.5.3-95.el7.x86_64 libvirt-1.2.17-2.el7.x86_64 virt-manager-1.2.1-2.el7.noarch (In reply to Harald Hoyer from comment #10) > (In reply to Amit Shah from comment #9) > > Fix was included upstream: > > > > b8981dc9aae25fa79e5f35609e63f50f078a572d > > Can we have this fix in Fedora rawhide, please? This is in qemu-2.4 and both fc23 and fc24 builds of qemu will have this commit already in: http://koji.fedoraproject.org/koji/packageinfo?packageID=3685 Bugus fratris on the hat shades of blue https://bugzilla.redhat.com/show_bug.cgi?id=1268708 This bug was accidentally moved from POST to MODIFIED via an error in automation, please see mmccune with any questions QE reproduced the bug on build qemu-kvm-rhev-2.3.0-6.el7.x86_64 How to reproduce the issue on QEMU and test steps was following as below, 1./usr/libexec/qemu-kvm -chardev udp,id=charrng0,host=1.2.3.4,port=1234,localaddr=,localport=1234 Actual results was same to Descriptions qemu-kvm: -chardev udp,id=charrng0,host=1.2.3.4,port=1234,localaddr=,localport=1234: Invalid parameter 'localaddr'... QE verified the bug on build qemu-kvm-rhev-2.6.0-22.el7.x86_64 1.steps boot up guest with the following cli /usr/libexec/qemu-kvm -chardev udp,id=charrng0,host=1.2.3.4,port=1234,localaddr=,localport=1234 Actual results, VNC server running on '::1;5900' Draw a conclusion,the original issue has been fixed on build qemu-kvm-rhev-2.6.0-22.el7.x86_64.Thanks ! 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, 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://rhn.redhat.com/errata/RHBA-2016-2673.html |