I got the cause,see the following,
welcome comments.
static int read_from_vdi_port(void)
{
/* There are 2 scenarios where we can get called recursively:
1) spice-vmc vmc_read triggering flush of throttled data,
recalling us
2) the buf we push to the client may be send immediately
On Tue, Nov 02, 2010 at 12:48:22PM +0800, Coolper Chen wrote:
> If spice client keeps connecting Windows XP(vdservice running on
> it),reboot XP remotely or locally,it's ok.
> when XP hung-up,use spice client connecting to XP,XP will continue
> reboot.
Nice workaround. We need to fix this bug.
>
If spice client keeps connecting Windows XP(vdservice running on
it),reboot XP remotely or locally,it's ok.
when XP hung-up,use spice client connecting to XP,XP will continue
reboot.
On Mon, 2010-11-01 at 17:47 +0800, Coolper Chen wrote:
> If no vdservice,there's no this issue.
>
> On Mon, 2010-1
If no vdservice,there's no this issue.
On Mon, 2010-11-01 at 17:26 +0800, Arnon Gilboa wrote:
> Please uninstall vdservice & vioser driver, try to reproduce it without
> them, and update us with the results.
> Thanks,
> Arnon
>
> Coolper Chen wrote:
> > hi,
> > I'm testing spice.I found an issue
Please uninstall vdservice & vioser driver, try to reproduce it without
them, and update us with the results.
Thanks,
Arnon
Coolper Chen wrote:
hi,
I'm testing spice.I found an issue about vd_agent,when there's no spice
client connected to the Windows XP guest,I can't remotely reboot Windows
XP
hi,
I'm testing spice.I found an issue about vd_agent,when there's no spice
client connected to the Windows XP guest,I can't remotely reboot Windows
XP more than 3 times,in the third time,the Windows XP guest will hung up
in shutting down process,then wait a long time,there's no change(I have
a mon
