search for: connhost

Displaying 4 results from an estimated 4 matches for "connhost".

Did you mean: conhost
2015 Oct 22
2
virt-manager
...click on the 'details' lightbulb. if I run virt-manager --debug, I get the following output after clicking on 'open'... 2015-10-22 16:08:36,377 (engine:471): window counter incremented to 2 2015-10-22 16:08:36,379 (console:1150): Starting connect process for proto=vnc trans=None connhost=localhost connuser=None connport=None gaddr=127.0.0.1 gport=5900 gsocket=None 2015-10-22 16:08:36,381 (console:378): VNC connecting to localhost:5900 2015-10-22 16:08:37,009 (console:1061): Viewer connected [xcb] Extra reply data still left in queue [xcb] This is most likely caused by a broken X e...
2015 Oct 22
0
virt-manager
...ghtbulb. > > if I run virt-manager --debug, I get the following output after clicking > on 'open'... > > 2015-10-22 16:08:36,377 (engine:471): window counter incremented to 2 > 2015-10-22 16:08:36,379 (console:1150): Starting connect process for > proto=vnc trans=None connhost=localhost connuser=None connport=None > gaddr=127.0.0.1 gport=5900 gsocket=None > 2015-10-22 16:08:36,381 (console:378): VNC connecting to localhost:5900 > 2015-10-22 16:08:37,009 (console:1061): Viewer connected > [xcb] Extra reply data still left in queue > [xcb] This is most likel...
2011 Jun 30
0
vnc over ssh failing
...u 10.04 host. kvmhost:~> virsh vncdisplay testing :0 kvmhost:~> telnet 127.0.0.1 5900 Trying 127.0.0.1... Connected to 127.0.0.1. Escape character is '^]'. RFB 003.008 Client virt-manager debug: 2011-06-24 11:28:56,055 (console:923): Starting connect process for proto=vnc trans=tcp connhost=192.168.1.10 connuser=pashdown connport=None gaddr=127.0.0.1 gport=5900 gsocket=None 2011-06-24 11:28:56,120 (console:810): Viewer disconnected I can reach the console with: xtightvncviewer -via 192.168.1.10 127.0.0.1:0 Any suggestions are appreciated. -------------- next part -------------- An...
2013 Mar 28
1
virt-manager connect remote KVM host and graphic control guest problem
...ink if 5911 listen 0.0.0.0 or 1.1.1.1 everything is ok. Here is my virt-manager.log: [Thu, 28 Mar 2013 00:57:16 virt-manager 3242] DEBUG (engine:471) window counter incremented to 2 [Thu, 28 Mar 2013 00:57:16 virt-manager 3242] DEBUG (console:1078) Starting connect process for proto=vnc trans=tcp connhost=2.2.2.2 connuser=root connport=None gaddr=127.0.0.1 gport=5911 gsocket=None [Thu, 28 Mar 2013 00:57:16 virt-manager 3242] DEBUG (console:374) VNC connecting to 2.2.2.2:5911 [Thu, 28 Mar 2013 00:57:18 virt-manager 3242] DEBUG (console:961) Viewer disconnected How can i use virt-manager to control m...