Hi,
On 08/26/2011 10:07 AM, Alon Levy wrote:
On Thu, Aug 25, 2011 at 01:57:21PM +0200, Hans de Goede wrote:
Hi,
On 08/25/2011 01:35 PM, Gerd Hoffmann wrote:
Hi,
Some examples of why having a generic spicevmc pass through is good:
(5) Redirect the serial or virtio console over spice. Espec
On Thu, Aug 25, 2011 at 01:57:21PM +0200, Hans de Goede wrote:
> Hi,
>
> On 08/25/2011 01:35 PM, Gerd Hoffmann wrote:
> >Hi,
> >
> >>Some examples of why having a generic spicevmc pass through is good:
> >
> >(5) Redirect the serial or virtio console over spice. Especially with
> >spice-gtk it sho
Hi,
On 08/25/2011 01:35 PM, Gerd Hoffmann wrote:
Hi,
Some examples of why having a generic spicevmc pass through is good:
(5) Redirect the serial or virtio console over spice. Especially with
spice-gtk it should be easy to wind up the spice client side to a
vte widget.
Right, so this would
Hi,
Some examples of why having a generic spicevmc pass through is good:
(5) Redirect the serial or virtio console over spice. Especially with
spice-gtk it should be easy to wind up the spice client side to a
vte widget.
cheers,
Gerd
__
On Thu, Aug 25, 2011 at 12:19:36PM +0200, Hans de Goede wrote:
ACK.
> While discussing various things with Alon in Vancouver, it came up that
> having a channel which simply passes through data coming out of a qemu
> chardev frontend unmodified, like the usbredir channel does, can be used
> for a
While discussing various things with Alon in Vancouver, it came up that
having a channel which simply passes through data coming out of a qemu
chardev frontend unmodified, like the usbredir channel does, can be used
for a lot of other cases too. To facilitate this the usbredir channel code
will be
