On 13.12.2011 01:48, Nathan March wrote: > On 12/12/2011 4:35 PM, Nathan March wrote: >> On 12/1/2011 3:18 PM, Nathan March wrote: >>> Can anyone tell me if it's normal to take over 2 seconds to connect >>> to the libvirt daemon? >>> >> >> Can anyone comment on this? Even just a quick test to see if it >> happens on your systems would be appreciated. >> > > I've rebuilt it with debugging and found the following: > > 16:47:29.640: 5972: debug : remoteIOEventLoop:10599 : Giving up the buck > 66 0x7ff564a59010 (nil) > 16:47:29.640: 5972: debug : remoteIO:10773 : All done with our call 66 > (nil) 0x7ff564a59010 > 16:47:29.641: 5972: debug : remoteIO:10673 : Do proc=1 serial=1 > length=48 wait=(nil) > 16:47:29.641: 5972: debug : remoteIO:10745 : We have the buck 1 > 0x10c6130 0x10c6130 > 16:47:31.670: 5972: debug : remoteIODecodeMessageLength:10066 : Got > length, now need 56 total (52 more) > 16:47:31.670: 5972: debug : remoteIOEventLoop:10599 : Giving up the buck > 1 0x10c6130 (nil) > 16:47:31.670: 5972: debug : remoteIO:10773 : All done with our call 1 > (nil) 0x10c6130 > 16:47:31.670: 5972: debug : doRemoteOpen:922 : Adding Handler for remote > events > 16:47:31.670: 5972: debug : virEventPollAddHandle:110 : Add handle fd=7 > events=1 cb=0x7ff > > The 2s gap is pretty visible, not sure why yet. Yeah, the gap is obvious. However, this is not telling us why. Can you please provide the daemon logs? As far as I can tell, we see client here, waiting for response for 2 secs. Therefore we need to inspect the daemon for what take it so long. Michal
