From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andrew Cooper Subject: Re: [TestDay] Xen crash on boot Date: Fri, 24 Jan 2014 01:44:03 +0000 Message-ID: <52E1C563.7050406@citrix.com> References: <1390244796.2322.6.camel@astar.houby.net> <52DE4CA1020000780011547D@nat28.tlf.novell.com> <1390297542.20516.90.camel@kazak.uk.xensource.com> <000001cf1695$0c960450$25c20cf0$@yahoo.com> <52DF8FB90200007800115AEC@nat28.tlf.novell.com> <1390455621.2415.56.camel@astar.houby.net> <52E1083602000078001161D5@nat28.tlf.novell.com> <1390524450.2281.12.camel@astar.houby.net> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <1390524450.2281.12.camel@astar.houby.net> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: ehouby@yahoo.com, Jan Beulich Cc: Ian Campbell , suravee.suthikulpanit@amd.com, xen-devel@lists.xen.org List-Id: xen-devel@lists.xenproject.org On 24/01/2014 00:47, Eric Houby wrote: > On Thu, 2014-01-23 at 11:16 +0000, Jan Beulich wrote: > >> But you didn't turn on interrupt remapping, or it got forcibly >> disabled: >> >> [Firmware Bug]: AMD-Vi: No southbridge IOAPIC found >> AMD-Vi: Disabling interrupt remapping > > Jan, > > If there is not a specific switch required to enable interrupt remapping > while booting 3.12.7 on bare hardware, then it was forcibly disabled. > Would boot logs from xen 4.1.3 be helpful? If so, they are attached. > >> If >> the kernel responds to that mentioned firmware bug by forcing >> interrupt remapping off, maybe we would have to do the same... >> >> Jan > > > That would be better than xen failing to boot. > > > Thanks, > > -Eric You probably want "iommu=debug,verbose" rather than verbos ~Andrew