From: "M. Nunberg" <mnunberg@haskalah.org>
To: xen-devel@lists.xensource.com
Subject: pvops acpi and xen 4 issues
Date: Fri, 26 Feb 2010 12:33:42 -0800 [thread overview]
Message-ID: <1267216422.31593.15.camel@debmed> (raw)
[-- Attachment #1: Type: text/plain, Size: 1559 bytes --]
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
[-- Attachment #2: dmidecode.bz2 --]
[-- Type: application/x-bzip, Size: 4557 bytes --]
[-- Attachment #3: lspci.bz2 --]
[-- Type: application/x-bzip, Size: 5093 bytes --]
[-- Attachment #4: xen4pvops-iommu.bz2 --]
[-- Type: application/x-bzip, Size: 18009 bytes --]
[-- Attachment #5: xen4pvops-noiommu.bz2 --]
[-- Type: application/x-bzip, Size: 15748 bytes --]
[-- Attachment #6: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
next reply other threads:[~2010-02-26 20:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-26 20:33 M. Nunberg [this message]
2010-02-26 23:23 ` pvops acpi and xen 4 issues Jeremy Fitzhardinge
2010-02-27 2:22 ` M. Nunberg
2010-03-01 16:13 ` Konrad Rzeszutek Wilk
2010-03-04 22:04 ` M. Nunberg
2010-03-08 20:02 ` Konrad Rzeszutek Wilk
2010-03-10 19:44 ` M. Nunberg
2010-03-10 23:48 ` Jeremy Fitzhardinge
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1267216422.31593.15.camel@debmed \
--to=mnunberg@haskalah.org \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).