From owner-freebsd-xen@FreeBSD.ORG Sun Mar 1 12:17:37 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 C7D6B891 for ; Sun, 1 Mar 2015 12:17:37 +0000 (UTC) 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" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 7A6DA84A for ; Sun, 1 Mar 2015 12:17:37 +0000 (UTC) X-IronPort-AV: E=Sophos;i="5.09,671,1418083200"; d="scan'208";a="238755337" Message-ID: <54F30359.8040801@citrix.com> Date: Sun, 1 Mar 2015 13:17:29 +0100 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.5.0 MIME-Version: 1.0 To: Shawn Webb Subject: Re: Kernel Panic on Xen HVM Guest References: <12692408.kQWUEGgiUB@shawnwebb-laptop> <54EB0EDF.2060108@citrix.com> <5232244.iGyx66OkOb@shawnwebb-laptop> In-Reply-To: <5232244.iGyx66OkOb@shawnwebb-laptop> Content-Type: text/plain; charset="windows-1252" Content-Transfer-Encoding: 8bit X-DLP: MIA2 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: Sun, 01 Mar 2015 12:17:37 -0000 Hello, El 28/02/15 a les 17.30, Shawn Webb ha escrit: > On Monday, February 23, 2015 12:28:31 PM Roger Pau Monné wrote: >> Hello, >> >> El 22/02/15 a les 2.08, Shawn Webb ha escrit: >>> Hey All, >>> >>> I'm experiencing a kernel panic at boot time on my RootBSD VPS on >>> FreeBSD- >>> CURRENT. >>> >>> Since I'm limited to VNC, I've uploaded a screenshot of the crash here: >>> http://imgur.com/yWtvJDc >> >> I'm aware of this issue, it's been introduced by r278977. I'm working >> with Gleb in order to solve it, sorry for the breakage. >> >> https://www.marc.info/?t=142430881000004&r=1&w=3 >> >> Roger. > > No worries. Has this been fixed? Yes, -current should be fine now. Roger.