Date: Mon, 22 Feb 2016 13:34:31 +0100 From: =?UTF-8?Q?Gustau_P=c3=a9rez?= <gustau.perez@gmail.com> To: =?UTF-8?Q?Roger_Pau_Monn=c3=a9?= <roger.pau@citrix.com>, FreeBSD XEN <freebsd-xen@freebsd.org> Subject: Re: Porting the block-iscsi hotplug script Message-ID: <56CB0057.1060509@gmail.com> In-Reply-To: <56CADEDA.4050007@citrix.com> References: <553DEB97.5000300@entel.upc.edu> <5540A053.4080409@entel.upc.edu> <5540F3FC.80606@citrix.com> <5541FC8A.8080009@citrix.com> <5542365D.10403@entel.upc.edu> <55423ECD.6000404@citrix.com> <5556F21D.2050005@entel.upc.edu> <555EEFBA.5080902@citrix.com> <555EF542.3090002@citrix.com> <555F9B3F.1000600@entel.upc.edu> <55602512.1090702@citrix.com> <56C6FA2F.8040900@gmail.com> <56CAC8CB.8030107@gmail.com> <56CADEDA.4050007@citrix.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> It might be that the IOMMU has an errata and Xen refuses to enable it. > Can you provide the serial output when you try to boot Xen + FreeBSD? > You might have to add console="com1,vga" to your xen_cmdline (although > AFAIK that's the default). > Hi Roger, I was able to get a dump of the output via the serial console [1]. If I force the detection of the iommu with [2] the system is able to boot the domU kernel and then it panics [3], it would appear it panics when detecting atapci0. Here I'm lost. Greets, Gustau [1] http://pastebin.com/yt27y6hM [2] iommu=force,no-intremap [3] http://pastebin.com/BQ8Y1ViT
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?56CB0057.1060509>