[ovirt-users] Re: vm console problem
On Wed, Mar 25, 2020 at 12:45 PM David David wrote: > > ovirt 4.3.8.2-1.el7 > gtk-vnc2-1.0.0-1.fc31.x86_64 > remote-viewer version 8.0-3.fc31 > > can't open vm console by remote-viewer > vm has vnc console protocol > when click on console button to connect to a vm, the remote-viewer > console disappear immediately > > remote-viewer debug in attachment You an issue with the certificates: (remote-viewer:2721): gtk-vnc-DEBUG: 11:56:25.238: ../src/vncconnection.c Set credential 2 libvirt (remote-viewer:2721): gtk-vnc-DEBUG: 11:56:25.239: ../src/vncconnection.c Searching for certs in /etc/pki (remote-viewer:2721): gtk-vnc-DEBUG: 11:56:25.239: ../src/vncconnection.c Searching for certs in /root/.pki (remote-viewer:2721): gtk-vnc-DEBUG: 11:56:25.239: ../src/vncconnection.c Failed to find certificate CA/cacert.pem (remote-viewer:2721): gtk-vnc-DEBUG: 11:56:25.239: ../src/vncconnection.c No CA certificate provided, using GNUTLS global trust (remote-viewer:2721): gtk-vnc-DEBUG: 11:56:25.239: ../src/vncconnection.c Failed to find certificate CA/cacrl.pem (remote-viewer:2721): gtk-vnc-DEBUG: 11:56:25.239: ../src/vncconnection.c Failed to find certificate libvirt/private/clientkey.pem (remote-viewer:2721): gtk-vnc-DEBUG: 11:56:25.239: ../src/vncconnection.c Failed to find certificate libvirt/clientcert.pem (remote-viewer:2721): gtk-vnc-DEBUG: 11:56:25.239: ../src/vncconnection.c Waiting for missing credentials (remote-viewer:2721): gtk-vnc-DEBUG: 11:56:25.239: ../src/vncconnection.c Got all credentials (remote-viewer:2721): gtk-vnc-DEBUG: 11:56:25.239: ../src/vncconnection.c No CA certificate provided; trying the system trust store instead (remote-viewer:2721): gtk-vnc-DEBUG: 11:56:25.240: ../src/vncconnection.c Using the system trust store and CRL (remote-viewer:2721): gtk-vnc-DEBUG: 11:56:25.240: ../src/vncconnection.c No client cert or key provided (remote-viewer:2721): gtk-vnc-DEBUG: 11:56:25.240: ../src/vncconnection.c No CA revocation list provided (remote-viewer:2721): gtk-vnc-DEBUG: 11:56:25.241: ../src/vncconnection.c Handshake was blocking (remote-viewer:2721): gtk-vnc-DEBUG: 11:56:25.243: ../src/vncconnection.c Handshake was blocking (remote-viewer:2721): gtk-vnc-DEBUG: 11:56:25.251: ../src/vncconnection.c Handshake was blocking (remote-viewer:2721): gtk-vnc-DEBUG: 11:56:25.298: ../src/vncconnection.c Handshake done (remote-viewer:2721): gtk-vnc-DEBUG: 11:56:25.298: ../src/vncconnection.c Validating (remote-viewer:2721): gtk-vnc-DEBUG: 11:56:25.301: ../src/vncconnection.c Error: The certificate is not trusted Adding people that may know more about this. Nir ___ 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/Y4MPGDLGXR5TZR2JUMHM4HBGE7TOMFWO/
[ovirt-users] Re: vm console problem
copied from qemu server all certs except "cacrl" to my desktop-station into /etc/pki/ but remote-viewer is still didn't work 2020-03-26 2:22 GMT+04:00, Nir Soffer : > On Wed, Mar 25, 2020 at 12:45 PM David David wrote: >> >> ovirt 4.3.8.2-1.el7 >> gtk-vnc2-1.0.0-1.fc31.x86_64 >> remote-viewer version 8.0-3.fc31 >> >> can't open vm console by remote-viewer >> vm has vnc console protocol >> when click on console button to connect to a vm, the remote-viewer >> console disappear immediately >> >> remote-viewer debug in attachment > > You an issue with the certificates: > > (remote-viewer:2721): gtk-vnc-DEBUG: 11:56:25.238: > ../src/vncconnection.c Set credential 2 libvirt > (remote-viewer:2721): gtk-vnc-DEBUG: 11:56:25.239: > ../src/vncconnection.c Searching for certs in /etc/pki > (remote-viewer:2721): gtk-vnc-DEBUG: 11:56:25.239: > ../src/vncconnection.c Searching for certs in /root/.pki > (remote-viewer:2721): gtk-vnc-DEBUG: 11:56:25.239: > ../src/vncconnection.c Failed to find certificate CA/cacert.pem > (remote-viewer:2721): gtk-vnc-DEBUG: 11:56:25.239: > ../src/vncconnection.c No CA certificate provided, using GNUTLS global > trust > (remote-viewer:2721): gtk-vnc-DEBUG: 11:56:25.239: > ../src/vncconnection.c Failed to find certificate CA/cacrl.pem > (remote-viewer:2721): gtk-vnc-DEBUG: 11:56:25.239: > ../src/vncconnection.c Failed to find certificate > libvirt/private/clientkey.pem > (remote-viewer:2721): gtk-vnc-DEBUG: 11:56:25.239: > ../src/vncconnection.c Failed to find certificate > libvirt/clientcert.pem > (remote-viewer:2721): gtk-vnc-DEBUG: 11:56:25.239: > ../src/vncconnection.c Waiting for missing credentials > (remote-viewer:2721): gtk-vnc-DEBUG: 11:56:25.239: > ../src/vncconnection.c Got all credentials > (remote-viewer:2721): gtk-vnc-DEBUG: 11:56:25.239: > ../src/vncconnection.c No CA certificate provided; trying the system > trust store instead > (remote-viewer:2721): gtk-vnc-DEBUG: 11:56:25.240: > ../src/vncconnection.c Using the system trust store and CRL > (remote-viewer:2721): gtk-vnc-DEBUG: 11:56:25.240: > ../src/vncconnection.c No client cert or key provided > (remote-viewer:2721): gtk-vnc-DEBUG: 11:56:25.240: > ../src/vncconnection.c No CA revocation list provided > (remote-viewer:2721): gtk-vnc-DEBUG: 11:56:25.241: > ../src/vncconnection.c Handshake was blocking > (remote-viewer:2721): gtk-vnc-DEBUG: 11:56:25.243: > ../src/vncconnection.c Handshake was blocking > (remote-viewer:2721): gtk-vnc-DEBUG: 11:56:25.251: > ../src/vncconnection.c Handshake was blocking > (remote-viewer:2721): gtk-vnc-DEBUG: 11:56:25.298: > ../src/vncconnection.c Handshake done > (remote-viewer:2721): gtk-vnc-DEBUG: 11:56:25.298: > ../src/vncconnection.c Validating > (remote-viewer:2721): gtk-vnc-DEBUG: 11:56:25.301: > ../src/vncconnection.c Error: The certificate is not trusted > > Adding people that may know more about this. > > Nir > > ___ 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/HJXFHCI66BTIFV3IYEMWESTEHT2RNJSA/
[ovirt-users] Re: vm console problem
David David writes: > copied from qemu server all certs except "cacrl" to my desktop-station > into /etc/pki/ This is not needed, the CA certificate is included in console.vv and no other certificate should be needed. > but remote-viewer is still didn't work The log looks like remote-viewer is attempting certificate authentication rather than password authentication. Do you have password in console.vv? It should look like: [virt-viewer] type=vnc host=192.168.122.2 port=5900 password=fxLazJu6BUmL # Password is valid for 120 seconds. ... Regards, Milan > 2020-03-26 2:22 GMT+04:00, Nir Soffer : >> On Wed, Mar 25, 2020 at 12:45 PM David David wrote: >>> >>> ovirt 4.3.8.2-1.el7 >>> gtk-vnc2-1.0.0-1.fc31.x86_64 >>> remote-viewer version 8.0-3.fc31 >>> >>> can't open vm console by remote-viewer >>> vm has vnc console protocol >>> when click on console button to connect to a vm, the remote-viewer >>> console disappear immediately >>> >>> remote-viewer debug in attachment >> >> You an issue with the certificates: >> >> (remote-viewer:2721): gtk-vnc-DEBUG: 11:56:25.238: >> ../src/vncconnection.c Set credential 2 libvirt >> (remote-viewer:2721): gtk-vnc-DEBUG: 11:56:25.239: >> ../src/vncconnection.c Searching for certs in /etc/pki >> (remote-viewer:2721): gtk-vnc-DEBUG: 11:56:25.239: >> ../src/vncconnection.c Searching for certs in /root/.pki >> (remote-viewer:2721): gtk-vnc-DEBUG: 11:56:25.239: >> ../src/vncconnection.c Failed to find certificate CA/cacert.pem >> (remote-viewer:2721): gtk-vnc-DEBUG: 11:56:25.239: >> ../src/vncconnection.c No CA certificate provided, using GNUTLS global >> trust >> (remote-viewer:2721): gtk-vnc-DEBUG: 11:56:25.239: >> ../src/vncconnection.c Failed to find certificate CA/cacrl.pem >> (remote-viewer:2721): gtk-vnc-DEBUG: 11:56:25.239: >> ../src/vncconnection.c Failed to find certificate >> libvirt/private/clientkey.pem >> (remote-viewer:2721): gtk-vnc-DEBUG: 11:56:25.239: >> ../src/vncconnection.c Failed to find certificate >> libvirt/clientcert.pem >> (remote-viewer:2721): gtk-vnc-DEBUG: 11:56:25.239: >> ../src/vncconnection.c Waiting for missing credentials >> (remote-viewer:2721): gtk-vnc-DEBUG: 11:56:25.239: >> ../src/vncconnection.c Got all credentials >> (remote-viewer:2721): gtk-vnc-DEBUG: 11:56:25.239: >> ../src/vncconnection.c No CA certificate provided; trying the system >> trust store instead >> (remote-viewer:2721): gtk-vnc-DEBUG: 11:56:25.240: >> ../src/vncconnection.c Using the system trust store and CRL >> (remote-viewer:2721): gtk-vnc-DEBUG: 11:56:25.240: >> ../src/vncconnection.c No client cert or key provided >> (remote-viewer:2721): gtk-vnc-DEBUG: 11:56:25.240: >> ../src/vncconnection.c No CA revocation list provided >> (remote-viewer:2721): gtk-vnc-DEBUG: 11:56:25.241: >> ../src/vncconnection.c Handshake was blocking >> (remote-viewer:2721): gtk-vnc-DEBUG: 11:56:25.243: >> ../src/vncconnection.c Handshake was blocking >> (remote-viewer:2721): gtk-vnc-DEBUG: 11:56:25.251: >> ../src/vncconnection.c Handshake was blocking >> (remote-viewer:2721): gtk-vnc-DEBUG: 11:56:25.298: >> ../src/vncconnection.c Handshake done >> (remote-viewer:2721): gtk-vnc-DEBUG: 11:56:25.298: >> ../src/vncconnection.c Validating >> (remote-viewer:2721): gtk-vnc-DEBUG: 11:56:25.301: >> ../src/vncconnection.c Error: The certificate is not trusted >> >> Adding people that may know more about this. >> >> Nir >> >> ___ 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/G4DV6YDFGORYDO64KLD3T6NF4F52QAEN/
[ovirt-users] Re: vm console problem
yes i have console.vv attached 2020-03-26 21:38 GMT+04:00, Milan Zamazal : > David David writes: > >> copied from qemu server all certs except "cacrl" to my desktop-station >> into /etc/pki/ > > This is not needed, the CA certificate is included in console.vv and no > other certificate should be needed. > >> but remote-viewer is still didn't work > > The log looks like remote-viewer is attempting certificate > authentication rather than password authentication. Do you have > password in console.vv? It should look like: > > [virt-viewer] > type=vnc > host=192.168.122.2 > port=5900 > password=fxLazJu6BUmL > # Password is valid for 120 seconds. > ... > > Regards, > Milan > >> 2020-03-26 2:22 GMT+04:00, Nir Soffer : >>> On Wed, Mar 25, 2020 at 12:45 PM David David wrote: ovirt 4.3.8.2-1.el7 gtk-vnc2-1.0.0-1.fc31.x86_64 remote-viewer version 8.0-3.fc31 can't open vm console by remote-viewer vm has vnc console protocol when click on console button to connect to a vm, the remote-viewer console disappear immediately remote-viewer debug in attachment >>> >>> You an issue with the certificates: >>> >>> (remote-viewer:2721): gtk-vnc-DEBUG: 11:56:25.238: >>> ../src/vncconnection.c Set credential 2 libvirt >>> (remote-viewer:2721): gtk-vnc-DEBUG: 11:56:25.239: >>> ../src/vncconnection.c Searching for certs in /etc/pki >>> (remote-viewer:2721): gtk-vnc-DEBUG: 11:56:25.239: >>> ../src/vncconnection.c Searching for certs in /root/.pki >>> (remote-viewer:2721): gtk-vnc-DEBUG: 11:56:25.239: >>> ../src/vncconnection.c Failed to find certificate CA/cacert.pem >>> (remote-viewer:2721): gtk-vnc-DEBUG: 11:56:25.239: >>> ../src/vncconnection.c No CA certificate provided, using GNUTLS global >>> trust >>> (remote-viewer:2721): gtk-vnc-DEBUG: 11:56:25.239: >>> ../src/vncconnection.c Failed to find certificate CA/cacrl.pem >>> (remote-viewer:2721): gtk-vnc-DEBUG: 11:56:25.239: >>> ../src/vncconnection.c Failed to find certificate >>> libvirt/private/clientkey.pem >>> (remote-viewer:2721): gtk-vnc-DEBUG: 11:56:25.239: >>> ../src/vncconnection.c Failed to find certificate >>> libvirt/clientcert.pem >>> (remote-viewer:2721): gtk-vnc-DEBUG: 11:56:25.239: >>> ../src/vncconnection.c Waiting for missing credentials >>> (remote-viewer:2721): gtk-vnc-DEBUG: 11:56:25.239: >>> ../src/vncconnection.c Got all credentials >>> (remote-viewer:2721): gtk-vnc-DEBUG: 11:56:25.239: >>> ../src/vncconnection.c No CA certificate provided; trying the system >>> trust store instead >>> (remote-viewer:2721): gtk-vnc-DEBUG: 11:56:25.240: >>> ../src/vncconnection.c Using the system trust store and CRL >>> (remote-viewer:2721): gtk-vnc-DEBUG: 11:56:25.240: >>> ../src/vncconnection.c No client cert or key provided >>> (remote-viewer:2721): gtk-vnc-DEBUG: 11:56:25.240: >>> ../src/vncconnection.c No CA revocation list provided >>> (remote-viewer:2721): gtk-vnc-DEBUG: 11:56:25.241: >>> ../src/vncconnection.c Handshake was blocking >>> (remote-viewer:2721): gtk-vnc-DEBUG: 11:56:25.243: >>> ../src/vncconnection.c Handshake was blocking >>> (remote-viewer:2721): gtk-vnc-DEBUG: 11:56:25.251: >>> ../src/vncconnection.c Handshake was blocking >>> (remote-viewer:2721): gtk-vnc-DEBUG: 11:56:25.298: >>> ../src/vncconnection.c Handshake done >>> (remote-viewer:2721): gtk-vnc-DEBUG: 11:56:25.298: >>> ../src/vncconnection.c Validating >>> (remote-viewer:2721): gtk-vnc-DEBUG: 11:56:25.301: >>> ../src/vncconnection.c Error: The certificate is not trusted >>> >>> Adding people that may know more about this. >>> >>> Nir >>> >>> > > console.vv Description: application/virt-viewer ___ 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/2A3NO2NWO7JCU6JQ4M7KKVXURRSTEW27/
[ovirt-users] Re: vm console problem
David David writes: > yes i have > console.vv attached It looks the same as mine. There is a difference in our logs, you have Possible auth 19 while I have Possible auth 2 So I still suspect a wrong authentication method is used, but I don't have any idea why. Regards, Milan > 2020-03-26 21:38 GMT+04:00, Milan Zamazal : >> David David writes: >> >>> copied from qemu server all certs except "cacrl" to my desktop-station >>> into /etc/pki/ >> >> This is not needed, the CA certificate is included in console.vv and no >> other certificate should be needed. >> >>> but remote-viewer is still didn't work >> >> The log looks like remote-viewer is attempting certificate >> authentication rather than password authentication. Do you have >> password in console.vv? It should look like: >> >> [virt-viewer] >> type=vnc >> host=192.168.122.2 >> port=5900 >> password=fxLazJu6BUmL >> # Password is valid for 120 seconds. >> ... >> >> Regards, >> Milan >> >>> 2020-03-26 2:22 GMT+04:00, Nir Soffer : On Wed, Mar 25, 2020 at 12:45 PM David David wrote: > > ovirt 4.3.8.2-1.el7 > gtk-vnc2-1.0.0-1.fc31.x86_64 > remote-viewer version 8.0-3.fc31 > > can't open vm console by remote-viewer > vm has vnc console protocol > when click on console button to connect to a vm, the remote-viewer > console disappear immediately > > remote-viewer debug in attachment You an issue with the certificates: (remote-viewer:2721): gtk-vnc-DEBUG: 11:56:25.238: ../src/vncconnection.c Set credential 2 libvirt (remote-viewer:2721): gtk-vnc-DEBUG: 11:56:25.239: ../src/vncconnection.c Searching for certs in /etc/pki (remote-viewer:2721): gtk-vnc-DEBUG: 11:56:25.239: ../src/vncconnection.c Searching for certs in /root/.pki (remote-viewer:2721): gtk-vnc-DEBUG: 11:56:25.239: ../src/vncconnection.c Failed to find certificate CA/cacert.pem (remote-viewer:2721): gtk-vnc-DEBUG: 11:56:25.239: ../src/vncconnection.c No CA certificate provided, using GNUTLS global trust (remote-viewer:2721): gtk-vnc-DEBUG: 11:56:25.239: ../src/vncconnection.c Failed to find certificate CA/cacrl.pem (remote-viewer:2721): gtk-vnc-DEBUG: 11:56:25.239: ../src/vncconnection.c Failed to find certificate libvirt/private/clientkey.pem (remote-viewer:2721): gtk-vnc-DEBUG: 11:56:25.239: ../src/vncconnection.c Failed to find certificate libvirt/clientcert.pem (remote-viewer:2721): gtk-vnc-DEBUG: 11:56:25.239: ../src/vncconnection.c Waiting for missing credentials (remote-viewer:2721): gtk-vnc-DEBUG: 11:56:25.239: ../src/vncconnection.c Got all credentials (remote-viewer:2721): gtk-vnc-DEBUG: 11:56:25.239: ../src/vncconnection.c No CA certificate provided; trying the system trust store instead (remote-viewer:2721): gtk-vnc-DEBUG: 11:56:25.240: ../src/vncconnection.c Using the system trust store and CRL (remote-viewer:2721): gtk-vnc-DEBUG: 11:56:25.240: ../src/vncconnection.c No client cert or key provided (remote-viewer:2721): gtk-vnc-DEBUG: 11:56:25.240: ../src/vncconnection.c No CA revocation list provided (remote-viewer:2721): gtk-vnc-DEBUG: 11:56:25.241: ../src/vncconnection.c Handshake was blocking (remote-viewer:2721): gtk-vnc-DEBUG: 11:56:25.243: ../src/vncconnection.c Handshake was blocking (remote-viewer:2721): gtk-vnc-DEBUG: 11:56:25.251: ../src/vncconnection.c Handshake was blocking (remote-viewer:2721): gtk-vnc-DEBUG: 11:56:25.298: ../src/vncconnection.c Handshake done (remote-viewer:2721): gtk-vnc-DEBUG: 11:56:25.298: ../src/vncconnection.c Validating (remote-viewer:2721): gtk-vnc-DEBUG: 11:56:25.301: ../src/vncconnection.c Error: The certificate is not trusted Adding people that may know more about this. Nir >> >> ___ 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/IPX2PHLII54CFWKEH7RTN3GPP7VQ2QVZ/
[ovirt-users] Re: vm console problem
here is debug from opening console.vv by remote-viewer 2020-03-27 14:09 GMT+04:00, Milan Zamazal : > David David writes: > >> yes i have >> console.vv attached > > It looks the same as mine. > > There is a difference in our logs, you have > > Possible auth 19 > > while I have > > Possible auth 2 > > So I still suspect a wrong authentication method is used, but I don't > have any idea why. > > Regards, > Milan > >> 2020-03-26 21:38 GMT+04:00, Milan Zamazal : >>> David David writes: >>> copied from qemu server all certs except "cacrl" to my desktop-station into /etc/pki/ >>> >>> This is not needed, the CA certificate is included in console.vv and no >>> other certificate should be needed. >>> but remote-viewer is still didn't work >>> >>> The log looks like remote-viewer is attempting certificate >>> authentication rather than password authentication. Do you have >>> password in console.vv? It should look like: >>> >>> [virt-viewer] >>> type=vnc >>> host=192.168.122.2 >>> port=5900 >>> password=fxLazJu6BUmL >>> # Password is valid for 120 seconds. >>> ... >>> >>> Regards, >>> Milan >>> 2020-03-26 2:22 GMT+04:00, Nir Soffer : > On Wed, Mar 25, 2020 at 12:45 PM David David > wrote: >> >> ovirt 4.3.8.2-1.el7 >> gtk-vnc2-1.0.0-1.fc31.x86_64 >> remote-viewer version 8.0-3.fc31 >> >> can't open vm console by remote-viewer >> vm has vnc console protocol >> when click on console button to connect to a vm, the remote-viewer >> console disappear immediately >> >> remote-viewer debug in attachment > > You an issue with the certificates: > > (remote-viewer:2721): gtk-vnc-DEBUG: 11:56:25.238: > ../src/vncconnection.c Set credential 2 libvirt > (remote-viewer:2721): gtk-vnc-DEBUG: 11:56:25.239: > ../src/vncconnection.c Searching for certs in /etc/pki > (remote-viewer:2721): gtk-vnc-DEBUG: 11:56:25.239: > ../src/vncconnection.c Searching for certs in /root/.pki > (remote-viewer:2721): gtk-vnc-DEBUG: 11:56:25.239: > ../src/vncconnection.c Failed to find certificate CA/cacert.pem > (remote-viewer:2721): gtk-vnc-DEBUG: 11:56:25.239: > ../src/vncconnection.c No CA certificate provided, using GNUTLS global > trust > (remote-viewer:2721): gtk-vnc-DEBUG: 11:56:25.239: > ../src/vncconnection.c Failed to find certificate CA/cacrl.pem > (remote-viewer:2721): gtk-vnc-DEBUG: 11:56:25.239: > ../src/vncconnection.c Failed to find certificate > libvirt/private/clientkey.pem > (remote-viewer:2721): gtk-vnc-DEBUG: 11:56:25.239: > ../src/vncconnection.c Failed to find certificate > libvirt/clientcert.pem > (remote-viewer:2721): gtk-vnc-DEBUG: 11:56:25.239: > ../src/vncconnection.c Waiting for missing credentials > (remote-viewer:2721): gtk-vnc-DEBUG: 11:56:25.239: > ../src/vncconnection.c Got all credentials > (remote-viewer:2721): gtk-vnc-DEBUG: 11:56:25.239: > ../src/vncconnection.c No CA certificate provided; trying the system > trust store instead > (remote-viewer:2721): gtk-vnc-DEBUG: 11:56:25.240: > ../src/vncconnection.c Using the system trust store and CRL > (remote-viewer:2721): gtk-vnc-DEBUG: 11:56:25.240: > ../src/vncconnection.c No client cert or key provided > (remote-viewer:2721): gtk-vnc-DEBUG: 11:56:25.240: > ../src/vncconnection.c No CA revocation list provided > (remote-viewer:2721): gtk-vnc-DEBUG: 11:56:25.241: > ../src/vncconnection.c Handshake was blocking > (remote-viewer:2721): gtk-vnc-DEBUG: 11:56:25.243: > ../src/vncconnection.c Handshake was blocking > (remote-viewer:2721): gtk-vnc-DEBUG: 11:56:25.251: > ../src/vncconnection.c Handshake was blocking > (remote-viewer:2721): gtk-vnc-DEBUG: 11:56:25.298: > ../src/vncconnection.c Handshake done > (remote-viewer:2721): gtk-vnc-DEBUG: 11:56:25.298: > ../src/vncconnection.c Validating > (remote-viewer:2721): gtk-vnc-DEBUG: 11:56:25.301: > ../src/vncconnection.c Error: The certificate is not trusted > > Adding people that may know more about this. > > Nir > > >>> >>> > > (remote-viewer:47852): virt-viewer-DEBUG: 14:16:35.872: Opening display to /home/david/Downloads/console.vv (remote-viewer:47852): virt-viewer-DEBUG: 14:16:35.873: Guest (null) has a vnc display (remote-viewer:47852): gtk-vnc-DEBUG: 14:16:35.873: ../src/vncconnection.c Init VncConnection=0x5578f6b75bf0 (remote-viewer:47852): gtk-vnc-DEBUG: 14:16:35.873: ../src/vncdisplaykeymap.c Using X11 backend (remote-viewer:47852): gtk-vnc-DEBUG: 14:16:35.873: ../src/vncdisplaykeymap.c XKB keyboard map name '(unnamed)' (remote-viewer:47852): gtk-vnc-DEBUG: 14:16:35.874: ../src/vncdisplaykeymap.c Server vendor is 'Fedora Project' (remote-viewer:47852): gtk-vnc-DEBUG: 14:16:35.874: ../src/vncdisplaykeymap.c Found extension 'Generic Event Extension' (remote-viewer:47852): gtk-vnc-DEBUG: 14:16:35.874: ../src/vncdi
[ovirt-users] Re: vm console problem
On March 27, 2020 12:23:10 PM GMT+02:00, David David wrote: >here is debug from opening console.vv by remote-viewer > >2020-03-27 14:09 GMT+04:00, Milan Zamazal : >> David David writes: >> >>> yes i have >>> console.vv attached >> >> It looks the same as mine. >> >> There is a difference in our logs, you have >> >> Possible auth 19 >> >> while I have >> >> Possible auth 2 >> >> So I still suspect a wrong authentication method is used, but I don't >> have any idea why. >> >> Regards, >> Milan >> >>> 2020-03-26 21:38 GMT+04:00, Milan Zamazal : David David writes: > copied from qemu server all certs except "cacrl" to my >desktop-station > into /etc/pki/ This is not needed, the CA certificate is included in console.vv >and no other certificate should be needed. > but remote-viewer is still didn't work The log looks like remote-viewer is attempting certificate authentication rather than password authentication. Do you have password in console.vv? It should look like: [virt-viewer] type=vnc host=192.168.122.2 port=5900 password=fxLazJu6BUmL # Password is valid for 120 seconds. ... Regards, Milan > 2020-03-26 2:22 GMT+04:00, Nir Soffer : >> On Wed, Mar 25, 2020 at 12:45 PM David David >> wrote: >>> >>> ovirt 4.3.8.2-1.el7 >>> gtk-vnc2-1.0.0-1.fc31.x86_64 >>> remote-viewer version 8.0-3.fc31 >>> >>> can't open vm console by remote-viewer >>> vm has vnc console protocol >>> when click on console button to connect to a vm, the >remote-viewer >>> console disappear immediately >>> >>> remote-viewer debug in attachment >> >> You an issue with the certificates: >> >> (remote-viewer:2721): gtk-vnc-DEBUG: 11:56:25.238: >> ../src/vncconnection.c Set credential 2 libvirt >> (remote-viewer:2721): gtk-vnc-DEBUG: 11:56:25.239: >> ../src/vncconnection.c Searching for certs in /etc/pki >> (remote-viewer:2721): gtk-vnc-DEBUG: 11:56:25.239: >> ../src/vncconnection.c Searching for certs in /root/.pki >> (remote-viewer:2721): gtk-vnc-DEBUG: 11:56:25.239: >> ../src/vncconnection.c Failed to find certificate CA/cacert.pem >> (remote-viewer:2721): gtk-vnc-DEBUG: 11:56:25.239: >> ../src/vncconnection.c No CA certificate provided, using GNUTLS >global >> trust >> (remote-viewer:2721): gtk-vnc-DEBUG: 11:56:25.239: >> ../src/vncconnection.c Failed to find certificate CA/cacrl.pem >> (remote-viewer:2721): gtk-vnc-DEBUG: 11:56:25.239: >> ../src/vncconnection.c Failed to find certificate >> libvirt/private/clientkey.pem >> (remote-viewer:2721): gtk-vnc-DEBUG: 11:56:25.239: >> ../src/vncconnection.c Failed to find certificate >> libvirt/clientcert.pem >> (remote-viewer:2721): gtk-vnc-DEBUG: 11:56:25.239: >> ../src/vncconnection.c Waiting for missing credentials >> (remote-viewer:2721): gtk-vnc-DEBUG: 11:56:25.239: >> ../src/vncconnection.c Got all credentials >> (remote-viewer:2721): gtk-vnc-DEBUG: 11:56:25.239: >> ../src/vncconnection.c No CA certificate provided; trying the >system >> trust store instead >> (remote-viewer:2721): gtk-vnc-DEBUG: 11:56:25.240: >> ../src/vncconnection.c Using the system trust store and CRL >> (remote-viewer:2721): gtk-vnc-DEBUG: 11:56:25.240: >> ../src/vncconnection.c No client cert or key provided >> (remote-viewer:2721): gtk-vnc-DEBUG: 11:56:25.240: >> ../src/vncconnection.c No CA revocation list provided >> (remote-viewer:2721): gtk-vnc-DEBUG: 11:56:25.241: >> ../src/vncconnection.c Handshake was blocking >> (remote-viewer:2721): gtk-vnc-DEBUG: 11:56:25.243: >> ../src/vncconnection.c Handshake was blocking >> (remote-viewer:2721): gtk-vnc-DEBUG: 11:56:25.251: >> ../src/vncconnection.c Handshake was blocking >> (remote-viewer:2721): gtk-vnc-DEBUG: 11:56:25.298: >> ../src/vncconnection.c Handshake done >> (remote-viewer:2721): gtk-vnc-DEBUG: 11:56:25.298: >> ../src/vncconnection.c Validating >> (remote-viewer:2721): gtk-vnc-DEBUG: 11:56:25.301: >> ../src/vncconnection.c Error: The certificate is not trusted >> >> Adding people that may know more about this. >> >> Nir >> >> >> >> Hello, You can try to take the engine's CA (maybe it's useless) and put it on your system in: /etc/pki/ca-trust/source/anchors (if it's EL7 or a Fedora) and then run update-ca-trust 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/G4EHEN7DOTYND5BQDVFEGW3VK4PFNEOU/
[ovirt-users] Re: vm console problem
I did as you said: copied from engine /etc/ovirt-engine/ca.pem onto my desktop into /etc/pki/ca-trust/source/anchors and then run update-ca-trust it didn’t help, still the same errors вс, 29 мар. 2020 г. в 10:47, David David : > I did as you said: > copied from engine /etc/ovirt-engine/ca.pem onto my desktop into > /etc/pki/ca-trust/source/anchors and then run update-ca-trust > it didn’t help, still the same errors > > > пт, 27 мар. 2020 г. в 21:56, Strahil Nikolov : > >> On March 27, 2020 12:23:10 PM GMT+02:00, David David >> wrote: >> >here is debug from opening console.vv by remote-viewer >> > >> >2020-03-27 14:09 GMT+04:00, Milan Zamazal : >> >> David David writes: >> >> >> >>> yes i have >> >>> console.vv attached >> >> >> >> It looks the same as mine. >> >> >> >> There is a difference in our logs, you have >> >> >> >> Possible auth 19 >> >> >> >> while I have >> >> >> >> Possible auth 2 >> >> >> >> So I still suspect a wrong authentication method is used, but I don't >> >> have any idea why. >> >> >> >> Regards, >> >> Milan >> >> >> >>> 2020-03-26 21:38 GMT+04:00, Milan Zamazal : >> David David writes: >> >> > copied from qemu server all certs except "cacrl" to my >> >desktop-station >> > into /etc/pki/ >> >> This is not needed, the CA certificate is included in console.vv >> >and no >> other certificate should be needed. >> >> > but remote-viewer is still didn't work >> >> The log looks like remote-viewer is attempting certificate >> authentication rather than password authentication. Do you have >> password in console.vv? It should look like: >> >> [virt-viewer] >> type=vnc >> host=192.168.122.2 >> port=5900 >> password=fxLazJu6BUmL >> # Password is valid for 120 seconds. >> ... >> >> Regards, >> Milan >> >> > 2020-03-26 2:22 GMT+04:00, Nir Soffer : >> >> On Wed, Mar 25, 2020 at 12:45 PM David David >> >> wrote: >> >>> >> >>> ovirt 4.3.8.2-1.el7 >> >>> gtk-vnc2-1.0.0-1.fc31.x86_64 >> >>> remote-viewer version 8.0-3.fc31 >> >>> >> >>> can't open vm console by remote-viewer >> >>> vm has vnc console protocol >> >>> when click on console button to connect to a vm, the >> >remote-viewer >> >>> console disappear immediately >> >>> >> >>> remote-viewer debug in attachment >> >> >> >> You an issue with the certificates: >> >> >> >> (remote-viewer:2721): gtk-vnc-DEBUG: 11:56:25.238: >> >> ../src/vncconnection.c Set credential 2 libvirt >> >> (remote-viewer:2721): gtk-vnc-DEBUG: 11:56:25.239: >> >> ../src/vncconnection.c Searching for certs in /etc/pki >> >> (remote-viewer:2721): gtk-vnc-DEBUG: 11:56:25.239: >> >> ../src/vncconnection.c Searching for certs in /root/.pki >> >> (remote-viewer:2721): gtk-vnc-DEBUG: 11:56:25.239: >> >> ../src/vncconnection.c Failed to find certificate CA/cacert.pem >> >> (remote-viewer:2721): gtk-vnc-DEBUG: 11:56:25.239: >> >> ../src/vncconnection.c No CA certificate provided, using GNUTLS >> >global >> >> trust >> >> (remote-viewer:2721): gtk-vnc-DEBUG: 11:56:25.239: >> >> ../src/vncconnection.c Failed to find certificate CA/cacrl.pem >> >> (remote-viewer:2721): gtk-vnc-DEBUG: 11:56:25.239: >> >> ../src/vncconnection.c Failed to find certificate >> >> libvirt/private/clientkey.pem >> >> (remote-viewer:2721): gtk-vnc-DEBUG: 11:56:25.239: >> >> ../src/vncconnection.c Failed to find certificate >> >> libvirt/clientcert.pem >> >> (remote-viewer:2721): gtk-vnc-DEBUG: 11:56:25.239: >> >> ../src/vncconnection.c Waiting for missing credentials >> >> (remote-viewer:2721): gtk-vnc-DEBUG: 11:56:25.239: >> >> ../src/vncconnection.c Got all credentials >> >> (remote-viewer:2721): gtk-vnc-DEBUG: 11:56:25.239: >> >> ../src/vncconnection.c No CA certificate provided; trying the >> >system >> >> trust store instead >> >> (remote-viewer:2721): gtk-vnc-DEBUG: 11:56:25.240: >> >> ../src/vncconnection.c Using the system trust store and CRL >> >> (remote-viewer:2721): gtk-vnc-DEBUG: 11:56:25.240: >> >> ../src/vncconnection.c No client cert or key provided >> >> (remote-viewer:2721): gtk-vnc-DEBUG: 11:56:25.240: >> >> ../src/vncconnection.c No CA revocation list provided >> >> (remote-viewer:2721): gtk-vnc-DEBUG: 11:56:25.241: >> >> ../src/vncconnection.c Handshake was blocking >> >> (remote-viewer:2721): gtk-vnc-DEBUG: 11:56:25.243: >> >> ../src/vncconnection.c Handshake was blocking >> >> (remote-viewer:2721): gtk-vnc-DEBUG: 11:56:25.251: >> >> ../src/vncconnection.c Handshake was blocking >> >> (remote-viewer:2721): gtk-vnc-DEBUG: 11:56:25.298: >> >> ../src/vncconnection.c Handshake done >> >> (remote-viewer:2721): gtk-vnc-DEBUG: 11:56:25.298: >> >> ../src/vncconnection.c Validating >> >> (remote-viewer:2721): gtk-v
[ovirt-users] Re: vm console problem
tested on four different workstations with: fedora20, fedora31 and windows10(remote-manager last vers) вс, 29 мар. 2020 г. в 12:39, Strahil Nikolov : > On March 29, 2020 9:47:02 AM GMT+03:00, David David > wrote: > >I did as you said: > >copied from engine /etc/ovirt-engine/ca.pem onto my desktop into > >/etc/pki/ca-trust/source/anchors and then run update-ca-trust > >it didn’t help, still the same errors > > > > > >пт, 27 мар. 2020 г. в 21:56, Strahil Nikolov : > > > >> On March 27, 2020 12:23:10 PM GMT+02:00, David David > > > >> wrote: > >> >here is debug from opening console.vv by remote-viewer > >> > > >> >2020-03-27 14:09 GMT+04:00, Milan Zamazal : > >> >> David David writes: > >> >> > >> >>> yes i have > >> >>> console.vv attached > >> >> > >> >> It looks the same as mine. > >> >> > >> >> There is a difference in our logs, you have > >> >> > >> >> Possible auth 19 > >> >> > >> >> while I have > >> >> > >> >> Possible auth 2 > >> >> > >> >> So I still suspect a wrong authentication method is used, but I > >don't > >> >> have any idea why. > >> >> > >> >> Regards, > >> >> Milan > >> >> > >> >>> 2020-03-26 21:38 GMT+04:00, Milan Zamazal : > >> David David writes: > >> > >> > copied from qemu server all certs except "cacrl" to my > >> >desktop-station > >> > into /etc/pki/ > >> > >> This is not needed, the CA certificate is included in console.vv > >> >and no > >> other certificate should be needed. > >> > >> > but remote-viewer is still didn't work > >> > >> The log looks like remote-viewer is attempting certificate > >> authentication rather than password authentication. Do you have > >> password in console.vv? It should look like: > >> > >> [virt-viewer] > >> type=vnc > >> host=192.168.122.2 > >> port=5900 > >> password=fxLazJu6BUmL > >> # Password is valid for 120 seconds. > >> ... > >> > >> Regards, > >> Milan > >> > >> > 2020-03-26 2:22 GMT+04:00, Nir Soffer : > >> >> On Wed, Mar 25, 2020 at 12:45 PM David David > > > >> >> wrote: > >> >>> > >> >>> ovirt 4.3.8.2-1.el7 > >> >>> gtk-vnc2-1.0.0-1.fc31.x86_64 > >> >>> remote-viewer version 8.0-3.fc31 > >> >>> > >> >>> can't open vm console by remote-viewer > >> >>> vm has vnc console protocol > >> >>> when click on console button to connect to a vm, the > >> >remote-viewer > >> >>> console disappear immediately > >> >>> > >> >>> remote-viewer debug in attachment > >> >> > >> >> You an issue with the certificates: > >> >> > >> >> (remote-viewer:2721): gtk-vnc-DEBUG: 11:56:25.238: > >> >> ../src/vncconnection.c Set credential 2 libvirt > >> >> (remote-viewer:2721): gtk-vnc-DEBUG: 11:56:25.239: > >> >> ../src/vncconnection.c Searching for certs in /etc/pki > >> >> (remote-viewer:2721): gtk-vnc-DEBUG: 11:56:25.239: > >> >> ../src/vncconnection.c Searching for certs in /root/.pki > >> >> (remote-viewer:2721): gtk-vnc-DEBUG: 11:56:25.239: > >> >> ../src/vncconnection.c Failed to find certificate > >CA/cacert.pem > >> >> (remote-viewer:2721): gtk-vnc-DEBUG: 11:56:25.239: > >> >> ../src/vncconnection.c No CA certificate provided, using > >GNUTLS > >> >global > >> >> trust > >> >> (remote-viewer:2721): gtk-vnc-DEBUG: 11:56:25.239: > >> >> ../src/vncconnection.c Failed to find certificate CA/cacrl.pem > >> >> (remote-viewer:2721): gtk-vnc-DEBUG: 11:56:25.239: > >> >> ../src/vncconnection.c Failed to find certificate > >> >> libvirt/private/clientkey.pem > >> >> (remote-viewer:2721): gtk-vnc-DEBUG: 11:56:25.239: > >> >> ../src/vncconnection.c Failed to find certificate > >> >> libvirt/clientcert.pem > >> >> (remote-viewer:2721): gtk-vnc-DEBUG: 11:56:25.239: > >> >> ../src/vncconnection.c Waiting for missing credentials > >> >> (remote-viewer:2721): gtk-vnc-DEBUG: 11:56:25.239: > >> >> ../src/vncconnection.c Got all credentials > >> >> (remote-viewer:2721): gtk-vnc-DEBUG: 11:56:25.239: > >> >> ../src/vncconnection.c No CA certificate provided; trying the > >> >system > >> >> trust store instead > >> >> (remote-viewer:2721): gtk-vnc-DEBUG: 11:56:25.240: > >> >> ../src/vncconnection.c Using the system trust store and CRL > >> >> (remote-viewer:2721): gtk-vnc-DEBUG: 11:56:25.240: > >> >> ../src/vncconnection.c No client cert or key provided > >> >> (remote-viewer:2721): gtk-vnc-DEBUG: 11:56:25.240: > >> >> ../src/vncconnection.c No CA revocation list provided > >> >> (remote-viewer:2721): gtk-vnc-DEBUG: 11:56:25.241: > >> >> ../src/vncconnection.c Handshake was blocking > >> >> (remote-viewer:2721): gtk-vnc-DEBUG: 11:56:25.243: > >> >> ../src/vncconnection.c Handshake was blocking > >> >> (remote-viewer:2721): gtk-vnc-DEBUG: 11:56:25.251: > >> >> ../src/vncconnection.c Handshake was blocking > >> >> (r
[ovirt-users] Re: vm console problem
there is no such problem with the ovirt-engine 4.2.5.2-1.el7 it appeared when upgrading to 4.3.* вс, 29 мар. 2020 г. в 12:46, David David : > tested on four different workstations with: fedora20, fedora31 and > windows10(remote-manager last vers) > > вс, 29 мар. 2020 г. в 12:39, Strahil Nikolov : > >> On March 29, 2020 9:47:02 AM GMT+03:00, David David >> wrote: >> >I did as you said: >> >copied from engine /etc/ovirt-engine/ca.pem onto my desktop into >> >/etc/pki/ca-trust/source/anchors and then run update-ca-trust >> >it didn’t help, still the same errors >> > >> > >> >пт, 27 мар. 2020 г. в 21:56, Strahil Nikolov : >> > >> >> On March 27, 2020 12:23:10 PM GMT+02:00, David David >> > >> >> wrote: >> >> >here is debug from opening console.vv by remote-viewer >> >> > >> >> >2020-03-27 14:09 GMT+04:00, Milan Zamazal : >> >> >> David David writes: >> >> >> >> >> >>> yes i have >> >> >>> console.vv attached >> >> >> >> >> >> It looks the same as mine. >> >> >> >> >> >> There is a difference in our logs, you have >> >> >> >> >> >> Possible auth 19 >> >> >> >> >> >> while I have >> >> >> >> >> >> Possible auth 2 >> >> >> >> >> >> So I still suspect a wrong authentication method is used, but I >> >don't >> >> >> have any idea why. >> >> >> >> >> >> Regards, >> >> >> Milan >> >> >> >> >> >>> 2020-03-26 21:38 GMT+04:00, Milan Zamazal : >> >> David David writes: >> >> >> >> > copied from qemu server all certs except "cacrl" to my >> >> >desktop-station >> >> > into /etc/pki/ >> >> >> >> This is not needed, the CA certificate is included in console.vv >> >> >and no >> >> other certificate should be needed. >> >> >> >> > but remote-viewer is still didn't work >> >> >> >> The log looks like remote-viewer is attempting certificate >> >> authentication rather than password authentication. Do you have >> >> password in console.vv? It should look like: >> >> >> >> [virt-viewer] >> >> type=vnc >> >> host=192.168.122.2 >> >> port=5900 >> >> password=fxLazJu6BUmL >> >> # Password is valid for 120 seconds. >> >> ... >> >> >> >> Regards, >> >> Milan >> >> >> >> > 2020-03-26 2:22 GMT+04:00, Nir Soffer : >> >> >> On Wed, Mar 25, 2020 at 12:45 PM David David >> > >> >> >> wrote: >> >> >>> >> >> >>> ovirt 4.3.8.2-1.el7 >> >> >>> gtk-vnc2-1.0.0-1.fc31.x86_64 >> >> >>> remote-viewer version 8.0-3.fc31 >> >> >>> >> >> >>> can't open vm console by remote-viewer >> >> >>> vm has vnc console protocol >> >> >>> when click on console button to connect to a vm, the >> >> >remote-viewer >> >> >>> console disappear immediately >> >> >>> >> >> >>> remote-viewer debug in attachment >> >> >> >> >> >> You an issue with the certificates: >> >> >> >> >> >> (remote-viewer:2721): gtk-vnc-DEBUG: 11:56:25.238: >> >> >> ../src/vncconnection.c Set credential 2 libvirt >> >> >> (remote-viewer:2721): gtk-vnc-DEBUG: 11:56:25.239: >> >> >> ../src/vncconnection.c Searching for certs in /etc/pki >> >> >> (remote-viewer:2721): gtk-vnc-DEBUG: 11:56:25.239: >> >> >> ../src/vncconnection.c Searching for certs in /root/.pki >> >> >> (remote-viewer:2721): gtk-vnc-DEBUG: 11:56:25.239: >> >> >> ../src/vncconnection.c Failed to find certificate >> >CA/cacert.pem >> >> >> (remote-viewer:2721): gtk-vnc-DEBUG: 11:56:25.239: >> >> >> ../src/vncconnection.c No CA certificate provided, using >> >GNUTLS >> >> >global >> >> >> trust >> >> >> (remote-viewer:2721): gtk-vnc-DEBUG: 11:56:25.239: >> >> >> ../src/vncconnection.c Failed to find certificate CA/cacrl.pem >> >> >> (remote-viewer:2721): gtk-vnc-DEBUG: 11:56:25.239: >> >> >> ../src/vncconnection.c Failed to find certificate >> >> >> libvirt/private/clientkey.pem >> >> >> (remote-viewer:2721): gtk-vnc-DEBUG: 11:56:25.239: >> >> >> ../src/vncconnection.c Failed to find certificate >> >> >> libvirt/clientcert.pem >> >> >> (remote-viewer:2721): gtk-vnc-DEBUG: 11:56:25.239: >> >> >> ../src/vncconnection.c Waiting for missing credentials >> >> >> (remote-viewer:2721): gtk-vnc-DEBUG: 11:56:25.239: >> >> >> ../src/vncconnection.c Got all credentials >> >> >> (remote-viewer:2721): gtk-vnc-DEBUG: 11:56:25.239: >> >> >> ../src/vncconnection.c No CA certificate provided; trying the >> >> >system >> >> >> trust store instead >> >> >> (remote-viewer:2721): gtk-vnc-DEBUG: 11:56:25.240: >> >> >> ../src/vncconnection.c Using the system trust store and CRL >> >> >> (remote-viewer:2721): gtk-vnc-DEBUG: 11:56:25.240: >> >> >> ../src/vncconnection.c No client cert or key provided >> >> >> (remote-viewer:2721): gtk-vnc-DEBUG: 11:56:25.240: >> >> >> ../src/vncconnection.c No CA revocation list provided >> >> >> (remote-viewer:2721): gtk-vnc-DEBUG: 11:56:25.241: >> >> >> ../src/vncconnection.c Handsh
[ovirt-users] Re: vm console problem
can connect to a vm which has spice console protocol by remote-viewer but that not working with vnc protocol the remote-viewer can't validate the server certs, is this a bug on the remote-viewerside or in the hypervisor? this problem is generally known? will it be fixed? вс, 29 мар. 2020 г. в 12:52, David David : > there is no such problem with the ovirt-engine 4.2.5.2-1.el7 > it appeared when upgrading to 4.3.* > > вс, 29 мар. 2020 г. в 12:46, David David : > >> tested on four different workstations with: fedora20, fedora31 and >> windows10(remote-manager last vers) >> >> вс, 29 мар. 2020 г. в 12:39, Strahil Nikolov : >> >>> On March 29, 2020 9:47:02 AM GMT+03:00, David David >>> wrote: >>> >I did as you said: >>> >copied from engine /etc/ovirt-engine/ca.pem onto my desktop into >>> >/etc/pki/ca-trust/source/anchors and then run update-ca-trust >>> >it didn’t help, still the same errors >>> > >>> > >>> >пт, 27 мар. 2020 г. в 21:56, Strahil Nikolov : >>> > >>> >> On March 27, 2020 12:23:10 PM GMT+02:00, David David >>> > >>> >> wrote: >>> >> >here is debug from opening console.vv by remote-viewer >>> >> > >>> >> >2020-03-27 14:09 GMT+04:00, Milan Zamazal : >>> >> >> David David writes: >>> >> >> >>> >> >>> yes i have >>> >> >>> console.vv attached >>> >> >> >>> >> >> It looks the same as mine. >>> >> >> >>> >> >> There is a difference in our logs, you have >>> >> >> >>> >> >> Possible auth 19 >>> >> >> >>> >> >> while I have >>> >> >> >>> >> >> Possible auth 2 >>> >> >> >>> >> >> So I still suspect a wrong authentication method is used, but I >>> >don't >>> >> >> have any idea why. >>> >> >> >>> >> >> Regards, >>> >> >> Milan >>> >> >> >>> >> >>> 2020-03-26 21:38 GMT+04:00, Milan Zamazal : >>> >> David David writes: >>> >> >>> >> > copied from qemu server all certs except "cacrl" to my >>> >> >desktop-station >>> >> > into /etc/pki/ >>> >> >>> >> This is not needed, the CA certificate is included in console.vv >>> >> >and no >>> >> other certificate should be needed. >>> >> >>> >> > but remote-viewer is still didn't work >>> >> >>> >> The log looks like remote-viewer is attempting certificate >>> >> authentication rather than password authentication. Do you have >>> >> password in console.vv? It should look like: >>> >> >>> >> [virt-viewer] >>> >> type=vnc >>> >> host=192.168.122.2 >>> >> port=5900 >>> >> password=fxLazJu6BUmL >>> >> # Password is valid for 120 seconds. >>> >> ... >>> >> >>> >> Regards, >>> >> Milan >>> >> >>> >> > 2020-03-26 2:22 GMT+04:00, Nir Soffer : >>> >> >> On Wed, Mar 25, 2020 at 12:45 PM David David >>> > >>> >> >> wrote: >>> >> >>> >>> >> >>> ovirt 4.3.8.2-1.el7 >>> >> >>> gtk-vnc2-1.0.0-1.fc31.x86_64 >>> >> >>> remote-viewer version 8.0-3.fc31 >>> >> >>> >>> >> >>> can't open vm console by remote-viewer >>> >> >>> vm has vnc console protocol >>> >> >>> when click on console button to connect to a vm, the >>> >> >remote-viewer >>> >> >>> console disappear immediately >>> >> >>> >>> >> >>> remote-viewer debug in attachment >>> >> >> >>> >> >> You an issue with the certificates: >>> >> >> >>> >> >> (remote-viewer:2721): gtk-vnc-DEBUG: 11:56:25.238: >>> >> >> ../src/vncconnection.c Set credential 2 libvirt >>> >> >> (remote-viewer:2721): gtk-vnc-DEBUG: 11:56:25.239: >>> >> >> ../src/vncconnection.c Searching for certs in /etc/pki >>> >> >> (remote-viewer:2721): gtk-vnc-DEBUG: 11:56:25.239: >>> >> >> ../src/vncconnection.c Searching for certs in /root/.pki >>> >> >> (remote-viewer:2721): gtk-vnc-DEBUG: 11:56:25.239: >>> >> >> ../src/vncconnection.c Failed to find certificate >>> >CA/cacert.pem >>> >> >> (remote-viewer:2721): gtk-vnc-DEBUG: 11:56:25.239: >>> >> >> ../src/vncconnection.c No CA certificate provided, using >>> >GNUTLS >>> >> >global >>> >> >> trust >>> >> >> (remote-viewer:2721): gtk-vnc-DEBUG: 11:56:25.239: >>> >> >> ../src/vncconnection.c Failed to find certificate CA/cacrl.pem >>> >> >> (remote-viewer:2721): gtk-vnc-DEBUG: 11:56:25.239: >>> >> >> ../src/vncconnection.c Failed to find certificate >>> >> >> libvirt/private/clientkey.pem >>> >> >> (remote-viewer:2721): gtk-vnc-DEBUG: 11:56:25.239: >>> >> >> ../src/vncconnection.c Failed to find certificate >>> >> >> libvirt/clientcert.pem >>> >> >> (remote-viewer:2721): gtk-vnc-DEBUG: 11:56:25.239: >>> >> >> ../src/vncconnection.c Waiting for missing credentials >>> >> >> (remote-viewer:2721): gtk-vnc-DEBUG: 11:56:25.239: >>> >> >> ../src/vncconnection.c Got all credentials >>> >> >> (remote-viewer:2721): gtk-vnc-DEBUG: 11:56:25.239: >>> >> >> ../src/vncconnection.c No CA certificate provided; trying the >>> >> >system >>> >> >> trust store instead >>> >> >> (remote-viewer:2721): gtk-vnc-DEBUG: 11:56:25.
[ovirt-users] Re: vm console problem
David David writes: > can connect to a vm which has spice console protocol by remote-viewer but > that not working with vnc protocol > the remote-viewer can't validate the server certs, is this a bug on the > remote-viewerside or in the hypervisor? > this problem is generally known? will it be fixed? It works for me, so it's either a problem with your remote-viewer or an unknown problem on the oVirt side. I'd suggest paying attention to the authentication method negotiation as pointed out earlier. I'm not expert in that area, so I can't help you with that but maybe someone else can. Regards, Milan > вс, 29 мар. 2020 г. в 12:52, David David : > >> there is no such problem with the ovirt-engine 4.2.5.2-1.el7 >> it appeared when upgrading to 4.3.* >> >> вс, 29 мар. 2020 г. в 12:46, David David : >> >>> tested on four different workstations with: fedora20, fedora31 and >>> windows10(remote-manager last vers) >>> >>> вс, 29 мар. 2020 г. в 12:39, Strahil Nikolov : >>> On March 29, 2020 9:47:02 AM GMT+03:00, David David wrote: >I did as you said: >copied from engine /etc/ovirt-engine/ca.pem onto my desktop into >/etc/pki/ca-trust/source/anchors and then run update-ca-trust >it didn’t help, still the same errors > > >пт, 27 мар. 2020 г. в 21:56, Strahil Nikolov : > >> On March 27, 2020 12:23:10 PM GMT+02:00, David David > >> wrote: >> >here is debug from opening console.vv by remote-viewer >> > >> >2020-03-27 14:09 GMT+04:00, Milan Zamazal : >> >> David David writes: >> >> >> >>> yes i have >> >>> console.vv attached >> >> >> >> It looks the same as mine. >> >> >> >> There is a difference in our logs, you have >> >> >> >> Possible auth 19 >> >> >> >> while I have >> >> >> >> Possible auth 2 >> >> >> >> So I still suspect a wrong authentication method is used, but I >don't >> >> have any idea why. >> >> >> >> Regards, >> >> Milan >> >> >> >>> 2020-03-26 21:38 GMT+04:00, Milan Zamazal : >> David David writes: >> >> > copied from qemu server all certs except "cacrl" to my >> >desktop-station >> > into /etc/pki/ >> >> This is not needed, the CA certificate is included in console.vv >> >and no >> other certificate should be needed. >> >> > but remote-viewer is still didn't work >> >> The log looks like remote-viewer is attempting certificate >> authentication rather than password authentication. Do you have >> password in console.vv? It should look like: >> >> [virt-viewer] >> type=vnc >> host=192.168.122.2 >> port=5900 >> password=fxLazJu6BUmL >> # Password is valid for 120 seconds. >> ... >> >> Regards, >> Milan >> >> > 2020-03-26 2:22 GMT+04:00, Nir Soffer : >> >> On Wed, Mar 25, 2020 at 12:45 PM David David > >> >> wrote: >> >>> >> >>> ovirt 4.3.8.2-1.el7 >> >>> gtk-vnc2-1.0.0-1.fc31.x86_64 >> >>> remote-viewer version 8.0-3.fc31 >> >>> >> >>> can't open vm console by remote-viewer >> >>> vm has vnc console protocol >> >>> when click on console button to connect to a vm, the >> >remote-viewer >> >>> console disappear immediately >> >>> >> >>> remote-viewer debug in attachment >> >> >> >> You an issue with the certificates: >> >> >> >> (remote-viewer:2721): gtk-vnc-DEBUG: 11:56:25.238: >> >> ../src/vncconnection.c Set credential 2 libvirt >> >> (remote-viewer:2721): gtk-vnc-DEBUG: 11:56:25.239: >> >> ../src/vncconnection.c Searching for certs in /etc/pki >> >> (remote-viewer:2721): gtk-vnc-DEBUG: 11:56:25.239: >> >> ../src/vncconnection.c Searching for certs in /root/.pki >> >> (remote-viewer:2721): gtk-vnc-DEBUG: 11:56:25.239: >> >> ../src/vncconnection.c Failed to find certificate >CA/cacert.pem >> >> (remote-viewer:2721): gtk-vnc-DEBUG: 11:56:25.239: >> >> ../src/vncconnection.c No CA certificate provided, using >GNUTLS >> >global >> >> trust >> >> (remote-viewer:2721): gtk-vnc-DEBUG: 11:56:25.239: >> >> ../src/vncconnection.c Failed to find certificate CA/cacrl.pem >> >> (remote-viewer:2721): gtk-vnc-DEBUG: 11:56:25.239: >> >> ../src/vncconnection.c Failed to find certificate >> >> libvirt/private/clientkey.pem >> >> (remote-viewer:2721): gtk-vnc-DEBUG: 11:56:25.239: >> >> ../src/vncconnection.c Failed to find certificate >> >> libvirt/clientcert.pem >> >> (remote-viewer:2721): gtk-vnc-DE
[ovirt-users] Re: vm console problem
solved using this link https://bugzilla.redhat.com/show_bug.cgi?id=1672587 чт, 2 апр. 2020 г. в 16:11, Milan Zamazal : > David David writes: > > > can connect to a vm which has spice console protocol by remote-viewer but > > that not working with vnc protocol > > the remote-viewer can't validate the server certs, is this a bug on the > > remote-viewerside or in the hypervisor? > > this problem is generally known? will it be fixed? > > It works for me, so it's either a problem with your remote-viewer or an > unknown problem on the oVirt side. I'd suggest paying attention to the > authentication method negotiation as pointed out earlier. I'm not > expert in that area, so I can't help you with that but maybe someone > else can. > > Regards, > Milan > > > вс, 29 мар. 2020 г. в 12:52, David David : > > > >> there is no such problem with the ovirt-engine 4.2.5.2-1.el7 > >> it appeared when upgrading to 4.3.* > >> > >> вс, 29 мар. 2020 г. в 12:46, David David : > >> > >>> tested on four different workstations with: fedora20, fedora31 and > >>> windows10(remote-manager last vers) > >>> > >>> вс, 29 мар. 2020 г. в 12:39, Strahil Nikolov : > >>> > On March 29, 2020 9:47:02 AM GMT+03:00, David David < > dd432...@gmail.com> > wrote: > >I did as you said: > >copied from engine /etc/ovirt-engine/ca.pem onto my desktop into > >/etc/pki/ca-trust/source/anchors and then run update-ca-trust > >it didn’t help, still the same errors > > > > > >пт, 27 мар. 2020 г. в 21:56, Strahil Nikolov >: > > > >> On March 27, 2020 12:23:10 PM GMT+02:00, David David > > > >> wrote: > >> >here is debug from opening console.vv by remote-viewer > >> > > >> >2020-03-27 14:09 GMT+04:00, Milan Zamazal : > >> >> David David writes: > >> >> > >> >>> yes i have > >> >>> console.vv attached > >> >> > >> >> It looks the same as mine. > >> >> > >> >> There is a difference in our logs, you have > >> >> > >> >> Possible auth 19 > >> >> > >> >> while I have > >> >> > >> >> Possible auth 2 > >> >> > >> >> So I still suspect a wrong authentication method is used, but I > >don't > >> >> have any idea why. > >> >> > >> >> Regards, > >> >> Milan > >> >> > >> >>> 2020-03-26 21:38 GMT+04:00, Milan Zamazal >: > >> David David writes: > >> > >> > copied from qemu server all certs except "cacrl" to my > >> >desktop-station > >> > into /etc/pki/ > >> > >> This is not needed, the CA certificate is included in > console.vv > >> >and no > >> other certificate should be needed. > >> > >> > but remote-viewer is still didn't work > >> > >> The log looks like remote-viewer is attempting certificate > >> authentication rather than password authentication. Do you > have > >> password in console.vv? It should look like: > >> > >> [virt-viewer] > >> type=vnc > >> host=192.168.122.2 > >> port=5900 > >> password=fxLazJu6BUmL > >> # Password is valid for 120 seconds. > >> ... > >> > >> Regards, > >> Milan > >> > >> > 2020-03-26 2:22 GMT+04:00, Nir Soffer : > >> >> On Wed, Mar 25, 2020 at 12:45 PM David David > > > >> >> wrote: > >> >>> > >> >>> ovirt 4.3.8.2-1.el7 > >> >>> gtk-vnc2-1.0.0-1.fc31.x86_64 > >> >>> remote-viewer version 8.0-3.fc31 > >> >>> > >> >>> can't open vm console by remote-viewer > >> >>> vm has vnc console protocol > >> >>> when click on console button to connect to a vm, the > >> >remote-viewer > >> >>> console disappear immediately > >> >>> > >> >>> remote-viewer debug in attachment > >> >> > >> >> You an issue with the certificates: > >> >> > >> >> (remote-viewer:2721): gtk-vnc-DEBUG: 11:56:25.238: > >> >> ../src/vncconnection.c Set credential 2 libvirt > >> >> (remote-viewer:2721): gtk-vnc-DEBUG: 11:56:25.239: > >> >> ../src/vncconnection.c Searching for certs in /etc/pki > >> >> (remote-viewer:2721): gtk-vnc-DEBUG: 11:56:25.239: > >> >> ../src/vncconnection.c Searching for certs in /root/.pki > >> >> (remote-viewer:2721): gtk-vnc-DEBUG: 11:56:25.239: > >> >> ../src/vncconnection.c Failed to find certificate > >CA/cacert.pem > >> >> (remote-viewer:2721): gtk-vnc-DEBUG: 11:56:25.239: > >> >> ../src/vncconnection.c No CA certificate provided, using > >GNUTLS > >> >global > >> >> trust > >> >> (remote-viewer:2721): gtk-vnc-DEBUG: 11:56:25.239: > >> >> ../src/vncconnection.c Failed to find certific
[ovirt-users] Re: vm console problem
David David writes: > solved using this link https://bugzilla.redhat.com/show_bug.cgi?id=1672587 Great, good to know. > чт, 2 апр. 2020 г. в 16:11, Milan Zamazal : > >> David David writes: >> >> > can connect to a vm which has spice console protocol by remote-viewer but >> > that not working with vnc protocol >> > the remote-viewer can't validate the server certs, is this a bug on the >> > remote-viewerside or in the hypervisor? >> > this problem is generally known? will it be fixed? >> >> It works for me, so it's either a problem with your remote-viewer or an >> unknown problem on the oVirt side. I'd suggest paying attention to the >> authentication method negotiation as pointed out earlier. I'm not >> expert in that area, so I can't help you with that but maybe someone >> else can. >> >> Regards, >> Milan >> >> > вс, 29 мар. 2020 г. в 12:52, David David : >> > >> >> there is no such problem with the ovirt-engine 4.2.5.2-1.el7 >> >> it appeared when upgrading to 4.3.* >> >> >> >> вс, 29 мар. 2020 г. в 12:46, David David : >> >> >> >>> tested on four different workstations with: fedora20, fedora31 and >> >>> windows10(remote-manager last vers) >> >>> >> >>> вс, 29 мар. 2020 г. в 12:39, Strahil Nikolov : >> >>> >> On March 29, 2020 9:47:02 AM GMT+03:00, David David < >> dd432...@gmail.com> >> wrote: >> >I did as you said: >> >copied from engine /etc/ovirt-engine/ca.pem onto my desktop into >> >/etc/pki/ca-trust/source/anchors and then run update-ca-trust >> >it didn’t help, still the same errors >> > >> > >> >пт, 27 мар. 2020 г. в 21:56, Strahil Nikolov > >: >> > >> >> On March 27, 2020 12:23:10 PM GMT+02:00, David David >> > >> >> wrote: >> >> >here is debug from opening console.vv by remote-viewer >> >> > >> >> >2020-03-27 14:09 GMT+04:00, Milan Zamazal : >> >> >> David David writes: >> >> >> >> >> >>> yes i have >> >> >>> console.vv attached >> >> >> >> >> >> It looks the same as mine. >> >> >> >> >> >> There is a difference in our logs, you have >> >> >> >> >> >> Possible auth 19 >> >> >> >> >> >> while I have >> >> >> >> >> >> Possible auth 2 >> >> >> >> >> >> So I still suspect a wrong authentication method is used, but I >> >don't >> >> >> have any idea why. >> >> >> >> >> >> Regards, >> >> >> Milan >> >> >> >> >> >>> 2020-03-26 21:38 GMT+04:00, Milan Zamazal > >: >> >> David David writes: >> >> >> >> > copied from qemu server all certs except "cacrl" to my >> >> >desktop-station >> >> > into /etc/pki/ >> >> >> >> This is not needed, the CA certificate is included in >> console.vv >> >> >and no >> >> other certificate should be needed. >> >> >> >> > but remote-viewer is still didn't work >> >> >> >> The log looks like remote-viewer is attempting certificate >> >> authentication rather than password authentication. Do you >> have >> >> password in console.vv? It should look like: >> >> >> >> [virt-viewer] >> >> type=vnc >> >> host=192.168.122.2 >> >> port=5900 >> >> password=fxLazJu6BUmL >> >> # Password is valid for 120 seconds. >> >> ... >> >> >> >> Regards, >> >> Milan >> >> >> >> > 2020-03-26 2:22 GMT+04:00, Nir Soffer : >> >> >> On Wed, Mar 25, 2020 at 12:45 PM David David >> > >> >> >> wrote: >> >> >>> >> >> >>> ovirt 4.3.8.2-1.el7 >> >> >>> gtk-vnc2-1.0.0-1.fc31.x86_64 >> >> >>> remote-viewer version 8.0-3.fc31 >> >> >>> >> >> >>> can't open vm console by remote-viewer >> >> >>> vm has vnc console protocol >> >> >>> when click on console button to connect to a vm, the >> >> >remote-viewer >> >> >>> console disappear immediately >> >> >>> >> >> >>> remote-viewer debug in attachment >> >> >> >> >> >> You an issue with the certificates: >> >> >> >> >> >> (remote-viewer:2721): gtk-vnc-DEBUG: 11:56:25.238: >> >> >> ../src/vncconnection.c Set credential 2 libvirt >> >> >> (remote-viewer:2721): gtk-vnc-DEBUG: 11:56:25.239: >> >> >> ../src/vncconnection.c Searching for certs in /etc/pki >> >> >> (remote-viewer:2721): gtk-vnc-DEBUG: 11:56:25.239: >> >> >> ../src/vncconnection.c Searching for certs in /root/.pki >> >> >> (remote-viewer:2721): gtk-vnc-DEBUG: 11:56:25.239: >> >> >> ../src/vncconnection.c Failed to find certificate >> >CA/cacert.pem >> >> >> (remote-viewer:2721): gtk-vnc-DEBUG: 11:56:25.239: >> >> >> ../src/vncconnection.c No CA certificate provided, using >>
[ovirt-users] Re: vm console problem
On Mon, Apr 20, 2020 at 9:49 AM David David wrote: > solved using this link https://bugzilla.redhat.com/show_bug.cgi?id=1672587 > > Does this mean that you are still using 4.3.0 or that the fix in 4.3.1 was not applied into your environment? Gianluca ___ 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/4G33I2T5T3ZZRJANMB2RIPN77FICHOEV/
[ovirt-users] Re: vm console problem
I have version 4.3.8 пн, 20 апр. 2020 г. в 12:46, Gianluca Cecchi : > On Mon, Apr 20, 2020 at 9:49 AM David David wrote: > >> solved using this link >> https://bugzilla.redhat.com/show_bug.cgi?id=1672587 >> >> > Does this mean that you are still using 4.3.0 or that the fix in 4.3.1 was > not applied into your environment? > > Gianluca > ___ 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/YWBU5WBNPYHMCTQUK6ROMGQJLW6PVIIN/
