[ovirt-users] Re: VM console does not work with new cluster.
Cannot connect even closed firewalld service on hosts. -Original Message- From: users-boun...@ovirt.org On Behalf Of matthew.st...@fujitsu.com Sent: Thursday, January 14, 2021 11:20 PM To: Strahil Nikolov ; tommy ; eev...@digitaldatatechs.com Cc: users@ovirt.org Subject: [ovirt-users] Re: VM console does not work with new cluster. Listed in firewalld service 'vdsm' -Original Message- From: Strahil Nikolov Sent: Wednesday, January 13, 2021 10:52 PM To: tommy ; Stier, Matthew ; eev...@digitaldatatechs.com Cc: users@ovirt.org Subject: Re: [ovirt-users] Re: VM console does not work with new cluster. I don't see the VNC ports at all (5900 and above). Here is my firewall on oVirt 4.3.10: public (active) target: default icmp-block-inversion: no interfaces: enp4s0 enp5s0f0 enp5s0f1 enp7s5f0 enp7s5f1 enp7s6f0 enp7s6f1 ovirtmgmt team0 sources: services: cockpit ctdb dhcpv6-client glusterfs libvirt-tls nfs nfs3 nrpe ovirt-imageio ovirt-storageconsole ovirt-vmconsole rpc-bind samba snmp ssh vdsm ports: 111/tcp 2049/tcp 54321/tcp 5900/tcp 5900-6923/tcp 5666/tcp 16514/tcp 54322/tcp 22/tcp 6081/udp 8080/tcp 963/udp 965/tcp protocols: masquerade: no forward-ports: source-ports: icmp-blocks: rich rules: Best Regards, Strahil Nikolov В 05:25 +0800 на 13.01.2021 (ср), tommy написа: > I encountered the question too. > > The follow file is the connect file for vm that can connect using > remote viewer: > > [virt-viewer] > type=vnc > host=192.168.10.41 > port=5900 > password=rdXQA4zr/UAY > # Password is valid for 120 seconds. > delete-this-file=1 > fullscreen=0 > title=HostedEngine:%d > toggle-fullscreen=shift+f11 > release-cursor=shift+f12 > secure-attention=ctrl+alt+end > versions=rhev-win64:2.0-160;rhev-win32:2.0-160;rhel8:7.0-3;rhel7:2.0- > 6;rhel6:99.0-1 > newer-version-url= > http://www.ovirt.org/documentation/admin-guide/virt/console-client-res > ources > > [ovirt] > host=ooeng.tltd.com:443 > vm-guid=76f99df2-ef79-45d9-8eea-a32b168f9ef3 > sso-token=4Up7TfLLBjSuQgPkQvRz3D- > fUGZWZg4ynApe2Y7ylkARCFwQWsfEr3dU8FjlK8esctm3Im4tz80mE1DjrNT3XQ > admin=1 > ca=-BEGIN CERTIFICATE- > \nMIIDqDCCApCgAwIBAgICEAAwDQYJKoZIhvcNAQELBQAwPzELMAkGA1UEBhMCVVMxETA > PBgNVBAoM\nCHRsdGQuY29tMR0wGwYDVQQDDBRvb2VuZy50bHRkLmNvbS4xNzczMDAeFw > 0yMTAxMTAxNjE1NDda\nFw0zMTAxMDkxNjE1NDdaMD8xCzAJBgNVBAYTAlVTMREwDwYDV > QQKDAh0bHRkLmNvbTEdMBsGA1UE\nAwwUb29lbmcudGx0ZC5jb20uMTc3MzAwggEiMA0G > CSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQCg\nYT9S7hWiXQUzAqFQKbg2nMjwyHDmb/J > mKeJAUVZqNKRg1q80IpWyoM12Zw0nX1eTwMnVY/JtJON4\n13PoEC3So8nniGt+wtHr44 > ysvCWfU0SBk/ZPnKmQ58o5MlSkidHwySChXfVPYLPWeUJ1JUrujna/\nCbi5bmmjx2pqw > LrZXX8Q5NO2MRKOTs0Dtg16Q6z+a3cXLIffVJfhPGS3AkIh6nznNaDeH5gFZZbd\nr3DK > E4xrpdw/7y6CgjmHe4vwGxOIyE+gElZ/lVtqznLMwohz7wgtgsDA36277mujNyMjMbrSF > heu\n5WfbIa9VVSZWEkISVq6eswLOQ1IRaFyJsFN9AgMBAAGjga0wgaowHQYDVR0OBBYE > FDYEqJOMqN8+\nQhCP7DAkqF3RZMFdMGgGA1UdIwRhMF+AFDYEqJOMqN8+QhCP7DAkqF3 > RZMFdoUOkQTA/MQswCQYD\nVQQGEwJVUzERMA8GA1UECgwIdGx0ZC5jb20xHTAbBgNVBA > MMFG9vZW5nLnRsdGQuY29tLjE3NzMw\nggIQADAPBgNVHRMBAf8EBTADAQH/MA4GA1UdD > wEB/wQEAwIBBjANBgkqhkiG9w0BAQsFAAOCAQEA\nAKs0/yQWkoOkGcL0PjF9ijekdMmj > rLZGyh5uLot7h9s/Y2+5l9n9IzEjjx9chi8xwt6MBsR6/nBT\n/skcciv2veM22HwNGjd > rHvhfbZFnZsGe2TU60kGzKjlv1En/8Pgd2aWBcwTlr+SErBXkehNEJRj9\n1saycPgwS4 > pHS04c2+4JMhpe+hxgsO2+N/SYkP95Lf7ZQynVsN/SKx7X3cWybErCqoB7G7McqaHN\nV > Ww+QNXo5islWUXqeDc3RcnW3kq0XUEzEtp6hoeRcLKO99QrAW31zqU/QY+EeZ6Fax1O/j > rDafZn\npTs0KJFNgeVnUhKanB29ONy+tmnUmTAgPMaKKw==\n-END > CERTIFICATE-\n > > the firewall list of the host 192.168.10.41 is: > > [root@ooengh1 ~]# firewall-cmd --list-all public (active) > target: default > icmp-block-inversion: no > interfaces: bond0 ovirtmgmt > sources: > services: cockpit dhcpv6-client libvirt-tls ovirt-imageio ovirt- > vmconsole snmp ssh vdsm > ports: 6900/tcp 22/tcp 6081/udp > protocols: > masquerade: no > forward-ports: > source-ports: > icmp-blocks: > rich rules: > > > > > > > > the follow file is the connect file that vm that cannot connect using > remote viewer: > > [virt-viewer] > type=vnc > host=ohost1.tltd.com > port=5900 > password=4/jWA+RLaSZe > # Password is valid for 120 seconds. > delete-this-file=1 > fullscreen=0 > title=testol:%d > toggle-fullscreen=shift+f11 > release-cursor=shift+f12 > secure-attention=ctrl+alt+end > versions=rhev-win64:2.0-160;rhev-win32:2.0-160;rhel8:7.0-3;rhel7:2.0- > 6;rhel6:99.0-1 > newer-version-url= > http://www.ovirt.org/documentation/admin-guide/virt/console-client-res > ources > > [ovirt] > host=ooeng.tltd.com:443 > vm-guid=2b0eeecf-e561-4f60-b16d-dccddfcc852a > sso-token=
[ovirt-users] Re: VM console does not work with new cluster.
Listed in firewalld service 'vdsm' -Original Message- From: Strahil Nikolov Sent: Wednesday, January 13, 2021 10:52 PM To: tommy ; Stier, Matthew ; eev...@digitaldatatechs.com Cc: users@ovirt.org Subject: Re: [ovirt-users] Re: VM console does not work with new cluster. I don't see the VNC ports at all (5900 and above). Here is my firewall on oVirt 4.3.10: public (active) target: default icmp-block-inversion: no interfaces: enp4s0 enp5s0f0 enp5s0f1 enp7s5f0 enp7s5f1 enp7s6f0 enp7s6f1 ovirtmgmt team0 sources: services: cockpit ctdb dhcpv6-client glusterfs libvirt-tls nfs nfs3 nrpe ovirt-imageio ovirt-storageconsole ovirt-vmconsole rpc-bind samba snmp ssh vdsm ports: 111/tcp 2049/tcp 54321/tcp 5900/tcp 5900-6923/tcp 5666/tcp 16514/tcp 54322/tcp 22/tcp 6081/udp 8080/tcp 963/udp 965/tcp protocols: masquerade: no forward-ports: source-ports: icmp-blocks: rich rules: Best Regards, Strahil Nikolov В 05:25 +0800 на 13.01.2021 (ср), tommy написа: > I encountered the question too. > > The follow file is the connect file for vm that can connect using > remote viewer: > > [virt-viewer] > type=vnc > host=192.168.10.41 > port=5900 > password=rdXQA4zr/UAY > # Password is valid for 120 seconds. > delete-this-file=1 > fullscreen=0 > title=HostedEngine:%d > toggle-fullscreen=shift+f11 > release-cursor=shift+f12 > secure-attention=ctrl+alt+end > versions=rhev-win64:2.0-160;rhev-win32:2.0-160;rhel8:7.0-3;rhel7:2.0- > 6;rhel6:99.0-1 > newer-version-url= > http://www.ovirt.org/documentation/admin-guide/virt/console-client-res > ources > > [ovirt] > host=ooeng.tltd.com:443 > vm-guid=76f99df2-ef79-45d9-8eea-a32b168f9ef3 > sso-token=4Up7TfLLBjSuQgPkQvRz3D- > fUGZWZg4ynApe2Y7ylkARCFwQWsfEr3dU8FjlK8esctm3Im4tz80mE1DjrNT3XQ > admin=1 > ca=-BEGIN CERTIFICATE- > \nMIIDqDCCApCgAwIBAgICEAAwDQYJKoZIhvcNAQELBQAwPzELMAkGA1UEBhMCVVMxETA > PBgNVBAoM\nCHRsdGQuY29tMR0wGwYDVQQDDBRvb2VuZy50bHRkLmNvbS4xNzczMDAeFw > 0yMTAxMTAxNjE1NDda\nFw0zMTAxMDkxNjE1NDdaMD8xCzAJBgNVBAYTAlVTMREwDwYDV > QQKDAh0bHRkLmNvbTEdMBsGA1UE\nAwwUb29lbmcudGx0ZC5jb20uMTc3MzAwggEiMA0G > CSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQCg\nYT9S7hWiXQUzAqFQKbg2nMjwyHDmb/J > mKeJAUVZqNKRg1q80IpWyoM12Zw0nX1eTwMnVY/JtJON4\n13PoEC3So8nniGt+wtHr44 > ysvCWfU0SBk/ZPnKmQ58o5MlSkidHwySChXfVPYLPWeUJ1JUrujna/\nCbi5bmmjx2pqw > LrZXX8Q5NO2MRKOTs0Dtg16Q6z+a3cXLIffVJfhPGS3AkIh6nznNaDeH5gFZZbd\nr3DK > E4xrpdw/7y6CgjmHe4vwGxOIyE+gElZ/lVtqznLMwohz7wgtgsDA36277mujNyMjMbrSF > heu\n5WfbIa9VVSZWEkISVq6eswLOQ1IRaFyJsFN9AgMBAAGjga0wgaowHQYDVR0OBBYE > FDYEqJOMqN8+\nQhCP7DAkqF3RZMFdMGgGA1UdIwRhMF+AFDYEqJOMqN8+QhCP7DAkqF3 > RZMFdoUOkQTA/MQswCQYD\nVQQGEwJVUzERMA8GA1UECgwIdGx0ZC5jb20xHTAbBgNVBA > MMFG9vZW5nLnRsdGQuY29tLjE3NzMw\nggIQADAPBgNVHRMBAf8EBTADAQH/MA4GA1UdD > wEB/wQEAwIBBjANBgkqhkiG9w0BAQsFAAOCAQEA\nAKs0/yQWkoOkGcL0PjF9ijekdMmj > rLZGyh5uLot7h9s/Y2+5l9n9IzEjjx9chi8xwt6MBsR6/nBT\n/skcciv2veM22HwNGjd > rHvhfbZFnZsGe2TU60kGzKjlv1En/8Pgd2aWBcwTlr+SErBXkehNEJRj9\n1saycPgwS4 > pHS04c2+4JMhpe+hxgsO2+N/SYkP95Lf7ZQynVsN/SKx7X3cWybErCqoB7G7McqaHN\nV > Ww+QNXo5islWUXqeDc3RcnW3kq0XUEzEtp6hoeRcLKO99QrAW31zqU/QY+EeZ6Fax1O/j > rDafZn\npTs0KJFNgeVnUhKanB29ONy+tmnUmTAgPMaKKw==\n-END > CERTIFICATE-\n > > the firewall list of the host 192.168.10.41 is: > > [root@ooengh1 ~]# firewall-cmd --list-all public (active) > target: default > icmp-block-inversion: no > interfaces: bond0 ovirtmgmt > sources: > services: cockpit dhcpv6-client libvirt-tls ovirt-imageio ovirt- > vmconsole snmp ssh vdsm > ports: 6900/tcp 22/tcp 6081/udp > protocols: > masquerade: no > forward-ports: > source-ports: > icmp-blocks: > rich rules: > > > > > > > > the follow file is the connect file that vm that cannot connect using > remote viewer: > > [virt-viewer] > type=vnc > host=ohost1.tltd.com > port=5900 > password=4/jWA+RLaSZe > # Password is valid for 120 seconds. > delete-this-file=1 > fullscreen=0 > title=testol:%d > toggle-fullscreen=shift+f11 > release-cursor=shift+f12 > secure-attention=ctrl+alt+end > versions=rhev-win64:2.0-160;rhev-win32:2.0-160;rhel8:7.0-3;rhel7:2.0- > 6;rhel6:99.0-1 > newer-version-url= > http://www.ovirt.org/documentation/admin-guide/virt/console-client-res > ources > > [ovirt] > host=ooeng.tltd.com:443 > vm-guid=2b0eeecf-e561-4f60-b16d-dccddfcc852a > sso-token=4Up7TfLLBjSuQgPkQvRz3D- > fUGZWZg4ynApe2Y7ylkARCFwQWsfEr3dU8FjlK8esctm3Im4tz80mE1DjrNT3XQ > admin=1 > ca=-BEGIN CERTIFICATE- > \nMIIDqDCCApCgAwIBAgICEAAwDQYJKoZIhvcNAQELBQAwPzELMAkGA1UEBhMCVVMxETA > PBgNVBAoM\nCHRsdGQuY29tMR0wGwYDVQQDDBRvb2VuZy50bHRkLmNvbS4xNzczMDAeFw > 0yMTAxMTAxNjE1NDda\nFw0zMTAxMDkxNjE1NDdaMD8xCzAJBgNVBAYTAlVTMREwDwYDV &
[ovirt-users] Re: VM console does not work with new cluster.
It not work even I stop the firewall on the hosts. So, I think firewall is not the cause. -Original Message- From: Strahil Nikolov Sent: Thursday, January 14, 2021 12:52 PM To: tommy ; matthew.st...@fujitsu.com; eev...@digitaldatatechs.com Cc: users@ovirt.org Subject: Re: [ovirt-users] Re: VM console does not work with new cluster. I don't see the VNC ports at all (5900 and above). Here is my firewall on oVirt 4.3.10: public (active) target: default icmp-block-inversion: no interfaces: enp4s0 enp5s0f0 enp5s0f1 enp7s5f0 enp7s5f1 enp7s6f0 enp7s6f1 ovirtmgmt team0 sources: services: cockpit ctdb dhcpv6-client glusterfs libvirt-tls nfs nfs3 nrpe ovirt-imageio ovirt-storageconsole ovirt-vmconsole rpc-bind samba snmp ssh vdsm ports: 111/tcp 2049/tcp 54321/tcp 5900/tcp 5900-6923/tcp 5666/tcp 16514/tcp 54322/tcp 22/tcp 6081/udp 8080/tcp 963/udp 965/tcp protocols: masquerade: no forward-ports: source-ports: icmp-blocks: rich rules: Best Regards, Strahil Nikolov В 05:25 +0800 на 13.01.2021 (ср), tommy написа: > I encountered the question too. > > The follow file is the connect file for vm that can connect using > remote viewer: > > [virt-viewer] > type=vnc > host=192.168.10.41 > port=5900 > password=rdXQA4zr/UAY > # Password is valid for 120 seconds. > delete-this-file=1 > fullscreen=0 > title=HostedEngine:%d > toggle-fullscreen=shift+f11 > release-cursor=shift+f12 > secure-attention=ctrl+alt+end > versions=rhev-win64:2.0-160;rhev-win32:2.0-160;rhel8:7.0-3;rhel7:2.0- > 6;rhel6:99.0-1 > newer-version-url= > http://www.ovirt.org/documentation/admin-guide/virt/console-client-res > ources > > [ovirt] > host=ooeng.tltd.com:443 > vm-guid=76f99df2-ef79-45d9-8eea-a32b168f9ef3 > sso-token=4Up7TfLLBjSuQgPkQvRz3D- > fUGZWZg4ynApe2Y7ylkARCFwQWsfEr3dU8FjlK8esctm3Im4tz80mE1DjrNT3XQ > admin=1 > ca=-BEGIN CERTIFICATE- > \nMIIDqDCCApCgAwIBAgICEAAwDQYJKoZIhvcNAQELBQAwPzELMAkGA1UEBhMCVVMxETA > PBgNVBAoM\nCHRsdGQuY29tMR0wGwYDVQQDDBRvb2VuZy50bHRkLmNvbS4xNzczMDAeFw > 0yMTAxMTAxNjE1NDda\nFw0zMTAxMDkxNjE1NDdaMD8xCzAJBgNVBAYTAlVTMREwDwYDV > QQKDAh0bHRkLmNvbTEdMBsGA1UE\nAwwUb29lbmcudGx0ZC5jb20uMTc3MzAwggEiMA0G > CSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQCg\nYT9S7hWiXQUzAqFQKbg2nMjwyHDmb/J > mKeJAUVZqNKRg1q80IpWyoM12Zw0nX1eTwMnVY/JtJON4\n13PoEC3So8nniGt+wtHr44 > ysvCWfU0SBk/ZPnKmQ58o5MlSkidHwySChXfVPYLPWeUJ1JUrujna/\nCbi5bmmjx2pqw > LrZXX8Q5NO2MRKOTs0Dtg16Q6z+a3cXLIffVJfhPGS3AkIh6nznNaDeH5gFZZbd\nr3DK > E4xrpdw/7y6CgjmHe4vwGxOIyE+gElZ/lVtqznLMwohz7wgtgsDA36277mujNyMjMbrSF > heu\n5WfbIa9VVSZWEkISVq6eswLOQ1IRaFyJsFN9AgMBAAGjga0wgaowHQYDVR0OBBYE > FDYEqJOMqN8+\nQhCP7DAkqF3RZMFdMGgGA1UdIwRhMF+AFDYEqJOMqN8+QhCP7DAkqF3 > RZMFdoUOkQTA/MQswCQYD\nVQQGEwJVUzERMA8GA1UECgwIdGx0ZC5jb20xHTAbBgNVBA > MMFG9vZW5nLnRsdGQuY29tLjE3NzMw\nggIQADAPBgNVHRMBAf8EBTADAQH/MA4GA1UdD > wEB/wQEAwIBBjANBgkqhkiG9w0BAQsFAAOCAQEA\nAKs0/yQWkoOkGcL0PjF9ijekdMmj > rLZGyh5uLot7h9s/Y2+5l9n9IzEjjx9chi8xwt6MBsR6/nBT\n/skcciv2veM22HwNGjd > rHvhfbZFnZsGe2TU60kGzKjlv1En/8Pgd2aWBcwTlr+SErBXkehNEJRj9\n1saycPgwS4 > pHS04c2+4JMhpe+hxgsO2+N/SYkP95Lf7ZQynVsN/SKx7X3cWybErCqoB7G7McqaHN\nV > Ww+QNXo5islWUXqeDc3RcnW3kq0XUEzEtp6hoeRcLKO99QrAW31zqU/QY+EeZ6Fax1O/j > rDafZn\npTs0KJFNgeVnUhKanB29ONy+tmnUmTAgPMaKKw==\n-END > CERTIFICATE-\n > > the firewall list of the host 192.168.10.41 is: > > [root@ooengh1 ~]# firewall-cmd --list-all public (active) > target: default > icmp-block-inversion: no > interfaces: bond0 ovirtmgmt > sources: > services: cockpit dhcpv6-client libvirt-tls ovirt-imageio ovirt- > vmconsole snmp ssh vdsm > ports: 6900/tcp 22/tcp 6081/udp > protocols: > masquerade: no > forward-ports: > source-ports: > icmp-blocks: > rich rules: > > > > > > > > the follow file is the connect file that vm that cannot connect using > remote viewer: > > [virt-viewer] > type=vnc > host=ohost1.tltd.com > port=5900 > password=4/jWA+RLaSZe > # Password is valid for 120 seconds. > delete-this-file=1 > fullscreen=0 > title=testol:%d > toggle-fullscreen=shift+f11 > release-cursor=shift+f12 > secure-attention=ctrl+alt+end > versions=rhev-win64:2.0-160;rhev-win32:2.0-160;rhel8:7.0-3;rhel7:2.0- > 6;rhel6:99.0-1 > newer-version-url= > http://www.ovirt.org/documentation/admin-guide/virt/console-client-res > ources > > [ovirt] > host=ooeng.tltd.com:443 > vm-guid=2b0eeecf-e561-4f60-b16d-dccddfcc852a > sso-token=4Up7TfLLBjSuQgPkQvRz3D- > fUGZWZg4ynApe2Y7ylkARCFwQWsfEr3dU8FjlK8esctm3Im4tz80mE1DjrNT3XQ > admin=1 > ca=-BEGIN CERTIFICATE- > \nMIIDqDCCApCgAwIBAgICEAAwDQYJKoZIhvcNAQELBQAwPzELMAkGA1UEBhMCVVMxETA > PBgNVBAoM\nCHRsdGQuY29tMR0wGwYDVQQDDBRvb2VuZy50bHRkLmNvbS4x
[ovirt-users] Re: VM console does not work with new cluster.
bmmjx2pqw > LrZXX8Q5NO2MRKOTs0Dtg16Q6z+a3cXLIffVJfhPGS3AkIh6nznNaDeH5gFZZbd\nr3DK > E4xrpdw/7y6CgjmHe4vwGxOIyE+gElZ/lVtqznLMwohz7wgtgsDA36277mujNyMjMbrSF > heu\n5WfbIa9VVSZWEkISVq6eswLOQ1IRaFyJsFN9AgMBAAGjga0wgaowHQYDVR0OBBYE > FDYEqJOMqN8+\nQhCP7DAkqF3RZMFdMGgGA1UdIwRhMF+AFDYEqJOMqN8+QhCP7DAkqF3 > RZMFdoUOkQTA/MQswCQYD\nVQQGEwJVUzERMA8GA1UECgwIdGx0ZC5jb20xHTAbBgNVBA > MMFG9vZW5nLnRsdGQuY29tLjE3NzMw\nggIQADAPBgNVHRMBAf8EBTADAQH/MA4GA1UdD > wEB/wQEAwIBBjANBgkqhkiG9w0BAQsFAAOCAQEA\nAKs0/yQWkoOkGcL0PjF9ijekdMmj > rLZGyh5uLot7h9s/Y2+5l9n9IzEjjx9chi8xwt6MBsR6/nBT\n/skcciv2veM22HwNGjd > rHvhfbZFnZsGe2TU60kGzKjlv1En/8Pgd2aWBcwTlr+SErBXkehNEJRj9\n1saycPgwS4 > pHS04c2+4JMhpe+hxgsO2+N/SYkP95Lf7ZQynVsN/SKx7X3cWybErCqoB7G7McqaHN\nV > Ww+QNXo5islWUXqeDc3RcnW3kq0XUEzEtp6hoeRcLKO99QrAW31zqU/QY+EeZ6Fax1O/j > rDafZn\npTs0KJFNgeVnUhKanB29ONy+tmnUmTAgPMaKKw==\n-END > CERTIFICATE-\n > > > the firewall list of the host ohost1.tltd.com(192.168.10.160) is: > > [root@ohost1 ~]# firewall-cmd --list-all public (active) > target: default > icmp-block-inversion: no > interfaces: bond0 ovirtmgmt > sources: > services: cockpit dhcpv6-client libvirt-tls ovirt-imageio ovirt- > vmconsole snmp ssh vdsm > ports: 22/tcp 6081/udp > protocols: > masquerade: no > forward-ports: > source-ports: > icmp-blocks: > rich rules: > > > Please give me some advice,thanks. > > > > > > > > > > > > > > > > > > > > > > -Original Message- > From: users-boun...@ovirt.org On Behalf Of > Strahil Nikolov via Users > Sent: Wednesday, January 13, 2021 3:15 AM > To: matthew.st...@fujitsu.com; eev...@digitaldatatechs.com; > users@ovirt.org > Subject: [ovirt-users] Re: VM console does not work with new cluster. > > > > It’s just that once the VM has been moved to the new cluster, > > selecting console results in the same behavior, but that virt- > > viewer > > starts and stops within a second. > > In order to debug, you will need to compare the files provided when > you press the "console" button from both clusters and identify the > problem. > > Have you compared the firewalld ports on 2 nodes (old and new > cluster) ? > > Best Regards, > Strahil Nikolov > ___ > Users mailing list -- users@ovirt.org > To unsubscribe send an email to users-le...@ovirt.org Privacy > Statement: https://www.ovirt.org/privacy-policy.html > oVirt Code of Conduct: > https://www.ovirt.org/community/about/community-guidelines/ > List Archives: > https://lists.ovirt.org/archives/list/users@ovirt.org/message/3U5ZIELTUSPKT6KZ7UZWWFCDRNCF5YLN/ > > ___ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-le...@ovirt.org Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/E2VHPU7BMV4FBQ5QTEFXT7GICGUOMXWQ/
[ovirt-users] Re: VM console does not work with new cluster.
Both IP and DNS name cannot be connected. Both using VNC, the windows program
is remote viewer.
I using netstat to trace, I found that at the begin the remote viewer estab a
tcp connection to VM's host's 5900 port, but soon the connection disconnect.
On the host, the qemu process listen on 5900 port, where to find the qemu's log
for the connection ?
-Original Message-
From: users-boun...@ovirt.org On Behalf Of
eev...@digitaldatatechs.com
Sent: Wednesday, January 13, 2021 6:46 AM
To: matthew.st...@fujitsu.com; 'Strahil Nikolov' ;
users@ovirt.org
Subject: [ovirt-users] Re: VM console does not work with new cluster.
Are you using IP or dns? Has the IP changed? Host IP? Vm id? It sounds like
virt viewer cannot find it's target. Connecting with spice or vnc? What do your
logs say about the connection? Look at event viewer after a try and see what's
in the application log.
Eric Evans
Digital Data Services LLC.
304.660.9080
-Original Message-
From: matthew.st...@fujitsu.com
Sent: Tuesday, January 12, 2021 1:08 PM
To: eev...@digitaldatatechs.com; 'Strahil Nikolov' ;
users@ovirt.org
Subject: [ovirt-users] Re: VM console does not work with new cluster.
Stop/Edit/Start is the only mechanism available. You cannot change the
cluster value for a VM, until it is stopped.
The VMs have static addresses. The VM is fully function on the new cluster.
It’s just that once the VM has been moved to the new cluster, selecting console
results in the same behavior, but that virt-viewer starts and stops within a
second.
-Original Message-
From: eev...@digitaldatatechs.com
Sent: Tuesday, January 12, 2021 11:40 AM
To: Stier, Matthew ; 'Strahil Nikolov'
; users@ovirt.org
Subject: RE: [ovirt-users] Re: VM console does not work with new cluster.
Did you shut down the vm's and start them up on the new cluster? It sounds like
they are associated with the default still and that's where virt viewer is
looking for them..
Eric Evans
Digital Data Services LLC.
304.660.9080
-Original Message-
From: matthew.st...@fujitsu.com
Sent: Tuesday, January 12, 2021 12:29 PM
To: Strahil Nikolov ; users@ovirt.org
Subject: [ovirt-users] Re: VM console does not work with new cluster.
Sounds like it, but VMs are running on the same network, with the same IP
address. The only firewall involved are on the hosts, and they are both
firewalld, and have the same ports and service permitted.
-Original Message-
From: Strahil Nikolov
Sent: Sunday, January 10, 2021 10:57 PM
To: users@ovirt.org; Stier, Matthew
Subject: Re: [ovirt-users] VM console does not work with new cluster.
This sounds like firewall issue.
Best Regards,
Strahil Nikolov
В понеделник, 11 януари 2021 г., 01:05:47 Гринуич+2, Matthew Stier
написа:
I've added several new hosts to my data center, and instead of adding them to
my 'default' cluster, I created a new cluster ('two').
I can access the VM console (virt-viewer) when the VM is on the 'default'
cluster, but once moved to the the new cluster, virt-viewer pops up and
disappears in sub-second fashion. Moving the VM back to 'default', restores
access.
I'm running virt-viewer 9.0-256 on my Windows 10 Pro laptop. (for months)
I'm running Oracle Linux Virtualization Manager on Oracle Linux 7u9 hosts.
The new ('two') cluster hosts are connected to the same networks as the
original systems ('default'). (They have the same assigned IP address.)
Firewalld is reporting the same ports and services enabled on 'default' and
'two' hosts. The VM's are not running firewalls.
Apparently I'm missing something.
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org Privacy Statement:
https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct:
https://www.ovirt.org/community/about/community-guidelines/
List Archives:
https://lists.ovirt.org/archives/list/users@ovirt.org/message/AAKYLXLBV2FCL5TLYT32IY6IT4G43WLH/
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org Privacy Statement:
https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct:
https://www.ovirt.org/community/about/community-guidelines/
List Archives:
https://lists.ovirt.org/archives/list/users@ovirt.org/message/CPQPPOYSQGANLSC2ZP36UYQPFHAUC647/
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org Privacy Statement:
https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct:
https://www.ovirt.org/community/about/community-guidelines/
List Archives:
https://lists.ovirt.org/archives/list/users@ovirt.org/message/RFYNLB53ALNITFTSEL5GF7IZANUGEDQZ/
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org Privacy Statement
[ovirt-users] Re: VM console does not work with new cluster.
Are you using IP or dns? Has the IP changed? Host IP? Vm id? It sounds like
virt viewer cannot find it's target. Connecting with spice or vnc? What do your
logs say about the connection? Look at event viewer after a try and see what's
in the application log.
Eric Evans
Digital Data Services LLC.
304.660.9080
-Original Message-
From: matthew.st...@fujitsu.com
Sent: Tuesday, January 12, 2021 1:08 PM
To: eev...@digitaldatatechs.com; 'Strahil Nikolov' ;
users@ovirt.org
Subject: [ovirt-users] Re: VM console does not work with new cluster.
Stop/Edit/Start is the only mechanism available. You cannot change the
cluster value for a VM, until it is stopped.
The VMs have static addresses. The VM is fully function on the new cluster.
It’s just that once the VM has been moved to the new cluster, selecting console
results in the same behavior, but that virt-viewer starts and stops within a
second.
-Original Message-
From: eev...@digitaldatatechs.com
Sent: Tuesday, January 12, 2021 11:40 AM
To: Stier, Matthew ; 'Strahil Nikolov'
; users@ovirt.org
Subject: RE: [ovirt-users] Re: VM console does not work with new cluster.
Did you shut down the vm's and start them up on the new cluster? It sounds like
they are associated with the default still and that's where virt viewer is
looking for them..
Eric Evans
Digital Data Services LLC.
304.660.9080
-Original Message-
From: matthew.st...@fujitsu.com
Sent: Tuesday, January 12, 2021 12:29 PM
To: Strahil Nikolov ; users@ovirt.org
Subject: [ovirt-users] Re: VM console does not work with new cluster.
Sounds like it, but VMs are running on the same network, with the same IP
address. The only firewall involved are on the hosts, and they are both
firewalld, and have the same ports and service permitted.
-Original Message-
From: Strahil Nikolov
Sent: Sunday, January 10, 2021 10:57 PM
To: users@ovirt.org; Stier, Matthew
Subject: Re: [ovirt-users] VM console does not work with new cluster.
This sounds like firewall issue.
Best Regards,
Strahil Nikolov
В понеделник, 11 януари 2021 г., 01:05:47 Гринуич+2, Matthew Stier
написа:
I've added several new hosts to my data center, and instead of adding them to
my 'default' cluster, I created a new cluster ('two').
I can access the VM console (virt-viewer) when the VM is on the 'default'
cluster, but once moved to the the new cluster, virt-viewer pops up and
disappears in sub-second fashion. Moving the VM back to 'default', restores
access.
I'm running virt-viewer 9.0-256 on my Windows 10 Pro laptop. (for months)
I'm running Oracle Linux Virtualization Manager on Oracle Linux 7u9 hosts.
The new ('two') cluster hosts are connected to the same networks as the
original systems ('default'). (They have the same assigned IP address.)
Firewalld is reporting the same ports and services enabled on 'default' and
'two' hosts. The VM's are not running firewalls.
Apparently I'm missing something.
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org Privacy Statement:
https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct:
https://www.ovirt.org/community/about/community-guidelines/
List Archives:
https://lists.ovirt.org/archives/list/users@ovirt.org/message/AAKYLXLBV2FCL5TLYT32IY6IT4G43WLH/
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org Privacy Statement:
https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct:
https://www.ovirt.org/community/about/community-guidelines/
List Archives:
https://lists.ovirt.org/archives/list/users@ovirt.org/message/CPQPPOYSQGANLSC2ZP36UYQPFHAUC647/
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org Privacy Statement:
https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct:
https://www.ovirt.org/community/about/community-guidelines/
List Archives:
https://lists.ovirt.org/archives/list/users@ovirt.org/message/RFYNLB53ALNITFTSEL5GF7IZANUGEDQZ/
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct:
https://www.ovirt.org/community/about/community-guidelines/
List Archives:
https://lists.ovirt.org/archives/list/users@ovirt.org/message/NWGE3UALUOD7727BN742LHRGWZJH3YIA/
[ovirt-users] Re: VM console does not work with new cluster.
> It’s just that once the VM has been moved to the new cluster, > selecting console results in the same behavior, but that virt-viewer > starts and stops within a second. In order to debug, you will need to compare the files provided when you press the "console" button from both clusters and identify the problem. Have you compared the firewalld ports on 2 nodes (old and new cluster) ? Best Regards, Strahil Nikolov ___ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-le...@ovirt.org Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/3U5ZIELTUSPKT6KZ7UZWWFCDRNCF5YLN/
[ovirt-users] Re: VM console does not work with new cluster.
Stop/Edit/Start is the only mechanism available. You cannot change the
cluster value for a VM, until it is stopped.
The VMs have static addresses. The VM is fully function on the new cluster.
It’s just that once the VM has been moved to the new cluster, selecting console
results in the same behavior, but that virt-viewer starts and stops within a
second.
-Original Message-
From: eev...@digitaldatatechs.com
Sent: Tuesday, January 12, 2021 11:40 AM
To: Stier, Matthew ; 'Strahil Nikolov'
; users@ovirt.org
Subject: RE: [ovirt-users] Re: VM console does not work with new cluster.
Did you shut down the vm's and start them up on the new cluster? It sounds like
they are associated with the default still and that's where virt viewer is
looking for them..
Eric Evans
Digital Data Services LLC.
304.660.9080
-Original Message-
From: matthew.st...@fujitsu.com
Sent: Tuesday, January 12, 2021 12:29 PM
To: Strahil Nikolov ; users@ovirt.org
Subject: [ovirt-users] Re: VM console does not work with new cluster.
Sounds like it, but VMs are running on the same network, with the same IP
address. The only firewall involved are on the hosts, and they are both
firewalld, and have the same ports and service permitted.
-Original Message-
From: Strahil Nikolov
Sent: Sunday, January 10, 2021 10:57 PM
To: users@ovirt.org; Stier, Matthew
Subject: Re: [ovirt-users] VM console does not work with new cluster.
This sounds like firewall issue.
Best Regards,
Strahil Nikolov
В понеделник, 11 януари 2021 г., 01:05:47 Гринуич+2, Matthew Stier
написа:
I've added several new hosts to my data center, and instead of adding them to
my 'default' cluster, I created a new cluster ('two').
I can access the VM console (virt-viewer) when the VM is on the 'default'
cluster, but once moved to the the new cluster, virt-viewer pops up and
disappears in sub-second fashion. Moving the VM back to 'default', restores
access.
I'm running virt-viewer 9.0-256 on my Windows 10 Pro laptop. (for months)
I'm running Oracle Linux Virtualization Manager on Oracle Linux 7u9 hosts.
The new ('two') cluster hosts are connected to the same networks as the
original systems ('default'). (They have the same assigned IP address.)
Firewalld is reporting the same ports and services enabled on 'default' and
'two' hosts. The VM's are not running firewalls.
Apparently I'm missing something.
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org Privacy Statement:
https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct:
https://www.ovirt.org/community/about/community-guidelines/
List Archives:
https://lists.ovirt.org/archives/list/users@ovirt.org/message/AAKYLXLBV2FCL5TLYT32IY6IT4G43WLH/
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org Privacy Statement:
https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct:
https://www.ovirt.org/community/about/community-guidelines/
List Archives:
https://lists.ovirt.org/archives/list/users@ovirt.org/message/CPQPPOYSQGANLSC2ZP36UYQPFHAUC647/
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct:
https://www.ovirt.org/community/about/community-guidelines/
List Archives:
https://lists.ovirt.org/archives/list/users@ovirt.org/message/RFYNLB53ALNITFTSEL5GF7IZANUGEDQZ/
[ovirt-users] Re: VM console does not work with new cluster.
Did you shut down the vm's and start them up on the new cluster? It sounds like
they are associated with the default still and that's where virt viewer is
looking for them..
Eric Evans
Digital Data Services LLC.
304.660.9080
-Original Message-
From: matthew.st...@fujitsu.com
Sent: Tuesday, January 12, 2021 12:29 PM
To: Strahil Nikolov ; users@ovirt.org
Subject: [ovirt-users] Re: VM console does not work with new cluster.
Sounds like it, but VMs are running on the same network, with the same IP
address. The only firewall involved are on the hosts, and they are both
firewalld, and have the same ports and service permitted.
-Original Message-
From: Strahil Nikolov
Sent: Sunday, January 10, 2021 10:57 PM
To: users@ovirt.org; Stier, Matthew
Subject: Re: [ovirt-users] VM console does not work with new cluster.
This sounds like firewall issue.
Best Regards,
Strahil Nikolov
В понеделник, 11 януари 2021 г., 01:05:47 Гринуич+2, Matthew Stier
написа:
I've added several new hosts to my data center, and instead of adding them to
my 'default' cluster, I created a new cluster ('two').
I can access the VM console (virt-viewer) when the VM is on the 'default'
cluster, but once moved to the the new cluster, virt-viewer pops up and
disappears in sub-second fashion. Moving the VM back to 'default', restores
access.
I'm running virt-viewer 9.0-256 on my Windows 10 Pro laptop. (for months)
I'm running Oracle Linux Virtualization Manager on Oracle Linux 7u9 hosts.
The new ('two') cluster hosts are connected to the same networks as the
original systems ('default'). (They have the same assigned IP address.)
Firewalld is reporting the same ports and services enabled on 'default' and
'two' hosts. The VM's are not running firewalls.
Apparently I'm missing something.
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org Privacy Statement:
https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct:
https://www.ovirt.org/community/about/community-guidelines/
List Archives:
https://lists.ovirt.org/archives/list/users@ovirt.org/message/AAKYLXLBV2FCL5TLYT32IY6IT4G43WLH/
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org Privacy Statement:
https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct:
https://www.ovirt.org/community/about/community-guidelines/
List Archives:
https://lists.ovirt.org/archives/list/users@ovirt.org/message/CPQPPOYSQGANLSC2ZP36UYQPFHAUC647/
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct:
https://www.ovirt.org/community/about/community-guidelines/
List Archives:
https://lists.ovirt.org/archives/list/users@ovirt.org/message/UEQMXFPHRAQPJTGC5VGKLMNJA3IPJTMH/
[ovirt-users] Re: VM console does not work with new cluster.
Sounds like it, but VMs are running on the same network, with the same IP
address. The only firewall involved are on the hosts, and they are both
firewalld, and have the same ports and service permitted.
-Original Message-
From: Strahil Nikolov
Sent: Sunday, January 10, 2021 10:57 PM
To: users@ovirt.org; Stier, Matthew
Subject: Re: [ovirt-users] VM console does not work with new cluster.
This sounds like firewall issue.
Best Regards,
Strahil Nikolov
В понеделник, 11 януари 2021 г., 01:05:47 Гринуич+2, Matthew Stier
написа:
I've added several new hosts to my data center, and instead of adding them to
my 'default' cluster, I created a new cluster ('two').
I can access the VM console (virt-viewer) when the VM is on the 'default'
cluster, but once moved to the the new cluster, virt-viewer pops up and
disappears in sub-second fashion. Moving the VM back to 'default', restores
access.
I'm running virt-viewer 9.0-256 on my Windows 10 Pro laptop. (for months)
I'm running Oracle Linux Virtualization Manager on Oracle Linux 7u9 hosts.
The new ('two') cluster hosts are connected to the same networks as the
original systems ('default'). (They have the same assigned IP address.)
Firewalld is reporting the same ports and services enabled on 'default' and
'two' hosts. The VM's are not running firewalls.
Apparently I'm missing something.
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org Privacy Statement:
https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct:
https://www.ovirt.org/community/about/community-guidelines/
List Archives:
https://lists.ovirt.org/archives/list/users@ovirt.org/message/AAKYLXLBV2FCL5TLYT32IY6IT4G43WLH/
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct:
https://www.ovirt.org/community/about/community-guidelines/
List Archives:
https://lists.ovirt.org/archives/list/users@ovirt.org/message/CPQPPOYSQGANLSC2ZP36UYQPFHAUC647/
[ovirt-users] Re: VM console does not work with new cluster.
This sounds like firewall issue.
Best Regards,
Strahil Nikolov
В понеделник, 11 януари 2021 г., 01:05:47 Гринуич+2, Matthew Stier
написа:
I've added several new hosts to my data center, and instead of adding them to
my 'default' cluster, I created a new cluster ('two').
I can access the VM console (virt-viewer) when the VM is on the 'default'
cluster, but once moved to the the new cluster, virt-viewer pops up and
disappears in sub-second fashion. Moving the VM back to 'default', restores
access.
I'm running virt-viewer 9.0-256 on my Windows 10 Pro laptop. (for months)
I'm running Oracle Linux Virtualization Manager on Oracle Linux 7u9 hosts.
The new ('two') cluster hosts are connected to the same networks as the
original systems ('default'). (They have the same assigned IP address.)
Firewalld is reporting the same ports and services enabled on 'default' and
'two' hosts. The VM's are not running firewalls.
Apparently I'm missing something.
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct:
https://www.ovirt.org/community/about/community-guidelines/
List Archives:
https://lists.ovirt.org/archives/list/users@ovirt.org/message/AAKYLXLBV2FCL5TLYT32IY6IT4G43WLH/
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct:
https://www.ovirt.org/community/about/community-guidelines/
List Archives:
https://lists.ovirt.org/archives/list/users@ovirt.org/message/XJZFU2ZLOYMFRALXP6D2ILYRNUBYVKTO/
