Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 682227 - qemu-kvm doesn't exit when binding to specified port fails
qemu-kvm doesn't exit when binding to specified port fails
Status: CLOSED ERRATA
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: qemu-kvm (Show other bugs)
6.1
x86_64 Linux
medium Severity low
: rc
: ---
Assigned To: Gerd Hoffmann
Virtualization Bugs
:
: 602153 (view as bug list)
Depends On:
Blocks: 580953 649196
  Show dependency treegraph
 
Reported: 2011-03-04 09:22 EST by David Jaša
Modified: 2013-01-09 18:37 EST (History)
10 users (show)

See Also:
Fixed In Version: qemu-kvm-0.12.1.2-2.182.el6
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2011-12-06 10:44:56 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2011:1531 normal SHIPPED_LIVE Moderate: qemu-kvm security, bug fix, and enhancement update 2011-12-05 20:23:30 EST

  None (edit)
Description David Jaša 2011-03-04 09:22:51 EST
Description of problem:
Qemu-kvm doesn't exit with error when it is told to run spice server on already-occupied port. 

Version-Release number of selected component (if applicable):
qemu-kvm-0.12.1.2-2.148.el6.x86_64
spice-server-0.7.3-2.el6.x86_64

How reproducible:
always

Steps to Reproduce:
1. run one qemu-kvm with parameter -spice port=3000
2. run another qemu-kvm with parameter -spice port=3000
  
Actual results:
second qemu-kvm should exit with error

Expected results:
qemu-kvm continues running and starts VM

Additional info: 
qemu-kvm CLI output:

do_spice_init: starting 0.7.3
reds_init_socket: reds_init_socket: binding socket to :3000 failed

spice_server_add_interface: SPICE_INTERFACE_KEYBOARD
spice_server_add_interface: SPICE_INTERFACE_MOUSE
Using CPU model "cpu64-rhel6"
Using CPU model "cpu64-rhel6"
spice_server_add_interface: SPICE_INTERFACE_QXL
red_worker_main: begin
spice_server_add_interface: SPICE_INTERFACE_RECORD
spice_server_add_interface: SPICE_INTERFACE_PLAYBACK
handle_dev_destroy_surfaces: 
handle_dev_input: start
handle_dev_destroy_surfaces: 
handle_dev_destroy_surfaces: 
handle_dev_input: oom current 18 pipe 0
^C
Comment 4 Gerd Hoffmann 2011-06-06 02:35:11 EDT
devel-acked
Comment 5 juzhang 2011-06-14 08:56:01 EDT
Reproduced with qemu-kvm-0.12.1.2-2.163.el6.x86_64, marked qa_ack+

guest 1
spice port=5930,disable-ticketing -vga qxl

guest 2
spice port=5930,disable-ticketing -vga qxl

Results:
reds_init_socket: reds_init_socket: binding socket to :5930 failed.
Comment 6 Gerd Hoffmann 2011-07-20 09:32:37 EDT
fix committed upstream, backport posted.
Comment 10 Qunfang Zhang 2011-08-26 01:08:54 EDT
Verified on qemu-kvm-0.12.1.2-2.184.el6, passed.

1. Boot guest A on host with -spice port=5930,disable-ticketing -vga qxl -global qxl-vga.vram_size=67108864

do_spice_init: starting 0.8.2
spice_server_add_interface: SPICE_INTERFACE_KEYBOARD
spice_server_add_interface: SPICE_INTERFACE_MOUSE
spice_server_add_interface: SPICE_INTERFACE_QXL
red_worker_main: begin
QEMU 0.12.1 monitor - type 'help' for more information
(qemu) 

2. Boot guest B on the same host still with -spice port=5930,disable-ticketing -vga qxl -global qxl-vga.vram_size=67108864

do_spice_init: starting 0.8.2
reds_init_socket: reds_init_socket: binding socket to :5930 failed
failed to initialize spice server
[root@localhost mnt]# 

So, this issue is fixed.
Comment 12 Alon Levy 2011-09-20 04:56:50 EDT
*** Bug 602153 has been marked as a duplicate of this bug. ***
Comment 13 Xiaoqing Wei 2011-11-16 01:45:29 EST
Hi, 

This bug  exists on 6.1.z too, 
qemu-kvm-0.12.1.2-2.160.el6_1.9.x86_64

any plan to fix it on rhel6.1.z ?

Sincerely,
Xiaoqing Wei.
Comment 14 Gerd Hoffmann 2011-11-16 04:01:09 EST
Minor issue, no plans to fix this in 6.1.z.
Comment 15 errata-xmlrpc 2011-12-06 10:44:56 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.

http://rhn.redhat.com/errata/RHSA-2011-1531.html

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