[Spice-devel] keyboard and Mouse Fails....

Naga Mohan Pothula nagamohan.pothula at yahoo.com
Thu May 17 14:46:32 PDT 2012


Hi Arnon,

This issue is not fixed yet. To find out root cause, I disabled VDAgent at guest and launch session with --full-screen=auto-conf then I'm able to see this issue.
But this issue doesn't happen on all linux clients. I'm seeing this with customized fedora based linux client
It means somehow keyboard/mouse don't get activated when we launch session with --full-screen=auto-conf if VDAgent is absent at guest.
Keyboard/Mouse works if we don't launch session with --full-screen=auto-conf.


Can you please provide suggestions to find out root cause further?


Thanks\Naga.


________________________________
 From: Arnon Gilboa <agilboa at redhat.com>
To: Naga Mohan Pothula <nagamohan.pothula at yahoo.com> 
Cc: Alon Levy <alevy at redhat.com>; David Jaša <djasa at redhat.com>; "spice-devel at lists.freedesktop.org" <spice-devel at lists.freedesktop.org>; Christophe Fergeau <cfergeau at redhat.com> 
Sent: Wednesday, February 8, 2012 9:02 AM
Subject: Re: [Spice-devel] keyboard and Mouse Fails....
 
Hi Naga,
I couldn't reproduce this issue with linux client, so debugging it is not trivial.
Have you tried using the new gtk client instead of the legacy client?
Will catch you on irc later.
Thanks,
Arnon

