----- Original Message -----
> From: "mzawdx wang" <mzawdx@xxxxxxxxx>
> To: "spice-devel" <spice-devel@xxxxxxxxxxxxxxxxxxxxx>
> Sent: Saturday, April 25, 2015 5:45:28 AM
> Subject: Re: spice proxy fail
>
> there is no issue on the VNC using the same test steps.
>
> 2015-04-20 14:42 GMT+08:00 mzawdx wang < mzawdx@xxxxxxxxx > :
>
>
>
> Hi all
> I met something strange when used netcat for proxy spice like this:
>
> I run the command on the proxy server(192.168.3.128):
>
> mkfifo backpipe
> nc -l 12345 0<backpipe | nc 192.168.3.30 6188 1>backpipe
>
> however, when I used spicy command to connect the vm on host(192.168.3.30):
>
> spicy -h 192.168.3.128 -p 12345
I am not sure about spicy but afaik spice-gkt should take the address of proxy from env variable and you still need to tell client where VM is hosted, so in ur case I guess:
export SPICE_PROXY=192.168.3.128:12345
spicy -h 192.168.3.30 -p 6188
>
> the console stuck, and the spicy window can not be opened.
>
>
> I have debug the spicy, found some clues：
>
> 1741 if (SPICE_IS_DISPLAY_CHANNEL(channel)) {
> 1742 if (id >= SPICE_N_ELEMENTS(conn->wins))
> 1743 return;
> 1744 if (conn->wins[id] != NULL)
> 1745 return;
> 1746 SPICE_DEBUG("new display channel (#%d)", id);
> 1747 g_signal_connect(channel, "notify::monitors",
> 1748 G_CALLBACK(display_monitors), conn);
> 1749 spice_channel_connect(channel);
> 1750 }
>
>
> the callback function: display_monitors was not called.
>
> By the way, meanwhile I test the ssh tunnel proxy too, and it sounds like
> good.
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> _______________________________________________
> Spice-devel mailing list
> Spice-devel@xxxxxxxxxxxxxxxxxxxxx
> http://lists.freedesktop.org/mailman/listinfo/spice-devel
>
_______________________________________________
Spice-devel mailing list
Spice-devel@xxxxxxxxxxxxxxxxxxxxx
http://lists.freedesktop.org/mailman/listinfo/spice-devel