Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:
The command line parameter value of "addr=<addr>" set the IP address spice is listening on, and default is any address. But can not boot guest when specify the spice client's ip address, this is not what we want.

Version-Release number of selected component (if applicable):
host info:
# uname -r && rpm -q qemu-kvm
2.6.32-220.el6.x86_64
qemu-kvm-0.12.1.2-2.210.el6.x86_64
# rpm -qa | grep vnc
tigervnc-1.0.90-0.17.20110314svn4359.el6.x86_64
gtk-vnc-0.3.10-3.el6.x86_64
gtk-vnc-python-0.3.10-3.el6.x86_64

How reproducible:
100%

Steps to Reproduce:
1. start a guest with the "addr=<addr>" specify the spice client's IP address.
...-spice disable-ticketing,port=5991,addr=${ip_of_client's} -vga qxl
2. connect to the guest with spciec in the specified client.
  
Actual results:
Can not boot guest when specify the spice client's IP address 

Expected results:
Boot guest successfully and the specified client connect to the guest without any error.

Additional info:

addr doesn't specify the ip address of the client, it specifies ip address the server should bind to.  This way spice-server can bind to specific network interfaces, for example to loopback (addr=127.0.0.1) which disables remote connects.