From owner-freebsd-xen@freebsd.org Thu Mar 29 23:32:28 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 F41B0F548C4 for ; Thu, 29 Mar 2018 23:32:27 +0000 (UTC) (envelope-from syseng@gfsys.co.uk) Received: from smtp.livemail.co.uk (smtp-out-60.livemail.co.uk [213.171.216.60]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "smtp.livemail.co.uk", Issuer "thawte SSL CA - G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 9A7536AEED for ; Thu, 29 Mar 2018 23:32:27 +0000 (UTC) (envelope-from syseng@gfsys.co.uk) Received: from [192.9.200.226] (host81-133-228-57.in-addr.btopenworld.com [81.133.228.57]) (Authenticated sender: syseng@gfsys.co.uk) by smtp.livemail.co.uk (Postfix) with ESMTPA id 058EE280E6F for ; Fri, 30 Mar 2018 00:32:19 +0100 (BST) Message-ID: <5ABD7783.3040901@gfsys.co.uk> Date: Thu, 29 Mar 2018 23:32:19 +0000 From: Chris User-Agent: Mozilla/5.0 (X11; SunOS sun4u; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2 MIME-Version: 1.0 To: freebsd-xen@freebsd.org Subject: [Bug 224003] xen kernel panics Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit 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: Thu, 29 Mar 2018 23:32:28 -0000 I'm having similar problems with xen on 11.1, AMD64, June 2017. The OS runs fine, but installed xen from package, setup exactly as per the handbook and get a kernel panic on two machines, complaining about iommu not being enabled. Machines are: a Sun X4170 to start, then a Proliant DL380 G7 with E5630 cpu. Both have all the virtualisation options enabled in the bios, but there are no options on either machine for iommu. Have other machines running FreeBSD, an Atom pc running as a nas box, a couple of other Intel based systems and a Sparc machine running 10.2, with a shedload of packages built to try and get an X desktop running. Got as far as xvnc remote desktop working, but still trying to get Firefox built. Normally, everything works out of the box with FreeBSD , so has this really been tested, or is xen just not mainstream ?. Trying to find info on xen / FreeBSD brings up a load of sometimes conflicting info. The xen site is no help either, with possibly out of date / not in sync with handbook info. FreeBSD is the escape plan from Solaris and zones, but need zfs, jails and xen to make it all work. Any ideas ?... Regards, Chris From owner-freebsd-xen@freebsd.org Fri Mar 30 12:07:46 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 59E13F66BE7 for ; Fri, 30 Mar 2018 12:07:46 +0000 (UTC) (envelope-from prvs=620b6eee9=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 C59BD8589A for ; Fri, 30 Mar 2018 12:07:45 +0000 (UTC) (envelope-from prvs=620b6eee9=roger.pau@citrix.com) X-IronPort-AV: E=Sophos;i="5.48,381,1517875200"; d="scan'208";a="70809236" Date: Fri, 30 Mar 2018 13:07:29 +0100 From: Roger Pau =?utf-8?B?TW9ubsOp?= To: Chris CC: Subject: Re: [Bug 224003] xen kernel panics Message-ID: <20180330120729.5jcuidllh2a4ya27@MacBook-Pro-de-Roger.local> References: <5ABD7783.3040901@gfsys.co.uk> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Disposition: inline In-Reply-To: <5ABD7783.3040901@gfsys.co.uk> User-Agent: NeoMutt/20180323 X-ClientProxiedBy: AMSPEX02CAS01.citrite.net (10.69.22.112) 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 30 Mar 2018 12:07:46 -0000 On Thu, Mar 29, 2018 at 11:32:19PM +0000, Chris wrote: > I'm having similar problems with xen on 11.1, AMD64, June 2017. > The OS runs fine, but installed xen from package, setup exactly > as per the handbook and get a kernel panic on two machines, > complaining about iommu not being enabled. FreeBSD/Xen Dom0 requires a working IOMMU, that's documented in the handbook [0] section 21.8.1. Can you paste the full output that you get when booting under Xen? > Machines are: a Sun X4170 to start, then a Proliant DL380 G7 > with E5630 cpu. Both have all the virtualisation options > enabled in the bios, but there are no options on either machine > for iommu. On Intel hardware the IOMMU is called VT-d. I have no idea if the hardware that you list has an IOMMU, it depends on both the CPU and the motherboard. Without VT-d (an IOMMU) FreeBSD/Xen Dom0 won't work. Roger. [0] https://www.freebsd.org/doc/handbook/virtualization-host-xen.html From owner-freebsd-xen@freebsd.org Fri Mar 30 17:43:24 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 5901DF50A34 for ; Fri, 30 Mar 2018 17:43:24 +0000 (UTC) (envelope-from syseng@gfsys.co.uk) Received: from smtp.livemail.co.uk (smtp-out-60.livemail.co.uk [213.171.216.60]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "smtp.livemail.co.uk", Issuer "thawte SSL CA - G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id EFDC37291D for ; Fri, 30 Mar 2018 17:43:23 +0000 (UTC) (envelope-from syseng@gfsys.co.uk) Received: from [192.9.200.226] (host81-133-228-57.in-addr.btopenworld.com [81.133.228.57]) (Authenticated sender: syseng@gfsys.co.uk) by smtp.livemail.co.uk (Postfix) with ESMTPA id B4E3A280E9D; Fri, 30 Mar 2018 18:43:21 +0100 (BST) Message-ID: <5ABE7739.2030008@gfsys.co.uk> Date: Fri, 30 Mar 2018 17:43:21 +0000 From: Chris User-Agent: Mozilla/5.0 (X11; SunOS sun4u; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2 MIME-Version: 1.0 To: =?ISO-8859-1?Q?Roger_Pau_Monn=E9?= , freebsd-xen@freebsd.org Subject: Re: [Bug 224003] xen kernel panics References: <5ABD7783.3040901@gfsys.co.uk> <20180330120729.5jcuidllh2a4ya27@MacBook-Pro-de-Roger.local> In-Reply-To: <20180330120729.5jcuidllh2a4ya27@MacBook-Pro-de-Roger.local> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit 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: Fri, 30 Mar 2018 17:43:24 -0000 On 03/30/18 12:07, Roger Pau Monné wrote: > On Thu, Mar 29, 2018 at 11:32:19PM +0000, Chris wrote: >> I'm having similar problems with xen on 11.1, AMD64, June 2017. >> The OS runs fine, but installed xen from package, setup exactly >> as per the handbook and get a kernel panic on two machines, >> complaining about iommu not being enabled. > > FreeBSD/Xen Dom0 requires a working IOMMU, that's documented in the > handbook [0] section 21.8.1. > > Can you paste the full output that you get when booting under Xen? > >> Machines are: a Sun X4170 to start, then a Proliant DL380 G7 >> with E5630 cpu. Both have all the virtualisation options >> enabled in the bios, but there are no options on either machine >> for iommu. > > On Intel hardware the IOMMU is called VT-d. I have no idea if the > hardware that you list has an IOMMU, it depends on both the CPU and > the motherboard. > > Without VT-d (an IOMMU) FreeBSD/Xen Dom0 won't work. > > Roger. > > [0] https://www.freebsd.org/doc/handbook/virtualization-host-xen.html > . > Roger, Thanks for the reply and clarification on the meaning of iommu. A bit more info on the machine: Cpu is actually an E5645, hex core, 2.4GHz 32 Gb ram, full ecc bios is dated 2011, with: VT-d, enabled Intel virtualisation tech, enabled It's difficult to log info on this, as there is just the "needs iommu" message on boot, then halt. Live cd and file edits brought the base system back, but nothing in /var/log/xen at all. DL380 Proliant is industry standard vanilla and they are very common and thus affordable second user. I know VMware runs on a G5 version of this model, so doubt there is any problem with the hardware. One thing found in the searches was a discussion about cpu "advisories ?" which produces this problem, but no info on how to get round it. This was from 2015, but would think such a bug would have been fixed by now. This a first attempt at getting xen running under FreeBSD or Xen at all, so a compete newbie in this area. Do Embedded rtos systems here, no specialisation in xen or freebsd in particular, but have time and can try various solutions if someone has any ideas. Today: deleted packages, updated system amd ports and rebuilding xen and tools from source. Might just be something out of sync, but will report back once it's finished... Regards & Thanks, Chris From owner-freebsd-xen@freebsd.org Fri Mar 30 18:02:38 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 72E04F520CF for ; Fri, 30 Mar 2018 18:02:38 +0000 (UTC) (envelope-from prvs=620b6eee9=roger.pau@citrix.com) Received: from SMTP.EU.CITRIX.COM (smtp.ctxuk.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 DD11273431 for ; Fri, 30 Mar 2018 18:02:37 +0000 (UTC) (envelope-from prvs=620b6eee9=roger.pau@citrix.com) X-IronPort-AV: E=Sophos;i="5.48,382,1517875200"; d="scan'208";a="70826266" Date: Fri, 30 Mar 2018 19:02:04 +0100 From: Roger Pau =?utf-8?B?TW9ubsOp?= To: Chris CC: Subject: Re: [Bug 224003] xen kernel panics Message-ID: <20180330180204.tmsks5yp4wxgavcq@MacBook-Pro-de-Roger.local> References: <5ABD7783.3040901@gfsys.co.uk> <20180330120729.5jcuidllh2a4ya27@MacBook-Pro-de-Roger.local> <5ABE7739.2030008@gfsys.co.uk> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <5ABE7739.2030008@gfsys.co.uk> User-Agent: NeoMutt/20180223-132-262c68-dirty 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 30 Mar 2018 18:02:38 -0000 On Fri, Mar 30, 2018 at 05:43:21PM +0000, Chris wrote: > On 03/30/18 12:07, Roger Pau Monné wrote: > > On Thu, Mar 29, 2018 at 11:32:19PM +0000, Chris wrote: > > > I'm having similar problems with xen on 11.1, AMD64, June 2017. > > > The OS runs fine, but installed xen from package, setup exactly > > > as per the handbook and get a kernel panic on two machines, > > > complaining about iommu not being enabled. > > > > FreeBSD/Xen Dom0 requires a working IOMMU, that's documented in the > > handbook [0] section 21.8.1. > > > > Can you paste the full output that you get when booting under Xen? > > > > > Machines are: a Sun X4170 to start, then a Proliant DL380 G7 > > > with E5630 cpu. Both have all the virtualisation options > > > enabled in the bios, but there are no options on either machine > > > for iommu. > > > > On Intel hardware the IOMMU is called VT-d. I have no idea if the > > hardware that you list has an IOMMU, it depends on both the CPU and > > the motherboard. > > > > Without VT-d (an IOMMU) FreeBSD/Xen Dom0 won't work. > > > > Roger. > > > > [0] https://www.freebsd.org/doc/handbook/virtualization-host-xen.html > > . > > > > Roger, > > Thanks for the reply and clarification on the meaning of iommu. A bit > more info on the machine: > > Cpu is actually an E5645, hex core, 2.4GHz > 32 Gb ram, full ecc > bios is dated 2011, with: > > VT-d, enabled > Intel virtualisation tech, enabled > > It's difficult to log info on this, as there is just the "needs iommu" > message on boot, then halt. Live cd and file edits brought the base > system back, but nothing in /var/log/xen at all. You can also boot into FreeBSD (without Xen) by dropping into the loader prompt and typing: > unload > unset xen_kernel I'm afraid you will need to connect to the server using a serial console and get the output from there. Without the full serial output it's hard to figure out what's going on. Thanks, Roger. From owner-freebsd-xen@freebsd.org Fri Mar 30 18:05:12 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 92CADF52363 for ; Fri, 30 Mar 2018 18:05:12 +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 2418A73591 for ; Fri, 30 Mar 2018 18:05:11 +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 w2UI54Lv069100; Fri, 30 Mar 2018 11:05:04 -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 w2UI531x069099; Fri, 30 Mar 2018 11:05:03 -0700 (PDT) (envelope-from freebsd-rwg) From: "Rodney W. Grimes" Message-Id: <201803301805.w2UI531x069099@pdx.rh.CN85.dnsmgr.net> Subject: Re: [Bug 224003] xen kernel panics In-Reply-To: <5ABE7739.2030008@gfsys.co.uk> To: Chris Date: Fri, 30 Mar 2018 11:05:03 -0700 (PDT) CC: =?ISO-8859-1?Q?Roger_Pau_Monn=E9?= , 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 30 Mar 2018 18:05:12 -0000 [ Charset ISO-8859-1 unsupported, converting... ] > On 03/30/18 12:07, Roger Pau Monn? wrote: > > On Thu, Mar 29, 2018 at 11:32:19PM +0000, Chris wrote: > >> I'm having similar problems with xen on 11.1, AMD64, June 2017. > >> The OS runs fine, but installed xen from package, setup exactly > >> as per the handbook and get a kernel panic on two machines, > >> complaining about iommu not being enabled. > > > > FreeBSD/Xen Dom0 requires a working IOMMU, that's documented in the > > handbook [0] section 21.8.1. > > > > Can you paste the full output that you get when booting under Xen? > > > >> Machines are: a Sun X4170 to start, then a Proliant DL380 G7 > >> with E5630 cpu. Both have all the virtualisation options > >> enabled in the bios, but there are no options on either machine > >> for iommu. > > > > On Intel hardware the IOMMU is called VT-d. I have no idea if the > > hardware that you list has an IOMMU, it depends on both the CPU and > > the motherboard. > > > > Without VT-d (an IOMMU) FreeBSD/Xen Dom0 won't work. > > > > Roger. > > > > [0] https://www.freebsd.org/doc/handbook/virtualization-host-xen.html > > . > > > > Roger, > > Thanks for the reply and clarification on the meaning of iommu. A bit > more info on the machine: > > Cpu is actually an E5645, hex core, 2.4GHz > 32 Gb ram, full ecc > bios is dated 2011, with: 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 I do not have VT-d enabled above infact I can not find that there is any setting for it on this hardware, though I am pretty sure I have used hardware passthrough in vmware with that box, which does requrire an iommu. But a wiki for bhyve tells me to do this on intel to find if there is a IOMMU avaliable: # acpidump -t | grep -A12 DMAR DMAR: Length=432, Revision=1, Checksum=213, OEMID=DELL, OEM Table ID=PE_SC3, OEM Revision=0x1, Creator ID=DELL, Creator Revision=0x1 Host Address Width=40 Flags= Type=DRHD Length=16 Flags={INCLUDE_ALL} Segment=0 Address=0x00000000fed90000 Type=RMRR If you have a DMAR table, you have a visible to FreeBSD iommu > VT-d, enabled > Intel virtualisation tech, enabled > > It's difficult to log info on this, as there is just the "needs iommu" > message on boot, then halt. Live cd and file edits brought the base > system back, but nothing in /var/log/xen at all. > > DL380 Proliant is industry standard vanilla and they are very common > and thus affordable second user. I know VMware runs on a G5 version > of this model, so doubt there is any problem with the hardware. VMware can run on almost any 64 bit processor, including those that do not have nested page tables, iommus, or for that matter even VT-x. They have software emulation of this stuff since there software predates many of these features. > One > thing found in the searches was a discussion about cpu "advisories ?" > which produces this problem, but no info on how to get round it. This > was from 2015, but would think such a bug would have been fixed by > now. This a first attempt at getting xen running under FreeBSD or Xen at > all, so a compete newbie in this area. Do Embedded rtos systems here, > no specialisation in xen or freebsd in particular, but have time and > can try various solutions if someone has any ideas. > > Today: deleted packages, updated system amd ports and rebuilding > xen and tools from source. Might just be something out of sync, but > will report back once it's finished... Can you boot FreeBSD without Xen on it and get some dmesg output like I did above, that would help to atleast affirm or deny that is being seen with respect to VT-x and VT-d? > Regards & Thanks, > Chris -- Rod Grimes rgrimes@freebsd.org From owner-freebsd-xen@freebsd.org Sat Mar 31 18:12:23 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 42B16F753B8 for ; Sat, 31 Mar 2018 18:12:23 +0000 (UTC) (envelope-from syseng@gfsys.co.uk) Received: from smtp.livemail.co.uk (smtp-out-60.livemail.co.uk [213.171.216.60]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "smtp.livemail.co.uk", Issuer "thawte SSL CA - G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id C5A986F584 for ; Sat, 31 Mar 2018 18:12:22 +0000 (UTC) (envelope-from syseng@gfsys.co.uk) Received: from [192.9.200.226] (host81-133-228-57.in-addr.btopenworld.com [81.133.228.57]) (Authenticated sender: syseng@gfsys.co.uk) by smtp.livemail.co.uk (Postfix) with ESMTPA id BDBA728070F for ; Sat, 31 Mar 2018 19:12:12 +0100 (BST) Message-ID: <5ABFCF7C.1050903@gfsys.co.uk> Date: Sat, 31 Mar 2018 18:12:12 +0000 From: Chris User-Agent: Mozilla/5.0 (X11; SunOS sun4u; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2 MIME-Version: 1.0 To: freebsd-xen@freebsd.org Subject: Re: [Bug 224003] xen kernel panics References: <201803301805.w2UI531x069099@pdx.rh.CN85.dnsmgr.net> In-Reply-To: <201803301805.w2UI531x069099@pdx.rh.CN85.dnsmgr.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit 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 18:12:23 -0000 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 > Rodney, Thanks for that and that test does confirm the DMAP table. Built xen from source yesterday, which pulls in a gcc build and loads of warnings during that and the build of various other packages, but when rebooting, am getting a stack underflow at the boot screen. Probably a typo in one of the config files, but they look ok, so include the config files below. Haven't defined any networking yet, as gettng the bare kernel running must be the first step. A bit like bringing up a an embedded system board from bare metal, though far more complex. Building from source and getting the same error suggests it's nothing out of sync, packages etc, put the disk aside and reinstalled the os and xen from scratch on another disk, to get a fresh start. It's a slightly later iso image, 31-July-2017. Still panics, with the following boot log via the serial port com 1. Sorry, lots of it, some line lengths edited:- ----------------------------------------------------------- ProLiant System BIOS - P67 (01/30/2011) Copyright 1982, 2011 Hewlett-Packard Development Company, L.P. 32 GB Installed 1 Processor(s) detected, 6 total cores enabled, Hyperthreading is disabled Proc 1: Intel(R) Xeon(R) CPU E5645 @ 2.40GHz QPI Speed: 5.8 GT/s HP Power Profile Mode: Balanced Power and Performance Power Regulator Mode: Dynamic Power Savings Advanced Memory Protection Mode: Advanced ECC Support Redundant ROM Detected - This system contains a valid backup system ROM. Inlet Ambient Temperature: 13C/55F Setup Utility Press "F10" key for System Maintenance Menu Press "F11" key for Default Boot Override Options Press "F12" key for Network Boot For access via BIOS Serial Console Press "ESC+9" for ROM-Based Setup Utility Press "ESC+0" for System Maintenance Menu Press "ESC+!" for Default Boot Override Options Press "ESC+@" for Network Boot Attempting Boot From CD-ROM Attempting Boot From Hard Drive (C:)-\|/- Consoles: internal video/keyboard BIOS drive A: is disk0BIOS drive C: is disk1BIOS drive D: is disk2BIOS drive E: is disk3BIOS 637kB/3396796kB available memory FreeBSD/x86 bootstrap loader, Revision 1.1(Fri Jul 21 02:03:08 UTC 2017 root@releng2.nyi.freebsd.org)|/-\|/- Loading /boot/defaults/loader.conf/-\|/- stack underflow message ??? \|/-(XEN) Bad console= option '' ??? Xen 4.7.2 (XEN) Xen version 4.7.2 (root@) (FreeBSD clang version 4.0.0 (tags/RELEASE_400/final 297347) (based on LLVM 4.0.0)) debug=n Thu Mar 15 18:36:39 UTC 2018 (XEN) Latest ChangeSet: (XEN) Bootloader: FreeBSD Loader (XEN) Command line: dom0_mem=2048M dom0_max_vcpus=6 dom0pvh=1 console=com1, vga com1=115200,8n1 guest_loglvl=all loglvl=all (XEN) Video information: (XEN) VGA is text mode 80x25, font 8x16 (XEN) VBE/DDC methods: V2; EDID transfer time: 1 seconds (XEN) Disc information: (XEN) Found 3 MBR signatures (XEN) Found 3 EDD information structures (XEN) Xen-e820 RAM map: (XEN) 0000000000000000 - 000000000009f400 (usable) (XEN) 000000000009f400 - 00000000000a0000 (reserved) (XEN) 00000000000f0000 - 0000000000100000 (reserved) (XEN) 0000000000100000 - 00000000cf62f000 (usable) (XEN) 00000000cf62f000 - 00000000cf63c000 (ACPI data) (XEN) 00000000cf63c000 - 00000000cf63d000 (usable) (XEN) 00000000cf63d000 - 00000000d4000000 (reserved) (XEN) 00000000fec00000 - 00000000fee10000 (reserved) (XEN) 00000000ff800000 - 0000000100000000 (reserved) (XEN) 0000000100000000 - 000000082ffff000 (usable) (XEN) ACPI: RSDP 000F4F00, 0024 (r2 HP ) (XEN) ACPI: XSDT CF630340, 00BC (r1 HP ProLiant 2 ̉ 162E) (XEN) ACPI: FACP CF630440, 00F4 (r3 HP ProLiant 2 ̉ 162E) (XEN) ACPI: DSDT CF630540, 20BD (r1 HP DSDT 1 INTL 20030228) (XEN) ACPI: FACS CF62F100, 0040 (XEN) ACPI: SPCR CF62F140, 0050 (r1 HP SPCRRBSU 1 ̉ 162E) (XEN) ACPI: MCFG CF62F1C0, 003C (r1 HP ProLiant 1 0) (XEN) ACPI: HPET CF62F200, 0038 (r1 HP ProLiant 2 ̉ 162E) (XEN) ACPI: FFFF CF62F240, 0064 (r2 HP ProLiant 2 ̉ 162E) (XEN) ACPI: SPMI CF62F2C0, 0040 (r5 HP ProLiant 1 ̉ 162E) (XEN) ACPI: ERST CF62F300, 01D0 (r1 HP ProLiant 1 ̉ 162E) (XEN) ACPI: APIC CF62F500, 015E (r1 HP ProLiant 2 0) (XEN) ACPI: SRAT CF62F680, 0570 (r1 HP Proliant 1 ̉ 162E) (XEN) ACPI: FFFF CF62FC00, 0176 (r1 HP ProLiant 1 ̉ 162E) (XEN) ACPI: BERT CF62FD80, 0030 (r1 HP ProLiant 1 ̉ 162E) (XEN) ACPI: HEST CF62FDC0, 00BC (r1 HP ProLiant 1 ̉ 162E) (XEN) ACPI: DMAR CF62FE80, 0168 (r1 HP ProLiant 1 ̉ 162E) (XEN) ACPI: SSDT CF632600, 0125 (r3 HP CRSPCI0 2 HP 1) (XEN) ACPI: SSDT CF632740, 0255 (r3 HP riser1a 2 INTL 20061109) (XEN) ACPI: SSDT CF6329C0, 025D (r3 HP riser2a 2 INTL 20061109) (XEN) ACPI: SSDT CF632C40, 03BB (r1 HP pcc 1 INTL 20090625) (XEN) ACPI: SSDT CF633000, 0377 (r1 HP pmab 1 INTL 20090625) (XEN) ACPI: SSDT CF633380, 105C (r1 INTEL PPM RCM 1 INTL 20061109) (XEN) System RAM: 32757MB (33543992kB) (XEN) SRAT: PXM 0 -> APIC 00 -> Node 0 (XEN) SRAT: PXM 0 -> APIC 02 -> Node 0 (XEN) SRAT: PXM 0 -> APIC 04 -> Node 0 (XEN) SRAT: PXM 0 -> APIC 10 -> Node 0 (XEN) SRAT: PXM 0 -> APIC 12 -> Node 0 (XEN) SRAT: PXM 0 -> APIC 14 -> Node 0 (XEN) SRAT: Node 0 PXM 0 0-d0000000 (XEN) SRAT: Node 0 PXM 0 100000000-830000000 (XEN) NUMA: Using 20 for the hash shift. (XEN) Domain heap initialised (XEN) found SMP MP-table at 000f4f80 (XEN) DMI 2.7 present. (XEN) Using APIC driver default (XEN) ACPI: PM-Timer IO Port: 0x908 (XEN) ACPI: SLEEP INFO: pm1x_cnt[1:904,1:0], pm1x_evt[1:900,1:0] (XEN) ACPI: wakeup_vec[cf62f10c], vec_size[20] (XEN) ACPI: Local APIC address 0xfee00000 (XEN) ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled) (XEN) ACPI: LAPIC (acpi_id[0x10] lapic_id[0x20] disabled) (XEN) ACPI: LAPIC (acpi_id[0x08] lapic_id[0x10] enabled) (XEN) ACPI: LAPIC (acpi_id[0x18] lapic_id[0x30] disabled) (XEN) ACPI: LAPIC (acpi_id[0x04] lapic_id[0x04] enabled) (XEN) ACPI: LAPIC (acpi_id[0x14] lapic_id[0x24] disabled) (XEN) ACPI: LAPIC (acpi_id[0x0c] lapic_id[0x14] enabled) (XEN) ACPI: LAPIC (acpi_id[0x1c] lapic_id[0x34] disabled) (XEN) ACPI: LAPIC (acpi_id[0x02] lapic_id[0x02] enabled) (XEN) ACPI: LAPIC (acpi_id[0x12] lapic_id[0x22] disabled) (XEN) ACPI: LAPIC (acpi_id[0x0a] lapic_id[0x12] enabled) (XEN) ACPI: LAPIC (acpi_id[0x1a] lapic_id[0x32] disabled) (XEN) ACPI: LAPIC (acpi_id[0x06] lapic_id[0x06] disabled) (XEN) ACPI: LAPIC (acpi_id[0x16] lapic_id[0x26] disabled) (XEN) ACPI: LAPIC (acpi_id[0x0e] lapic_id[0x16] disabled) (XEN) ACPI: LAPIC (acpi_id[0x1e] lapic_id[0x36] disabled) (XEN) ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] disabled) (XEN) ACPI: LAPIC (acpi_id[0x11] lapic_id[0x21] disabled) (XEN) ACPI: LAPIC (acpi_id[0x09] lapic_id[0x11] disabled) (XEN) ACPI: LAPIC (acpi_id[0x19] lapic_id[0x31] disabled) (XEN) ACPI: LAPIC (acpi_id[0x05] lapic_id[0x05] disabled) (XEN) ACPI: LAPIC (acpi_id[0x15] lapic_id[0x25] disabled) (XEN) ACPI: LAPIC (acpi_id[0x0d] lapic_id[0x15] disabled) (XEN) ACPI: LAPIC (acpi_id[0x1d] lapic_id[0x35] disabled) (XEN) ACPI: LAPIC (acpi_id[0x03] lapic_id[0x03] disabled) (XEN) ACPI: LAPIC (acpi_id[0x13] lapic_id[0x23] disabled) (XEN) ACPI: LAPIC (acpi_id[0x0b] lapic_id[0x13] disabled) (XEN) ACPI: LAPIC (acpi_id[0x1b] lapic_id[0x33] disabled) (XEN) ACPI: LAPIC (acpi_id[0x07] lapic_id[0x07] disabled) (XEN) ACPI: LAPIC (acpi_id[0x17] lapic_id[0x27] disabled) (XEN) ACPI: LAPIC (acpi_id[0x0f] lapic_id[0x17] disabled) (XEN) ACPI: LAPIC (acpi_id[0x1f] lapic_id[0x37] disabled) (XEN) ACPI: LAPIC_NMI (acpi_id[0xff] dfl dfl lint[0x1]) (XEN) ACPI: IOAPIC (id[0x08] address[0xfec00000] gsi_base[0]) (XEN) IOAPIC[0]: apic_id 8, version 32, address 0xfec00000, GSI 0-23 (XEN) ACPI: IOAPIC (id[0x00] address[0xfec80000] gsi_base[24]) (XEN) IOAPIC[1]: apic_id 0, version 32, address 0xfec80000, GSI 24-47 (XEN) ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 high edge) (XEN) ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level) (XEN) ACPI: IRQ0 used by override. (XEN) ACPI: IRQ2 used by override. (XEN) ACPI: IRQ9 used by override. (XEN) Enabling APIC mode: Flat. Using 2 I/O APICs (XEN) ACPI: HPET id: 0x8086a201 base: 0xfed00000 (XEN) Failed to get Error Log Address Range. (XEN) HEST: Table parsing has been initialized (XEN) Using ACPI (MADT) for SMP configuration information (XEN) SMP: Allowing 32 CPUs (26 hotplug CPUs) (XEN) IRQ limits: 48 GSI, 1120 MSI/MSI-X (XEN) Intel machine check reporting enabled (XEN) Using scheduler: SMP Credit Scheduler (credit) (XEN) Detected 2399.372 MHz processor. (XEN) Initing memory sharing. (XEN) alt table ffff82d0802bf2f0 -> ffff82d0802bfc44 (XEN) PCI: MCFG configuration 0: base d0000000 segment 0000 buses 00 - 3f (XEN) PCI: MCFG area at d0000000 reserved in E820 (XEN) PCI: Using MCFG for segment 0000 bus 00-3f (XEN) [VT-D]Disabling IOMMU due to Intel 5500/5520/X58 Chipset errata #47, #53 (XEN) I/O virtualisation disabled (XEN) nr_sockets: 5 (XEN) Enabled directed EOI with ioapic_ack_old on! (XEN) ENABLING IO-APIC IRQs (XEN) -> Using old ACK method (XEN) ..TIMER: vector=0xF0 apic1=0 pin1=2 apic2=-1 pin2=-1 (XEN) Platform timer is 14.318MHz HPET (XEN) Allocated console ring of 64 KiB. (XEN) mwait-idle: MWAIT substates: 0x1120 (XEN) mwait-idle: v0.4.1 model 0x2c (XEN) mwait-idle: lapic_timer_reliable_states 0xffffffff (XEN) VMX: Supported advanced features: (XEN) - APIC MMIO access virtualisation (XEN) - APIC TPR shadow (XEN) - Extended Page Tables (EPT) (XEN) - Virtual-Processor Identifiers (VPID) (XEN) - Virtual NMI (XEN) - MSR direct-access bitmap (XEN) - Unrestricted Guest (XEN) HVM: ASIDs enabled. (XEN) HVM: VMX enabled (XEN) HVM: Hardware Assisted Paging (HAP) detected (XEN) HVM: HAP page sizes: 4kB, 2MB, 1GB (XEN) Brought up 6 CPUs (XEN) ACPI sleep modes: S3 (XEN) VPMU: disabled (XEN) mcheck_poll: Machine check polling timer started. (XEN) Dom0 has maximum 624 PIRQs (XEN) NX (Execute Disable) protection active (XEN) *** LOADING DOMAIN 0 *** (XEN) Xen kernel: 64-bit, lsb, compat32 (XEN) Dom0 kernel: 64-bit, PAE, lsb, paddr 0x200000 -> 0x1e90da0 (XEN) Dom0 symbol map 0x1e90da0 -> 0x2167b80 (XEN) PHYSICAL MEMORY ARRANGEMENT: (XEN) Dom0 alloc.: 0000000814000000->0000000818000000 (507901 pages to be allocated) (XEN) Init. ramdisk: 000000082fdfd000->000000082fe00000 (XEN) VIRTUAL MEMORY ARRANGEMENT: (XEN) Loaded kernel: ffffffff80200000->ffffffff82167b80 (XEN) Init. ramdisk: ffffffff82168000->ffffffff8216b000 (XEN) Phys-Mach map: ffffffff8216b000->ffffffff8256b000 (XEN) Start info: ffffffff8256b000->ffffffff8256c4b4 (XEN) Page tables: ffffffff8256d000->ffffffff82584000 (XEN) Boot stack: ffffffff82584000->ffffffff82585000 (XEN) TOTAL: ffffffff80000000->ffffffff82800000 (XEN) ENTRY ADDRESS: ffffffff80ec8000 (XEN) Dom0 has maximum 6 VCPUs (XEN) (XEN) **************************************** (XEN) Panic on CPU 0: (XEN) Presently, iommu must be enabled for PVH hardware domain (XEN) (XEN) **************************************** (XEN) (XEN) Reboot in five seconds... Included kernel debugging with this install. No idea how to drive that though. Hope this is some use and thanks again for the help with this... Regards, Chris From owner-freebsd-xen@freebsd.org Sat Mar 31 18:17:05 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 B3825F75819 for ; Sat, 31 Mar 2018 18:17:05 +0000 (UTC) (envelope-from syseng@gfsys.co.uk) Received: from smtp.livemail.co.uk (smtp-out-60.livemail.co.uk [213.171.216.60]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "smtp.livemail.co.uk", Issuer "thawte SSL CA - G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 55A426F73E for ; Sat, 31 Mar 2018 18:17:04 +0000 (UTC) (envelope-from syseng@gfsys.co.uk) Received: from [192.9.200.226] (host81-133-228-57.in-addr.btopenworld.com [81.133.228.57]) (Authenticated sender: syseng@gfsys.co.uk) by smtp.livemail.co.uk (Postfix) with ESMTPA id BB8282805FD; Sat, 31 Mar 2018 19:17:01 +0100 (BST) Message-ID: <5ABFD09D.8070903@gfsys.co.uk> Date: Sat, 31 Mar 2018 18:17:01 +0000 From: Chris User-Agent: Mozilla/5.0 (X11; SunOS sun4u; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2 MIME-Version: 1.0 To: "Rodney W. Grimes" , freebsd-xen@freebsd.org Subject: Re: [Bug 224003] xen kernel panics References: <201803301805.w2UI531x069099@pdx.rh.CN85.dnsmgr.net> <5ABFCF3A.1010601@gfsys.co.uk> In-Reply-To: <5ABFCF3A.1010601@gfsys.co.uk> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit 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 18:17:05 -0000 Here are all the config files: ### /etc/sysctl.conf: #security.bsd.see_other_uids=0 kern.randompid=3854 # # Xen Kernel vm.max_wired=-1 ### /etc/login.conf ~/bin:\ :nologin=/var/run/nologin:\ :cputime=unlimited:\ :datasize=unlimited:\ :stacksize=unlimited:\ :memorylocked=unlimited:\ :memoryuse=unlimited:\ :filesize=unlimited:\ :coredumpsize=unlimited:\ :openfiles=unlimited:\ :maxproc=unlimited:\ :sbsize=unlimited:\ :vmemoryuse=unlimited:\ :swapuse=unlimited:\ :pseudoterminals=unlimited:\ :kqueues=unlimited:\ :umtxp=unlimited:\ :priority=0:\ :ignoretime@:\ :umask=022: ### /etc/ttys: # # Xen Console # ----------- xc0 "/usr/libexec/getty Pc" xterm on secure # ### /boot/menu.rc.local # # Xen kernel try-include /boot/xen.4th ### /boot/loader.conf # # Xen Kernel # ---------- hw.pci.mcfg=0 xen_kernel="/boot/xen" xen_cmdline="dom0_mem=2048M dom0_max_vcpus=6 dom0pvh=1 console=com1, vga com1=115200,8n1 guest_loglvl=all loglvl=all" ### /etc/rc/conf # # Local rc.conf, icq, 30-Jun-2017 # 09-Mar-2018 # ------------------------------- hostname="freebsdxen" # # Network ifconfig_bce0="inet 192.9.xxx.xxx netmask 255.255.255.0" defaultrouter="192.9.xxx.xxx" # # Services sshd_enable="YES" ntpd_enable="YES" ntpdate_enable="YES" ntpd_sync_on_start="YES" zfs_enable="YES" powerd_enable="YES" # # Radeon Kernel Mode Driver kld_list="radeonkms" # # Gui Services moused_enable="YES" dbus_enable="YES" hald_enable="YES" slim_enable="YES" # # Disabled Services sendmail_enable="NONE" # # Set dumpdev to "AUTO" to enable crash dumps, "NO" to disable dumpdev="AUTO" # # Xen Configuration # ----------------- xencommons_enable="yes" # autobridge_interfaces="bridge0" # autobridge_bridge0="igb0" Regards, Chris From owner-freebsd-xen@freebsd.org Sat Mar 31 18:24:45 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 CB5BAF76098 for ; Sat, 31 Mar 2018 18:24:45 +0000 (UTC) (envelope-from syseng@gfsys.co.uk) Received: from smtp.livemail.co.uk (smtp-out-60.livemail.co.uk [213.171.216.60]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "smtp.livemail.co.uk", Issuer "thawte SSL CA - G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 677036FDBF for ; Sat, 31 Mar 2018 18:24:45 +0000 (UTC) (envelope-from syseng@gfsys.co.uk) Received: from [192.9.200.226] (host81-133-228-57.in-addr.btopenworld.com [81.133.228.57]) (Authenticated sender: syseng@gfsys.co.uk) by smtp.livemail.co.uk (Postfix) with ESMTPA id 238CD26091A; Sat, 31 Mar 2018 19:24:44 +0100 (BST) Message-ID: <5ABFD26B.8030601@gfsys.co.uk> Date: Sat, 31 Mar 2018 18:24:43 +0000 From: Chris User-Agent: Mozilla/5.0 (X11; SunOS sun4u; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2 MIME-Version: 1.0 To: "Rodney W. Grimes" , freebsd-xen@freebsd.org Subject: Re: [Bug 224003] xen kernel panics References: <201803301805.w2UI531x069099@pdx.rh.CN85.dnsmgr.net> <5ABFCF3A.1010601@gfsys.co.uk> In-Reply-To: <5ABFCF3A.1010601@gfsys.co.uk> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit 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 18:24:46 -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 >> >> 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.... Regards, Chris 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"