https://bugzilla.novell.com/show_bug.cgi?id=851445
https://bugzilla.novell.com/show_bug.cgi?id=851445#c2
--- Comment #2 from A R
What's the reason you picked component Xen rather than Kernel?
this OOPS was only occurring when booting to kernel-xen+Xen. hence, "Xen", and the initial caveat: "I'll **start** here ..."
Also posting partial logs is generally not helpful - please attach full guest kernel logs (from both the oopsing and non-oopsing attempts).
as I've continued to investigate, I find -- so far -- ALL my machines (atm, 4) that (1) are working 12.3+xen Dom0 servers (2) have /boot-on-RAID(soft, RAID-1) and LVM-on-RAID(soft, RAID1 or RAID10) (3) have nfs-kernel-server installed (4) mount shares @ other nfs servers (5) have been in-place upgraded to 13.1 are now failing to boot. Booting these machines to kernel-xen+Xen always hangs, and results frequently-not-always in an OOPS; booting the same machines to kernel-default always hangs, but no OOPS. OTOH, all upgraded machines that are Xen Guests, or just kernel-desktop or kernel-default boots, and have NO RAID in the mix, but DO have !boot-on-LVM are booting OK. that's true for both new installs, and in-place 12.3 -> 13.3 upgrades. ATM, I'm trying to figure out if/how mdadm + lvm2 is involved, if not responsible ... (https://bugzilla.novell.com/show_bug.cgi?id=851741 and http://www.spinics.net/lists/raid/msg44943.html) I'm working to get something consistent/useful to post/attach. No problem for me if this issue gets moved to !Xen. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.