https://bugzilla.suse.com/show_bug.cgi?id=1184157 https://bugzilla.suse.com/show_bug.cgi?id=1184157#c5 Fabian Vogt <fvogt@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |CONFIRMED Summary|JeOS Xen image: Boot never |JeOS Xen image: Wrong |finishes without NIC |console parameters for Xen | |PV --- Comment #5 from Fabian Vogt <fvogt@suse.com> --- (In reply to Ulrich Windl from comment #3)
(In reply to Fabian Vogt from comment #1)
Is that after or before the jeos-firstboot wizard?
I don't remember, but my guess is before the jeos-firstboot wizard. Did you have a look at the console messages?
Yes.
My suspicion is that you only have the serial console enabled, but jeos-firstboot starts on tty0, so it's "invisible". Does it work if you add a graphical output?
Adding graphical output woiuld be against the philosophy of JEOS IMHO.
It's just for testing. I could reproduce the issue in a Xen PV VM. The issue is that it needs console=hvc0 instead. console=ttyS0 doesn't exist, and it just failed to boot because of that. So it might be necessary to add console=hvc0 to the list and implement displaying jeos-firstboot on all consoles (bug 1179157).
Wicked should start only after completion of jeos-firstboot.
-- You are receiving this mail because: You are on the CC list for the bug.