From owner-freebsd-xen@FreeBSD.ORG Tue May 26 07:35:13 2015 Return-Path: Delivered-To: freebsd-xen@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id A5098255; Tue, 26 May 2015 07:35:13 +0000 (UTC) (envelope-from 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 "Cybertrust Public SureServer SV CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 1F9E88D; Tue, 26 May 2015 07:35:12 +0000 (UTC) (envelope-from roger.pau@citrix.com) X-IronPort-AV: E=Sophos;i="5.13,496,1427760000"; d="scan'208";a="265854378" Message-ID: <55642229.9020106@citrix.com> Date: Tue, 26 May 2015 09:35:05 +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: "Eggert, Lars" CC: Roman Bogorodskiy , "freebsd-xen@freebsd.org" Subject: Re: Xen dom0 crash References: <7CB114B9-B666-4764-86B6-B94F07973389@netapp.com> <5559EB2E.6080609@citrix.com> <20150522161117.GA59488@kloomba> <555F58DC.2040807@citrix.com> <46625CAE-750E-4ECE-8B39-DF8EDDFA912F@netapp.com> In-Reply-To: <46625CAE-750E-4ECE-8B39-DF8EDDFA912F@netapp.com> Content-Type: text/plain; charset="windows-1252" Content-Transfer-Encoding: 8bit X-DLP: MIA1 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: Tue, 26 May 2015 07:35:13 -0000 El 26/05/15 a les 9.30, Eggert, Lars ha escrit: > On 2015-5-22, at 18:27, Roger Pau Monné wrote: >> >> The issue mentioned in this thread has been fixed in the xen-kernel port >> with the following commit: >> >> https://svnweb.freebsd.org/ports?view=revision&revision=386935 > > Will this make it into upstream Xen? I hope so, I've already sent the patch and it has been acked by one of the Intel VMX maintainers, so I guess it's not going to take long before it's committed: http://lists.xenproject.org/archives/html/xen-devel/2015-05/msg03068.html Roger.