WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

Re: [Xen-users] Xen 4.0.1 kernel panic

To: mohammad mohammadi <m_mohammadi_dinani@xxxxxxxxx>
Subject: Re: [Xen-users] Xen 4.0.1 kernel panic
From: "Fajar A. Nugraha" <list@xxxxxxxxx>
Date: Sat, 12 Mar 2011 20:57:17 +0700
Cc: xen-users@xxxxxxxxxxxxxxxxxxx
Delivery-date: Sat, 12 Mar 2011 05:59:16 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <218147.22005.qm@xxxxxxxxxxxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <218147.22005.qm@xxxxxxxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
On Sat, Mar 12, 2011 at 2:17 PM, mohammad mohammadi
<m_mohammadi_dinani@xxxxxxxxx> wrote:
> Hi
>
> Has anybody got an idea why xen 4.0.1 panics during boot?!
> I have a Tyan server with 48 AMD cores and 128GB RAM. I compiled and
> installed xen 3.X along with CentOS 5.5 default xen kernel. Everything was
> OK there. The only problem I had was that CentOS kernel is allowed to see
> only 32 cores and 32GB of RAM which is actually supposed to be. However I
> wanted to see all cores and RAM in dom0,

Why?

For most practical purposes, it's useless to have all cores and RAM in dom0:
- you'd want to start domU's, which would require memory, thus dom0
memory would need to balloon-down. Doing so involves some overhead
(and depending on some circumstances like the amount ballooned-down,
it can cause crash)
- domUs will need some processing power, thus making all cores
available to dom0 is kinda pointless as domU will take some processing
power from it anyway

Best practice is to:
- dedicate a certain amount of RAM to dom0 (usually 512M - 1G is
enough), so dom0 will never need to balloon down
- dedicate one core (or more, depending on what you run on dom0) and
set domUs to use other cores.

> so I went for xen 4.0.1

Why?

Do you know the difference between xen HYPERVISOR and dom0 KERNEL?
If you say "CentOS kernel is allowed to see only 32 cores and 32GB of
RAM" then you should be compiling a kernel, not the hypervisor.

FWIW, if you need to use Xen 4.0.1 hypervisor with RHEL/Centos
kernel-xen, last time I check yo need "pci=nomsi" on some
configurations (in my case it was HP smart array). Also, comment-out
"quiet" and "rhgb" so you can see better what cause the kernel panic.
Your grub/menu.lst should look something like this

title CentOS (2.6.18-194.el5.customxen)
        root (hd0,1)
        kernel /boot/xen-4.0.1.gz
        module /boot/vmlinuz-2.6.18-194.el5.customxen ro root=LABEL=/ pci=nomsi
        module /boot/initrd-2.6.18-194.el5.customxen.img

-- 
Fajar

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users

<Prev in Thread] Current Thread [Next in Thread>