Date: Fri, 30 Mar 2018 17:43:21 +0000 From: Chris <syseng@gfsys.co.uk> To: =?ISO-8859-1?Q?Roger_Pau_Monn=E9?= <roger.pau@citrix.com>, freebsd-xen@freebsd.org Subject: Re: [Bug 224003] xen kernel panics Message-ID: <5ABE7739.2030008@gfsys.co.uk> In-Reply-To: <20180330120729.5jcuidllh2a4ya27@MacBook-Pro-de-Roger.local> References: <5ABD7783.3040901@gfsys.co.uk> <20180330120729.5jcuidllh2a4ya27@MacBook-Pro-de-Roger.local>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5ABE7739.2030008>