Date: Wed, 16 Oct 2019 11:12:30 +0200 From: Roger Pau =?iso-8859-1?Q?Monn=E9?= <roger.pau@citrix.com> To: Stefan Parvu <sparvu@kronometrix.org> Cc: <freebsd-xen@freebsd.org> Subject: Re: cannot install FreeBSD 12.0 Xen 4.12.1 on Intel Core i7 CPU 930 Message-ID: <20191016091230.GF14005@Air-de-Roger> In-Reply-To: <9D9848D6-2634-4777-9EE0-8DECAD2FE5CD@kronometrix.org> References: <DEEE41ED-5D88-439B-B583-7C3450C696FF@kronometrix.org> <20191016084050.GD14005@Air-de-Roger> <4D6CBDA5-711B-4501-AFC1-A41D1134EF73@kronometrix.org> <20191016090022.GE14005@Air-de-Roger> <9D9848D6-2634-4777-9EE0-8DECAD2FE5CD@kronometrix.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Oct 16, 2019 at 12:07:50PM +0300, Stefan Parvu wrote: > > > If your box doesn't have a serial header, you can add noreboot to > > xen_cmdline and paste a photo of the screen with the panic message, > > it's not great but at least we would get an idea of what's wrong. > > > > Im not sure I can setup a serial console on this wkst. Will check. > > The last thing I see is this: > http://www.kronometrix.org/bugs/freebsd_xen.jpg <http://www.kronometrix.org/bugs/freebsd_xen.jpg>; but nothing like a thread dump, > stack trace etc … Your box doesn't seem to have an iommu (aka vt-d for Intel). > But you need all boot log. I will try your option tonight. I cant access the hardware now. If you can that would be helpful, but AFAIK this box is simply not capable of running a Xen PVH dom0 (which is the only mode FreeBSD supports in order to work as dom0). Either it has a broken iommu or no iommu at all. Roger.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20191016091230.GF14005>