+++ This bug was initially created as a clone of Bug #769512 +++

Description of problem:
The command line parameter value of ipv4/ipv6 force using the specified IP version. But when use the ipv6 parameter in the CLI, the addresses reported looks broken, it isn't a valid ipv6 address.

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 spice
spice-glib-0.6-2.el6.x86_64
spice-gtk-0.6-2.el6.x86_64
spice-gtk-python-0.6-2.el6.x86_64
spice-client-0.8.2-7.el6.x86_64
spice-vdagent-0.8.1-3.el6.x86_64
spice-server-0.8.2-5.el6.x86_64

How reproducible:
100%

Steps to Reproduce:
1. start a guest and force specific ip protocol by using the ipv4/ipv6 parameter.
eg:
   ...-spice disable-ticketing,port=5991,ipv4 -vga qxl
   ...-spice disable-ticketing,port=5991,ipv6 -vga qxl
2. check whenever spice client and server are using
ipv4 or ipv6.
for the parameter of ipv4:
(qemu) info spice 
Server:
     address: 0.0.0.0:5910
        auth: none
Channel:
     address: 10.66.8.242:34462
     session: 1804289383
     channel: 1:0
...
# netstat -ant
Active Internet connections (servers and established)
Proto Recv-Q Send-Q Local Address               Foreign Address             State      
...
tcp        0      0 10.66.9.109:5910            10.66.8.242:34462           ESTABLISHED 
...

for the parameter of ipv6:
(qemu) info spice 
Server:
     address: 0.0.0.0:5910
        auth: none
Channel:
     address: ::1c00:0:1c00:0%3263259504:55574
     session: 1804289383
     channel: 1:0
...
# netstat -ant
Active Internet connections (servers and established)
Proto Recv-Q Send-Q Local Address               Foreign Address             State      
...    
tcp        0      0 ::ffff:10.66.9.109:5910     ::ffff:10.66.8.242:59698    ESTABLISHED
...
  
Actual results:
For the parameter of ipv4，the addresses reported was correctly.
For the parameter of ipv6，the addresses reported was broken, it certainly isn't a valid ipv6 address.

Expected results:
The addresses reported was correctly, or even should display some message at least when was broken.

Additional info:

--- Additional comment from yhalperi on 2011-12-22 09:58:53 EST ---

The title of this bug is confusing.
You mean that the "info spice", when the client is connected with ipv6 address,
doesn't print the address correctly, right?

--- Additional comment from sluo on 2011-12-23 04:14:26 EST ---

(In reply to comment #1)
> The title of this bug is confusing.
> You mean that the "info spice", when the client is connected with ipv6 address,
> doesn't print the address correctly, right?

Hi Yonit,

   Because it didn't display the address correctly, so i have no idea how to connect the guest by the ipv6 address. It just didn't display the address correctly（ipv6 addr）by using the "info spice" command in the Monitor. 

The IPV6 of the host is enabled, but "info spice" cann't print IPV6 info correctly. The ifconfig of host info as following:
# ifconfig switch
switch    Link encap:Ethernet  HWaddr 78:2B:CB:9A:8C:C9  
          inet addr:10.66.9.109  Bcast:10.66.11.255  Mask:255.255.252.0
          inet6 addr: fe80::7a2b:cbff:fe9a:8cc9/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:184530998 errors:0 dropped:0 overruns:0 frame:0
          TX packets:88482966 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:301251797212 (280.5 GiB)  TX bytes:123991899146 (115.4 GiB)

eg: For the parameter of ipv6
(qemu) info spice 
Server:
     address: 0.0.0.0:5910
        auth: none
Channel:
     address: ::1c00:0:1c00:0%3263259504:55574
     session: 1804289383
     channel: 1:0
...
In the host:
# netstat -ant
Active Internet connections (servers and established)
Proto Recv-Q Send-Q Local Address               Foreign Address            
State      
...    
tcp        0      0 ::ffff:10.66.9.109:5910     ::ffff:10.66.8.242:59698   
ESTABLISHED

--- Additional comment from kraxel on 2012-01-03 06:45:38 EST ---

Created attachment 550400 [details]
rfc partch for spice server

Damn.  Bug is in the spice server library API.  struct sockaddr is simply too small to hold a full ipv6 address.  Guess we need a patch like the attached (for spice server), and qemu adaptions to use the new fields (if present) of course.