https://bugzilla.novell.com/show_bug.cgi?id=715980 https://bugzilla.novell.com/show_bug.cgi?id=715980#c1 André Jagusch changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |myself@andrejagusch.de --- Comment #1 from André Jagusch 2011-09-19 16:44:04 UTC ---

Reproducible: Always

Steps to Reproduce: 1. start a opensuse 11.4 with a xen kernel 2. open /sbin/yast

Actual Results: not startable. xen doesn't work either

Hi, I can reproduce the error message and behaviour with regards to yast. It is possible however to use xen domUs on my machine after executing: chkconfig xencommons off and rebooting the machine. Best Regards, Andre -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=715980 https://bugzilla.novell.com/show_bug.cgi?id=715980#c3 Karl Scowen changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |karl@mailx1.com --- Comment #3 from Karl Scowen 2011-10-18 21:04:13 UTC --- I've found the same with a SUSE Studio build I did. YaST gives me the error sbin/yast2: line 423: 5057 Illegal instruction $ybindir/y2base $module "$@" "$SELECTED_GUI" $Y2_GEOMETRY $Y2UI_ARGS The same message is given whether VT_x is enabled or disabled in the BIOS. Sometimes YaST won't even start, other times it only occurs when loading a YaST module. But it always occurs before I can do anything with YaST. I don't know if Xen virtualisation works or not as I haven't tried. I've found that the build works fine in VirtualBox. Firefox doesn't work when running on hardware, but works fine in VirtualBox once again – which may or may not be related. My hardware is a Sandy Bridge i5 2500K CPU in a Gigabyte GA-P67A-UD3R-B3 motherboard with 4 GB RAM. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=715980 https://bugzilla.novell.com/show_bug.cgi?id=715980#c5 Raymond Obin changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |suse@beneford.com --- Comment #5 from Raymond Obin 2011-11-30 11:05:28 UTC --- If anyone needs a work-around, I have just switched from xen to kvm on OpenSuSE 11.4. KVM appears to be working fine with my Windows 2011 SBS and SuSE11.4 VMs. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=715980 https://bugzilla.novell.com/show_bug.cgi?id=715980#c6 Jan Beulich changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |novell@kapsler.ch --- Comment #6 from Jan Beulich 2012-03-26 09:09:32 UTC --- I don't think you ever specified which exact hypervisor and kernel versions you're using. Please update to the most recent maintenance updates and re-check. If the problem persists, try - adding "noxsaveopt" to the kernel (not Xen) command line - adding "noxsave" to the kernel (not Xen) command line - 12.1 hypervisor - 12.1 kernel -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=715980 https://bugzilla.novell.com/show_bug.cgi?id=715980#c8 --- Comment #8 from Jan Beulich 2012-05-02 07:38:10 UTC --- Mind providing the technical details of the crash then? Otherwise I don't see why you added the above comment... -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=715980 https://bugzilla.novell.com/show_bug.cgi?id=715980#c10 --- Comment #10 from Jan Beulich 2012-05-03 09:30:01 UTC --- Please see #6 for what to do next. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=715980 https://bugzilla.novell.com/show_bug.cgi?id=715980#c12 Jan Beulich changed: What |Removed |Added ---------------------------------------------------------------------------- Component|Kernel |Basesystem Found By|--- |Community User AssignedTo|jbeulich@suse.com |bnc-team-screening@forge.pr | |ovo.novell.com --- Comment #12 from Jan Beulich 2012-05-11 07:14:14 UTC --- If this is without the hypervisor being forced to enable xsave, and without it defaulting to do so (which could be overridden with "xsave=0" on its command line), then this is likely the meanwhile well known glibc issue of not looking at CPUID.OSXSAVE when determining whether AVX or FMA can be used. -- 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.