From owner-freebsd-xen@freebsd.org Tue May 17 09:43:10 2016 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 D9327B3E472 for ; Tue, 17 May 2016 09:43:10 +0000 (UTC) (envelope-from prvs=938cbf5a0=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 9AE2917A9 for ; Tue, 17 May 2016 09:43:10 +0000 (UTC) (envelope-from prvs=938cbf5a0=roger.pau@citrix.com) X-IronPort-AV: E=Sophos;i="5.26,324,1459814400"; d="scan'208";a="354714199" Date: Tue, 17 May 2016 11:43:01 +0200 From: Roger Pau =?iso-8859-1?Q?Monn=E9?= To: Miguel C CC: "freebsd-xen@freebsd.org" Subject: Re: xn ethernet issues as DOMU under NetBSD DOM0 FIXED! Message-ID: <20160517094301.h4oa4nyyakbj7r3h@mac> References: <20160512162247.64x5hyud5i2jfgqy@mac> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.6.0-neo (2016-04-07) X-DLP: MIA1 X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.22 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: Tue, 17 May 2016 09:43:10 -0000 On Sat, May 14, 2016 at 08:32:43PM +0100, Miguel C wrote: > Somewhat related to this is the fact that at some point "xenhvm" as not > longer available as a module, this means if I want to upgrade 9.3 machine > to 10.3 with freebsd-update I get stuck with the bug, but before this > change I could just patch the xenhvm module and rebuild the single module... With previous FreeBSD 9.X versions, in order to get Xen support you had to compile a specific kernel (XENHVM), we wanted to remove this for FreeBSD 10, so we included the Xen components into the GENERIC kernel and made sure there were no weird interactions on bare metal. However, this change was too big to merge into 9, so in order to try to improve the situation on 9 Colin decided to pack all the Xen support into a kernel module, in order to remove the need to compile a specific kernel for Xen VMs. And I guess if you want to update from 9.X to 10.X you will have to remove the xenhvm_load="YES" from your loader file. > Now I guess I need to rebuild the full kernel to do it? Or is there a way > around that? Yes, on 10.X you will have to rebuild the full kernel in order to get the fix. Roger.