On Fri, Oct 12, 2018 at 08:47:55AM +0100, Daniel P. Berrangé wrote:
> On Thu, Oct 11, 2018 at 03:57:10PM -0400, Laine Stump wrote:
> > On 10/11/2018 06:20 AM, Daniel P. Berrangé wrote:
> > > On Mon, Sep 24, 2018 at 10:41:37AM +0300, Nikolay Shirokovskiy wrote:
> > >
> > >> What speed up is
On Thu, Oct 11, 2018 at 03:57:10PM -0400, Laine Stump wrote:
> On 10/11/2018 06:20 AM, Daniel P. Berrangé wrote:
> > On Mon, Sep 24, 2018 at 10:41:37AM +0300, Nikolay Shirokovskiy wrote:
> >
> >> What speed up is possible on conservative approach? First we can remove
> >> for
> >> test purpuses
On 10/11/2018 06:20 AM, Daniel P. Berrangé wrote:
> On Mon, Sep 24, 2018 at 10:41:37AM +0300, Nikolay Shirokovskiy wrote:
>
>> What speed up is possible on conservative approach? First we can remove for
>> test purpuses firewall ruleLock, gentech dirver updateMutex and filter object
>> mutex
On 11.10.2018 13:20, Daniel P. Berrangé wrote:
> On Mon, Sep 24, 2018 at 10:41:37AM +0300, Nikolay Shirokovskiy wrote:
>> Hi, all.
>>
>> On fat hosts which are capable to run hundreds of VMs restarting libvirtd
>> makes it's services unavailable for a long time if VMs use network filters.
>>
On Mon, Sep 24, 2018 at 10:41:37AM +0300, Nikolay Shirokovskiy wrote:
> Hi, all.
>
> On fat hosts which are capable to run hundreds of VMs restarting libvirtd
> makes it's services unavailable for a long time if VMs use network filters. In
> my tests each of 100 VMs has no-promisc [1] and
ping
On 24.09.2018 10:41, Nikolay Shirokovskiy wrote:
> Hi, all.
>
>
> On fat hosts which are capable to run hundreds of VMs restarting libvirtd
> makes it's services unavailable
Hi, all.
On fat hosts which are capable to run hundreds of VMs restarting libvirtd
makes it's services unavailable for a long time if VMs use network filters. In
