- Posted In
- Red Hat Virtualization
Display network doen't work for me
I have installed RHEV (with FreeIPA).
There are two networks in RHEVM. Display network 172.17.205.200/29 and rhevm network 172.17.192.128/26. Display and rhevm networks are in different VLANs. Both RHEVM and RHEVH hosts has display and rhevm IPs.
There are two desktops which connect to network via Cisco VPN. First (adminitrator) desktop has access to rhevm and display network. RHEVM and spice work fine. Second desktop has not access to rhevm network (Cisco admin prohibits this access). User can access UserPortal but spice doesn't work because spice client tries to connect to rhevm IP. So all spice traffic goes throught rhevm network. Why?
the display network problem should have been fixed by vdsm-4.9-112.2.el6 , changes posted upstream at http://gerrit.ovirt.org/255
As noted earlier, there was a bug in Beta with displayNetwork and is fixed in GA which includes vdsm-4.9-112.
If you are using RHEV3 beta, you need to test this with GA and revert back with your feedback.
I've updated RHEV-M and have installed second host with RHEV-H GA (restarted hosts and jbosass) .
But problem still persists. Spicec connects to rhevm IPs. From user desktop spice doesn't work.
Red Hat Enterprise Virtualization Hypervisor release 6.2 (20120116.0.el6_2)
Need to separate two things here
1. display network setting means the set network will be the one where VMs from the relevant cluster will be listening for spice/vnc connections.
Does this work OK? When you start a VM, check for `ps -ef |grep qemu` and see where the spice/vnc listener is attached
2. when you use a client machine, and try to connect to a VM's console, the client should know on which network to try accessing the console.
So if you look at the connections, do you see the spice client go to the right ports on the right host via the right network?
2) Spice client goes to host in rhevm network (not spice network)
1. looks like it's listening on all the IPs - this is definitely wrong
2. again - not the right behaviour.
Let me try and recreate this internally, I'll keep you posted
I have found some interesting strings in spice log
and after migration
So UserPortal gets IP adress of management network (not FQDN) before migration and FQDN after migration (via spice protocol).
Just for information:
I've got VM info by Rest API
seems like the issue should be resolved in vdsm 112.4
please make sure you're up to date
Yes, display network works now! Thanks.
Waiting for RHEV-H respin.