On 12/01/2014 04:48 AM, Bob Ball wrote:
Hi all,
Following instructions at http://wiki.centos.org/QaWiki/Xen4 to setup Xen on CentOS 6.4. Unfortunately after installing Xen and modifying the boot line there is a kernel panic during the boot process causing the host to enter a reboot loop. Console log attached.
[<ffffffff81575480>] panic+0xc4/0x1e1 [<ffffffff81054836>] find_new_reaper+0x176/0x180 [<ffffffff81055345>] forget_original_parent+0x45/0x2c0 [<ffffffff81107214>] ? task_function_call+0x44/0x50 [<ffffffff810555d7>] exit_notify+0x17/0x140 [<ffffffff81057053>] do_exit+0x1f3/0x450 [<ffffffff81057305>] do_group_exit+0x55/0xd0 [<ffffffff81057397>] sys_exit_group+0x17/0x20 [<ffffffff815806a9>] system_call_fastpath+0x16/0x1b
xen-4.2.2-23.el6.centos.alt.x86_64 kernel-3.4.53-8.el6.centos.alt.x86_64
title xen root (hd0,0) kernel /xen.gz dom0_mem=256M,max:256M loglvl=all guest_loglvl=all module /vmlinuz-3.4.53-8.el6.centos.alt.x86_64 ro root=/dev/mapper/vg_cs-lv_root rd_NO_LUKS KEYBOARDTYPE=pc KEYTABLE=uk LANG=en_US.UTF-8 rd_LVM_LV=vg_cs/lv_root rd_Np module /initramfs-3.4.53-8.el6.centos.alt.x86_64.img
This issue was found in an automated environment that actually uses Dave Scott's Xen 4.4 branch (http://xenbits.xen.org/djs/centos-xen-4-4/) however in trying to diagnose the issue we found that the base xen-c6 combination failed in the same way. Note also that the last successful run (which was a while ago due to a configuration issue) used the same xen and kernel as the now-failing environments. Both the failing and passing environments are using xen-4.4.0-2.el6.x86_64 and kernel-3.4.53-8.el6.centos.alt.x86_64.
Is the current combination of xen/kernel in xen-c6 working for others at the moment? Are there any thoughts on what might be causing this regression?
Bob
It works fine for me .. you might consider using CentOS-6.6 and not CentOS-6.4 .. also, we now use a 3.10 kernel and the latest version of xen is 4.2.5 in the /6.6/xen4/ repo.
Use this link: http://wiki.centos.org/HowTos/Xen/Xen4QuickStart
BUT .. it seems to be a hardware/driver issue.
Thanks, Johnny Hughes