Re: non-blocking virtConnectOpen

[Timon Wang <timonwst@xxxxxxxxx>]

We do it in a  global cache, each hyper-visor with  an instance, when want to call api from an connection first get the connection from the cache, when get failed try reconnect. Then is will only be block when the first time the connection build, or the connection is broken.

On Wed, Sep 5, 2012 at 11:41 PM, lulin Fan <fan.luliin@xxxxxxxxx> wrote:

Hi

I am writing a web-based management tool for KVM, it will manager a lot of remote KVM host, when user add a new connection from the UI, it will take a long time to open the libvirt connection sometimes due to the network problem, during this progress, the management tool will block the request of other user, it is not a good idea for users.

BR

Fan

On 5 September 2012 14:55, Timon Wang <timonwst@xxxxxxxxx> wrote:

On Wed, Sep 5, 2012 at 11:53 AM, lulin Fan <fan.luliin@xxxxxxxxx> wrote:
> Hi all,
>
> does anybody know how to do non-blocking virtConnectOpen? does libvirt
> support it or not cause I can't find any document about it? or should I need
> create a thread to do it?

It's worth to use non-blocking? What will you do without connect? If it's not related with libvirt connection, you can do in it in another thread if you like.
>
>
> Thanks
>
> Fan
>
> _______________________________________________
> libvirt-users mailing list
> libvirt-users@xxxxxxxxxx
> https://www.redhat.com/mailman/listinfo/libvirt-users



--
Focus on: Server Vitualization, Network security,Scanner,NodeJS,JAVA,WWW
Blog: http://www.nohouse.net

-- 
Focus on: Server Vitualization, Network security,Scanner,NodeJS,JAVA,WWW
Blog: http://www.nohouse.net
_______________________________________________
libvirt-users mailing list
libvirt-users@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/libvirt-users