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.
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.
Attached are four bzipped text file:
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.
Regards
dmidecode.bz2
Description: application/bzip
lspci.bz2
Description: application/bzip
xen4pvops-iommu.bz2
Description: application/bzip
xen4pvops-noiommu.bz2
Description: application/bzip
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
| 
Home