Unable to connect to the graphic server
This is a multi-part message in MIME format. --b1_576a8a5bb40fefc5c569d4cd3c0b589a Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: base64 SSd2ZSBidWlsdCBhbmQgcmVidWlsdCBhYm91dCA0IG9WaXJ0IHNlcnZlcnMuICBDb25zaWRlciBt eXNlbGYgcHJldHR5IGdvb2QgYXQgdGhpcy4gIExPTC4KU28gSSBhbSBzZXR0aW5nIHVwIGEgb1Zp cnQgc2VydmVyIGZvciBhIGZyaWVuZCBvbiBoaXMgcjcxMC4gIENlbnRPUyA3LCBvdmlydCA0LjIu ICAgL2V0Yy9ob3N0cyBoYXMgdGhlIGNvcnJlY3QgSVAgYW5kIEZRRE4gc2V0dXAuCgpXaGVuIEkg YnVpbGQgYSBWTSBhbmQgdHJ5IHRvIG9wZW4gYSBjb25zb2xlIHNlc3Npb24gdmlhICBTUElDRSBJ IGFtIHVuYWJsZSB0byBjb25uZWN0IHRvIHRoZSBncmFwaGljIHNlcnZlci4gIEknbSBjb25uZWN0 aW5nIGZyb20gYSBXaW5kb3dzIDEwIGJveC4gICBVc2luZyB2aXJ0LW1hbmFnZXIgdG8gY29ubmVj dC4KCkkndmUgZ29vZ2xlZCBhbmQgSSBqdXN0IGNhbnQgc2VlbSB0byBmaW5kIGFueSByZXNvbHV0 aW9uIHRvIHRoaXMuICBOb3csIEkgZGlkIGJ1aWxkIHRoZSBzZXJ2ZXIgb24gbXkgaG9tZSBuZXR3 b3JrIGJ1dCB0aGUgc3VibmV0IGl0cyBvbiBpcyB0aGUgc2FtZS4uIGludGVybmFsIDE5Mi4xNjgu MS54eHguICAgVGhlIHdlYiBpbnRlcmZhY2UgaXMgYWNjZXNzaWJsZSBhbHNvLgoKQW55IGhpbnRz IGFzIHRvIHdoYXQgZWxzZSBJIGNhbiBjaGVjaz8KClRoYW5rcyEKClNlbnQgd2l0aCBbUHJvdG9u TWFpbF0oaHR0cHM6Ly9wcm90b25tYWlsLmNvbSkgU2VjdXJlIEVtYWlsLg== --b1_576a8a5bb40fefc5c569d4cd3c0b589a Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: base64 PGRpdj5JJ3ZlIGJ1aWx0IGFuZCByZWJ1aWx0IGFib3V0IDQgb1ZpcnQgc2VydmVycy4mbmJzcDsg Q29uc2lkZXIgbXlzZWxmIHByZXR0eSBnb29kIGF0IHRoaXMuJm5ic3A7IExPTC48YnI+PC9kaXY+ PGRpdj5TbyBJIGFtIHNldHRpbmcgdXAgYSBvVmlydCBzZXJ2ZXIgZm9yIGEgZnJpZW5kIG9uIGhp cyByNzEwLiZuYnNwOyBDZW50T1MgNywgb3ZpcnQgNC4yLiZuYnNwOyZuYnNwOyAvZXRjL2hvc3Rz IGhhcyB0aGUgY29ycmVjdCBJUCBhbmQgRlFETiBzZXR1cC48YnI+PC9kaXY+PGRpdj48YnI+PC9k aXY+PGRpdj5XaGVuIEkgYnVpbGQgYSBWTSBhbmQgdHJ5IHRvIG9wZW4gYSBjb25zb2xlIHNlc3Np b24gdmlhJm5ic3A7IFNQSUNFIEkgYW0gdW5hYmxlIHRvIGNvbm5lY3QgdG8gdGhlIGdyYXBoaWMg c2VydmVyLiZuYnNwOyBJJ20gY29ubmVjdGluZyBmcm9tIGEgV2luZG93cyAxMCBib3guJm5ic3A7 Jm5ic3A7IFVzaW5nIHZpcnQtbWFuYWdlciB0byBjb25uZWN0Ljxicj48L2Rpdj48ZGl2Pjxicj48 L2Rpdj48ZGl2PkkndmUgZ29vZ2xlZCBhbmQgSSBqdXN0IGNhbnQgc2VlbSB0byBmaW5kIGFueSBy ZXNvbHV0aW9uIHRvIHRoaXMuJm5ic3A7IE5vdywgSSBkaWQgYnVpbGQgdGhlIHNlcnZlciBvbiBt eSBob21lIG5ldHdvcmsgYnV0IHRoZSBzdWJuZXQgaXRzIG9uIGlzIHRoZSBzYW1lLi4gaW50ZXJu YWwgMTkyLjE2OC4xLnh4eC4mbmJzcDsmbmJzcDsgVGhlIHdlYiBpbnRlcmZhY2UgaXMgYWNjZXNz aWJsZSBhbHNvLjxicj48L2Rpdj48ZGl2Pjxicj48L2Rpdj48ZGl2PkFueSBoaW50cyBhcyB0byB3 aGF0IGVsc2UgSSBjYW4gY2hlY2s/PGJyPjwvZGl2PjxkaXY+PGJyPjwvZGl2PjxkaXY+VGhhbmtz ITxicj48L2Rpdj48ZGl2Pjxicj48L2Rpdj48ZGl2IGNsYXNzPSJwcm90b25tYWlsX3NpZ25hdHVy ZV9ibG9jayI+PGRpdiBjbGFzcz0icHJvdG9ubWFpbF9zaWduYXR1cmVfYmxvY2stdXNlciBwcm90 b25tYWlsX3NpZ25hdHVyZV9ibG9jay1lbXB0eSI+PGJyPjwvZGl2PjxkaXYgY2xhc3M9InByb3Rv bm1haWxfc2lnbmF0dXJlX2Jsb2NrLXByb3RvbiI+U2VudCB3aXRoIDxhIGhyZWY9Imh0dHBzOi8v cHJvdG9ubWFpbC5jb20iPlByb3Rvbk1haWw8L2E+IFNlY3VyZSBFbWFpbC48YnI+PC9kaXY+PC9k aXY+PGRpdj48YnI+PC9kaXY+ --b1_576a8a5bb40fefc5c569d4cd3c0b589a--
On Wed, Feb 14, 2018 at 5:20 AM, Alex Bartonek <Alex@unix1337.com> wrote:
I've built and rebuilt about 4 oVirt servers. Consider myself pretty good at this. LOL. So I am setting up a oVirt server for a friend on his r710. CentOS 7, ovirt 4.2. /etc/hosts has the correct IP and FQDN setup.
When I build a VM and try to open a console session via SPICE I am unable to connect to the graphic server. I'm connecting from a Windows 10 box. Using virt-manager to connect.
What happens when you try?
I've googled and I just cant seem to find any resolution to this. Now, I did build the server on my home network but the subnet its on is the same.. internal 192.168.1.xxx. The web interface is accessible also.
Any hints as to what else I can check?
If virt-viewer does open up but fails to connect, check (e.g. with netstat) where it tries to connect to. Check that you have network access there (no filtering/routing/NAT/etc issues), that qemu on the host is listening on the port it tries etc. If it does not open, try to tell your browser (if it does not already) to not open it automatically, but ask you what to do. Then save the file you get and check it. Best regards,
Thanks!
Sent with ProtonMail Secure Email.
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
-- Didi
-------- Original Message -------- On February 14, 2018 2:23 AM, Yedidyah Bar David <didi@redhat.com> wrote:
On Wed, Feb 14, 2018 at 5:20 AM, Alex Bartonek Alex@unix1337.com wrote:
I've built and rebuilt about 4 oVirt servers. Consider myself pretty good at this. LOL. So I am setting up a oVirt server for a friend on his r710. CentOS 7, ovirt 4.2. /etc/hosts has the correct IP and FQDN setup. When I build a VM and try to open a console session via SPICE I am unable to connect to the graphic server. I'm connecting from a Windows 10 box. Using virt-manager to connect.
What happens when you try?
Unable to connect to the graphic console is what the error says. Here is the .vv file other than the cert stuff in it: [virt-viewer] type=spice host=192.168.1.83 port=-1 password=<removed> # Password is valid for 120 seconds. delete-this-file=1 fullscreen=0 title=Win_7_32bit:%d toggle-fullscreen=shift+f11 release-cursor=shift+f12 tls-port=5900 enable-smartcard=0 enable-usb-autoshare=1 usb-filter=-1,-1,-1,-1,0 tls-ciphers=DEFAULT host-subject=O=williams.com,CN=randb.williams.com Port 5900 is listening by IP on the server, so that looks correct. I shut the firewall off just in case it was the issue..no go.
On Wed, Feb 14, 2018 at 9:20 PM, Alex Bartonek <Alex@unix1337.com> wrote:
-------- Original Message -------- On February 14, 2018 2:23 AM, Yedidyah Bar David <didi@redhat.com> wrote:
On Wed, Feb 14, 2018 at 5:20 AM, Alex Bartonek Alex@unix1337.com wrote:
I've built and rebuilt about 4 oVirt servers. Consider myself pretty good at this. LOL. So I am setting up a oVirt server for a friend on his r710. CentOS 7, ovirt 4.2. /etc/hosts has the correct IP and FQDN setup. When I build a VM and try to open a console session via SPICE I am unable to connect to the graphic server. I'm connecting from a Windows 10 box. Using virt-manager to connect.
What happens when you try?
Unable to connect to the graphic console is what the error says. Here is the .vv file other than the cert stuff in it:
[virt-viewer] type=spice host=192.168.1.83 port=-1 password=<removed> # Password is valid for 120 seconds. delete-this-file=1 fullscreen=0 title=Win_7_32bit:%d toggle-fullscreen=shift+f11 release-cursor=shift+f12 tls-port=5900 enable-smartcard=0 enable-usb-autoshare=1 usb-filter=-1,-1,-1,-1,0 tls-ciphers=DEFAULT host-subject=O=williams.com,CN=randb.williams.com
Port 5900 is listening by IP on the server, so that looks correct. I shut the firewall off just in case it was the issue..no go.
Did you verify that you can connect there manually (e.g. with telnet)? Can you run a sniffer on both sides to make sure traffic passes correctly? Can you check vdsm/libvirt logs on the host side? Thanks, -- Didi
-------- Original Message -------- On February 15, 2018 12:52 AM, Yedidyah Bar David <didi@redhat.com> wrote:
On Wed, Feb 14, 2018 at 9:20 PM, Alex Bartonek Alex@unix1337.com wrote:
On Wed, Feb 14, 2018 at 5:20 AM, Alex Bartonek Alex@unix1337.com wrote:
I've built and rebuilt about 4 oVirt servers. Consider myself pretty good at this. LOL. So I am setting up a oVirt server for a friend on his r710. CentOS 7, ovirt 4.2. /etc/hosts has the correct IP and FQDN setup. When I build a VM and try to open a console session via SPICE I am unable to connect to the graphic server. I'm connecting from a Windows 10 box. Using virt-manager to connect. What happens when you try? Unable to connect to the graphic console is what the error says. Here is the .vv file other than the cert stuff in it: [virt-viewer] type=spice host=192.168.1.83
-------- Original Message -------- On February 14, 2018 2:23 AM, Yedidyah Bar David didi@redhat.com wrote: port=-1 password=<removed> Password is valid for 120 seconds.
delete-this-file=1 fullscreen=0 title=Win_7_32bit:%d toggle-fullscreen=shift+f11 release-cursor=shift+f12 tls-port=5900 enable-smartcard=0 enable-usb-autoshare=1 usb-filter=-1,-1,-1,-1,0 tls-ciphers=DEFAULT host-subject=O=williams.com,CN=randb.williams.com Port 5900 is listening by IP on the server, so that looks correct. I shut the firewall off just in case it was the issue..no go.
Did you verify that you can connect there manually (e.g. with telnet)? Can you run a sniffer on both sides to make sure traffic passes correctly? Can you check vdsm/libvirt logs on the host side?
Ok.. I must have tanked it on install with the firewall. The firewall is blocking port 5900. This is on CentOS 7. If I flush the rules, it works.
On Fri, Feb 16, 2018 at 5:50 AM, Alex Bartonek <Alex@unix1337.com> wrote:
-------- Original Message -------- On February 15, 2018 12:52 AM, Yedidyah Bar David <didi@redhat.com> wrote:
On Wed, Feb 14, 2018 at 9:20 PM, Alex Bartonek Alex@unix1337.com wrote:
On Wed, Feb 14, 2018 at 5:20 AM, Alex Bartonek Alex@unix1337.com wrote:
I've built and rebuilt about 4 oVirt servers. Consider myself pretty good at this. LOL. So I am setting up a oVirt server for a friend on his r710. CentOS 7, ovirt 4.2. /etc/hosts has the correct IP and FQDN setup. When I build a VM and try to open a console session via SPICE I am unable to connect to the graphic server. I'm connecting from a Windows 10 box. Using virt-manager to connect. What happens when you try? Unable to connect to the graphic console is what the error says. Here is the .vv file other than the cert stuff in it: [virt-viewer] type=spice host=192.168.1.83
-------- Original Message -------- On February 14, 2018 2:23 AM, Yedidyah Bar David didi@redhat.com wrote: port=-1 password=<removed> Password is valid for 120 seconds.
delete-this-file=1 fullscreen=0 title=Win_7_32bit:%d toggle-fullscreen=shift+f11 release-cursor=shift+f12 tls-port=5900 enable-smartcard=0 enable-usb-autoshare=1 usb-filter=-1,-1,-1,-1,0 tls-ciphers=DEFAULT host-subject=O=williams.com,CN=randb.williams.com Port 5900 is listening by IP on the server, so that looks correct. I shut the firewall off just in case it was the issue..no go.
Did you verify that you can connect there manually (e.g. with telnet)? Can you run a sniffer on both sides to make sure traffic passes correctly? Can you check vdsm/libvirt logs on the host side?
Ok.. I must have tanked it on install with the firewall. The firewall is blocking port 5900. This is on CentOS 7. If I flush the rules, it works.
Thanks for the report. Did you choose to have firewall configured automatically, or did you configure it yourself? Best regards, -- Didi
-------- Original Message -------- On February 18, 2018 12:32 AM, Yedidyah Bar David <didi@redhat.com> wrote:
On Fri, Feb 16, 2018 at 5:50 AM, Alex Bartonek Alex@unix1337.com wrote:
-------- Original Message -------- On February 15, 2018 12:52 AM, Yedidyah Bar David didi@redhat.com wrote:
On Wed, Feb 14, 2018 at 9:20 PM, Alex Bartonek Alex@unix1337.com wrote:
On Wed, Feb 14, 2018 at 5:20 AM, Alex Bartonek Alex@unix1337.com wrote:
I've built and rebuilt about 4 oVirt servers. Consider myself pretty good at this. LOL. So I am setting up a oVirt server for a friend on his r710. CentOS 7, ovirt 4.2. /etc/hosts has the correct IP and FQDN setup. When I build a VM and try to open a console session via SPICE I am unable to connect to the graphic server. I'm connecting from a Windows 10 box. Using virt-manager to connect. What happens when you try? Unable to connect to the graphic console is what the error says. Here is the .vv file other than the cert stuff in it: [virt-viewer] type=spice host=192.168.1.83 port=-1 password=<removed> Password is valid for 120 seconds.
delete-this-file=1 fullscreen=0
-------- Original Message -------- On February 14, 2018 2:23 AM, Yedidyah Bar David didi@redhat.com wrote: title=Win_7_32bit:%d toggle-fullscreen=shift+f11 release-cursor=shift+f12 tls-port=5900 enable-smartcard=0 enable-usb-autoshare=1 usb-filter=-1,-1,-1,-1,0 tls-ciphers=DEFAULT host-subject=O=williams.com,CN=randb.williams.com Port 5900 is listening by IP on the server, so that looks correct. I shut the firewall off just in case it was the issue..no go. Did you verify that you can connect there manually (e.g. with telnet)? Can you run a sniffer on both sides to make sure traffic passes correctly? Can you check vdsm/libvirt logs on the host side? Ok.. I must have tanked it on install with the firewall. The firewall is blocking port 5900. This is on CentOS 7. If I flush the rules, it works.
Thanks for the report.
Did you choose to have firewall configured automatically, or did you configure it yourself?
I did configure the host to manage the firewall. Just to make sure, I deleted the host, recreated and still had the issue. I ended up making the firewall rule manually which took care of it. Never had to do that before. -Alex
On Mon, Feb 19, 2018 at 12:46 AM, Alex Bartonek <Alex@unix1337.com> wrote:
-------- Original Message -------- On February 18, 2018 12:32 AM, Yedidyah Bar David <didi@redhat.com> wrote:
On Fri, Feb 16, 2018 at 5:50 AM, Alex Bartonek Alex@unix1337.com wrote:
-------- Original Message -------- On February 15, 2018 12:52 AM, Yedidyah Bar David didi@redhat.com wrote:
On Wed, Feb 14, 2018 at 9:20 PM, Alex Bartonek Alex@unix1337.com wrote:
On Wed, Feb 14, 2018 at 5:20 AM, Alex Bartonek Alex@unix1337.com wrote: >I've built and rebuilt about 4 oVirt servers. Consider myself pretty good > at this. LOL. > So I am setting up a oVirt server for a friend on his r710. CentOS 7, ovirt > 4.2. /etc/hosts has the correct IP and FQDN setup. > When I build a VM and try to open a console session via SPICE I am unable > to connect to the graphic server. I'm connecting from a Windows 10 box. > Using virt-manager to connect. > What happens when you try? > Unable to connect to the graphic console is what the error says. Here is the .vv file other than the cert stuff in it: > [virt-viewer] > type=spice > host=192.168.1.83 > port=-1 > password=<removed> > Password is valid for 120 seconds. > delete-this-file=1 fullscreen=0
-------- Original Message -------- On February 14, 2018 2:23 AM, Yedidyah Bar David didi@redhat.com wrote: title=Win_7_32bit:%d toggle-fullscreen=shift+f11 release-cursor=shift+f12 tls-port=5900 enable-smartcard=0 enable-usb-autoshare=1 usb-filter=-1,-1,-1,-1,0 tls-ciphers=DEFAULT host-subject=O=williams.com,CN=randb.williams.com Port 5900 is listening by IP on the server, so that looks correct. I shut the firewall off just in case it was the issue..no go. Did you verify that you can connect there manually (e.g. with telnet)? Can you run a sniffer on both sides to make sure traffic passes correctly? Can you check vdsm/libvirt logs on the host side? Ok.. I must have tanked it on install with the firewall. The firewall is blocking port 5900. This is on CentOS 7. If I flush the rules, it works.
Thanks for the report.
Did you choose to have firewall configured automatically, or did you configure it yourself?
I did configure the host to manage the firewall. Just to make sure, I deleted the host, recreated and still had the issue. I ended up making the firewall rule manually which took care of it. Never had to do that before.
Can you please share relevant logs? On the engine in /var/log/ovirt-engine/host-deploy and /var/log/ovirt-engine/engine.log. Thanks! Also adding Ondra. Best regards, -- Didi
participants (2)
-
Alex Bartonek -
Yedidyah Bar David