From owner-freebsd-xen@freebsd.org Sun Jul 26 13:16:47 2015 Return-Path: Delivered-To: freebsd-xen@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A57F89AA3F8 for ; Sun, 26 Jul 2015 13:16:47 +0000 (UTC) (envelope-from kp@vega.codepro.be) Received: from venus.codepro.be (venus.codepro.be [IPv6:2a01:4f8:162:1127::2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.codepro.be", Issuer "Gandi Standard SSL CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 1756DCAF; Sun, 26 Jul 2015 13:16:47 +0000 (UTC) (envelope-from kp@vega.codepro.be) Received: from vega.codepro.be (unknown [172.16.1.3]) by venus.codepro.be (Postfix) with ESMTP id 77BDB11CBD; Sun, 26 Jul 2015 15:16:42 +0200 (CEST) Received: by vega.codepro.be (Postfix, from userid 1001) id 243601D4B1; Sun, 26 Jul 2015 15:16:42 +0200 (CEST) Date: Sun, 26 Jul 2015 15:16:42 +0200 From: Kristof Provost To: Colin Percival Cc: Mark Felder , freebsd-xen@freebsd.org, gnn@freebsd.org Subject: Re: Networking under Xen Message-ID: <20150726131642.GC2484@vega.codepro.be> References: <4E7B7075-4E0D-4EA7-9F5D-6D252CFBD487@gmail.com> <1436890526.3162974.323521249.6B73E6E2@webmail.messagingengine.com> <55A55AE8.4090101@freebsd.org> <1436901780.3211878.323698017.360F8D73@webmail.messagingengine.com> <20F2398D-ECDF-4CF4-966D-18C894779C4C@FreeBSD.org> <55A611B1.6000000@freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <55A611B1.6000000@freebsd.org> X-Checked-By-NSA: Probably User-Agent: Mutt/1.5.23 (2014-03-12) X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Discussion of the freebsd port to xen - implementation and usage List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 26 Jul 2015 13:16:47 -0000 On 2015-07-15 00:54:25 (-0700), Colin Percival wrote: > In my tests, deleting these lines from pf_ioctl.c > > 3570 /* We need a proper CSUM befor we start (s. OpenBSD ip_output) */ > 3571 if ((*m)->m_pkthdr.csum_flags & CSUM_DELAY_DATA) { > 3572 in_delayed_cksum(*m); > 3573 (*m)->m_pkthdr.csum_flags &= ~CSUM_DELAY_DATA; > 3574 } > > unbreaks pf+TSO on EC2 instances. I'm not entirely sure why these lines > are there in the first place, which is why I didn't want to simply go in > and remove them -- but it may be that wrapping those lines in something > like "if ((csum_flags & CSUM_TSO) == 0)" would solve the problem without > breaking anything else. > I think the reason for this checksum calculation is that pf sometimes modifies the packet, so it also updates the checksum. In case of TSO (or CSUM_TCP) that doesn't actually work because the TCP checksum is the pseudo IP(6) header checksum, not the final checksum. Starting from a full checksum the update is correct however, so that's why pf works on non-TSO interfaces. It doesn't work on Xen TSO interfaces because (I assume) it expects to get the pseudo header checksum, not the full checksum. It's not entirely clear to my why it's not broken on my hardware (which claims TSO support), but perhaps Xen is more picky than actual hardware. Adding the if (CSUM_TSO) check will improve matters, but it will still break on packets which get changed by pf (rdr/nat/...). I think the real solution is to make pf_cksum_fixup() a bit more intelligent. It should look at m->m_pkthdr.csum_flags to determine if it should touch the checksum or not. If CSUM_TCP is set we know we've got a pseudo header checksum and we shouldn't touch it unless we've modified the source or destination IP address (or length or protocol, but that's less likely). If CSUM_TCP is not set we should have a full checksum and should do the fixup as before. Actually, perhaps CSUM_DELAY_DATA is better than CSUM_TCP, because we'll have to do the same for UDP. Regards, Kristof From owner-freebsd-xen@freebsd.org Mon Jul 27 01:03:00 2015 Return-Path: Delivered-To: freebsd-xen@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C2FCD9AAA94 for ; Mon, 27 Jul 2015 01:03:00 +0000 (UTC) (envelope-from bounces+73574-0602-freebsd-xen=freebsd.org@sendgrid.net) Received: from o1.l99.sendgrid.net (o1.l99.sendgrid.net [198.37.153.74]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 874B39BA for ; Mon, 27 Jul 2015 01:03:00 +0000 (UTC) (envelope-from bounces+73574-0602-freebsd-xen=freebsd.org@sendgrid.net) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sendgrid.info; h=from:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding; s=smtpapi; bh=oFlzynLs9Izgk2zCrcjDoAC7gA4=; b=T+6ege9Qp5+/MZwqoB EbAbOcheEkoQeThJESme96EubFu28l/iSfgJjQ6gOuupsUuaAEDTWAkXiadytNCX r8NooGXDdVOfNIo7k/psYsNT0CWDMhflzGeX9iTd9OJ6l2hySThINxOMcQn/wNHw 5aeDWi0PIyZnXH37RFWW4NqQY= Received: by filter0442p1mdw1.sendgrid.net with SMTP id filter0442p1mdw1.28957.55B5833D1 2015-07-27 01:02:53.118587706 +0000 UTC Received: from mail.tarsnap.com (ec2-54-86-246-204.compute-1.amazonaws.com [54.86.246.204]) by ismtpd0003p1iad1.sendgrid.net (SG) with ESMTP id GAu2kr36TrWfbFUeDaKZtA for ; Mon, 27 Jul 2015 01:02:53 +0000 (UTC) Received: (qmail 37222 invoked from network); 27 Jul 2015 00:58:51 -0000 Received: from unknown (HELO clamshell.daemonology.net) (127.0.0.1) by ec2-107-20-205-189.compute-1.amazonaws.com with ESMTP; 27 Jul 2015 00:58:51 -0000 Received: (qmail 3370 invoked from network); 27 Jul 2015 01:01:21 -0000 Received: from unknown (HELO clamshell.daemonology.net) (127.0.0.1) by clamshell.daemonology.net with SMTP; 27 Jul 2015 01:01:21 -0000 Message-ID: <55B582E1.5070803@freebsd.org> Date: Sun, 26 Jul 2015 18:01:21 -0700 From: Colin Percival User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.7.0 MIME-Version: 1.0 To: Kristof Provost CC: Mark Felder , freebsd-xen@freebsd.org, gnn@freebsd.org Subject: Re: Networking under Xen References: <4E7B7075-4E0D-4EA7-9F5D-6D252CFBD487@gmail.com> <1436890526.3162974.323521249.6B73E6E2@webmail.messagingengine.com> <55A55AE8.4090101@freebsd.org> <1436901780.3211878.323698017.360F8D73@webmail.messagingengine.com> <20F2398D-ECDF-4CF4-966D-18C894779C4C@FreeBSD.org> <55A611B1.6000000@freebsd.org> <20150726131642.GC2484@vega.codepro.be> In-Reply-To: <20150726131642.GC2484@vega.codepro.be> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-SG-EID: RUbAm5H8PjswBj/QH+sYVehaJogg3iBnZcyVi1bw/IxTBz5nIqHF+596TznUcf7ShWYzh4sT+zszhk 0aPbjknEqQbs5EQbm5GTp+CV3g5UrdiVT/FOgJ+K4lKk2eqbGQA2skZuzB95PVPY9x567t9o12zuSf eK3ISeI6K0RrvHI= X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Discussion of the freebsd port to xen - implementation and usage List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Jul 2015 01:03:01 -0000 On 07/26/15 06:16, Kristof Provost wrote: > On 2015-07-15 00:54:25 (-0700), Colin Percival wrote: >> In my tests, deleting these lines from pf_ioctl.c >> 3570 /* We need a proper CSUM befor we start (s. OpenBSD ip_output) */ >> [...] >> unbreaks pf+TSO on EC2 instances. I'm not entirely sure why these lines >> are there in the first place, which is why I didn't want to simply go in >> and remove them -- but it may be that wrapping those lines in something >> like "if ((csum_flags & CSUM_TSO) == 0)" would solve the problem without >> breaking anything else. > > I think the reason for this checksum calculation is that pf sometimes > modifies the packet, so it also updates the checksum. Aha, this is exactly the sort of thing I was worried about. I'm glad you understand this stuff better than me. > It doesn't work on Xen TSO interfaces because (I assume) it expects to > get the pseudo header checksum, not the full checksum. > It's not entirely clear to my why it's not broken on my hardware (which > claims TSO support), but perhaps Xen is more picky than actual hardware. I'm not 100% certain about this, but I don't think Xen is doing anything with the checksum; rather, everything is being passed through to the underlying hardware, and some NICs are pickier than others. I'll refrain from commenting on your plans for fixing this since, as I mentioned above, you understand how pf and the network stack work far better than I do. :-) -- Colin Percival Security Officer Emeritus, FreeBSD | The power to serve Founder, Tarsnap | www.tarsnap.com | Online backups for the truly paranoid From owner-freebsd-xen@freebsd.org Wed Jul 29 07:00:36 2015 Return-Path: Delivered-To: freebsd-xen@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 5854D9AD527 for ; Wed, 29 Jul 2015 07:00:36 +0000 (UTC) (envelope-from kpielorz_lst@tdx.co.uk) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 42780B3F for ; Wed, 29 Jul 2015 07:00:36 +0000 (UTC) (envelope-from kpielorz_lst@tdx.co.uk) Received: by mailman.ysv.freebsd.org (Postfix) id 3F86B9AD526; Wed, 29 Jul 2015 07:00:36 +0000 (UTC) Delivered-To: xen@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 3E11C9AD525 for ; Wed, 29 Jul 2015 07:00:36 +0000 (UTC) (envelope-from kpielorz_lst@tdx.co.uk) Received: from smtp.krpservers.com (smtp.krpservers.com [62.13.128.145]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "smtp.krpservers.com", Issuer "COMODO RSA Domain Validation Secure Server CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id DEBEDB3E for ; Wed, 29 Jul 2015 07:00:32 +0000 (UTC) (envelope-from kpielorz_lst@tdx.co.uk) Received: from [10.12.30.100] (vpn01-01.tdx.co.uk [62.13.130.213]) (authenticated bits=0) by smtp.krpservers.com (8.14.9/8.14.9) with ESMTP id t6T6lSBh052967 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Wed, 29 Jul 2015 07:47:29 +0100 (BST) (envelope-from kpielorz_lst@tdx.co.uk) Date: Wed, 29 Jul 2015 07:47:28 +0100 From: Karl Pielorz To: xen@FreeBSD.org Subject: Poor network performance with Xen + OpenVPN? Message-ID: X-Mailer: Mulberry/4.0.8 (Mac OS X) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Discussion of the freebsd port to xen - implementation and usage List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 29 Jul 2015 07:00:36 -0000 Hi All, A while ago I ran into an issue with FreeBSD + Xen and networking (where FreeBSD PVHVM domU's can't "route" traffic to/from other domU's (fbsd/linux/windows) - e.g. as a default gateway). I seem to have run into what appears to be another network issue now - XenServer 6.5-SP1 +hotfixes, with FreeBSD 10.1-p4 (as PVHVM), and OpenVPN 2.3.7 Everything 'works OK' - but the performance is pretty poor. Most noticeable - if you have a browser open fetching pages via the VPN - the pages arrive very slowly, and any ssh sessions etc. are instantly put on a 'go slow', you also start getting ping timeouts when pinging hosts the other side of the VM/VPN until the pages are fetched. Swap back to a bare metal system (on the same networks) - it works fine, switch back over to the VM - and again, performance is lousy. The host running OpenVPN isn't really under any load (it's only job is running OpenVPN) - nor is it's XenServer. If I connect to another OpenVPN host which is running on an HVM FreeBSD 9.1 domU - performance is indistinguishable from the bare metal (as you'd expect considering the relatively low volumes of traffic over the VPN etc.) Can anyone suggest any fixes / where to look to try and keep it as PVHVM, and get the performance back? - as we've already got a collection of HVM machines (to work round the other network problem) - which I don't really want to add to, as they're not agile :( Cheers, -Karl From owner-freebsd-xen@freebsd.org Wed Jul 29 12:35:39 2015 Return-Path: Delivered-To: freebsd-xen@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E8E1E9AD11D for ; Wed, 29 Jul 2015 12:35:38 +0000 (UTC) (envelope-from egoitz@sarenet.es) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id D11C9C6E for ; Wed, 29 Jul 2015 12:35:38 +0000 (UTC) (envelope-from egoitz@sarenet.es) Received: by mailman.ysv.freebsd.org (Postfix) id CE0549AD11C; Wed, 29 Jul 2015 12:35:38 +0000 (UTC) Delivered-To: xen@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id CD8B79AD11A for ; Wed, 29 Jul 2015 12:35:38 +0000 (UTC) (envelope-from egoitz@sarenet.es) Received: from cu1176c.smtpx.saremail.com (cu1176c.smtpx.saremail.com [195.16.148.151]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 70FF4C6D for ; Wed, 29 Jul 2015 12:35:37 +0000 (UTC) (envelope-from egoitz@sarenet.es) Received: from [172.16.2.46] (izaro.sarenet.es [192.148.167.11]) by proxypop02.sare.net (Postfix) with ESMTPSA id 1B8469DC4AF; Wed, 29 Jul 2015 14:28:24 +0200 (CEST) Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2102\)) Subject: Re: Poor network performance with Xen + OpenVPN? From: Egoitz Aurrekoetxea In-Reply-To: Date: Wed, 29 Jul 2015 14:28:16 +0200 Cc: xen@FreeBSD.org Message-Id: <40E060AB-F0B9-48F3-9309-947CAB5C1939@sarenet.es> References: To: Karl Pielorz X-Mailer: Apple Mail (2.2102) Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.20 X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Discussion of the freebsd port to xen - implementation and usage List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 29 Jul 2015 12:35:39 -0000 Hi! Have you disabled tso, lro and friends?. Regards, Egoitz Aurrekoetxea Departamento de sistemas 944 209 470 Parque Tecnol=C3=B3gico. Edificio 103 48170 Zamudio (Bizkaia) egoitz@sarenet.es www.sarenet.es Antes de imprimir este correo electr=C3=B3nico piense si es necesario = hacerlo. > El 29/7/2015, a las 8:47, Karl Pielorz = escribi=C3=B3: >=20 >=20 > Hi All, >=20 > A while ago I ran into an issue with FreeBSD + Xen and networking = (where FreeBSD PVHVM domU's can't "route" traffic to/from other domU's = (fbsd/linux/windows) - e.g. as a default gateway). >=20 > I seem to have run into what appears to be another network issue now = - XenServer 6.5-SP1 +hotfixes, with FreeBSD 10.1-p4 (as PVHVM), and = OpenVPN 2.3.7 >=20 > Everything 'works OK' - but the performance is pretty poor. Most = noticeable - if you have a browser open fetching pages via the VPN - the = pages arrive very slowly, and any ssh sessions etc. are instantly put on = a 'go slow', you also start getting ping timeouts when pinging hosts the = other side of the VM/VPN until the pages are fetched. >=20 > Swap back to a bare metal system (on the same networks) - it works = fine, switch back over to the VM - and again, performance is lousy. >=20 > The host running OpenVPN isn't really under any load (it's only job is = running OpenVPN) - nor is it's XenServer. >=20 > If I connect to another OpenVPN host which is running on an HVM = FreeBSD 9.1 domU - performance is indistinguishable from the bare metal = (as you'd expect considering the relatively low volumes of traffic over = the VPN etc.) >=20 > Can anyone suggest any fixes / where to look to try and keep it as = PVHVM, and get the performance back? - as we've already got a collection = of HVM machines (to work round the other network problem) - which I = don't really want to add to, as they're not agile :( >=20 > Cheers, >=20 > -Karl > _______________________________________________ > freebsd-xen@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-xen > To unsubscribe, send any mail to "freebsd-xen-unsubscribe@freebsd.org" From owner-freebsd-xen@freebsd.org Wed Jul 29 13:59:51 2015 Return-Path: Delivered-To: freebsd-xen@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1214A9ACD4C for ; Wed, 29 Jul 2015 13:59:51 +0000 (UTC) (envelope-from kpielorz_lst@tdx.co.uk) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id EE0BEA44 for ; Wed, 29 Jul 2015 13:59:50 +0000 (UTC) (envelope-from kpielorz_lst@tdx.co.uk) Received: by mailman.ysv.freebsd.org (Postfix) id EB0879ACD48; Wed, 29 Jul 2015 13:59:50 +0000 (UTC) Delivered-To: xen@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id EA8B39ACD47 for ; Wed, 29 Jul 2015 13:59:50 +0000 (UTC) (envelope-from kpielorz_lst@tdx.co.uk) Received: from smtp.krpservers.com (smtp.krpservers.com [62.13.128.145]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "smtp.krpservers.com", Issuer "COMODO RSA Domain Validation Secure Server CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 77DE7A43 for ; Wed, 29 Jul 2015 13:59:49 +0000 (UTC) (envelope-from kpielorz_lst@tdx.co.uk) Received: from [10.12.30.106] (vpn01-01.tdx.co.uk [62.13.130.213]) (authenticated bits=0) by smtp.krpservers.com (8.14.9/8.14.9) with ESMTP id t6TDxcBM081327 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 29 Jul 2015 14:59:43 +0100 (BST) (envelope-from kpielorz_lst@tdx.co.uk) Date: Wed, 29 Jul 2015 14:58:50 +0100 From: Karl Pielorz To: Egoitz Aurrekoetxea cc: xen@FreeBSD.org Subject: Re: Poor network performance with Xen + OpenVPN? Message-ID: <5A7F36D35FF28CD4B9D2DE92@[10.12.30.106]> In-Reply-To: <40E060AB-F0B9-48F3-9309-947CAB5C1939@sarenet.es> References: <40E060AB-F0B9-48F3-9309-947CAB5C1939@sarenet.es> X-Mailer: Mulberry/4.0.8 (Win32) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Discussion of the freebsd port to xen - implementation and usage List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 29 Jul 2015 13:59:51 -0000 --On 29 July 2015 14:28 +0200 Egoitz Aurrekoetxea wrote: > Hi! > > Have you disabled tso, lro and friends?. > If by that you mean, ifconfig xn0 -rxcsum -txcsum -tso4 -lro Yes - I've tried that on the virtual host running OpenVPN, it didn't seem to make any difference :( I'll hopefully get some more time later to look at it again. Regards, -Karl From owner-freebsd-xen@freebsd.org Thu Jul 30 09:41:26 2015 Return-Path: Delivered-To: freebsd-xen@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 918309AEBF9 for ; Thu, 30 Jul 2015 09:41:26 +0000 (UTC) (envelope-from seanrees@gmail.com) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 7099469B for ; Thu, 30 Jul 2015 09:41:26 +0000 (UTC) (envelope-from seanrees@gmail.com) Received: by mailman.ysv.freebsd.org (Postfix) id 6F8FE9AEBF8; Thu, 30 Jul 2015 09:41:26 +0000 (UTC) Delivered-To: xen@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 55FFD9AEBF6 for ; Thu, 30 Jul 2015 09:41:26 +0000 (UTC) (envelope-from seanrees@gmail.com) Received: from mail-wi0-x230.google.com (mail-wi0-x230.google.com [IPv6:2a00:1450:400c:c05::230]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id ED6E0696 for ; Thu, 30 Jul 2015 09:41:22 +0000 (UTC) (envelope-from seanrees@gmail.com) Received: by wibud3 with SMTP id ud3so13634656wib.1 for ; Thu, 30 Jul 2015 02:41:21 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=YynCTeCqCkYfBCH5/LOewcB/Y8h8YCz9ZMZLF/xMXtU=; b=Wt1zgmi0A3gLU4JCi3Hk/BBx5uiKnXxNUWGffKHqOXTRWKzWEt9bkuWb+PfrUkliLx P3d1k5rhQ3cnLpvBDkDQGxiGm5vyPZqi4c/HpM6eSmQhgyL2Lkn1pTk27Ha3ijNu7NXz nIKhRwsj00W1JAhf5GPn8HkQKn8+W2TvZhWe+I+Uu5CoDr1sx5Q0XcfX2yIEEapTZjAW zyi9ZFoZOlIBG2/4t/TyL8WgfbEC/WFqr5VEc7DINdAoCX2217FO5jmEhbjuM6+5hEdj kofLCld/yP1ESOCFAV7MqTIc8VWouw0Lc7+mF9Jw0ugKWDrFrHDeAOQSOVT+fEQ3EDs6 6ZEg== MIME-Version: 1.0 X-Received: by 10.194.122.132 with SMTP id ls4mr82087922wjb.130.1438249281293; Thu, 30 Jul 2015 02:41:21 -0700 (PDT) Received: by 10.28.99.193 with HTTP; Thu, 30 Jul 2015 02:41:21 -0700 (PDT) In-Reply-To: <5A7F36D35FF28CD4B9D2DE92@10.12.30.106> References: <40E060AB-F0B9-48F3-9309-947CAB5C1939@sarenet.es> <5A7F36D35FF28CD4B9D2DE92@10.12.30.106> Date: Thu, 30 Jul 2015 10:41:21 +0100 Message-ID: Subject: Re: Poor network performance with Xen + OpenVPN? From: "seanrees@gmail.com" To: Karl Pielorz Cc: Egoitz Aurrekoetxea , "freebsd-xen@freebsd.org" Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.20 X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Discussion of the freebsd port to xen - implementation and usage List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 30 Jul 2015 09:41:26 -0000 I have the same issue. I managed to track it down to a difference between somewhere between Xen 3.4 and 4.4 (my provider uses both). 3.4 works fine (I can sustain a few mbps through OpenVPN). 4.4 I get ~0.05mbps max. I wasn't able to track it down. Both with the virtual drivers (if_xn) with all combinations of tso, lro, rxcsum and txcsum on/off tested. Sean On Wed, Jul 29, 2015 at 2:58 PM, Karl Pielorz wrote: > > > --On 29 July 2015 14:28 +0200 Egoitz Aurrekoetxea > wrote: > > Hi! >> >> Have you disabled tso, lro and friends?. >> >> > If by that you mean, > > ifconfig xn0 -rxcsum -txcsum -tso4 -lro > > Yes - I've tried that on the virtual host running OpenVPN, it didn't seem > to make any difference :( > > I'll hopefully get some more time later to look at it again. > > Regards, > > -Karl > _______________________________________________ > freebsd-xen@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-xen > To unsubscribe, send any mail to "freebsd-xen-unsubscribe@freebsd.org" > From owner-freebsd-xen@freebsd.org Fri Jul 31 13:47:25 2015 Return-Path: Delivered-To: freebsd-xen@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 2A1289AE6DD for ; Fri, 31 Jul 2015 13:47:25 +0000 (UTC) (envelope-from kpielorz_lst@tdx.co.uk) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 142A9197F for ; Fri, 31 Jul 2015 13:47:25 +0000 (UTC) (envelope-from kpielorz_lst@tdx.co.uk) Received: by mailman.ysv.freebsd.org (Postfix) id 112D29AE6DB; Fri, 31 Jul 2015 13:47:25 +0000 (UTC) Delivered-To: xen@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0F9A99AE6D9 for ; Fri, 31 Jul 2015 13:47:25 +0000 (UTC) (envelope-from kpielorz_lst@tdx.co.uk) Received: from smtp.krpservers.com (smtp.krpservers.com [62.13.128.145]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "smtp.krpservers.com", Issuer "COMODO RSA Domain Validation Secure Server CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id A235B197E for ; Fri, 31 Jul 2015 13:47:23 +0000 (UTC) (envelope-from kpielorz_lst@tdx.co.uk) Received: from [10.12.30.106] (vpn01-01.tdx.co.uk [62.13.130.213]) (authenticated bits=0) by smtp.krpservers.com (8.14.9/8.14.9) with ESMTP id t6VDl8w2071380 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Fri, 31 Jul 2015 14:47:09 +0100 (BST) (envelope-from kpielorz_lst@tdx.co.uk) Date: Fri, 31 Jul 2015 14:47:00 +0100 From: Karl Pielorz To: xen@FreeBSD.org Subject: Boot FreeBSD 10 in HVM mode under Xen? Message-ID: X-Mailer: Mulberry/4.0.8 (Win32) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Discussion of the freebsd port to xen - implementation and usage List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 31 Jul 2015 13:47:25 -0000 Hi, Is there any way of booting FreeBSD 10.x as HVM under Xen? I've tried removing, options XENHVM device xenpci >From the kernel - but this just panics on boot now. seems to suggest you can no longer boot 10 under Xen as HVM? If I can't boot HVM, I can't get HVM network support (i.e. Realtek) - and I can't get that, all the VM's I have to run as HVM due to a number of xen/freebsd/network oddities can't be 10.x machines :( This is painting those roles/systems into non-agile HVM 9.x boxes that have no upgrade path now :( Unless there's a workaround to ditch xn and replace it with re and / or boot HVM under FreeBSD 10? -Karl From owner-freebsd-xen@freebsd.org Fri Jul 31 14:18:49 2015 Return-Path: Delivered-To: freebsd-xen@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C2F589AECE6 for ; Fri, 31 Jul 2015 14:18:49 +0000 (UTC) (envelope-from jeroen@dckd.nl) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id AD6C31B1B for ; Fri, 31 Jul 2015 14:18:49 +0000 (UTC) (envelope-from jeroen@dckd.nl) Received: by mailman.ysv.freebsd.org (Postfix) id AA4849AECE5; Fri, 31 Jul 2015 14:18:49 +0000 (UTC) Delivered-To: xen@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A9E029AECE4 for ; Fri, 31 Jul 2015 14:18:49 +0000 (UTC) (envelope-from jeroen@dckd.nl) Received: from positron.dckd.nl (positron.dckd.nl [IPv6:2a02:898:62:f6::63]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 73E9B1B1A for ; Fri, 31 Jul 2015 14:18:49 +0000 (UTC) (envelope-from jeroen@dckd.nl) Received: from [172.16.34.199] (unknown [213.154.252.196]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by positron.dckd.nl (Postfix) with ESMTPSA id E15FD29F3B; Fri, 31 Jul 2015 16:18:37 +0200 (CEST) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2102\)) Subject: Re: Boot FreeBSD 10 in HVM mode under Xen? From: Jeroen van der Ham In-Reply-To: Date: Fri, 31 Jul 2015 16:18:37 +0200 Cc: xen@FreeBSD.org Content-Transfer-Encoding: quoted-printable Message-Id: References: To: Karl Pielorz X-Mailer: Apple Mail (2.2102) X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Discussion of the freebsd port to xen - implementation and usage List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 31 Jul 2015 14:18:49 -0000 Hi Karl, You=E2=80=99re running into the exact same issue as I did. There is way = too much outdated documentation. I=E2=80=99ve attempted to contribute a fix: = https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D201787 That bug report contains a working configuration for a VPS that is = running FreeBSD 10 in HVM mode, with a vanilla kernel (HVM support has = been merged already in the 10-RELEASE kernel) Regards, Jeroen. From owner-freebsd-xen@freebsd.org Fri Jul 31 14:19:08 2015 Return-Path: Delivered-To: freebsd-xen@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 476929AECFA for ; Fri, 31 Jul 2015 14:19:08 +0000 (UTC) (envelope-from prvs=6471f8e05=roger.pau@citrix.com) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 322451B43 for ; Fri, 31 Jul 2015 14:19:08 +0000 (UTC) (envelope-from prvs=6471f8e05=roger.pau@citrix.com) Received: by mailman.ysv.freebsd.org (Postfix) id 312849AECF9; Fri, 31 Jul 2015 14:19:08 +0000 (UTC) Delivered-To: xen@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 30C4B9AECF8 for ; Fri, 31 Jul 2015 14:19:08 +0000 (UTC) (envelope-from prvs=6471f8e05=roger.pau@citrix.com) Received: from SMTP02.CITRIX.COM (smtp02.citrix.com [66.165.176.63]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "mail.citrix.com", Issuer "Verizon Public SureServer CA G14-SHA2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id DD9801B41 for ; Fri, 31 Jul 2015 14:19:07 +0000 (UTC) (envelope-from prvs=6471f8e05=roger.pau@citrix.com) X-IronPort-AV: E=Sophos;i="5.15,584,1432598400"; d="scan'208";a="289819194" Message-ID: <55BB8392.4050000@citrix.com> Date: Fri, 31 Jul 2015 16:17:54 +0200 From: =?windows-1252?Q?Roger_Pau_Monn=E9?= User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:31.0) Gecko/20100101 Thunderbird/31.7.0 MIME-Version: 1.0 To: Karl Pielorz , Subject: Re: Boot FreeBSD 10 in HVM mode under Xen? References: In-Reply-To: Content-Type: text/plain; charset="windows-1252" Content-Transfer-Encoding: 7bit X-DLP: MIA2 X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Discussion of the freebsd port to xen - implementation and usage List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 31 Jul 2015 14:19:08 -0000 El 31/07/15 a les 15.47, Karl Pielorz ha escrit: > > Hi, > > Is there any way of booting FreeBSD 10.x as HVM under Xen? > > I've tried removing, > > options XENHVM > device xenpci > >> From the kernel - but this just panics on boot now. This is a bug then. You should be able to boot without XENHVM/xenpci, and get a pure HVM guest with no PV devices at all. > seems to suggest you can no > longer boot 10 under Xen as HVM? > > If I can't boot HVM, I can't get HVM network support (i.e. Realtek) - > and I can't get that, all the VM's I have to run as HVM due to a number > of xen/freebsd/network oddities can't be 10.x machines :( Since this seems to be getting quite popular (booting without PV devices), I think adding a sysctl to disable PV nics and PV hard drives would be interesting. We could still use some of the PV goodies, like the timer. > This is painting those roles/systems into non-agile HVM 9.x boxes that > have no upgrade path now :( > > Unless there's a workaround to ditch xn and replace it with re and / or > boot HVM under FreeBSD 10? I will deal with this ASAP. Roger. From owner-freebsd-xen@freebsd.org Fri Jul 31 14:28:37 2015 Return-Path: Delivered-To: freebsd-xen@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1DDB69AEF1E for ; Fri, 31 Jul 2015 14:28:37 +0000 (UTC) (envelope-from mcdouga9@egr.msu.edu) Received: from mail.egr.msu.edu (hill.egr.msu.edu [35.9.37.163]) by mx1.freebsd.org (Postfix) with ESMTP id ED4CC1F16 for ; Fri, 31 Jul 2015 14:28:36 +0000 (UTC) (envelope-from mcdouga9@egr.msu.edu) Received: from hill (localhost [127.0.0.1]) by mail.egr.msu.edu (Postfix) with ESMTP id 1D1A952DC7 for ; Fri, 31 Jul 2015 10:18:31 -0400 (EDT) X-Virus-Scanned: amavisd-new at egr.msu.edu Received: from mail.egr.msu.edu ([127.0.0.1]) by hill (hill.egr.msu.edu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hMgVlQqtvo-Q for ; Fri, 31 Jul 2015 10:18:30 -0400 (EDT) Received: from EGR authenticated sender mcdouga9 Subject: Re: Boot FreeBSD 10 in HVM mode under Xen? To: freebsd-xen@freebsd.org References: From: Adam McDougall Message-ID: <55BB83B6.6010808@egr.msu.edu> Date: Fri, 31 Jul 2015 10:18:30 -0400 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:38.0) Gecko/20100101 Thunderbird/38.1.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Discussion of the freebsd port to xen - implementation and usage List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 31 Jul 2015 14:28:37 -0000 On 07/31/2015 09:47, Karl Pielorz wrote: > > Hi, > > Is there any way of booting FreeBSD 10.x as HVM under Xen? > > I've tried removing, > > options XENHVM > device xenpci > >> From the kernel - but this just panics on boot now. > > seems to suggest you can no > longer boot 10 under Xen as HVM? > > If I can't boot HVM, I can't get HVM network support (i.e. Realtek) - > and I can't get that, all the VM's I have to run as HVM due to a number > of xen/freebsd/network oddities can't be 10.x machines :( > > This is painting those roles/systems into non-agile HVM 9.x boxes that > have no upgrade path now :( > > Unless there's a workaround to ditch xn and replace it with re and / or > boot HVM under FreeBSD 10? > > -Karl I use a custom kernel config containing: include MYNORMALCONFIGFILE ident SPECIALCONFIG nooptions XENHVM nodevice xenpci The system running that is 10.1-STABLE #0 r283511 from May 24 2015. It previously ran an earlier build, probably from March or Jan. re0 is available with this config. From owner-freebsd-xen@freebsd.org Fri Jul 31 14:38:48 2015 Return-Path: Delivered-To: freebsd-xen@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id DA2A19AF13A for ; Fri, 31 Jul 2015 14:38:48 +0000 (UTC) (envelope-from kpielorz_lst@tdx.co.uk) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id BDA4718D0 for ; Fri, 31 Jul 2015 14:38:48 +0000 (UTC) (envelope-from kpielorz_lst@tdx.co.uk) Received: by mailman.ysv.freebsd.org (Postfix) id BC8149AF139; Fri, 31 Jul 2015 14:38:48 +0000 (UTC) Delivered-To: xen@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id BC18A9AF138 for ; Fri, 31 Jul 2015 14:38:48 +0000 (UTC) (envelope-from kpielorz_lst@tdx.co.uk) Received: from smtp.krpservers.com (smtp.krpservers.com [62.13.128.145]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "smtp.krpservers.com", Issuer "COMODO RSA Domain Validation Secure Server CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 5F6D618CF for ; Fri, 31 Jul 2015 14:38:47 +0000 (UTC) (envelope-from kpielorz_lst@tdx.co.uk) Received: from [10.12.30.106] (vpn01-01.tdx.co.uk [62.13.130.213]) (authenticated bits=0) by smtp.krpservers.com (8.14.9/8.14.9) with ESMTP id t6VEclU0074850 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 31 Jul 2015 15:38:48 +0100 (BST) (envelope-from kpielorz_lst@tdx.co.uk) Date: Fri, 31 Jul 2015 15:38:39 +0100 From: Karl Pielorz To: =?UTF-8?Q?Roger_Pau_Monn=C3=A9?= , xen@FreeBSD.org Subject: Re: Boot FreeBSD 10 in HVM mode under Xen? Message-ID: In-Reply-To: <55BB8392.4050000@citrix.com> References: <55BB8392.4050000@citrix.com> X-Mailer: Mulberry/4.0.8 (Win32) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: quoted-printable Content-Disposition: inline X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Discussion of the freebsd port to xen - implementation and usage List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 31 Jul 2015 14:38:48 -0000 --On 31 July 2015 16:17 +0200 Roger Pau Monn=C3=A9 = wrote: > This is a bug then. You should be able to boot without XENHVM/xenpci, > and get a pure HVM guest with no PV devices at all. I'm just setting up another less critical system to reproduce it. To=20 confirm, I just take GENERIC and remove 'XENHVM' and 'xenpci', and it=20 should boot without PV. I'll post the results / panic & exact versions when I get it (though some=20 goes off the top of the console =3D could be interesting). > Since this seems to be getting quite popular (booting without PV > devices), I think adding a sysctl to disable PV nics and PV hard drives > would be interesting. We could still use some of the PV goodies, like > the timer. Can you technically have a system that has HVM network (i.e. realtek) but=20 still has disk PV, and/or is agile? (i.e. can run xen-tools)? That'd kind of be a 'perfect' workaround for all our network woes (openvpn, = routing etc.) at the moment - even if the performance of HVM re0 isn't as=20 good as a PV xn0 Cheers, -Karl From owner-freebsd-xen@freebsd.org Fri Jul 31 14:59:57 2015 Return-Path: Delivered-To: freebsd-xen@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 984D69AF71B for ; Fri, 31 Jul 2015 14:59:57 +0000 (UTC) (envelope-from kpielorz_lst@tdx.co.uk) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 80FE41BDA for ; Fri, 31 Jul 2015 14:59:57 +0000 (UTC) (envelope-from kpielorz_lst@tdx.co.uk) Received: by mailman.ysv.freebsd.org (Postfix) id 7D8879AF71A; Fri, 31 Jul 2015 14:59:57 +0000 (UTC) Delivered-To: xen@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 7D1B19AF719 for ; Fri, 31 Jul 2015 14:59:57 +0000 (UTC) (envelope-from kpielorz_lst@tdx.co.uk) Received: from smtp.krpservers.com (smtp.krpservers.com [62.13.128.145]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "smtp.krpservers.com", Issuer "COMODO RSA Domain Validation Secure Server CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 069461BD9 for ; Fri, 31 Jul 2015 14:59:56 +0000 (UTC) (envelope-from kpielorz_lst@tdx.co.uk) Received: from [10.12.30.106] (vpn01-01.tdx.co.uk [62.13.130.213]) (authenticated bits=0) by smtp.krpservers.com (8.14.9/8.14.9) with ESMTP id t6VExvTR076252 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 31 Jul 2015 15:59:58 +0100 (BST) (envelope-from kpielorz_lst@tdx.co.uk) Date: Fri, 31 Jul 2015 15:59:49 +0100 From: Karl Pielorz To: =?UTF-8?Q?Roger_Pau_Monn=C3=A9?= , xen@FreeBSD.org Subject: Re: Boot FreeBSD 10 in HVM mode under Xen? Message-ID: <32FBD53695D759928A181828@[10.12.30.106]> In-Reply-To: <55BB8392.4050000@citrix.com> References: <55BB8392.4050000@citrix.com> X-Mailer: Mulberry/4.0.8 (Win32) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: quoted-printable Content-Disposition: inline X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Discussion of the freebsd port to xen - implementation and usage List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 31 Jul 2015 14:59:57 -0000 --On 31 July 2015 16:17 +0200 Roger Pau Monn=C3=A9 = wrote: > This is a bug then. You should be able to boot without XENHVM/xenpci, > and get a pure HVM guest with no PV devices at all. After removing XENHVM and xenpci - booting a FreeBSD 10.1-p8 AMD64 kernel=20 under XenServer 6.5 gets the output below (first few lines scroll off the=20 console in XenServer). " cpuid =3D 0; apic id =3D 00 instruction pointer =3D 0x20:0xffffffff80d96af9 stack pointer =3D 0x28:0xffffffff8191bbe0 frame pointer =3D 0x28:0xffffffff8191bbf0 code segment =3D base 0x0, limit 0xfffff, type 0x1b =3D DPL 0, pres 1, long 1, def32 0, gran 1 processor eflags =3D interrupt enabled, IOPL =3D 0 current process =3D 0 (swapper) trap number =3D 9 panic: general protection fault cpuid =3D 0 KDB: strack backtrace: #0 0xffffffff80946ae0 at kdb_backtrace+0x60 #1 0xffffffff8090bc05 at panic+0x155 #2 0xffffffff80d02aef at trap_fatal+0x38f #3 0xffffffff80d0274c at trap+0x75c #4 0xffffffff80ce8432 at calltrap+0x8 #5 0xffffffff80918e1f at tc_init+0x23f #6 0xffffffff80d967a1 at hv_vmbus_init+0x191 #7 0xffffffff80d9735e at vmbus_bus_init+0x1e #8 0xffffffff808bad38 at mi_startup+0x108 #9 0xffffffff802d9f0c at btext+0x2c " I'll try rebuilding it with debugger support (it's been a while). Cheers, -Karl From owner-freebsd-xen@freebsd.org Fri Jul 31 15:01:11 2015 Return-Path: Delivered-To: freebsd-xen@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 8A8199AF744 for ; Fri, 31 Jul 2015 15:01:11 +0000 (UTC) (envelope-from prvs=6471f8e05=roger.pau@citrix.com) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 74C611D66 for ; Fri, 31 Jul 2015 15:01:11 +0000 (UTC) (envelope-from prvs=6471f8e05=roger.pau@citrix.com) Received: by mailman.ysv.freebsd.org (Postfix) id 733869AF743; Fri, 31 Jul 2015 15:01:11 +0000 (UTC) Delivered-To: xen@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 72CB49AF742 for ; Fri, 31 Jul 2015 15:01:11 +0000 (UTC) (envelope-from prvs=6471f8e05=roger.pau@citrix.com) Received: from SMTP02.CITRIX.COM (smtp02.citrix.com [66.165.176.63]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "mail.citrix.com", Issuer "Verizon Public SureServer CA G14-SHA2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 2AAC71D65 for ; Fri, 31 Jul 2015 15:01:10 +0000 (UTC) (envelope-from prvs=6471f8e05=roger.pau@citrix.com) X-IronPort-AV: E=Sophos;i="5.15,585,1432598400"; d="scan'208";a="289838299" Message-ID: <55BB8DB2.6040705@citrix.com> Date: Fri, 31 Jul 2015 17:01:06 +0200 From: =?UTF-8?B?Um9nZXIgUGF1IE1vbm7DqQ==?= User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:31.0) Gecko/20100101 Thunderbird/31.7.0 MIME-Version: 1.0 To: Karl Pielorz , Subject: Re: Boot FreeBSD 10 in HVM mode under Xen? References: <55BB8392.4050000@citrix.com> In-Reply-To: Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-DLP: MIA2 X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Discussion of the freebsd port to xen - implementation and usage List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 31 Jul 2015 15:01:11 -0000 El 31/07/15 a les 16.38, Karl Pielorz ha escrit: > > > --On 31 July 2015 16:17 +0200 Roger Pau Monné wrote: > >> This is a bug then. You should be able to boot without XENHVM/xenpci, >> and get a pure HVM guest with no PV devices at all. > > I'm just setting up another less critical system to reproduce it. To > confirm, I just take GENERIC and remove 'XENHVM' and 'xenpci', and it > should boot without PV. > > I'll post the results / panic & exact versions when I get it (though > some goes off the top of the console = could be interesting). Could you setup the serial console on FreeBSD following: https://www.freebsd.org/doc/handbook/serialconsole-setup.html Then add serial='pty' to your config file and create the domain using `xl create -c `. This way you can get the full serial output. > >> Since this seems to be getting quite popular (booting without PV >> devices), I think adding a sysctl to disable PV nics and PV hard drives >> would be interesting. We could still use some of the PV goodies, like >> the timer. > > Can you technically have a system that has HVM network (i.e. realtek) > but still has disk PV, and/or is agile? (i.e. can run xen-tools)? > > That'd kind of be a 'perfect' workaround for all our network woes > (openvpn, routing etc.) at the moment - even if the performance of HVM > re0 isn't as good as a PV xn0 Yes, this is certainly possible. IIRC I posted a patch to the freebsd-xen mailing list in order to do that. I will try to find/refresh it and post it again so you can try it. It might have to wait until Monday however, since I'm quite busy today. Roger. From owner-freebsd-xen@freebsd.org Fri Jul 31 15:03:44 2015 Return-Path: Delivered-To: freebsd-xen@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A33EC9AF8AF for ; Fri, 31 Jul 2015 15:03:44 +0000 (UTC) (envelope-from syd.meyer@gmail.com) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 827451EF5 for ; Fri, 31 Jul 2015 15:03:44 +0000 (UTC) (envelope-from syd.meyer@gmail.com) Received: by mailman.ysv.freebsd.org (Postfix) id 7ED869AF8AE; Fri, 31 Jul 2015 15:03:44 +0000 (UTC) Delivered-To: xen@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 660B19AF8AD for ; Fri, 31 Jul 2015 15:03:44 +0000 (UTC) (envelope-from syd.meyer@gmail.com) Received: from mail-wi0-x232.google.com (mail-wi0-x232.google.com [IPv6:2a00:1450:400c:c05::232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 0177C1EF4 for ; Fri, 31 Jul 2015 15:03:43 +0000 (UTC) (envelope-from syd.meyer@gmail.com) Received: by wicgj17 with SMTP id gj17so21753308wic.1 for ; Fri, 31 Jul 2015 08:03:42 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date :content-transfer-encoding:message-id:references:to; bh=r+5LHjgdXhprGlofOC840RNaKdOhvPXTCtNd9Cu/sXM=; b=VOEknDg+UGWqSL2AhszFhiE2sBHoKnpBwNWAhBgEo4RRISNXBZCdDoATLVTaSeSQcR v52f7eMJTa3Skx6ZmMYuwG8i7a1EvyX13Bb8/wx6WW6Cj0qzW8zG1jZHizTAG4NrIy+s tP5avjpQy+kl58xkMp1A/M3mdxbGKPY0HKOU//zetbKB5LIi3zRFaG1XuwSr1PakhewH lZtytejFiBosOL8pKHelGXhXRobU3IWXM8OrF3TwrwviVdeg60zbz75J4w+N1TKDqlsf hdsy7REM0l2AKCvH8WeaMRLewJCDbkkYxfjXSii8ziJ8ukPyols1g9v5iiySucWNaWgH jVQg== X-Received: by 10.180.76.232 with SMTP id n8mr8019663wiw.72.1438355022507; Fri, 31 Jul 2015 08:03:42 -0700 (PDT) Received: from ?IPv6:2a02:a03f:aff:5c00:9f9:b743:4cf4:bd85? ([2a02:a03f:aff:5c00:9f9:b743:4cf4:bd85]) by smtp.gmail.com with ESMTPSA id eu2sm4918909wic.8.2015.07.31.08.03.41 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 31 Jul 2015 08:03:41 -0700 (PDT) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 9.0 \(3073\)) Subject: Re: Boot FreeBSD 10 in HVM mode under Xen? From: Sydney Meyer In-Reply-To: <32FBD53695D759928A181828@[10.12.30.106]> Date: Fri, 31 Jul 2015 17:03:39 +0200 Content-Transfer-Encoding: quoted-printable Message-Id: References: <55BB8392.4050000@citrix.com> <32FBD53695D759928A181828@[10.12.30.106]> To: xen@FreeBSD.org X-Mailer: Apple Mail (2.3073) X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Discussion of the freebsd port to xen - implementation and usage List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 31 Jul 2015 15:03:44 -0000 If you have access to the hypervisor, you could also set = "xen_platform_pci=3D0" in the DomU's config. > On 31 Jul 2015, at 16:59, Karl Pielorz wrote: >=20 >=20 >=20 > --On 31 July 2015 16:17 +0200 Roger Pau Monn=C3=A9 = wrote: >=20 >> This is a bug then. You should be able to boot without XENHVM/xenpci, >> and get a pure HVM guest with no PV devices at all. >=20 > After removing XENHVM and xenpci - booting a FreeBSD 10.1-p8 AMD64 = kernel under XenServer 6.5 gets the output below (first few lines scroll = off the console in XenServer). >=20 > " > cpuid =3D 0; apic id =3D 00 > instruction pointer =3D 0x20:0xffffffff80d96af9 > stack pointer =3D 0x28:0xffffffff8191bbe0 > frame pointer =3D 0x28:0xffffffff8191bbf0 > code segment =3D base 0x0, limit 0xfffff, type 0x1b > =3D DPL 0, pres 1, long 1, def32 0, gran 1 > processor eflags =3D interrupt enabled, IOPL =3D 0 > current process =3D 0 (swapper) > trap number =3D 9 > panic: general protection fault > cpuid =3D 0 > KDB: strack backtrace: > #0 0xffffffff80946ae0 at kdb_backtrace+0x60 > #1 0xffffffff8090bc05 at panic+0x155 > #2 0xffffffff80d02aef at trap_fatal+0x38f > #3 0xffffffff80d0274c at trap+0x75c > #4 0xffffffff80ce8432 at calltrap+0x8 > #5 0xffffffff80918e1f at tc_init+0x23f > #6 0xffffffff80d967a1 at hv_vmbus_init+0x191 > #7 0xffffffff80d9735e at vmbus_bus_init+0x1e > #8 0xffffffff808bad38 at mi_startup+0x108 > #9 0xffffffff802d9f0c at btext+0x2c > " >=20 >=20 > I'll try rebuilding it with debugger support (it's been a while). >=20 > Cheers, >=20 > -Karl > _______________________________________________ > freebsd-xen@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-xen > To unsubscribe, send any mail to "freebsd-xen-unsubscribe@freebsd.org" From owner-freebsd-xen@freebsd.org Fri Jul 31 15:10:50 2015 Return-Path: Delivered-To: freebsd-xen@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 77F0C9AFA62 for ; Fri, 31 Jul 2015 15:10:50 +0000 (UTC) (envelope-from prvs=6471f8e05=roger.pau@citrix.com) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 6268E11D3 for ; Fri, 31 Jul 2015 15:10:50 +0000 (UTC) (envelope-from prvs=6471f8e05=roger.pau@citrix.com) Received: by mailman.ysv.freebsd.org (Postfix) id 610BA9AFA60; Fri, 31 Jul 2015 15:10:50 +0000 (UTC) Delivered-To: xen@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 60A569AFA5E for ; Fri, 31 Jul 2015 15:10:50 +0000 (UTC) (envelope-from prvs=6471f8e05=roger.pau@citrix.com) Received: from SMTP.CITRIX.COM (smtp.citrix.com [66.165.176.89]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "mail.citrix.com", Issuer "Verizon Public SureServer CA G14-SHA2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 1976611D0 for ; Fri, 31 Jul 2015 15:10:49 +0000 (UTC) (envelope-from prvs=6471f8e05=roger.pau@citrix.com) X-IronPort-AV: E=Sophos;i="5.15,585,1432598400"; d="scan'208";a="286601885" Message-ID: <55BB8F9B.2040301@citrix.com> Date: Fri, 31 Jul 2015 17:09:15 +0200 From: =?UTF-8?B?Um9nZXIgUGF1IE1vbm7DqQ==?= User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:31.0) Gecko/20100101 Thunderbird/31.7.0 MIME-Version: 1.0 To: Karl Pielorz , Subject: Re: Boot FreeBSD 10 in HVM mode under Xen? References: <55BB8392.4050000@citrix.com> <32FBD53695D759928A181828@[10.12.30.106]> In-Reply-To: <32FBD53695D759928A181828@[10.12.30.106]> Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-DLP: MIA2 X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Discussion of the freebsd port to xen - implementation and usage List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 31 Jul 2015 15:10:50 -0000 El 31/07/15 a les 16.59, Karl Pielorz ha escrit: > > > --On 31 July 2015 16:17 +0200 Roger Pau Monné wrote: > >> This is a bug then. You should be able to boot without XENHVM/xenpci, >> and get a pure HVM guest with no PV devices at all. > > After removing XENHVM and xenpci - booting a FreeBSD 10.1-p8 AMD64 > kernel under XenServer 6.5 gets the output below (first few lines scroll > off the console in XenServer). > > " > cpuid = 0; apic id = 00 > instruction pointer = 0x20:0xffffffff80d96af9 > stack pointer = 0x28:0xffffffff8191bbe0 > frame pointer = 0x28:0xffffffff8191bbf0 > code segment = base 0x0, limit 0xfffff, type 0x1b > = DPL 0, pres 1, long 1, def32 0, gran 1 > processor eflags = interrupt enabled, IOPL = 0 > current process = 0 (swapper) > trap number = 9 > panic: general protection fault > cpuid = 0 > KDB: strack backtrace: > #0 0xffffffff80946ae0 at kdb_backtrace+0x60 > #1 0xffffffff8090bc05 at panic+0x155 > #2 0xffffffff80d02aef at trap_fatal+0x38f > #3 0xffffffff80d0274c at trap+0x75c > #4 0xffffffff80ce8432 at calltrap+0x8 > #5 0xffffffff80918e1f at tc_init+0x23f > #6 0xffffffff80d967a1 at hv_vmbus_init+0x191 > #7 0xffffffff80d9735e at vmbus_bus_init+0x1e > #8 0xffffffff808bad38 at mi_startup+0x108 > #9 0xffffffff802d9f0c at btext+0x2c > " Ouch, I guess this is the Xen HyperV support badly interacting with FreeBSD again. XenServer enables the "viridian" extensions by default, which really messes up with FreeBSD. You should be able to disable the extensions by hand, as reported in: https://lists.freebsd.org/pipermail/freebsd-xen/2013-October/001756.html But we need a proper way to sort this out anyway. Roger. From owner-freebsd-xen@freebsd.org Fri Jul 31 15:22:28 2015 Return-Path: Delivered-To: freebsd-xen@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 251AF9AFED1 for ; Fri, 31 Jul 2015 15:22:28 +0000 (UTC) (envelope-from kpielorz_lst@tdx.co.uk) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 0D2921142 for ; Fri, 31 Jul 2015 15:22:28 +0000 (UTC) (envelope-from kpielorz_lst@tdx.co.uk) Received: by mailman.ysv.freebsd.org (Postfix) id 0BA0E9AFED0; Fri, 31 Jul 2015 15:22:28 +0000 (UTC) Delivered-To: xen@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0B3C69AFECE for ; Fri, 31 Jul 2015 15:22:28 +0000 (UTC) (envelope-from kpielorz_lst@tdx.co.uk) Received: from smtp.krpservers.com (smtp.krpservers.com [62.13.128.145]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "smtp.krpservers.com", Issuer "COMODO RSA Domain Validation Secure Server CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id A24951141 for ; Fri, 31 Jul 2015 15:22:26 +0000 (UTC) (envelope-from kpielorz_lst@tdx.co.uk) Received: from [10.12.30.106] (vpn01-01.tdx.co.uk [62.13.130.213]) (authenticated bits=0) by smtp.krpservers.com (8.14.9/8.14.9) with ESMTP id t6VFMSZu077712 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 31 Jul 2015 16:22:29 +0100 (BST) (envelope-from kpielorz_lst@tdx.co.uk) Date: Fri, 31 Jul 2015 16:22:20 +0100 From: Karl Pielorz To: =?UTF-8?Q?Roger_Pau_Monn=C3=A9?= , xen@FreeBSD.org Subject: Re: Boot FreeBSD 10 in HVM mode under Xen? Message-ID: <9B60E53D7F086CE86B2A98ED@[10.12.30.106]> In-Reply-To: <55BB8F9B.2040301@citrix.com> References: <55BB8392.4050000@citrix.com> <32FBD53695D759928A181828@[10.12.30.106]> <55BB8F9B.2040301@citrix.com> X-Mailer: Mulberry/4.0.8 (Win32) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: quoted-printable Content-Disposition: inline X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Discussion of the freebsd port to xen - implementation and usage List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 31 Jul 2015 15:22:28 -0000 --On 31 July 2015 17:09 +0200 Roger Pau Monn=C3=A9 = wrote: > Ouch, I guess this is the Xen HyperV support badly interacting with > FreeBSD again. XenServer enables the "viridian" extensions by default, > which really messes up with FreeBSD. You should be able to disable the > extensions by hand, as reported in: > > https://lists.freebsd.org/pipermail/freebsd-xen/2013-October/001756.html Fantastic - that works! Cheers, -Karl From owner-freebsd-xen@freebsd.org Fri Jul 31 15:24:20 2015 Return-Path: Delivered-To: freebsd-xen@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 909A19AFF7C for ; Fri, 31 Jul 2015 15:24:20 +0000 (UTC) (envelope-from kpielorz_lst@tdx.co.uk) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 78677152A for ; Fri, 31 Jul 2015 15:24:20 +0000 (UTC) (envelope-from kpielorz_lst@tdx.co.uk) Received: by mailman.ysv.freebsd.org (Postfix) id 76CF89AFF7B; Fri, 31 Jul 2015 15:24:20 +0000 (UTC) Delivered-To: xen@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 766009AFF79 for ; Fri, 31 Jul 2015 15:24:20 +0000 (UTC) (envelope-from kpielorz_lst@tdx.co.uk) Received: from smtp.krpservers.com (smtp.krpservers.com [62.13.128.145]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "smtp.krpservers.com", Issuer "COMODO RSA Domain Validation Secure Server CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 19CD91529 for ; Fri, 31 Jul 2015 15:24:19 +0000 (UTC) (envelope-from kpielorz_lst@tdx.co.uk) Received: from [10.12.30.106] (vpn01-01.tdx.co.uk [62.13.130.213]) (authenticated bits=0) by smtp.krpservers.com (8.14.9/8.14.9) with ESMTP id t6VFOGnX077849 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 31 Jul 2015 16:24:17 +0100 (BST) (envelope-from kpielorz_lst@tdx.co.uk) Date: Fri, 31 Jul 2015 16:24:08 +0100 From: Karl Pielorz To: =?UTF-8?Q?Roger_Pau_Monn=C3=A9?= , xen@FreeBSD.org Subject: Re: Boot FreeBSD 10 in HVM mode under Xen? Message-ID: In-Reply-To: <55BB8DB2.6040705@citrix.com> References: <55BB8392.4050000@citrix.com> <55BB8DB2.6040705@citrix.com> X-Mailer: Mulberry/4.0.8 (Win32) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: quoted-printable Content-Disposition: inline X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Discussion of the freebsd port to xen - implementation and usage List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 31 Jul 2015 15:24:20 -0000 --On 31 July 2015 17:01 +0200 Roger Pau Monn=C3=A9 = wrote: >> Can you technically have a system that has HVM network (i.e. realtek) >> but still has disk PV, and/or is agile? (i.e. can run xen-tools)? > > Yes, this is certainly possible. IIRC I posted a patch to the > freebsd-xen mailing list in order to do that. I will try to find/refresh > it and post it again so you can try it. It might have to wait until > Monday however, since I'm quite busy today. That'd be wonderful if you can sort that at some point - it'd be a much=20 better work around than we currently have for a number of machines. Heck we = could probably get rid of a whole pool of 'have to run non-agile HVM only'=20 FBSD machines. Thanks for your time, -Karl From owner-freebsd-xen@freebsd.org Fri Jul 31 16:27:28 2015 Return-Path: Delivered-To: freebsd-xen@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 5F36E9AF3E3 for ; Fri, 31 Jul 2015 16:27:28 +0000 (UTC) (envelope-from mcdouga9@egr.msu.edu) Received: from mail.egr.msu.edu (boomhauer.egr.msu.edu [35.9.37.164]) by mx1.freebsd.org (Postfix) with ESMTP id D704F2A91 for ; Fri, 31 Jul 2015 16:27:27 +0000 (UTC) (envelope-from mcdouga9@egr.msu.edu) Received: from boomhauer (localhost [127.0.0.1]) by mail.egr.msu.edu (Postfix) with ESMTP id 33BB138AA9 for ; Fri, 31 Jul 2015 12:20:06 -0400 (EDT) X-Virus-Scanned: amavisd-new at egr.msu.edu Received: from mail.egr.msu.edu ([127.0.0.1]) by boomhauer (boomhauer.egr.msu.edu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0IWkq3SUYKN4 for ; Fri, 31 Jul 2015 12:20:06 -0400 (EDT) Received: from EGR authenticated sender mcdouga9 Subject: Re: Boot FreeBSD 10 in HVM mode under Xen? To: freebsd-xen@freebsd.org References: <55BB8392.4050000@citrix.com> <32FBD53695D759928A181828@[10.12.30.106]> <55BB8F9B.2040301@citrix.com> <9B60E53D7F086CE86B2A98ED@[10.12.30.106]> From: Adam McDougall Message-ID: <55BBA035.1000006@egr.msu.edu> Date: Fri, 31 Jul 2015 12:20:05 -0400 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:38.0) Gecko/20100101 Thunderbird/38.1.0 MIME-Version: 1.0 In-Reply-To: <9B60E53D7F086CE86B2A98ED@[10.12.30.106]> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Discussion of the freebsd port to xen - implementation and usage List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 31 Jul 2015 16:27:28 -0000 On 07/31/2015 11:22, Karl Pielorz wrote: > > --On 31 July 2015 17:09 +0200 Roger Pau Monné wrote: > >> Ouch, I guess this is the Xen HyperV support badly interacting with >> FreeBSD again. XenServer enables the "viridian" extensions by default, >> which really messes up with FreeBSD. You should be able to disable the >> extensions by hand, as reported in: >> >> https://lists.freebsd.org/pipermail/freebsd-xen/2013-October/001756.html > > Fantastic - that works! > > Cheers, > > -Karl I'm guessing my kernel boots fine probably because I've disabled hyperv support in my kernel config. viridian probably explains why I see this in dmesg though: Hypervisor: Origin = "Microsoft Hv" From owner-freebsd-xen@freebsd.org Sat Aug 1 11:45:30 2015 Return-Path: Delivered-To: freebsd-xen@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6FCA69B08C5 for ; Sat, 1 Aug 2015 11:45:30 +0000 (UTC) (envelope-from egoitz@sarenet.es) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 555FB1C3 for ; Sat, 1 Aug 2015 11:45:30 +0000 (UTC) (envelope-from egoitz@sarenet.es) Received: by mailman.ysv.freebsd.org (Postfix) id 5237F9B08C4; Sat, 1 Aug 2015 11:45:30 +0000 (UTC) Delivered-To: xen@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 394C39B08C3 for ; Sat, 1 Aug 2015 11:45:30 +0000 (UTC) (envelope-from egoitz@sarenet.es) Received: from cu1176c.smtpx.saremail.com (cu1176c.smtpx.saremail.com [195.16.148.151]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id EC43F1C2 for ; Sat, 1 Aug 2015 11:45:28 +0000 (UTC) (envelope-from egoitz@sarenet.es) Received: from [172.16.2.236] (izaro.sarenet.es [192.148.167.11]) by proxypop02.sare.net (Postfix) with ESMTPSA id 5AE6D9DC6A5; Sat, 1 Aug 2015 13:45:19 +0200 (CEST) Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2102\)) Subject: Re: Poor network performance with Xen + OpenVPN? From: Egoitz Aurrekoetxea In-Reply-To: Date: Sat, 1 Aug 2015 13:45:16 +0200 Cc: Karl Pielorz , "freebsd-xen@freebsd.org" Message-Id: References: <40E060AB-F0B9-48F3-9309-947CAB5C1939@sarenet.es> <5A7F36D35FF28CD4B9D2DE92@10.12.30.106> To: seanrees@gmail.com X-Mailer: Apple Mail (2.2102) Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.20 X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Discussion of the freebsd port to xen - implementation and usage List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 01 Aug 2015 11:45:30 -0000 Could you paste your onpenvpn=E2=80=99s server and client config files?. = Which OS the client runs? Have you tested this openvpn connectivity without any network devices = between them?. With for example an ip in the=20 loopback interface of the openvpn server? Best regards, Egoitz Aurrekoetxea Departamento de sistemas 944 209 470 Parque Tecnol=C3=B3gico. Edificio 103 48170 Zamudio (Bizkaia) egoitz@sarenet.es www.sarenet.es Antes de imprimir este correo electr=C3=B3nico piense si es necesario = hacerlo. > El 30/7/2015, a las 11:41, seanrees@gmail.com escribi=C3=B3: >=20 > I have the same issue. I managed to track it down to a difference = between somewhere between Xen 3.4 and 4.4 (my provider uses both). >=20 > 3.4 works fine (I can sustain a few mbps through OpenVPN). 4.4 I get = ~0.05mbps max. I wasn't able to track it down. >=20 > Both with the virtual drivers (if_xn) with all combinations of tso, = lro, rxcsum and txcsum on/off tested. >=20 > Sean >=20 > On Wed, Jul 29, 2015 at 2:58 PM, Karl Pielorz > wrote: >=20 >=20 > --On 29 July 2015 14:28 +0200 Egoitz Aurrekoetxea > wrote: >=20 > Hi! >=20 > Have you disabled tso, lro and friends?. >=20 >=20 > If by that you mean, >=20 > ifconfig xn0 -rxcsum -txcsum -tso4 -lro >=20 > Yes - I've tried that on the virtual host running OpenVPN, it didn't = seem to make any difference :( >=20 > I'll hopefully get some more time later to look at it again. >=20 > Regards, >=20 > -Karl > _______________________________________________ > freebsd-xen@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-xen = > To unsubscribe, send any mail to "freebsd-xen-unsubscribe@freebsd.org = " >=20