Bug 1263986 - qemu crash while start a guest with invalid vnc socket path
qemu crash while start a guest with invalid vnc socket path
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: qemu-kvm-rhev (Show other bugs)
x86_64 Unspecified
unspecified Severity medium
: rc
: ---
Assigned To: Gerd Hoffmann
Guo, Zhiyi
Depends On: 1261263
  Show dependency treegraph
Reported: 2015-09-17 05:16 EDT by mazhang
Modified: 2016-11-07 15:39 EST (History)
18 users (show)

See Also:
Fixed In Version: qemu-kvm-rhev-2.5.0
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 1261263
Last Closed: 2016-11-07 15:39:08 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Comment 1 mazhang 2015-09-17 05:19:18 EDT
This bug also happened on qemu-kvm-1.5.3-103.el7.

(gdb) r -display vnc=unix:/blabla/bla
Starting program: /usr/libexec/qemu-kvm -display vnc=unix:/blabla/bla
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
[New Thread 0x7fffe8372700 (LWP 16978)]
[New Thread 0x7fffde1ff700 (LWP 16980)]
qemu-kvm: iohandler.c:60: qemu_set_fd_handler2: Assertion `fd >= 0' failed.

Program received signal SIGABRT, Aborted.
0x00007ffff10e35f7 in raise () from /lib64/libc.so.6
Comment 3 Gerd Hoffmann 2015-09-18 07:24:51 EDT
7.2 is blocker+exceptions, this isn't *that* important, defering to 7.3
Comment 4 Gerd Hoffmann 2016-04-15 07:37:29 EDT
Upstream commit 3d00ac1a2ee0294fc3d460e6013a5cdd9c73ea6c is in 2.4.0
So fixed by rebase.
Comment 12 errata-xmlrpc 2016-11-07 15:39:08 EST
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.


Note You need to log in before you can comment on or make changes to this bug.