Date: Thu, 4 Jul 2019 10:59:56 +0200 From: Christian M <christian.marcos@gmail.com> To: Karl Pielorz <kpielorz_lst@tdx.co.uk> Cc: =?UTF-8?Q?Roger_Pau_Monn=C3=A9?= <roger.pau@citrix.com>, freebsd-xen@freebsd.org, Eugene Grosbein <eugen@grosbein.net>, freebsd-net@freebsd.org Subject: Re: Very slow and inconsistent internal network speed (between, VM's on the same host) for FreeBSD 11.0+ as guest on, XCP-ng/XenServer Message-ID: <CAKwR995TYN4aa%2B7XXFxMe5Grw15nA6VR5f%2BFQVh%2BwLfVg4_BFA@mail.gmail.com> In-Reply-To: <A8BE57412B591EFA4671481B@10.12.30.106> References: <d89b2b9a-5005-c9ee-5364-9affff5fd1f5@grosbein.net> <CAKwR995FNv-QjkUQKaHw7Wb2jhA3DoiWzQ7prnA-k56qE8vifw@mail.gmail.com> <9c377fe7-5546-9e0b-fac9-076dd094cbac@grosbein.net> <CAKwR996i6ZJLt4iBFTedDNzPaO2mFt5jz3P6iFM-Y1SJ0pu_wA@mail.gmail.com> <ce1f2ebb-c0bf-73c5-f857-be6b24e71da1@grosbein.net> <CAKwR997Zjxkpr48DJ08csLobLK5u5bBY%2BKrQ8r22hdZYJUNREA@mail.gmail.com> <47bb1bfe-ac39-78d3-c9b9-17ff1896e0ec@grosbein.net> <CAKwR9968gf1RkgP7hD8XOh4Z-Ti917P6W5Lt3-Lakx6r9pei9g@mail.gmail.com> <20190627101901.3szaaxhp4xzjiay5@MacBook-Air-de-Roger.local> <CAKwR994OYS2Hjhu=QdR2DSoZVyDWEky2Nkmu_LWDQRJiggqxmA@mail.gmail.com> <20190704072354.6ycduisiidz5iy2x@Air-de-Roger> <A8BE57412B591EFA4671481B@10.12.30.106>
next in thread | previous in thread | raw e-mail | index | archive | help
>From my tests I found that 10.4-RELEASE was as fast as you could expect (>10Gbit/s), then something changed in 11.0-RELEASE and carried on and got even worse in 12.0-RELEASE. Would it not be a good idea to begin there (10.4 -> 11.0), and try to identify what changes could impact the performance drop so significantly? This is perhaps a much harder task than it sounds for someone that knows nothing about what changes was made, and how difficult it would be to identify what changes actually could be relevant. Just a thought. Regards, Christian Den tors 4 juli 2019 kl 10:39 skrev Karl Pielorz <kpielorz_lst@tdx.co.uk>: > > > --On 04 July 2019 09:23 +0200 Roger Pau Monn=C3=A9 <roger.pau@citrix.com> > wrote: > > > As a workaround you can switch to the emulated network card by > > setting 'hw.xen.disable_pv_nics=3D1' in /boot/loader.conf. That will > > give you worse performance than a fully working PV network card, but > > at least should be consistent. There are others that have switched to > > virtio-net, but I have no idea how to do that with XCP. > > Just to add my $0.02's to the conversation... > > As Roger knows we've had numerous issues with Xen xn based networking and > FreeBSD guests over the years. We currently run VirtIO (vtnet) on > XenServer > 7.1 and it solves all these issues (it's probably not quite as > 'performant' > as xn - but it's close for what we're using it with - it is miles better > than e1000 performance). > > Unfortunately in XenServer 7.6 virtio is no longer compiled into Qemu fro= m > what I can see. XCP-ng has the same issue (as it's based on XenServer) - > so > virtio is currently not an option with XCP-ng either. > > e1000/rtl8139 will solve 'weirdness' (think of VM's routing traffic, doin= g > DHCP or VPN duties) - but virtio solves the same issues, with much better > performance. > > I've posted to the XCP-ng forums asking if virtio can be enabled in XCP-n= g > builds (as this is probably more likely that getting XenServer to release > with it enabled). > > Aside from getting Xen xn 'fixed' for the cases it currently fails (no > small undertaking from what I understand) - it leaves FreeBSD pretty much > stuck, at least for some usage cases. > > > Regards, > > -Karl >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAKwR995TYN4aa%2B7XXFxMe5Grw15nA6VR5f%2BFQVh%2BwLfVg4_BFA>