Hi
I just read the document
“
Benchmark Report on SPICE
Remote Display Protocol
2010”
.
I want to know how can I build the testing environment and get the outputs? Is
there any user manual?
Thanks in advance.
Best regards.
___
Spice-devel m
ack
On Sun, Jun 10, 2012 at 11:36 PM, Christophe Fergeau
wrote:
> This patch makes sure we emit a SPICE_CHANNEL_ERROR_TLS before
> giving up on channel creation to inform the application that
> an error happened.
--
Marc-André Lureau
___
Spice-devel
When trying to start remote-viewer with SPICE over TLS with
--spice-ca-file with a wrong filename, the connection fails
but remote-viewer keeps displaying the "Trying to connect"
message. The only hint that something went wrong is:
(remote-viewer:12924): GSpice-WARNING **: loading ca certs from
a/
Hi,
On 06/10/2012 05:32 PM, Hans de Goede wrote:
Hi,
On 06/10/2012 11:05 AM, Yonit Halperin wrote:
Hi,
As the qemu team rejected integrating spice connection migration in
qemu migration process, we remain with a solution that will involve
libvirt, and passing data from the src to the target vi
Hi
- Mensaje original -
> Thanks. I didn't notice the executable remote-viewer.com, it works
> fine
> with spice://server:port.
>
> But what would be the correct URI for virt-viewer? I looked up the id
> of
> the vm, but
>
> virt-viewer.exe --connect qemu://server:port/ id
It's the libv
On Sun, Jun 10, 2012 at 05:11:06PM +0200, Hans de Goede wrote:
> Hi,
>
> On 06/10/2012 04:44 PM, Alon Levy wrote:
>
>
>
> >>>Obligatory migration data:
> >>>-
> >>>(1) agent/spicevmc/smartcard write buffer. i.e., data that reached the
> >>>server after savevm, and thus
Hi,
On 06/10/2012 04:44 PM, Alon Levy wrote:
Obligatory migration data:
-
(1) agent/spicevmc/smartcard write buffer. i.e., data that reached the server
after savevm, and thus was not written to the device.
Currently, spicevmc and smartcard do not have write buffer, bu
On Sun, Jun 10, 2012 at 04:32:54PM +0200, Hans de Goede wrote:
> Hi,
>
> On 06/10/2012 11:05 AM, Yonit Halperin wrote:
> >Hi,
> >
> >As the qemu team rejected integrating spice connection migration in qemu
> >migration process, we remain with a solution that will involve libvirt, and
> >passing
Hi,
On 06/10/2012 11:05 AM, Yonit Halperin wrote:
Hi,
As the qemu team rejected integrating spice connection migration in qemu
migration process, we remain with a solution that will involve libvirt, and
passing data from the src to the target via the client. Before I continue with
the implem
Thanks. I didn't notice the executable remote-viewer.com, it works fine
with spice://server:port.
But what would be the correct URI for virt-viewer? I looked up the id of
the vm, but
virt-viewer.exe --connect qemu://server:port/ id
gave the error "Unable to connect to libvirt with URI qemu:/
Hi,
As the qemu team rejected integrating spice connection migration in qemu
migration process, we remain with a solution that will involve libvirt,
and passing data from the src to the target via the client. Before I
continue with the implementation I'd like to hear your comments on the
deta
11 matches
Mail list logo
