Re: pvops acpi and xen 4 issues

[Jeremy Fitzhardinge <jeremy@goop.org>]

On 02/26/2010 12:33 PM, M. Nunberg wrote:
> I recently tested the kernels from xen/next and xen/stable, together
> with Xen 4.0 rc4, and experienced issues with all of them.
>
> The main issues seem to be with iommu (which fails with the same thing
> every time i try it, on various xen versions), as well as ACPI (which
> seems to be unique to the pvops kernels.
>    

xen/next and xen/stable don't yet have full ACPI support for things like 
CPU performance control.  But your ACPI problem looks more fundimental 
than that.  Try xen/master to see if it is any different.

> Unfortunately, because the systems takes such a long time to  boot (and
> this is my only usable machine), I do not have the ability (or rather
> patience) to test many different configurations and such. But I am
> throwing these logs out there in case they might be helpful.
>    

I'd like to see a native boot of, say, xen/next, and a Xen+native boot 
of xen/master, and the contents of /proc/interrupts for each case.

Why does the machine take so long to boot?  Does it have a painfully 
slow-booting BIOS?

> Attached are four bzipped text file:
>    

(Unless the files are really huge, please post uncompressed; it's much 
easier to be able to browse them inline with the mail rather than having 
to separately detach/decompress.)

> dmidecode.bz2: output from dmidecode on a running system
> lspci.bz2: output from lspci
>
> the above two files should provide a complete picture of the hardware
> i'm using.
>
> xen4pvops-iommu.bz2: log of xen/stable (i think, it could be xen/next,
> but the output was more or less the same) with iommu enabled on the
> hypervisor
> xen4pvops-noiommu.bz2: log of the same (i think) with iommu disabled.
>
> The main issue with iommu is that it cannot find my / which resides on a
> megasas raid (perc 5i) controller. I think the USB issues in the log
> might be because of CPU issues and are attributable to the newer version
> of xen.
>
> The config for all these kernels is more or less based on pasi's config,
> with some optimization options tweaked for my kernel (e.g. core2, SMT
> support) and some other things removed which i  will never use (e.g.
> exotic PATA controllers)
>
> I might include some more logs later if I have the time and am asked for
> it.
>    

Can you boot the same kernel natively?  I'm interested to see 
/proc/interrupts; it appears you have the ACPI SCI interrupt on irq 20, 
which is unusual (its usually 9).  Also, does it boot correctly natively 
with the DMAR enabled?  Some drivers are still broken.

     J