Can anyone explain what is happening. After call virConnectOpen virEventRegisterDefaultImpl() call virConnectSetKeepAlive returns VirtError(1): internal error: the caller doesn't support keepalive protocol; perhaps it's missing event loop implementation, but the next call this sequence of commands returns success. Why virConnectSetKeepAlive not work right the first time? -- Fl at sh
At Tue, 1 Apr 2014 17:29:25 +0400, Fl@sh wrote:> > Can anyone explain what is happening. > After call > virConnectOpen > virEventRegisterDefaultImpl() > call virConnectSetKeepAlive returns > VirtError(1): internal error: the caller doesn't > support keepalive protocol; perhaps it's missing > event loop implementation, > but the next call this sequence of commands returns success. > Why virConnectSetKeepAlive not work right the first time?AFAIK, you have to call virEventRegisterDefaultImpl *before* opening a connection. I'm pretty sure that it was documented somewhere, but now I can't seem to find it...
On Wed, Apr 02, 2014 at 12:04:34PM +0200, Claudio Bley wrote:> At Tue, 1 Apr 2014 17:29:25 +0400, > Fl@sh wrote: > > > > Can anyone explain what is happening. > > After call > > virConnectOpen > > virEventRegisterDefaultImpl() > > call virConnectSetKeepAlive returns > > VirtError(1): internal error: the caller doesn't > > support keepalive protocol; perhaps it's missing > > event loop implementation, > > but the next call this sequence of commands returns success. > > Why virConnectSetKeepAlive not work right the first time? > > AFAIK, you have to call virEventRegisterDefaultImpl *before* opening a > connection.Yes, that's correct> I'm pretty sure that it was documented somewhere, but now I can't seem > to find it...Our docs on events in general are pretty non-existant :-( Regards, Daniel -- |: http://berrange.com -o- http://www.flickr.com/photos/dberrange/ :| |: http://libvirt.org -o- http://virt-manager.org :| |: http://autobuild.org -o- http://search.cpan.org/~danberr/ :| |: http://entangle-photo.org -o- http://live.gnome.org/gtk-vnc :|
On Wed, 02 Apr 2014 12:04:34 +0200 Claudio Bley <cbley@av-test.de> wrote:> At Tue, 1 Apr 2014 17:29:25 +0400, > Fl@sh wrote: > > > > Can anyone explain what is happening. > > After call > > virConnectOpen > > virEventRegisterDefaultImpl() > > call virConnectSetKeepAlive returns > > VirtError(1): internal error: the caller doesn't > > support keepalive protocol; perhaps it's missing > > event loop implementation, > > but the next call this sequence of commands returns success. > > Why virConnectSetKeepAlive not work right the first time? > > AFAIK, you have to call virEventRegisterDefaultImpl *before* opening a > connection. > > I'm pretty sure that it was documented somewhere, but now I can't seem > to find it...Thanks! -- Fl@sh