https://bugzilla.novell.com/show_bug.cgi?id=743985 https://bugzilla.novell.com/show_bug.cgi?id=743985#c2 --- Comment #2 from Wolfgang Trier 2012-01-31 17:43:23 UTC --- An analogical behavior shows my system. But I saw that grub was missing the link or file /boot/xen.gz . The package kernel-xen-3.1.0-1.2.1.i586.rpm doesn't seem o.k. Then /boot/xen.gz is missing in the file list in this package (as in directory /boot too). Also the installation via yast2 -> Software Management -> kernel-xen (resp. kernel-xen-base) results in the same behavior. -- 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=743985 https://bugzilla.novell.com/show_bug.cgi?id=743985#c4 rens groenewegen changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|rens.groenewegen@xs4all.nl | --- Comment #4 from rens groenewegen 2012-02-02 19:15:03 UTC --- charles removed the vgamode line and turned default runlevel via yast to 3 result is the same. kernel loads, (xen.gz) and then nothing. I have the same suspicion about video: there is signal, according to the sony LCD monitor, but there is nothing to see. can this be related to backlight support or something like that ? rens -- 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=743985 https://bugzilla.novell.com/show_bug.cgi?id=743985#c6 --- Comment #6 from rens groenewegen 2012-02-02 19:32:10 UTC --- Charles, the messages log is the result of adding nomodeset x11failsave to the kernel commandline..... which allows xen to boot without issue. funny that runlevel 3 in itself was not able to achieve this...... rens -- 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=743985 https://bugzilla.novell.com/show_bug.cgi?id=743985#c8 Jan Beulich changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Found By|--- |Community User InfoProvider| |rens.groenewegen@xs4all.nl --- Comment #8 from Jan Beulich 2012-02-03 08:30:02 UTC --- As with almost anything that doesn't work kernel or hypervisor wise - without handing us (complete) logs of the problem case, there's very little we can do in the absence of having a system to reproduce this on ourselves. So please provide logs (quite necessarily obtained via serial console). Further, with "x11failsafe" not being a kernel option (and with the option as spelled by you not existing anywhere at all afaik), I cannot see how use of this option can affect the kernel coming up properly at least in run level 3. Any drivers automatically loaded normally would also be with the option in use. In run level 3 (i.e. with X not being started at all), there shouldn't be anything done graphics-wise when "nomodeset" is in effect, unless you also have some configuration issue. Additionally it ought to be possible for you to suppress starting of certain specific services (e.g. xdm) manually (via the "confirm" kernel command line option). Also, your statements like "kernel loads, (xen.gz) and then nothing" are rather confusing: Neither is xen.gz the kernel, nor is it likely that there is no output at all after it loaded, yet there is output with any kernel option added. So please be more precise about what is actually happening. For the *kernel* to be more verbose, you may want to alter its command line options ("ignore_loglevel" and/or "splash=verbose"), in which case it *may* be that you're able to see (and hence photo if you can't for some reason set up a serial console) something useful. -- 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=743985 https://bugzilla.novell.com/show_bug.cgi?id=743985#c10 Jan Beulich changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P3 - Medium Status|NEW |NEEDINFO InfoProvider| |rens.groenewegen@xs4all.nl --- Comment #10 from Jan Beulich 2012-02-07 08:02:46 UTC --- (In reply to comment #9)

"it does not boot" means I do not get a login prompt from a working linux.

We distinguish "does not boot" from "does not fully come up".

There is not a shred of kernel logging to be found in /var/log/messages or so. Wether it is exactly the kernel or something that the kernel needs that fails, is hairsplitting, which is not an activity I participate in, not my patch.

Very well "your patch", I would think. This is openSUSE, a community effort. So you're expected to contribute your share.

I emptied messages, then tried the xenboot, and there is *nothing* in messages after forcing a reboot via ctrl-alt-delete

nothing as in 0 lines, 0 characters.

if you know of some other log file, please let me know, happy to send it.

As said before, this is to be expected. You will have to collect the messages via serial cable on a second system.

x11failsave is a kernel option, believe it or not.

If it is not, please explain why every suse standard installation is putting the next line as a kernel command line with every "SuSE failsave boot" in the menu.lst: _________________________________________________________________ showopts apm=off noresume edd=off powersaved=off nohz=off highres=off processor.max_cstate=1 nomodeset x11failsafe

Note the spelling difference? And not everything that's on the kernel command line is being recognized by the kernel. Options can as well be read and acted upon by user mode components.

with x11failsave and nomodeset, it does boot. with only x11failsave it does not boot. and with only nomodeset it does not boot either.

Again, given the consistent spelling mistake you're making I have to put this under question.

xen,gz is the kernel, and the module lines after that are the kernel for the dom0 domain and corresponding initrd, or at least that is what the readme's tell me.

From the perspective of the boot loader that's correct, but from the perspective of software layering it isn't - xen.gz is the hypervisor, the first "module" is the kernel.

I am going to have a serial console, but the gear I had was with a too short cable to get to the com1 connector on the board.......

so perhaps we will have to wait for that to arrive.....

Great to hear; the alternative, as unfortunate as it may sound, would have been to close the bug with the "noresponse" resolution. Again, please keep in mind that it is openSUSE you're using, not any of the SLE products. -- 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=743985 https://bugzilla.novell.com/show_bug.cgi?id=743985#c12 rens groenewegen changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|rens.groenewegen@xs4all.nl | --- Comment #12 from rens groenewegen 2012-02-07 20:52:24 UTC --- jan , you better close this one with no response. although we have a technical connection, you do not communicate in a way that is comprehensible to me, or workable. having to go on preaching from your high horse where you could have helped by simply saying " hey, it is saFe, not saVe" is a waste of energy that I cannot afford to participate in. I simply do not have the time for it. so close it, by all means. no hard feelings.

From the experience I shared with you, I would say that the kernel apparently has enough with x11fail to understand. it probably does not read beyond the a of safe/save

or it would ignore the option, which it does not. best of luck, rens -- 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=743985 https://bugzilla.novell.com/show_bug.cgi?id=743985#c14 Jan Beulich changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |NORESPONSE Summary|on a AMD FX 8 core with |on a AMD FX 8 core GUI does |ASUS mboard M5A88M-EVO 16 |not come up under Xen |Gbyte ram kingston Xen | |cannot boot. | --- Comment #14 from Jan Beulich 2012-02-08 08:06:49 UTC --- Doing as requested, albeit I would have preferred to actually fix the problem. (For the record, it's [possibly among others] the xdm startup script that recognizes "x11failsafe" [fully spelled out] via reading /proc/cmdline. According to my run of grep, there is a single instance of "x11fa" in the kernel sources, as part of a hex number.) -- 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.