Re: [Xen-devel] [TestDay] Xen crash on boot

[Eric Houby <ehouby@xxxxxxxxx>]

On Fri, 2014-01-24 at 09:01 +0000, Jan Beulich wrote:
> >>> On 24.01.14 at 01:47, Eric Houby <ehouby@xxxxxxxxx> wrote:
> > On Thu, 2014-01-23 at 11:16 +0000, Jan Beulich wrote:
> >> If
> >> the kernel responds to that mentioned firmware bug by forcing
> >> interrupt remapping off, maybe we would have to do the same...
> > 
> > That would be better than xen failing to boot.
> 
> You may also want to try booting with "ivrs_ioapic[0]=00:14.0" or
> "ivrs_ioapic[1]=00:14.0", but I'm afraid that would still not work
> properly as the base system related ACPI tables are also lacking
> that second IO-APIC (and I'm not convinced that adding a
> respective command line option would help either).
> 
> Jan
> 

I tried the above ivrs_ioapic commands and didn't see any improvements
in behavior.  Logs of xen booting four times with different combinations
of ivrs_ioapic.

(XEN) Command line: placeholder dom0_mem=2048M,max:2048M
dom0_max_vcpus=2 dom0_vcpus_pin loglvl=all guest_loglvl=all
iommu=debug,verbose ivrs-ioapic[1]=00:14.0 com1=38400,8n1,pci
console=com1

(XEN) Command line: placeholder dom0_mem=2048M,max:2048M
dom0_max_vcpus=2 dom0_vcpus_pin loglvl=all guest_loglvl=all
iommu=debug,no-intremap ivrs-ioapic[1]=00:14.0 com1=38400,8n1,pci
console=com1

(XEN) Command line: placeholder dom0_mem=2048M,max:2048M
dom0_max_vcpus=2 dom0_vcpus_pin loglvl=all guest_loglvl=all
iommu=debug,verbose ivrs-ioapic[0]=00:14.0 com1=38400,8n1,pci
console=com1

(XEN) Command line: placeholder dom0_mem=2048M,max:2048M
dom0_max_vcpus=2 dom0_vcpus_pin loglvl=all guest_loglvl=all
iommu=debug,verbose,no-intremap com1=38400,8n1,pci console=com1

-Eric

Attachment: ivrs-ioapic.txt
Description: Text document

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel