search for: gport

jaromil, > > > > wanted to ask again if someone has some online documentation on the > > icecast (or shoutcast) protocol at the socket/data level. > > have a look into MuSE/libmpeg/httpinput.cc (http://muse.dyne.org) > i hope that code can help you figuring out > No actually not. It just makes the connection to the shoutcast/icecast server. I've gotten this

...--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 extension library [xcb] Aborting, sorry about that. python: xc...

...ng 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 extension library > [xcb] Aborting, sor...

...; 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 HTML attachment was scrubbed... URL: <http://listman.redhat.com/...

...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 my guest by graphic? thank you very much!!! --------------...

*RESEND* due to exceeding the mailinglists limit for attachment size. Hi, I''m trying to get secondary vga-passthrough on a HVM guest to work with a AMD HD6570 and the native kernel radeon driver and kernel modesetting. So the guest still gets the emulated stdvga or cirrus device(used in my case here) as primary/boot vga adapter. - When i don''t passthrough the radeon card, the

Hi,all I have tried to passthrough GPU card(Nvidia quadro 4000) on the latest Xen unstable version (QEMU is using Qemu-upsteam-unstable, not traditional Qemu). This issue as below: Windows7 64-bit guest will blue screen when GPU passthrough configure 4g memory,blue screen code is 50, and SUSE 11 64-bit guest will always stay at the grub screen. I noticed that it will relocate RAM that