Naga Mohan Pothula wrote:
> Hi Arnon,
> 
> This issue happens with Windows guest connecting from Linux client only.
> We noticed this issue doesn't happen if Spice client is launched after VDAgent starts. It happens only when Spice is launched from linux machine before VDAgent starts.
> 
> When Spice client is launched from Windows machine before VDAgent starts, this issue is not reproducible.
> why this happens and how to make sure Spice client is launched from linux machine after VDAgent starts?
> 
> 
> Appreciated your help.
> 
> 
> Thanks\Naga.
> 
> 
> ________________________________
>  From: Arnon Gilboa <agilboa at redhat.com>
> To: Naga Mohan Pothula <nagamohan.pothula at yahoo.com> Cc: Alon Levy <alevy at redhat.com>; David Jaša <djasa at redhat.com>; "spice-devel at lists.freedesktop.org" <spice-devel at lists.freedesktop.org>; Christophe Fergeau <cfergeau at redhat.com> Sent: Wednesday, January 11, 2012 3:06 AM
> Subject: Re: [Spice-devel] keyboard and Mouse Fails....
>  Hi Naga,
> See comments below.
> Thanks,
> Arnon
> 
> Naga Mohan Pothula wrote:
>  
>> Arnon,
>> 
>> 
>> Thanks for your suggestions and attachment. Issue still exists and please find the attached logs.
>>      
> Looking at vdagent.log & vdservice.log, it seems in 15:30:30-32 vdagent got the auto-conf request, set the displays accordingly, and via vdservice forwarded the reply ack using virtio-serial (to spice-server which sends it to spice-client).
> 
> Note these lines in spicec.log:
> 1326144675 INFO [4457:4464] RedClient::handle_init:
> 1326144675 WARN [4457:4464] RedClient::init_guest_display: no agent running, display options have been ignored
> 
> For some reason, the server reported the client that agent is not connected, which is suspicious.
> Please reproduce again, and send all logs including qemu log.
>  
>>   Haven't seen
>> "AgentTimer::response: timeout " in spicec.log
>>      
> The above explain why you didn't see it - client thinks there is no agent connected at all.
>  
>> Have seen in
>> vdagent.log while authenticating user credentials(winlogon) which is acceptable.
>>     "DisplaySetting::get_user_process_id::explorer.exe not found
>>      DisplaySetting::reload_from_registry::get_user_process_id failed."
>>      
> This is not relevant to the issue.
>  
>>   Client machine is not attached to dual-head. Qemu launched guest
>> with two QXL devices.
>>      
> Try running qemu with only one qxl (-vga qxl, but no additional -device qxl) and post the results.
>  
>>   Most of customers use full-screen option. I can keep without
>> Auto-conf, but has so many issues that Auto Adjustment screen resolution
>> wouldn't work. Screen resolution doesn't persist after restart/shutdown system
>> for user level (we have some restrictions at our environment)      
> Ok
>  
>>   I tried url "irc.gimp.net/6667" but it is not
>> working.      
> Try again. We are all there. 6667 is the port.
>  
>> Thanks,
>> Mohan.
>> 
>> 
>> ________________________________
>>   From: Arnon Gilboa <agilboa at redhat.com>
>> To: Naga Mohan Pothula <nagamohan.pothula at yahoo.com> Cc: Alon Levy <alevy at redhat.com>; David Jaša <djasa at redhat.com>; "spice-devel at lists.freedesktop.org" <spice-devel at lists.freedesktop.org>; Christophe Fergeau <cfergeau at redhat.com> Sent: Monday, January 9, 2012 9:30 AM
>> Subject: Re: [Spice-devel] keyboard and Mouse Fails....
>>   Hi Mohan,
>> 
>> Few notes:
>> 1. The client should connect after 30 sec even if vdagent does not response to the auto-conf request.
>> 2. Please delete the client log ~/.spicec/spicec.log, and in a run with "Keyboard/Mouse lock" look for a log line with: "AgentTimer::response: timeout while waiting for agent response".
>> 3. Debug version of vdagent & vdservice will be sent to you following this msg. Please send logs of client and vdagent/vdservice with only the lines relevant to the failed run (delete it before).
>> 4. It seems you have 2 monitors on the client machine and the second one is disabled. Try to launch spicec after enabling it/disabling the first one/on a machine with only one display etc.
>> 5. Although important, I cannot see how the "auto-conf" bug can be a showstopper. Why not remove this param until we solve it?
>> 6. Try to catch us on #spice at irc.gimp.net/6667. This is the place to get things done.
>> 
>> Thanks,
>> Arnon
>> 
>> Naga Mohan Pothula wrote:
>>      
>>> Hi Alon/Arnon,
>>> 
>>> Keyboard/Mouse lock issue is showstopper issue. Can you please provide suggestions to proceed further investigation on this issue?
>>> Haven't received VdAgent build. Thanks\Mohan.
>>> 
>>> 
>>> 
>>> ________________________________
>>>    From: Naga Mohan Pothula <nagamohan.pothula at yahoo.com>
>>> To: Naga Mohan Pothula <nagamohan.pothula at yahoo.com>; Arnon Gilboa <agilboa at redhat.com> Cc: David Jaša <djasa at redhat.com>; "spice-devel at lists.freedesktop.org" <spice-devel at lists.freedesktop.org>; Christophe Fergeau <cfergeau at redhat.com> Sent: Thursday, January 5, 2012 4:43 PM
>>> Subject: Re: [Spice-devel] keyboard and Mouse Fails....
>>>    Arnon, VDAgent is running as expected when Keyboard/Mouse lock issue happens.
>>> Can you please send VDAgent build?
>>> 
>>> 
>>> Thanks/Naga.
>>> 
>>> 
>>> ________________________________
>>>    From: Naga Mohan Pothula <nagamohan.pothula at yahoo.com>
>>> To: Arnon Gilboa <agilboa at redhat.com> Cc: David Jaša <djasa at redhat.com>; "spice-devel at lists.freedesktop.org" <spice-devel at lists.freedesktop.org>; Christophe Fergeau <cfergeau at redhat.com> Sent: Friday, December 30, 2011 5:44 AM
>>> Subject: Re: [Spice-devel] keyboard and Mouse Fails....
>>>    Hi Arnon,
>>>    Please find the attached VDAgent, VDService logs. I know RHEV Spice Agent is for handling Auto-conf for resolution adjustment, mouse support for multi-head monitors, and Clipboard functionality. In what scenarios Keyboard lock happens?
>>>    Keyboard/Mouse lock issue happens only with Windows guest connecing from Linux Spice client..(This is major issue that need to do system restart or close Xwindows session to restart Spice session)
>>>    Black screen issue happens with Windows/Linux guests connecting from Linux Spice client.
>>>    Can you please forward scratch build for vdagent? I see whether it may fix the issues at my environment.
>>>     Thanks,
>>> Mohan.
>>>    From: Arnon Gilboa <agilboa at redhat.com>
>>> To: Naga Mohan Pothula <nagamohan.pothula at yahoo.com> Cc: Alon Levy <alevy at redhat.com>; David Jaša <djasa at redhat.com>; "spice-devel at lists.freedesktop.org" <spice-devel at lists.freedesktop.org>; Christophe Fergeau <cfergeau at redhat.com> Sent: Thursday, December 29, 2011 8:22 AM
>>> Subject: Re: [Spice-devel] keyboard and Mouse Fails....
>>> 
>>> Hi Mohan, see below.
>>> 
>>> Naga Mohan Pothula wrote:
>>>            
>>>> Hi Alon,
>>>> 
>>>> Please refer my inline comments.
>>>> 
>>>> Thanks/Mohan.
>>>> 
>>>> 
>>>> ________________________________
>>>>     From: Alon Levy <alevy at redhat.com>
>>>> To: Naga Mohan Pothula <nagamohan.pothula at yahoo.com> Cc: David Jaša <djasa at redhat.com>; "spice-devel at lists.freedesktop.org" <spice-devel at lists.freedesktop.org>; Christophe Fergeau <cfergeau at redhat.com> Sent: Wednesday, December 28, 2011 5:54 AM
>>>> Subject: Re: [Spice-devel] keyboard and Mouse Fails....
>>>>     On Tue, Dec 27, 2011 at 12:04:28PM -0800, Naga Mohan Pothula wrote:
>>>>                    
>>>>>       Can anyone please respond on this?
>>>>>       Thanks/Mohan.
>>>>> 
>>>>>       --------------------------------------------------------------------------
>>>>> 
>>>>>       From: Naga Mohan Pothula <nagamohan.pothula at yahoo.com>
>>>>>       To: David Jaša <djasa at redhat.com>
>>>>>       Cc: "spice-devel at lists.freedesktop.org"
>>>>>       <spice-devel at lists.freedesktop.org>; Christophe Fergeau
>>>>>       <cfergeau at redhat.com>
>>>>>       Sent: Thursday, December 22, 2011 12:13 PM
>>>>>       Subject: Re: [Spice-devel] keyboard and
>>>>>                        
>>>    Mouse Fails....
>>>            
>>>>>       Hi,
>>>>>       I'm facing severe below issues when connecting Windows guests from Linux
>>>>>       clients with Full-screen+Auto-Config only        1.)    Keyboard/mouse lock issue happens when session is connected
>>>>>       from guestגs shutdown/restart state.                            
>>>> Are you
>>>>                  
>>>    running an agent in the guest? does this happen when not running
>>>            
>>>> an agent in the guest?
>>>> Agent is running in the guest. These two Issues do not happen when Agent is not running in the guest.                    
>>> We have a patch fixing agent crash on connection during guest startup (on rare cases) and I can send you a scratch build.
>>> Do you think it's the case? the agent crash locks the mouse but should have no effect on keyboard. Can you give more details about it?
>>> Posting your %windir%\temp\vdagent.log & vdservice.log may help.
>>>            
>>>>                    
>>>>>           2.)    Black screen appears when session is reconnected from guestגs
>>>>>       disconnected state.
>>>>>                            
>>>> What does this mean? what's disconnected state? no client connected? so
>>>> you connect from a linux client to a windows guest and you get a black
>>>> screen? It means Spice client is not connected
>>>>                  
>>>    to guest. we don't see this issue if we specify "./spicec -h <ip addr> -p 5924"
>>>            
>>>> we see it only when we specify "./spicec -h <ip addr> -p 5924 --full-screen=auto-conf"
>>>>                    
>>> Seems like for some reason the client doesn't get auto-conf ack from the guest agent. Does it timeout & exit after 30 sec?
>>> This can also be the case if the agent crashed during startup. However, you say that without the --full-screen=auto-conf it works.
>>> Please check in all cases if vdservice & vdagent processes are up.
>>>            
>>>> if that is the case can you give more details on the guest and
>>>> 
>>>> client, version of client, version of driver in guest, agent existance
>>>> and if so version.
>>>> Guest:
>>>>           Windows 7 32/64 bit          QXL driver: built the code taken from spice git repository (v1.4.1.1)
>>>>             VDAgent: built the code
>>>>                  
>>>    taken from spice git repository(v1.1.0.1009)
>>>            
>>>> Client:
>>>>         Spice Client: v0.10.0
>>>>         Client machine: Fedora14 Live image loaded into RAM.
>>>> 
>>>>                    
>>>>>       This issue would not be reproducible all the time from Linux Desktops but
>>>>>       can be reproducible consistently if we load Fedora14 Live Image into RAM
>>>>>       and launch Spice connection.
>>>>>       Thanks,
>>>>>       Naga.
>>>>>                            
>>>> I don't understand the last part - you only get those two issues when
>>>> running a client from a fedora 14 live image? or is fedora14 related to the guest, in which case it contradicts the guest being windows?
>>>> Yes. These two issues happen when Spice client running from Fedora 14 Live image connecting to Windows 7 guest.
>>>> Steps to reproduce:
>>>> 1.)Fedora14 Live image
>>>>                  
>>>    is loaded into RAM thru "live_ram" option for booting. we may not see these issues if we don't load into RAM.
>>>            
>>>> 2.)Spice session is launched with Full-Screen+Auto-config only.
>>>>       ./spicec -h <ip addr> -p 5924 --full-screen=auto-conf        (we see issues)
>>>>       ./spicec -h <ip addr> -p 5924                                            (we don't see issues)
>>>>                    
>>> I will try to repro from F14 and update you.
>>>            
>>>>                    
>>>>>       --------------------------------------------------------------------------
>>>>> 
>>>>>       From: David Jaša <djasa at redhat.com>
>>>>>       To: Naga Mohan Pothula <nagamohan.pothula at yahoo.com>
>>>>>       Cc: Christophe Fergeau <cfergeau at redhat.com>;
>>>>>       "spice-devel at lists.freedesktop.org" <spice-devel at lists.freedesktop.org>
>>>>>       Sent: Tuesday, December 20, 2011 2:50 AM
>>>>>       Subject: Re: [Spice-devel] keyboard and Mouse Fails....
>>>>>       Naga Mohan Pothula píše v Po 19. 12. 2011 v 10:13 -0800:
>>>>>                          
>>>      > We can move mouse over the guest but the guest doesn't respond for
>>>            
>>>>>       > user actions like mouse click.
>>>>> 
>>>>>       I've seen something similar that was caused by agent. Keyboard worked
>>>>>       fine so I used it to restart agent service and everything started
>>>>>       working normally. I was not able to make clear reproducer for this
>>>>>       however, so if you have a reliable step-by-step one, it would be great
>>>>> 
>>>>>       David
>>>>>       >
>>>>>       > In the same way for keyboard actions. Client machine needs to get
>>>>>       > restarted or close Xwindows to reconnect guest.
>>>>>       > This issue happens only when we connect windows guest in fullscreen
>>>>>       > mode with auto-conf from linux client(but not from windows client).
>>>>>       > It doesn't happen if we connect guest in windowed mode.
>>>>>       >
>>>>>                            
>>>    >
>>>            
>>>>>       >
>>>>>       >
>>>>>       > Thanks/Mohan.
>>>>>       >
>>>>>       >
>>>>>       >
>>>>>       > ______________________________________________________________________
>>>>>       > From: Christophe Fergeau <[1]cfergeau at redhat.com>
>>>>>       > To: Naga Mohan Pothula <[2]nagamohan.pothula at yahoo.com>
>>>>>       > Cc: "[3]spice-devel at lists.freedesktop.org"
>>>>>       > <[4]spice-devel at lists.freedesktop.org>
>>>>>       > Sent: Monday, December 19, 2011 3:20 AM
>>>>>       > Subject: Re: [Spice-devel] keyboard and Mouse Fails....
>>>>>       >
>>>>>       > On Mon, Dec 19, 2011 at 12:32:47AM -0800, Naga Mohan Pothula wrote:
>>>>>       > > Hi,
>>>>>       > >
>>>>>       > > Keyboard and Mouse failure happens when windows guests are connected
>>>>>       > from linux client.
>>>>>       >
>>>>>       > What do you mean exactly by keyboard and mouse failures? You can't
>>>>>       > type
>>>>>       > anything nor move the mouse? Or do you observe a different kind of
>>>>>                            
>>>    > failure?
>>>            
>>>>>       >
>>>>>       >
>>>>>                        
>>>    Christophe
>>>            
>>>>>       >
>>>>>       >
>>>>>       >
>>>>>       > _______________________________________________
>>>>>       > Spice-devel mailing list
>>>>>       > [5]Spice-devel at lists.freedesktop.org
>>>>>       > http://lists.freedesktop.org/mailman/listinfo/spice-devel
>>>>> 
>>>>>       --
>>>>> 
>>>>>       David Jaša, RHCE
>>>>> 
>>>>>       SPICE QE based in Brno
>>>>>       GPG Key:    22C33E24
>>>>>       Fingerprint: 513A 060B D1B4 2A72 7F0D 0278 B125 CD00 22C3 3E24
>>>>> 
>>>>>                            
>>>    _______________________________________________
>>>            
>>>>>       Spice-devel mailing list
>>>>>       [6]Spice-devel at lists.freedesktop.org
>>>>>       [7]http://lists.freedesktop.org/mailman/listinfo/spice-devel
>>>>> 
>>>>> References
>>>>> 
>>>>>       Visible links
>>>>>       1. mailto:cfergeau at redhat.com
>>>>>       2. mailto:nagamohan.pothula at yahoo.com
>>>>>       3. mailto:spice-devel at lists.freedesktop.org
>>>>>       4. mailto:spice-devel at lists.freedesktop.org
>>>>>       5. mailto:Spice-devel at lists.freedesktop.org
>>>>>       6. mailto:Spice-devel at lists.freedesktop.org
>>>>>       7. http://lists.freedesktop.org/mailman/listinfo/spice-devel
>>>>>                            
>>>>                    
>>>>> _______________________________________________
>>>>> Spice-devel mailing list
>>>>> Spice-devel at lists.freedesktop.org
>>>>> http://lists.freedesktop.org/mailman/listinfo/spice-devel
>>>>>       ------------------------------------------------------------------------
>>>>> 
>>>>> _______________________________________________
>>>>> Spice-devel mailing list
>>>>> Spice-devel at lists.freedesktop.org
>>>>> http://lists.freedesktop.org/mailman/listinfo/spice-devel
>>>>>                            
>>> _______________________________________________
>>> Spice-devel mailing list
>>> Spice-devel at lists.freedesktop.org
>>> http://lists.freedesktop.org/mailman/listinfo/spice-devel
>>>            
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/spice-devel/attachments/20120517/5bb73884/attachment.htm>


More information about the Spice-devel mailing list