Thank you for the guidance, I will execute and report back if I still face trouble.
To further understand this VPC networking issue I created a Linux VM behind the VPC / ipsec VPN and I'm seeing similar poor ping times. Maybe the driver is not entirely at fault. Here is some brief analysis. *VPC Outside IP* 64 bytes from 192.64.185.238: icmp_seq=17 ttl=61 time=4.030 ms 64 bytes from 192.64.185.238: icmp_seq=18 ttl=61 time=4.245 ms 64 bytes from 192.64.185.238: icmp_seq=19 ttl=61 time=3.947 ms 64 bytes from 192.64.185.238: icmp_seq=20 ttl=61 time=4.003 ms 64 bytes from 192.64.185.238: icmp_seq=21 ttl=61 time=4.291 ms *VPC Hosted Linux Instance* 64 bytes from 192.168.0.85: icmp_seq=334 ttl=62 time=10.627 ms 64 bytes from 192.168.0.85: icmp_seq=335 ttl=62 time=8.268 ms 64 bytes from 192.168.0.85: icmp_seq=336 ttl=62 time=37.855 ms 64 bytes from 192.168.0.85: icmp_seq=337 ttl=62 time=19.595 ms 64 bytes from 192.168.0.85: icmp_seq=338 ttl=62 time=7.344 ms 64 bytes from 192.168.0.85: icmp_seq=339 ttl=62 time=49.439 ms 64 bytes from 192.168.0.85: icmp_seq=340 ttl=62 time=6.376 ms Why is the latency so terrible behind the VPC? As a test I migrated each host and the virtual router to their on individual server. Same problem. Dustin On Wed, Oct 26, 2016 at 3:22 PM, David Mabry <dma...@ena.com> wrote: > Dustin, > > Did you download the latest windows virtio drivers that are signed by > Redhat/Fedora? If not, you can find the latest stable ISOs at the > following link: > > https://fedorapeople.org/groups/virt/virtio-win/direct- > downloads/archive-virtio/virtio-win-0.1.126-2/ > > Once you get the ISO downloaded, install the drivers, shutdown the VM, > change the VM’s OS Type to be Windows PV and finally start the VM. Windows > will take a moment during this first boot to reconfigure its hardware and > any reboots after this initial one should be faster. > > Also, you can verify the drivers being used in Device Manager. Look for > devices that say RedHat Virtio, or something similar to that. > > I hope that helps. > > Thanks, > David Mabry > > From: Dustin Wright <dwri...@untangledtechnology.com> > Sent: Wednesday, October 26, 2016 8:16 AM > To: users@cloudstack.apache.org > Subject: Re: Slow Networking > > I don't work in Windows much so I might just be doing it wrong. I tried to > run drvload.exe each inf file. No luck. Is there a better way to install > the drivers so Windows will pick up and change? > > Dustin > > Sent from my iPhone > > > On Oct 26, 2016, at 9:04 AM, Simon Weller <swel...@ena.com> wrote: > > > > Dustin, > > > > > > So just to clarify here, if you install the virtIO drivers while in non > PV mode and then switching the template to Windows PV doesn't fix the > problem? > > > > > > - Si > > > > ________________________________ > > From: Dustin Wright <dwri...@untangledtechnology.com> > > Sent: Tuesday, October 25, 2016 9:44 PM > > To: users@cloudstack.apache.org > > Subject: Slow Networking > > > > Users, > > > > I am facing a problem with one client running a VPC on my HVM-backed > > CloudStack 4.5.2. The machines behind the VR get poor ping times and slow > > transfers. I think the issue is the Intel network adapter driver... > > Typically I setup Windows VM's with Windows PV as the OS type and add the > > drivers in myself. That did not happen and now they have a production > > environment running the generic Intel driver. > > > > Anyone know how to get a standard instance setup /w the additional > drivers > > so I can switch it over to Windows PV OS type? I think using the Red Hat > > VirtIO drivers will help resolve the problem. > > > > Any suggestions for converting a Windows instance to Windows PV? If I > just > > switch the OS will not boot... > > > > Any known issues with the VPC VR and general slowness? I see between 50M > ~ > > 100M max throughput and really wild latency between 10ms -> 200ms across > > the 1000mbits data center LAN. Would the default Intel driver explain > some > > of these troubles? > > > > Thanks in advance for any guidance you can provide, > > > > Dustin >
