From: Alex Moskalenko <mav@elserv.ru>
To: xen-devel@lists.xen.org
Subject: Re: Pv_ops Dom0 crash on IBM eServer x3400
Date: Thu, 07 Jun 2012 23:00:00 +0400 [thread overview]
Message-ID: <4FD0FA30.6080705@elserv.ru> (raw)
In-Reply-To: <20120607172402.GS9472@phenom.dumpdata.com>
07.06.2012 21:24, Konrad Rzeszutek Wilk пишет:
> On Thu, Jun 07, 2012 at 01:29:33PM +0400, Alex Moskalenko wrote:
>> Hi people,
>>
>> I ran into a trouble when trying to run Xen 4.1.x with pv_ops kernel
>> on IBM eServer x3400. Without noacpi command line option dom0 kernel
> Well yes! We don't do 'noacpi' Why do you supply 'noacpi'?
If I don't supply 'noacpi' option, dom0 kernel crashes with messages
mentioned in my previous letter. 'noacpi' allows kernel to boot with
some IRQ issues (only RAID ant network adapters work properly, any other
onboard PCI device does not work at all).
>> crashes on ACPI initialization. Kermels 2.6.32 (with konrad xen
>> patches), 3.1, 3.3, Xen 4.1.2 behave the same way. Without
>> hypervisor all kernels run without any problems.
>>
>> There are several patches (available on http://git.altlinux.org/people/silicium/packages/?p=kernel-image.git;a=shortlog;h=refs/heads/kernel-image-xen-dom0,
>> commits f1f91babc9cc9402ccee8938b888240f5bae1574,
>> 72db7b5e069002765ced64f030c1117d72352331,
>> adc4c567a08d4d2377060179639cbfdc3d9d8e0e and
>> 9beeac5589ce5c415e4513016c78e96374b8a895) that allow kernel 2.6.32
>> to boot on this hardware. This patches written by kernel package
>> maintainer of ALT Linux distribution. Discussion of this issue is
>> available on Sysadmins ALTLinux mailing list
>> (http://lists.altlinux.org/pipermail/sysadmins/2011-April/034471.html
>> and follows) in Russian.
>>
>> I attached Xen 4.1.0 with kernel 2.6.32 crash messages. If you need
>> this messages for more recent versions of Xen and kernel, or more
>> information about hardware, please let me know.
> Please provide the crash using the v3.4 kernel.
I will provide it as soon as possible.
>> Ideally, I would like to run current versions of Xen and Linux
>> kernels on this hardware. Can you help me please?
> Well sure. But pls explain to me why:
> - you are using 'noacpi'
> - why are not using the v3.4 kernel?
- Only with 'noacpi' kernel does not crush. Without it kernel crashes
with logs I previously attached.
- I deal with this issue in April 2011, when 3.x kernel was not yet
ready to work as dom0 kernel. Periodically I test new kernel versions
(3.1, 3.2, 3.3 including 3.3.8), bul all of they are also crashing in
ACPI initialization. I will try 3.4 kernel as soon as possible.
Thank you for reply!
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2012-06-07 19:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-07 9:29 Pv_ops Dom0 crash on IBM eServer x3400 Alex Moskalenko
2012-06-07 17:24 ` Konrad Rzeszutek Wilk
2012-06-07 19:00 ` Alex Moskalenko [this message]
2012-06-07 21:25 ` Pasi Kärkkäinen
2012-06-08 7:43 ` Jan Beulich
2012-06-08 10:19 ` Alex Moskalenko
2012-06-08 11:47 ` Jan Beulich
2012-06-08 21:11 ` Alex Moskalenko
2012-06-11 7:59 ` Jan Beulich
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=4FD0FA30.6080705@elserv.ru \
--to=mav@elserv.ru \
--cc=xen-devel@lists.xen.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.