[Spice-devel] Possible Windows vdagent problems

John A. Sullivan III jsullivan at opensourcedevel.com
Fri Jul 8 19:25:22 PDT 2011


On Tue, 2011-07-05 at 10:49 -0400, John A. Sullivan III wrote:
> On Tue, 2011-07-05 at 12:31 +0300, Arnon Gilboa wrote:
> > John A. Sullivan III wrote:
> > > On Tue, 2011-07-05 at 09:44 +0300, Arnon Gilboa wrote:
> > >   
> > >> Hi John,
> > >> See my comments below.
> > >> Arnon
> > >>
> > >> John A. Sullivan III wrote:
> > >>     
> > >>> Hello, all.  I'm spinning this off of the "Unfair Comparisons with RDP"
> > >>> thread as that one is getting a bit long.  However, in it, Yaniv
> > >>> identified that we were not using vdagent in our Windows guest based
> > >>> upon the packet traces we submitted.  That sounded plausible as we have
> > >>> noticed the agent being quite unstable.  We are often unable to connect
> > >>> or the session seems to die.  We then connect as administrator via RDP
> > >>> and restart the RHEV Spice Agent and all is well again.
> > >>>   
> > >>>       
> > >> Can you please be more specific with regards to "agent being quite 
> > >> unstable"?
> > >> Please describe the problems, and we'll try to solve them.
> > >>     
> > >
> > > Alas, there is not more than I have already said.  Often, when we try to
> > > access the guest via SPICE, we simply get a black screen and then a
> > > connection timeout.  We connect to the guest via RDP as admin, restart
> > > RHEV Spice Agent service and we are then able to login.  Every once in a
> > > while, the SPICE client stops responding.  We restart the RHEV Spice
> > > Agent service as described and we are now able to work again.  There is
> > > nothing in event logs to indicate there was a problem.
> > >
> > >   
> > Try disabling power saving / sleep in your guest and see if it still 
> > reproduced.
> > In case it still happens, please send your %windir%\temp\vdservice.log & 
> > %windir%\temp\vdagemt.log files.
> > >> <snip>> So then I thought our qemu configuration must be off or the needed
> > >>     
> <snip>
> Alas, it has happened again.  I was not able to open a spice session -
> just a black screen followed by "Error: unhandled exception: vdagent
> timeout".  I double checked the Power Settings while unable to login and
> they were indeed on high performance with suspend video set to never.
> 
> I can also add that the keyboard was extremely lagged in SPICE.  I was
> using it without disabling effects so I exited and went in via RDP and
> noticed no lag.  I also ran background pings to see if we had problems
> on the connection and it was quite healthy.  I then tried SPICE again
> disabling all effects.  That's when I noticed I could not get in.  I
> restarted RHEV Spice Agent and was now able to get in with effects
> disabled but it was still very lagged.  It had clearly disabled effects;
> the difference in the font rendering was quite noticeable.  I exited
> again and tried via RDP and there was no lag.  I then tried connecting
> again and once again got only the black screen.
> 
> It was at that point that I grabbed the attached logs.  I then restarted
> the agent again, went in via SPICE without disabling effects and the
> response is much better now although keyboarding is still noticeably
> less crisp than RDP.
> 
> The logs look like they do not contain sensitive information so I have
> attached them herewith.  Thanks - John
<snip>
Alas, it has happened again for the first time in a few days.  I've
attached the logs.  How do we figure out what is wrong and stabilize
this? Thanks - John
-------------- next part --------------
A non-text attachment was scrubbed...
Name: vdagent.logs.20110708.zip
Type: application/zip
Size: 32948 bytes
Desc: not available
URL: <http://lists.freedesktop.org/archives/spice-devel/attachments/20110708/033b52bf/attachment-0001.zip>


More information about the Spice-devel mailing list