From owner-freebsd-xen@freebsd.org  Sun Apr  1 02:38:32 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 AF683F74690
 for <freebsd-xen@mailman.ysv.freebsd.org>;
 Sun,  1 Apr 2018 02:38:32 +0000 (UTC)
 (envelope-from freebsd-rwg@pdx.rh.CN85.dnsmgr.net)
Received: from pdx.rh.CN85.dnsmgr.net (br1.CN84in.dnsmgr.net [69.59.192.140])
 (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 2A9CC83F75
 for <freebsd-xen@freebsd.org>; Sun,  1 Apr 2018 02:38:31 +0000 (UTC)
 (envelope-from freebsd-rwg@pdx.rh.CN85.dnsmgr.net)
Received: from pdx.rh.CN85.dnsmgr.net (localhost [127.0.0.1])
 by pdx.rh.CN85.dnsmgr.net (8.13.3/8.13.3) with ESMTP id w312cTKK075774;
 Sat, 31 Mar 2018 19:38:29 -0700 (PDT)
 (envelope-from freebsd-rwg@pdx.rh.CN85.dnsmgr.net)
Received: (from freebsd-rwg@localhost)
 by pdx.rh.CN85.dnsmgr.net (8.13.3/8.13.3/Submit) id w312cSHg075773;
 Sat, 31 Mar 2018 19:38:28 -0700 (PDT) (envelope-from freebsd-rwg)
From: "Rodney W. Grimes" <freebsd-rwg@pdx.rh.CN85.dnsmgr.net>
Message-Id: <201804010238.w312cSHg075773@pdx.rh.CN85.dnsmgr.net>
Subject: Re: [Bug 224003] xen kernel panics
In-Reply-To: <5ABFD26B.8030601@gfsys.co.uk>
To: Chris <syseng@gfsys.co.uk>
Date: Sat, 31 Mar 2018 19:38:28 -0700 (PDT)
CC: freebsd-xen@freebsd.org
X-Mailer: ELM [version 2.4ME+ PL121h (25)]
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset=US-ASCII
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: Sun, 01 Apr 2018 02:38:32 -0000

> 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.

Its linux centric, and I am not quiet sure how to apply those
knobs to loader.conf to make xen do the right thing, but it
should be possible.


-- 
Rod Grimes                                                 rgrimes@freebsd.org