From: Cris Daniluk <cris.daniluk@gmail.com>
To: "Pasi Kärkkäinen" <pasik@iki.fi>
Cc: xen-devel@lists.xensource.com
Subject: Re: Dom0 panic on xen 3.4.3
Date: Fri, 20 Aug 2010 20:20:54 -0400 [thread overview]
Message-ID: <AANLkTi=jOdNFU-G9QHwR-VbcqREr+=jrjbxaCCC7Zptc@mail.gmail.com> (raw)
In-Reply-To: <20100820235913.GU2804@reaktio.net>
On Fri, Aug 20, 2010 at 7:59 PM, Pasi Kärkkäinen <pasik@iki.fi> wrote:
> On Fri, Aug 20, 2010 at 02:15:25PM -0400, Cris Daniluk wrote:
>> I'm running Xen 3.4.3 final and observing the following kernel panic
>> when I fire up the 9th domU. dom0 is CentOS 5.5 running a XenLinux
>> kernel. grub.conf entry is below, followed by the dump. The kernel
>> crash is immediately after the 9th domU is unpaused.
>>
>> title Xen 3.4.3 CentOS (2.6.18-194.11.1.el5xen)
>> root (hd0,0)
>> kernel /xen-3.4.3.gz dom0_mem=768M loglvl=all guest_loglvl=all
>> com1=38400
>> 0,8n1 console=com1 sync_console noreboot
>> module /vmlinuz-2.6.18-194.11.1.el5xen ro root=/dev/vg_internal/lv_base
>> console=hvc0,38400 norhgb netloop.nloopbacks=100
>> module /mpp-2.6.18-194.11.1.el5xen.img
>> title CentOS (2.6.18-194.11.1.el5) with MPP
>> root (hd0,0)
>>
>
> so I assume this crash doesn't happen if you use the el5 default xen hypervisor?
>
> Have you tried using latest linux-2.6.18-xen (from xen.org) ?
>
> -- Pasi
>
The dom0 kernel is the el5 default, but I have not tried running their
hypervisor since it is so dated. I'll give a shot with the latest
xen.org kernel.
Thanks,
Cris
next prev parent reply other threads:[~2010-08-21 0:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-20 18:15 Dom0 panic on xen 3.4.3 Cris Daniluk
2010-08-20 23:59 ` Pasi Kärkkäinen
2010-08-21 0:20 ` Cris Daniluk [this message]
2010-08-21 10:12 ` Pasi Kärkkäinen
2010-08-21 22:27 ` Cris Daniluk
2010-11-01 10:28 ` Paolo Bonzini
2010-12-28 0:50 ` prickett233
2010-12-28 10:38 ` Pasi Kärkkäinen
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='AANLkTi=jOdNFU-G9QHwR-VbcqREr+=jrjbxaCCC7Zptc@mail.gmail.com' \
--to=cris.daniluk@gmail.com \
--cc=pasik@iki.fi \
--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).