|
Bugzilla – Full Text Bug Listing |
| Summary: | yast cannot be used with 11.4 and kernel-xen on sandy bridge (i5/i7) | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE 11.4 | Reporter: | Roman Haag <novell> |
| Component: | Basesystem | Assignee: | E-mail List <bnc-team-screening> |
| Status: | VERIFIED NORESPONSE | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Critical | ||
| Priority: | P5 - None | CC: | help, jonathanjstevens, joser.condado.ext, karl, myself, suse |
| Version: | Factory | ||
| Target Milestone: | --- | ||
| Hardware: | x86-64 | ||
| OS: | openSUSE 11.4 | ||
| Whiteboard: | |||
| Found By: | Community User | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
|
Description
Roman Haag
2011-09-05 13:11:03 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
I have just replaced the motherboard/processor in my OpenSuse 11.4 XEN system, and have exactly the same problem with the majority of Yast2 components. The new processor is a Sandy Bridge (model name : Intel(R) Core(TM) i3-2100 CPU @ 3.10GHz), the MB chip-set is a P67 (stepping B3). I have no problems with XEN (OK, so first boot I forgot to enable the virtualisation options in the BIOS - but let's not talk about that... ) - all my XEN VMs appear to be running happily. This appear to be (from the googling I have done) an issue specific to the processor with xen. 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. (In reply to comment #3) > 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. I can confirm that the same build works fine on a Pentium 4 541 in a Asus P5K SE motherboard, and also works fine with the normal kernel (I installed it using the P4, then booted it with the i5, and it worked fine (used the normal kernel by default)). 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. 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 I'm using the following : kernel-xen-2.6.37.6-0.11.1.x86_64 kernel-desktop-2.6.37.6-0.11.1.x86_64 xen-libs-4.0.3_01-0.2.1.x86_64 When running the xen kernel yast crashes, works fine with the desktop kernel. Mind providing the technical details of the crash then? Otherwise I don't see why you added the above comment... The crash is the same as listed above, from the command line as root, "yast" sbin/yast: line 423: 4678 Illegal instruction $ybindir/y2base $module "$@" "$SELECTED_GUI" $Y2_GEOMETRY $Y2UI_ARGS Please see #6 for what to do next. - adding "noxsaveopt" to the kernel (not Xen) command line - adding "noxsave" to the kernel (not Xen) command line Neither of these made a difference, still get the same crash listed above when running yast. 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. Long time no response, so closed. Feel free to reopen it. |