From owner-freebsd-xen@freebsd.org  Mon Apr  2 13:36:59 2018
Return-Path: <owner-freebsd-xen@freebsd.org>
Delivered-To: freebsd-xen@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id DB39EF59E3C
 for <freebsd-xen@mailman.ysv.freebsd.org>;
 Mon,  2 Apr 2018 13:36:58 +0000 (UTC)
 (envelope-from prvs=623839fe0=roger.pau@citrix.com)
Received: from SMTP.EU.CITRIX.COM (smtp.eu.citrix.com [185.25.65.24])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client CN "mail.citrix.com",
 Issuer "DigiCert SHA2 Secure Server CA" (verified OK))
 by mx1.freebsd.org (Postfix) with ESMTPS id 4D4427EC96
 for <freebsd-xen@freebsd.org>; Mon,  2 Apr 2018 13:36:57 +0000 (UTC)
 (envelope-from prvs=623839fe0=roger.pau@citrix.com)
X-IronPort-AV: E=Sophos;i="5.48,395,1517875200"; d="scan'208";a="70911289"
Date: Mon, 2 Apr 2018 14:35:39 +0100
From: Roger Pau =?utf-8?B?TW9ubsOp?= <roger.pau@citrix.com>
To: "Rodney W. Grimes" <freebsd-rwg@pdx.rh.CN85.dnsmgr.net>
CC: Chris <syseng@gfsys.co.uk>, <freebsd-xen@freebsd.org>
Subject: Re: [Bug 224003] xen kernel panics
Message-ID: <20180402133539.4x2wvuz4tia3nukp@MacBook-Pro-de-Roger.local>
References: <5ABFD26B.8030601@gfsys.co.uk>
 <201804010238.w312cSHg075773@pdx.rh.CN85.dnsmgr.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <201804010238.w312cSHg075773@pdx.rh.CN85.dnsmgr.net>
User-Agent: NeoMutt/20180323
X-ClientProxiedBy: AMSPEX02CAS02.citrite.net (10.69.22.113) To
 AMSPEX02CL02.citrite.net (10.69.22.126)
X-BeenThere: freebsd-xen@freebsd.org
X-Mailman-Version: 2.1.25
Precedence: list
List-Id: Discussion of the freebsd port to xen - implementation and usage
 <freebsd-xen.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-xen>,
 <mailto:freebsd-xen-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-xen/>
List-Post: <mailto:freebsd-xen@freebsd.org>
List-Help: <mailto:freebsd-xen-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-xen>,
 <mailto:freebsd-xen-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 02 Apr 2018 13:36:59 -0000

On Sat, Mar 31, 2018 at 07:38:28PM -0700, Rodney W. Grimes wrote:
> > On 03/31/18 18:11, Chris wrote:
> > > On 03/30/18 18:05, Rodney W. Grimes wrote:
> > >
> > >> I can affirm that a E56xx cpu should be very capable of supporting Xen.
> > >> CPU: Intel(R) Xeon(R) CPU X5675 @ 3.07GHz (3059.07-MHz K8-class CPU)
> > >> Origin="GenuineIntel" Id=0x206c2 Family=0x6 Model=0x2c Stepping=2
> > >> Features=0xbfebfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE>
> > >>
> > >> Features2=0x29ee3ff<SSE3,PCLMULQDQ,DTES64,MON,DS_CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,DCA,SSE4.1,SSE4.2,POPCNT,AESNI>
> > >>
> > >> AMD Features=0x2c100800<SYSCALL,NX,Page1GB,RDTSCP,LM>
> > >> AMD Features2=0x1<LAHF>
> > >> VT-x: PAT,HLT,MTF,PAUSE,EPT,UG,VPID
> > >> TSC: P-state invariant, performance statistics
> > >>
> > 
> > Looks like this might be the problem:-
> > 
> > > (XEN) [VT-D]Disabling IOMMU due to Intel 5500/5520/X58 Chipset errata
> > > #47, #53
> > 
> > Been in a rush today, but should have looked at that a bit more closely
> > before posting, as istr, saw that  mentioned as a bug eleswhere back
> > from 2015 or so....
> 
> https://support.citrix.com/article/CTX136517
> 
> That has some info on how to work around this issue.  You can turn
> of the interrupt remapping and still have an iommu, though it is
> not going be very effective for passthrough of devices.

Just add iommu=no-intremap to your xen_cmdline in loader.conf.

Roger.