On Wed, Feb 7, 2018 at 4:16 AM, Marshall Mitchell <
Marshall(a)marshallholdingco.com> wrote:
I’m attempting to get my first install of oVirt going in full swing.
I
have all the hosts installed and an engine running. All is smooth. I’m not
trying to connect to the Spice console with my Remote Viewer and I have no
clue how to figure out what port I should be connecting too. I’ve been all
over the web via google looking for a process to install / configure /
verify spice is operational, but I’ve not been lucky. How do I go about
connecting / finding the port numbers for my VM’s? I did open the firewall
range required. I appreciate the help.
-Marshall
I don't know if I correctly understand your question.
It is the web admin gui or the portal gui that takes care of using the
correct host ip (that is where the VM is running at that moment) and the
correct port on it to connect to the vnc/spice console.
At host side the qemu-kvm process for a particular VM will have this snip
in its command line (in my case it is a VM with console configured as
Spice+VNC):
. . . -vnc 192.168.50.21:0,password -k en-us -spice
tls-port=5901,addr=192.168.50.21,x509-dir=/etc/pki/vdsm/libvirt-spice,tls-channel=default,tls-channel=main,tls-channel=display,tls-channel=inputs,tls-channel=cursor,tls-channel=playback,tls-channel=record,tls-channel=smartcard,tls-channel=usbredir,seamless-migration=on
. . .
Take in consideration that if you live migrate this VM, it will seamlessly
change the host ip in the new qemu-kvm process on destination host and also
the port, if the previous one is already taken.
In recent releases of oVirt your spice client window will remain up and the
same both during and after the live migration of the vm, even if the
material host to which it connects changes.
HIH,
Gianluca