From owner-freebsd-xen@freebsd.org Sat Mar 31 20:02:32 2018 Return-Path: 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 E06D6F7C956 for ; Sat, 31 Mar 2018 20:02:32 +0000 (UTC) (envelope-from mail@jservice.org) Received: from mail.jservice.org (mail.jservice.org [91.237.88.109]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 37C957419F for ; Sat, 31 Mar 2018 20:02:32 +0000 (UTC) (envelope-from mail@jservice.org) Received: from mail.jservice.org (localhost [127.0.0.1]) by mail.jservice.org (Postfix) with ESMTP id 8C257B0054B for ; Sat, 31 Mar 2018 21:54:20 +0200 (CEST) Authentication-Results: mail.jservice.org (amavisd-new); dkim=pass reason="pass (just generated, assumed good)" header.d=jservice.org DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=jservice.org; h= user-agent:message-id:references:in-reply-to:subject:subject:to :from:from:date:date:content-transfer-encoding:content-type :content-type:mime-version; s=dkim; t=1522526060; x=1523390061; bh=1t6Uo/yr+dJXRffD8e17njkH+f+aJXPa5L6+m9lHF8E=; b=Uj7nsJpLz3Il 1ztjhbMfFL/45pTa2frAYkCIJkEhe1vCD9kb5jnRE/oXv9XhC0qCWnOwv+oP8jkT ipe6mjvJehkfqlg+oPp2x7u+JhoeQfZ9mkGGDaioV0s0P3sLM25/wtBQrZJ9TUmg raE7s55mQySNQWTLke2/3w3O2SXjjBo= X-Virus-Scanned: Debian amavisd-new at mail.jservice.org Received: from mail.jservice.org ([127.0.0.1]) by mail.jservice.org (mail.jservice.org [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id snsCBWy0R8dV for ; Sat, 31 Mar 2018 21:54:20 +0200 (CEST) Received: from _ (localhost [127.0.0.1]) by mail.jservice.org (Postfix) with ESMTPSA id CC473B0052C; Sat, 31 Mar 2018 21:54:19 +0200 (CEST) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Date: Sat, 31 Mar 2018 21:54:19 +0200 From: mail@jservice.org To: Chris Cc: freebsd-xen@freebsd.org Subject: Re: [Bug 224003] xen kernel panics In-Reply-To: <5ABFD26B.8030601@gfsys.co.uk> References: <201803301805.w2UI531x069099@pdx.rh.CN85.dnsmgr.net> <5ABFCF3A.1010601@gfsys.co.uk> <5ABFD26B.8030601@gfsys.co.uk> Message-ID: X-Sender: mail@jservice.org User-Agent: Roundcube Webmail 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 31 Mar 2018 20:02:33 -0000 Am 2018-03-31 20:24, schrieb Chris: > 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 >>> >>> Features2=0x29ee3ff >>> >>> AMD Features=0x2c100800 >>> AMD Features2=0x1 >>> 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.... i had the same problem with an older poweredge r410, just for fun (and profit) i patched this and xen started working like expected. it has been tested just for a short time, but booting vms was possible. i am sure that i figured out which limitation this had but i cant remember see my notes at gist https://gist.github.com/jserviceorg/e8479c6cc1b485cacf21682ebb22bd27 > > Regards, > > Chris > _______________________________________________ > freebsd-xen@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-xen > To unsubscribe, send any mail to "freebsd-xen-unsubscribe@freebsd.org"