Date: Fri, 11 Mar 2016 23:03:27 +0900 (JST) From: =?UTF-8?Q?Roger_Pau_Monn=C3=A9?= <royger@FreeBSD.org> To: "skarida@gmail.com" <skarida@gmail.com> Cc: freebsd-xen@freebsd.org Subject: Re: FreeBSD 11 XEN Dom0 hangs and reboot Message-ID: <alpine.OSX.2.20.1603112300430.24317@macbook-air-de-roger.local> In-Reply-To: <CALggc5r25yTZkNELvx=sCV0M%2BmnHuSo%2B4bL3vqeCF5VgPxdvtA@mail.gmail.com> References: <CALggc5r25yTZkNELvx=sCV0M%2BmnHuSo%2B4bL3vqeCF5VgPxdvtA@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 11 Mar 2016, skarida@gmail.com wrote: Hello, > Hello all, > > I have tried to run FreeBSD 11 rev.296614 and /usr/ports/emulator/xen on > two different hardware configurations and the result was the same. XEN > kernel loads successfully but it hangs and restart on dom0 Init with > *"Error* creating domain 0" and "ELF boundaries" error. > > I tried on : > *) Dell Vostro with CPU i7-2640M > *) SuperMicro X10DRW-N with CPU E5-2667 v3 > > Both CPU are listed to support VT-d and VT-x. On both machines I have EPT > and DMAR available. > On both machines virtualization is enabled in BIOS. > > How can I proceed to catch the error source hardware related, XEN related > or FreeBSD related ? This has also been reported in the freebsd-virt mailing list: https://lists.freebsd.org/pipermail/freebsd-virtualization/2016-March/004257.html It seems like something is broken while linking the kernel, so the resulting ELF program headers physical address is wrong. AFAICT using r295683 or older revisions should work fine. As said in the other email, I'm currently bisecting the kernel in order to try to find the cause of the issue. Roger.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.OSX.2.20.1603112300430.24317>