Hello,
I have compiled a new kernel-xen RPM with this patch included and it
boots now. So the patch is working. However, cluster startup fails as if there
were some version mismatch between the in-kernel dlm and userspace.
sh-3.2# tail /var/log/messages
Nov 12 15:26:38 openais[3863]: [TOTEM] entering OPERATIONAL state.
Nov 12 15:26:38 openais[3863]: [CLM ] got nodejoin message 10.1.29.81
Nov 12 15:26:38 openais[3863]: [CLM ] got nodejoin message 10.1.29.82
Nov 12 15:26:38 ccsd[3815]: Initial status:: Quorate
Nov 12 15:27:01 ccsd[3815]: Unable to connect to cluster infrastructure after
30 seconds.
Nov 12 15:27:31 ccsd[3815]: Unable to connect to cluster infrastructure after
60 seconds.
Nov 12 15:28:01 ccsd[3815]: Unable to connect to cluster infrastructure after
90 seconds.
Nov 12 15:28:31 ccsd[3815]: Unable to connect to cluster infrastructure after
120 seconds.
Nov 12 15:29:01 ccsd[3815]: Unable to connect to cluster infrastructure after
150 seconds.
Nov 12 15:29:09 ccsd[3815]: Stopping ccsd, SIGTERM received.
At that point I issued /etc/init.d/cman stop
cman-2.0.94-1.el5
kmod-gfs-0.1.28-1.el5
kmod-gfs-xen-0.1.28-1.el5
These packages are the newest available from RHN (I subscribed the systém to
beta channels for virtualisation, clustering and cluster storage too).
Has anyone tried cluster in the beta? It does not work even with the normal
non-xen kernel.
Thanks,
Daniel
-----Original Message-----
From: Anton Arapov [mailto:[EMAIL PROTECTED]
Sent: Tuesday, November 11, 2008 9:50 PM
To: Red Hat Enterprise Linux 5 (Tikanga) discussion mailing-list
Cc: Zavodsky, Daniel (GE Money)
Subject: Re: [rhelv5-list] RHEL 5.3 beta - kernel-xen fails to boot
On Tue, Nov 11, 2008 at 09:36:46AM +0100, Zavodsky, Daniel (GE Money) wrote:
> Hello,
> I have decided to try out the new RHEL 5.3 beta... I upgraded one
> testing 5.2 system but I cannot boot into the Xen kernel.
> The system is a 64-bit SunFire x4200 with 2x dual-core CPU and 16
> GB RAM. Has anyone had a similar experience with 5.3 beta or knows
> what is wrong?
Seems, the bug could be related to bugzilla #470202. There is the fix addressed
to issue. Will be great if you can test it.
https://bugzilla.redhat.com/show_bug.cgi?id=470202
Please, let me know if you will face the problems with compiling custom kernel.
I will provide you.
Thanks in advance!
-- Anton
> This is what I copied from the console:
>
>
> PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
> Memory: 689152k/794624k available (2445k kernel code, 96936k reserved,
> 1363k data, 184k init) Calibrating delay using timer specific
> routine.. 6483.26 BogoMIPS
> (lpj=12966525)
> Security Framework v1.0.0 initialized
> SELinux: Initializing.
> selinux_register_security: Registering secondary module capability
> Capability LSM initialized as secondary Mount-cache hash table
> entries: 256
> CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line)
> CPU: L2 Cache: 1024K (64 bytes/line)
> CPU: Physical Processor ID: 0
> CPU: Processor Core ID: 0
> (SMP-)alternatives turned off
> Initializing CPU#1
> Brought up 3 CPUs
> Initializing CPU#2
> migration_cost=383
> checking if image is initramfs... it is Grant table initialized
> NET: Registered protocol family 16
> ACPI Exception (utmutex-0262): AE_BAD_PARAMETER, Thread 11E27A0 could
> not acquire Mutex [2] [20060707] No dock devices found.
> ACPI Exception (utmutex-0262): AE_BAD_PARAMETER, Thread 11E27A0 could
> not acquire Mutex [2] [20060707]
> PCI: Using configuration type 1
> ACPI: Interpreter disabled.
> Linux Plug and Play Support v0.97 (c) Adam Belay
> pnp: PnP ACPI: disabled
> xen_mem: Initialising balloon driver.
> usbcore: registered new driver usbfs
> usbcore: registered new driver hub
> PCI: Probing PCI hardware
> Unable to handle kernel NULL pointer dereference at 0000000000000000
> RIP:
> [<ffffffff8034346a>] pci_create_bus+0x59/0x1f3 PGD 0
> Oops: 0000 [1] SMP
> last sysfs file:
> CPU 0
> Modules linked in:
> Pid: 1, comm: swapper Not tainted 2.6.18-120.el5xen #1
> RIP: e030:[<ffffffff8034346a>] [<ffffffff8034346a>]
> pci_create_bus+0x59/0x1f3
> RSP: e02b:ffff8800011ffd50 EFLAGS: 00010286
> RAX: ffff88002fefb000 RBX: ffff88002ff09200 RCX: 0000000000000000
> RDX: ffffffffff578000 RSI: 0000000000000005 RDI: 0000000000000000
> RBP: 0000000000000000 R08: ffff88002ff09400 R09: 0000000000000000
> R10: ffff8800011ffda0 R11: 0000000000000100 R12: ffff88002fefb000
> R13: 0000000000000005 R14: ffffffff805429d0 R15: 0000000000000000
> FS: 0000000000000000(0000) GS:ffffffff805b9000(0000)
> knlGS:0000000000000000
> CS: e033 DS: 0000 ES: 0000
> Process swapper (pid: 1, threadinfo ffff8800011fe000, task
> ffff8800011e27a0)
> Stack: 0000000000000005 0000000000000005 0000000000000004
> 0000000000000000 0000000000000000 0000000000000000 0000000000000000
> ffffffff8034433a
> 0000000000000005 ffffffff80650503
> Call Trace:
> [<ffffffff8034433a>] pci_scan_bus_parented+0x6/0x21
> [<ffffffff80650503>] pcibios_irq_init+0x177/0x491
> [<ffffffff806347e5>] init+0x1f9/0x2fe [<ffffffff8025fb2c>]
> child_rip+0xa/0x12 [<ffffffff80351d59>] vgacon_cursor+0x0/0x1a5
> [<ffffffff806345ec>] init+0x0/0x2fe [<ffffffff8025fb22>]
> child_rip+0x0/0x12
>
>
> Code: 8b 7d 00 e8 e2 43 00 00 48 85 c0 0f 85 68 01 00 00 48 c7 c7 RIP
> [<ffffffff8034346a>] pci_create_bus+0x59/0x1f3 RSP <ffff8800011ffd50>
> CR2: 0000000000000000
> <0>Kernel panic - not syncing: Fatal exception
> (XEN) Domain 0 crashed: rebooting machine in 5 seconds.
>
>
>
> Best regards,
> Daniel Zavodsky
> _______________________________________________
> rhelv5-list mailing list
> [email protected]
> https://www.redhat.com/mailman/listinfo/rhelv5-list
--
-Anton
_______________________________________________
rhelv5-list mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/rhelv5-list
