Description of problem:
spice client gets disconnected when display network is used. The reason is described in detail in bug 920719:

(In reply to comment #0)
> Description of problem:
> When spice migration is initiated, rhevm instructs libvirt on migration
> source machine (via vdsm) to migrate the VM to the destination host,
> specifying among others libvirt uri of destination. Source libvirt then
> connects to the destination libvirt that will then tell the source
> connection details. The source libvirt in turn instructs connected client
> (via qemu) connection details such as hostname, port and others.
> 
> This configuration works in stock RHEV setups but it will break in more
> complex ones:
>   * if hostname of destination host does not resolve to the address of
>     display network interface (IOW if display network is configured to
>     be separate from management network)
>   * if upcoming display network address override is used (bug 788977)

Version-Release number of selected component (if applicable):
3.0-3.2

How reproducible:
always

Steps to Reproduce:
1. set up a display network separate from management network, start VM
2. connect with client to the VM
3. migrate VM
  
Actual results:
client gets disconnected

Expected results:
client stays connected

Additional info: