Hi all:
My spice server version is 0.10.1 and my spice client is spice-gtk
(0.10). I found that spicy is not very stable , which often calls error
and the vm(instance) is often shutdown.
for exmple: while I am doing work on WORD(MicroSoft), it often calls as
follows:
qemu: malloc.c:3795: _int
Hi all:
I have install my USB Print (Brother) successfully on my vm(Windows XP
inside) through USB redirection. However, when I use it to print a photo ,
it crashed as follow:
qemu: /builddir/build/BUILD/qemu-kvm-0.15.1/hw/usb.c:336:
usb_packet_complete: Assertion `p->owner != ((void *)0)' fail
HI all:
What is the difference between spice and Xspice ? Is Xspice for Windows
Server only ?
Thanks!
--
Yours.
suyi
___
Spice-devel mailing list
Spice-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/spice-devel
On Fri, Mar 23, 2012 at 11:37:47AM +0100, David Jaša wrote:
> Anthony James píše v Pá 23. 03. 2012 v 06:26 -0400:
> > David,
> >
> > Thanks for the reply. I've tried adding --ca-file to the spicec
> > command line but still receive the same error. Here is the command:
> >
> > spicec -h localhos
Problem resolved, it was a cert issue. Thanks for the help.
On Fri, Mar 23, 2012 at 8:03 AM, Anthony James wrote:
> I did have spaces after the commas in the host subject but after
> regenerating the certs and modifying the command I receive the same error.
> I followed the steps to create the
Anthony James píše v Pá 23. 03. 2012 v 08:03 -0400:
> I did have spaces after the commas in the host subject but after
> regenerating the certs
Hi Anthony,
You should not need to regenerate the certs, just do 's/, /,/' on the
existing string.
> and modifying the command I receive the same error
I did have spaces after the commas in the host subject but after
regenerating the certs and modifying the command I receive the same error.
I followed the steps to create the certs from the
http://www.spice-space.org/page/SSLConnection site. Should those steps
work?
On Fri, Mar 23, 2012 at 7:36
Hi Anthony,
I don't see anything clearly wrong in what you posted in your last two
mails. Just one note: -spice addr=127.0.0.1 means that the host will
only be accessible on the localhost - if you add "" element to "" element in domain xml, qemu
will bind to all ipv4 addresses.
I'd just check the
I just tried connecting using remote-viewer, here is the command:
remote-viewer --spice-ca-file=ca-cert.pem
--spice-host-subject="$HOSTSUBJECT"
spice://localhost/?port=$PORT&tls-port=$SPORT
It connects but using only the non-tls port. When I remove port=$PORT to
try and force it to use the tls-p
I created and started the VM with virt-manager. Here is what looks like
the qemu cmd from /var/log/libvirt/qemu/$VM.log
/usr/bin/qemu-kvm -S -M pc-0.15 -cpu core2duo,+lahf_lm,
+rdtscp,+popcnt,+sse4.2,+sse4.1,+pdcm,+xtpr,+cx16,+tm2,+est,+smx,+vmx,+ds_cpl,+dtes64,+pbe,+tm,+ht,+ss,+acpi,+ds
-enable
Anthony James píše v Pá 23. 03. 2012 v 06:46 -0400:
> David,
>
>
> I just tried about 20 times in a row, same error. When you say it's a
> known bug in spicec when connecting manually, what is the alternative
> to connecting manually? Is this bug present in spicy or
> remote-viewer? Thanks in
David,
I just tried about 20 times in a row, same error. When you say it's a
known bug in spicec when connecting manually, what is the alternative to
connecting manually? Is this bug present in spicy or remote-viewer?
Thanks in advance.
On Fri, Mar 23, 2012 at 6:37 AM, David Jaša wrote:
> An
Anthony James píše v Pá 23. 03. 2012 v 06:26 -0400:
> David,
>
> Thanks for the reply. I've tried adding --ca-file to the spicec
> command line but still receive the same error. Here is the command:
>
> spicec -h localhost -p $PORT -s $SPORT --secure-channels all
> --host-subject "$HOSTSUBJECT"
David,
Thanks for the reply. I've tried adding --ca-file to the spicec command
line but still receive the same error. Here is the command:
spicec -h localhost -p $PORT -s $SPORT --secure-channels all --host-subject
"$HOSTSUBJECT" --ca-file ca-cert.pem -w $PASSWD
Same error:
Error: failed to c
On Fri, Mar 23, 2012 at 09:59:26AM +, Charles.Tsai-蔡清海-研究發展部 wrote:
> Alon,
>
> I read the spice code and found a spice tunnel channel there. What is
> the purpose of the tunnel channel? Is it for network tunneling?
> What is the use case for tunnel channel in spice?
Yes, it is
Hi Anthony,
Anthony James píše v Čt 22. 03. 2012 v 15:40 -0400:
> I'm having problems connecting to a spice virtual machine using SSL.
> I use the following command to connect:
>
>
> spicec -h localhost -p $PORT -s $SPORT --secure-channels all
> --host-subject "$HOSTSUBJECT" -w $PASSWD
>
You'r
Hi Frederic,
Frederic Bouchard píše v Po 19. 03. 2012 v 15:25 -0400:
> Hi,
>
>
> I would like to know if with the spice client for windows can run in
> full screen mode.
The client available at download page is capable of it - run it with -f
option (or --full-screen=auto-conf that will also ad
Alon,
I read the spice code and found a spice tunnel channel there. What is
the purpose of the tunnel channel? Is it for network tunneling?
What is the use case for tunnel channel in spice?
___
Spice-devel mailing list
Spice-devel@lists
Alon,
Thank you for information.
In order isolate the issue, I simply just ran the following script to create
the printing channel.
Initially, I disable the Virio serial adapter. When I enable the Virtio serial
adapter, the Windows is totally locked up.
I am going to debug the Windows virtio
On Fri, Mar 23, 2012 at 05:08:34AM +, Charles.Tsai-蔡清海-研究發展部 wrote:
> Alon,
>
> In Windows, driver name is provided by the device driver. In this case ,
> "com.redhat.print.0" is the device visible to application.
> Because device "com.redhat.print.0" is created by the Qemu which is in Linux,
20 matches
Mail list logo
