Bug 689380

Please attach y2logs. If you are in doubt follow:
http://en.opensuse.org/openSUSE:Bugreport_YaST
Thanks!

Created attachment 428884 [details]
y2log

this is the yast log...

Could you please attach all needed logs as described as follows?

http://en.opensuse.org/openSUSE:Bugreport_YaST#I_reported_a_YaST2_bug.2C_and_now_I_am_asked_to_.22attach_y2logs.22._What_does_that_mean.2C_and_how_do_I_do_that.3F

Thank you.

Created attachment 429379 [details]
Yast Logs

Attaches all Yast logs

(In reply to comment #0)
> I have a server running xenserver 5.6fp1 which has multiple instances of
> OpenSUSE 11.3 x64 running on it.  After change to a intel DH67gdb3 motherboard
> and Intel i7 2600 processor yast2 will no longer load returning error:
> sbin/yast2: line 399:  2603 Illegal instruction     $ybindir/y2base $module
> "$@" "$SELECTED_GUI" $Y2_GEOMETRY $Y2UI_ARGS

Does yast2 only crash in the guest installation or does it also crash on the host just bringing up the 'YaST2 Control Center'?

Are the guests you are installing fully virtualized or para virtualized?

When I try to install an openSUSE guest from scratch after it loads the installer system and starts to load YAST it returns a message saying there was
an error with the installation.

When I try to run yast from the command line on an already setup openSUSE guest it returns: sbin/yast2: line 399:  2603 Illegal instruction     $ybindir/y2base $module "$@" "$SELECTED_GUI" $Y2_GEOMETRY $Y2UI_ARGS

All guests are para-virtualized

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.

Created attachment 433281 [details]
Messages log

I exported all the guests and reinstalled xenserver 5.6 SP2 from scratch and then imported the guests back.  I have also attached the messages log and I restarted the guest on june 7 at about 9:25 if that helps any.

I guess it would be helpful if I mentioned that the problem still exists after reinstalling Xenserver.

Thanks

While we want our openSUSE guests to run well on Xenserver, we cannot reproduce this problem given that 1) the motherboard swap seems to have introduced the problem and 2) Xenserver is not our product and we don't have much experience with it.