https://bugzilla.novell.com/show_bug.cgi?id=675363 https://bugzilla.novell.com/show_bug.cgi?id=675363#c30 Jan Beulich <jbeulich@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEEDINFO InfoProvider| |jfunk@funktronics.ca --- Comment #30 from Jan Beulich <jbeulich@novell.com> 2011-04-12 09:32:59 UTC --- (In reply to comment #29) There are way too few kernel messages in there - did you change your kernel log level? Without those messages being complete we cannot be sure that none of the debugging printk()-s ever triggered, and hence this run only tells us that (as expected) what used to be a hypervisor crash now is a kernel one. Adding "ignore_loglevel" to the kernel (not Xen) command line generally is a good idea if you're not certain about your kernel log level setting (or don't want to modify it globally).
I really hope this provides enough information. This is a work system and today is my last day so I won't be able to do much testing. :-)
Does this mean we won't be able to make any progress here anymore? If so, could you at least still provide full hardware details (namely /proc/cpuinfo contents and "lspci -nn" output)? -- 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.