https://bugzilla.novell.com/show_bug.cgi?id=689380 https://bugzilla.novell.com/show_bug.cgi?id=689380#c8 --- Comment #8 from Charles Arnold <carnold@novell.com> 2011-06-03 21:08:21 UTC --- With a significant hardware change resulting in a crash in yast2, I'm not sure this problem can be duplicated in order to debug it. There are Xen tools to capture the state of an entire guest when it crashes, but nothing that notices crashes within the guest from user space modules. I suppose the best approach would be to work with a guest that is already installed. The assumption is that it boots up ok. Check the /var/log/messages file from the guest after booting for errors and attach to this bug. Based on the error from the description, the /sbin/yast2 script could be debugged to trace the source of the error but I would think one of the yast engineers would be better suited for that (Jiri?). As a 'when all else fails' approach, you may want to try re-installing the Xen kernel, hypervisor and tools in your xenserver 5.6fp1 if that is possible. However, without knowing the real cause of the 'Illegal instruction' in yast I don't know if this would help. -- 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.