[Openstack-operators] Problem with Heavy Network IO and Dnsmasq

Thomas Vachon vachon at sessionm.com
Wed Aug 15 14:35:39 UTC 2012


On Wed, Aug 15, 2012 at 10:32 AM, Narayan Desai <narayan.desai at gmail.com> wrote:
> On Wed, Aug 15, 2012 at 9:31 AM, Thomas Vachon <vachon at sessionm.com> wrote:
>> On Wed, Aug 15, 2012 at 10:28 AM, Narayan Desai <narayan.desai at gmail.com> wrote:
>>> On Wed, Aug 15, 2012 at 9:16 AM, Thomas Vachon <vachon at sessionm.com> wrote:
>>>> On Wed, Aug 15, 2012 at 9:58 AM, Thomas Vachon <vachon at sessionm.com> wrote:
>>>>> On Wed, Aug 15, 2012 at 8:54 AM, Thomas Vachon <vachon at sessionm.com> wrote:
>>>>>>
>>>>>> On Wed, Aug 15, 2012 at 8:53 AM, Narayan Desai <narayan.desai at gmail.com> wrote:
>>>>>> > On Wed, Aug 15, 2012 at 7:24 AM, Thomas Vachon <vachon at sessionm.com> wrote:
>>>>>> >
>>>>>> >> I am also on Precise.  Downing/Up'ing the interface via VNC did work.
>>>>>> >> How exactly did you setup vhost_net, can you provide your libvirt?
>>>>>> >
>>>>>> > Hm, that might mean that isn't the problem, but this is an easy enough
>>>>>> > thing to check.
>>>>>> >
>>>>>> > Setting up vhost_net is pretty easy; it is auto-detected by kvm, so
>>>>>> > all you need to do is modprobe it on the hypervisor.
>>>>>> >  -nld
>>>>>>
>>>>>> Found the docs saying that.  It might help, I will report back on this
>>>>>> thread when I run the tests in a bit
>>>>>
>>>>> OK, I lost all connectivity between nova-network and my vm's.  DNSMasq
>>>>> is running and I added the vhost_net module (and confirmed libvirt
>>>>> sees it).  Do I need to do something to the guests now too?
>>>>
>>>> I think I found the root bug:
>>>> https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/997978
>>>
>>> Yeah, this is where i found the vhost_net workaround. (it seems to
>>> work for some people and not for others, so I suspect the problem is
>>> more complicated somehow)
>>>  -nld
>>
>> The workaround of adding it?  When I added it, I lose all connectivity
>> to the instances.
>
> Yeah, I think that all instances will need to be restarted. Or freshly
> spawned even.
>  -nld

I rebooted the whole thing (physical and all).  I also launched a
Cirros image and it had no connectivity.  I removed it, rebooted the
physical and I can connect now at least.

It seems to be highly related to bonding multiple nic's together on
the physical host for FT and HA.



More information about the OpenStack-operators mailing list