openstack team mailing list archive
-
openstack team
-
Mailing list archive
-
Message #24001
Re: Internet access within launched instances too slow
Same issues after restarting nova-compute daemons and launching new
instances?
---
JuanFra
2013/5/28 Rahul Sharma <rahulsharmaait@xxxxxxxxx>
> Nope. Still the same problem.
>
> -Regards
> Rahul
>
>
> On Tue, May 28, 2013 at 4:15 PM, Rahul Sharma <rahulsharmaait@xxxxxxxxx>wrote:
>
>> Thanks JuanFra. I will use these and let you know the status.
>>
>> Thanks and Regards
>> Rahul Sharma
>>
>>
>> On Tue, May 28, 2013 at 4:04 PM, JuanFra Rodriguez Cardoso <
>> juanfra.rodriguez.cardoso@xxxxxxxxx> wrote:
>>
>>> Have you tried configuring your compute nodes with the following options
>>> in file 'nova.conf'?
>>>
>>> These options could be improve your instance performance:
>>>
>>> libvirt_cpu_mode = host-passthrough
>>> libvirt_use_virtio_for_bridges = True
>>>
>>>
>>>
>>> PD: I suppose you are using:
>>>
>>> libvirt_type = kvm
>>> compute_driver = libvirt.LibvirtDriver
>>>
>>>
>>> ---
>>> JuanFra
>>>
>>>
>>> 2013/5/28 Rahul Sharma <rahulsharmaait@xxxxxxxxx>
>>>
>>>> I checked, they are fine. nslookup is giving correct result.
>>>>
>>>> root@instance1:/home/ubuntu# nslookup www.google.com
>>>> Server: 192.168.0.4
>>>> Address: 192.168.0.4#53
>>>>
>>>> Non-authoritative answer:
>>>> Name: www.google.com
>>>> Address: 74.125.135.147
>>>> Name: www.google.com
>>>> Address: 74.125.135.99
>>>> Name: www.google.com
>>>> Address: 74.125.135.103
>>>> Name: www.google.com
>>>> Address: 74.125.135.104
>>>> Name: www.google.com
>>>> Address: 74.125.135.105
>>>> Name: www.google.com
>>>> Address: 74.125.135.106
>>>>
>>>> -Regards
>>>> Rahul
>>>>
>>>>
>>>> On Tue, May 28, 2013 at 3:42 PM, Balamurugan V G <
>>>> balamuruganvg@xxxxxxxxx> wrote:
>>>>
>>>>> Check if you have the right DNS server settings on your VM. Sometimes
>>>>> even that can slow the access.
>>>>>
>>>>> Regards,
>>>>> Balu
>>>>>
>>>>> On Tue, May 28, 2013 at 3:31 PM, Rahul Sharma <
>>>>> rahulsharmaait@xxxxxxxxx> wrote:
>>>>> > Yes, I am using KVM.
>>>>> >
>>>>> > -Regards
>>>>> > Rahul Sharma
>>>>> >
>>>>> >
>>>>> > On Tue, May 28, 2013 at 2:49 PM, JuanFra Rodriguez Cardoso
>>>>> > <juanfra.rodriguez.cardoso@xxxxxxxxx> wrote:
>>>>> >>
>>>>> >> Hi:
>>>>> >>
>>>>> >> Which hypervisor are you using? KVM with virtio driver?
>>>>> >>
>>>>> >> ---
>>>>> >> JuanFra
>>>>> >>
>>>>> >>
>>>>> >> 2013/5/28 Rahul Sharma <rahulsharmaait@xxxxxxxxx>
>>>>> >>>
>>>>> >>> Hi All,
>>>>> >>>
>>>>> >>> I have a multinode setup of Openstack-Grizzly release with
>>>>> Networking
>>>>> >>> node as a separate machine. I am able to successfully bring up
>>>>> instances and
>>>>> >>> ping to google from within the instances. Everything is working
>>>>> fine except
>>>>> >>> the speed of internet access from within the instances.
>>>>> >>>
>>>>> >>> When I try to "wget <file>" or do "apt-get update", its taking a
>>>>> lot of
>>>>> >>> time(1 hr 40 mins for apt-get update). However, if I do the same
>>>>> on the
>>>>> >>> physical compute-nodes or on the network-node, it updates within
>>>>> seconds. I
>>>>> >>> am not sure why the network access within the instances is so slow
>>>>> which on
>>>>> >>> the other hand is quite fast on the hosts.
>>>>> >>>
>>>>> >>> Any pointers or steps to debug the issue would be really helpful.
>>>>> Please
>>>>> >>> let me know how I can debug this scenario.
>>>>> >>>
>>>>> >>> Thanks and Regards
>>>>> >>> Rahul Sharma
>>>>> >>>
>>>>> >>> _______________________________________________
>>>>> >>> Mailing list: https://launchpad.net/~openstack
>>>>> >>> Post to : openstack@xxxxxxxxxxxxxxxxxxx
>>>>> >>> Unsubscribe : https://launchpad.net/~openstack
>>>>> >>> More help : https://help.launchpad.net/ListHelp
>>>>> >>>
>>>>> >>
>>>>> >
>>>>> >
>>>>> > _______________________________________________
>>>>> > Mailing list: https://launchpad.net/~openstack
>>>>> > Post to : openstack@xxxxxxxxxxxxxxxxxxx
>>>>> > Unsubscribe : https://launchpad.net/~openstack
>>>>> > More help : https://help.launchpad.net/ListHelp
>>>>> >
>>>>>
>>>>
>>>>
>>>
>>
>
Follow ups
References