From owner-freebsd-xen@FreeBSD.ORG Thu Feb 19 15:20:27 2015 Return-Path: Delivered-To: freebsd-xen@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 5E44ABC2 for ; Thu, 19 Feb 2015 15:20:27 +0000 (UTC) Received: from mail.tdx.com (mail.tdx.com [62.13.128.18]) by mx1.freebsd.org (Postfix) with ESMTP id 23A9D30E for ; Thu, 19 Feb 2015 15:20:26 +0000 (UTC) Received: from [10.12.30.106] (vpn01-01.tdx.co.uk [62.13.130.213]) (authenticated bits=0) by mail.tdx.com (8.14.3/8.14.3/) with ESMTP id t1JFHd6m027189 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 19 Feb 2015 15:17:39 GMT Date: Thu, 19 Feb 2015 15:17:38 +0000 From: Karl Pielorz To: Michael MacLeod , Miguel Clara Subject: Re: [Bug 188261] [xen] FreeBSD DomU PVHVM guests cannot 'route' traffic for other Xen PV guests on same Dom0 Host. Message-ID: <96E16668BD46052D41141B94@[10.12.30.106]> In-Reply-To: References: <54E4D37A.7010905@pdsvelebit.hr> 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 Cc: freebsd-xen@freebsd.org X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.18-1 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, 19 Feb 2015 15:20:27 -0000 --On 18 February 2015 14:49 -0500 Michael MacLeod wrote: > I've been using the OSS Xen releases for years, and have never been able > to get PVM domU to be functional as a gateway - I've either had to use > HVM or setup a separate box as the router. This has been the case since > at least FBSD8 I think, or whenever XENHVM became an option. As the original bug filer... I've tried FBSD 9, 10 and 11 - I was hoping (under the "you never know" banner) that XS 6.5 with updated Xen etc. might make a difference - but sadly it doesn't, as people have pointed out - it's a likely issue with netfront/back code in FBSD. This is a real pain for us - apart from the hours initially wasted figuring it out - and the 'accidents' when people forget, we either have a bunch of non-agile machines polluting our main pools, or a secondary "pool of shame" where all the FBSD boxes that do things like VPN, routing, DHCP, firewalling are running in HVM mode [and again, not agile]. Performance of HVM NIC's and disk isn't as good as PV either (as you'd expect). I have the stuff to test this setup in house here - I just don't know where to start to look at it :( - but open to suggestions ;) Cheers, -Karl