http://bugzilla.suse.com/show_bug.cgi?id=937237 http://bugzilla.suse.com/show_bug.cgi?id=937237#c1 --- Comment #1 from Dinar Valeev --- journal says: failed at step NAMESPACE spawning /usr/lib/systemd/systemd-udevd: invalid argument -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=937237 http://bugzilla.suse.com/show_bug.cgi?id=937237#c3 Dinar Valeev changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(dvaleev@suse.com) | --- Comment #3 from Dinar Valeev --- This is a rescue image, there are no yast logs -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=937237 Dr. Werner Fink changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |crrodriguez@opensuse.org, | |jengelh@inai.de -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=937237 http://bugzilla.suse.com/show_bug.cgi?id=937237#c6 Dinar Valeev changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(dvaleev@suse.com) | --- Comment #6 from Dinar Valeev --- 13.2 is fine in this regard. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=937237 http://bugzilla.suse.com/show_bug.cgi?id=937237#c8 Dinar Valeev changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(dvaleev@suse.com) | --- Comment #8 from Dinar Valeev --- If rescue is started over serial (no vga attached), then it is not possible to login, there is no login prompt. If machine started with VGA, then sure, there is login prompt, but hvc0 is not used in this case. I don't see the same behaviour on installed system. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=937237 http://bugzilla.suse.com/show_bug.cgi?id=937237#c10 Dr. Werner Fink changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(dvaleev@suse.com) --- Comment #10 from Dr. Werner Fink --- Dinar? Please provide an answer on comment #8 -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=937237 http://bugzilla.suse.com/show_bug.cgi?id=937237#c12 Dinar Valeev changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(dvaleev@suse.com) | --- Comment #12 from Dinar Valeev --- Info from installed machine: localhost:~ # cat /proc/cmdline BOOT_IMAGE=/boot/vmlinux-4.1.6-3-default root=UUID=16c8375f-dd26-4e1c-bed5-64644a5c92b1 quiet splash=silent localhost:~ # ps aux | grep agetty root 569 0.0 0.0 3072 2112 tty1 Ss+ 10:18 0:00 /sbin/agetty --noclear tty1 linux root 1367 0.0 0.0 4160 2368 hvc0 S+ 10:20 0:00 grep --color=auto agetty localhost:~ # Also I don't see system boot output during boot: Loading Linux 4.1.6-3-default ... * finddevice /memory grub workaround * Loading initial ramdisk ... * finddevice /memory grub workaround * OF stdout device is: /vdevice/vty@71000000 Preparing to boot Linux version 4.1.6-3-default (geeko@buildhost) (gcc version 5.1.1 20150713 [gcc-5-branch revision 225736] (SUSE Linux) ) #1 SMP Fri Aug 28 10:59:34 UTC 2015 (d867e86) Detected machine type: 0000000000000101 Max number of cores passed to firmware: 2048 (NR_CPUS = 2048) Calling ibm,client-architecture-support... done command line: BOOT_IMAGE=/boot/vmlinux-4.1.6-3-default root=UUID=16c8375f-dd26-4e1c-bed5-64644a5c92b1 quiet splash=silent memory layout at init: memory_limit : 0000000000000000 (16 MB aligned) alloc_bottom : 0000000003b80000 alloc_top : 0000000030000000 alloc_top_hi : 0000000100000000 rmo_top : 0000000030000000 ram_top : 0000000100000000 instantiating rtas at 0x000000002fff0000... done prom_hold_cpus: skipped copying OF device tree... Building dt strings... Building dt structure... Device tree strings 0x0000000003b90000 -> 0x0000000003b90820 Device tree struct 0x0000000003ba0000 -> 0x0000000003bb0000 Quiescing Open Firmware ... Booting Linux via __start() ... -> smp_release_cpus() spinning_secondaries = 0 <- smp_release_cpus() <- setup_system() SUSE Linux #1 SMP Fri Aug 2 Welcome to openSUSE 20150903 "Tumbleweed" - Kernel 4.1.6-3-default (hvc0). -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=937237 http://bugzilla.suse.com/show_bug.cgi?id=937237#c15 --- Comment #15 from Dr. Werner Fink --- (In reply to Dinar Valeev from comment #8)

I don't see the same behaviour on installed system.

.... this looks more like a problem in the installation system. Maybe the file /usr/lib/udev/rules.d/99-systemd.rules is missed in the installation system and/or the line: SUBSYSTEM=="tty", KERNEL=="tty[a-zA-Z]*|hvc*|xvc*|hvsi*|ttysclp*|sclp_line*|3270/tty*", TAG+="systemd" does miss `hvc*|' -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=937237 http://bugzilla.suse.com/show_bug.cgi?id=937237#c17 --- Comment #17 from Dinar Valeev --- localhost:~ # cat /usr/lib/udev/rules.d/99-systemd.rules | grep hvc SUBSYSTEM=="tty", KERNEL=="tty[a-zA-Z]*|hvc*|xvc*|hvsi*|ttysclp*|sclp_line*|3270/tty*", TAG+="systemd" -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=937237 http://bugzilla.suse.com/show_bug.cgi?id=937237#c19 --- Comment #19 from Dinar Valeev --- rescue system have udev rule: SUBSYSTEM=="tty", KERNEL=="tty[a-zA-Z]*|hvc*|xvc*|hvsi*|ttysclp*|sclp_line*|3270/tty*", TAG+="systemd" systemctl status --all dev-hvc0.device ● dev-hvc0.device Loaded: loaded Active: inactive (dead) Oct 05 15:08:44 Rescue systemd[1]: Job dev-hvc0.device/start timed out. Oct 05 15:08:44 Rescue systemd[1]: Timed out waiting for device dev-hvc0.device. Oct 05 15:08:44 Rescue systemd[1]: Job dev-hvc0.device/start failed with result 'timeout'. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=937237 http://bugzilla.suse.com/show_bug.cgi?id=937237#c21 --- Comment #21 from Dinar Valeev --- Created attachment 650211 --> http://bugzilla.suse.com/attachment.cgi?id=650211&action=edit boot.msg boot.msg from rescue boot -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=937237 http://bugzilla.suse.com/show_bug.cgi?id=937237#c23 --- Comment #23 from Dr. Werner Fink --- (In reply to Dr. Werner Fink from comment #22)

which describes a bug in glibc in i686 with a similar behaviour. Related to this I have found

the bugzillas I provided shows that the gcc had misscompiled the glibc, therefore I have added the maintainers of gcc to the carbon copy list. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=937237 http://bugzilla.suse.com/show_bug.cgi?id=937237#c25 Dr. Werner Fink changed: What |Removed |Added ---------------------------------------------------------------------------- Component|Basesystem |Installation Assignee|systemd-maintainers@suse.de |yast2-maintainers@suse.de QA Contact|qa-bugs@suse.de |jsrain@suse.com --- Comment #25 from Dr. Werner Fink --- (In reply to Dinar Valeev from comment #24) Indeed ... /dev/tty1 *is* the first virtual console of /dev/tty0, the current virtual console aka the VESA console of the graphic card. The question rises: Why there is no serial support in the installation system? -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=937237 http://bugzilla.suse.com/show_bug.cgi?id=937237#c26 --- Comment #26 from Dinar Valeev --- Should we have something like: d etc/systemd/system/serial-getty.target.wants s /usr/lib/systemd/system/serial-getty@.service etc/systemd/system/serial-getty.target.wants/serial-getty@hvc0.service ? But how installed system handles this autiomatically, without doing a symlink manualy? -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=937237 http://bugzilla.suse.com/show_bug.cgi?id=937237#c28 --- Comment #28 from Jan Engelhardt --- If something like console=ttyS0 is on the command line, the getty generator kicks in, creating the particular "wants" link: /run/systemd/generator/getty.target.wants/serial-getty@ttyS0.service This ought to work similarly when having console=hvc0 on the line, and that is what it does, at least, the last time I checked with xvc0 (xen) on systemd-210. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=937237 http://bugzilla.suse.com/show_bug.cgi?id=937237#c30 --- Comment #30 from Dinar Valeev --- (In reply to Jan Engelhardt from comment #28)

If something like console=ttyS0 is on the command line, the getty generator kicks in, creating the particular "wants" link:

/run/systemd/generator/getty.target.wants/serial-getty@ttyS0.service

This ought to work similarly when having console=hvc0 on the line, and that is what it does, at least, the last time I checked with xvc0 (xen) on systemd-210.

I tried to boot resuce with console=hvc0, doesn't help with the currect installation-images code -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=937237 http://bugzilla.suse.com/show_bug.cgi?id=937237#c32 --- Comment #32 from Jan Engelhardt ---

(systemd-getty-generator.8): It will also instantiate serial-getty@.service instances for virtualizer consoles, if execution in a virtualized environment is detected.

So maybe that virtual environment is not detected properly? Run systemd-detect-virt(8). -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=937237 http://bugzilla.suse.com/show_bug.cgi?id=937237#c34 --- Comment #34 from Dinar Valeev --- tried to change tty1 to hvc0 and getty to serial-getty -> fail. It leads me to think that /dev/hvc0 is not there. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=937237 http://bugzilla.suse.com/show_bug.cgi?id=937237#c36 --- Comment #36 from Dr. Werner Fink --- (In reply to Jan Engelhardt from comment #35) Yes the generator does use ... after handling containers ... first the current active console(s) and further add a serial out of the list hvc0, xvc0, hvsi0, sclp_line0, ttysclp0, and 3270!tty1 if exists below /sys/class/tty/ NB: the ! in 3270!tty1 is a replacement for / Nevertheless for getting agetty to work the devices to exist. The question rises if in the installation image is udevd running and the getty generator has been executed ... I doubt that this had happen if I read https://github.com/openSUSE/installation-images/blob/master/data/rescue/resc... as this looks more like setting up the first virtual console with a script language instead of executing /usr/lib/systemd/system-generators/systemd-getty-generator at boot time maybe with e /usr/lib/systemd/system-generators/systemd-getty-generator but I do not know if this would work out. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=937237 http://bugzilla.suse.com/show_bug.cgi?id=937237#c38 --- Comment #38 from Steffen Winterfeldt --- Well, at least the intention is that the rescue system is just a normal system; so udevd should be running. And afaics it is. It may well be that something is missing but I don't see what. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=937237 http://bugzilla.suse.com/show_bug.cgi?id=937237#c40 --- Comment #40 from Dr. Werner Fink --- (In reply to Dinar Valeev from comment #39) Hmmm ... then something is missed in the namespace/context for starting systemd-udevd like a sticky /tmp -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=937237 http://bugzilla.suse.com/show_bug.cgi?id=937237#c42 --- Comment #42 from Dinar Valeev --- trying to build iio with patched systemd -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=937237 http://bugzilla.suse.com/show_bug.cgi?id=937237#c44 --- Comment #44 from Dinar Valeev --- Nope, doest help. Could somebody please take a look at it? vncviewer cabernet.arch:55 -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=937237 http://bugzilla.suse.com/show_bug.cgi?id=937237#c46 --- Comment #46 from Thomas Blume --- (In reply to Thomas Blume from comment #45)

I still see the error message:

Failed to set up the root directory for shared mount propagation: Invalid argument

in the journal log.

btw. I suspect a context with bug 902226. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=937237 http://bugzilla.suse.com/show_bug.cgi?id=937237#c48 --- Comment #48 from Steffen Winterfeldt --- Hm, mount doesn't show a mountpoint for / but /proc/mounts does. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=937237 http://bugzilla.suse.com/show_bug.cgi?id=937237#c50 --- Comment #50 from Steffen Winterfeldt --- So probably the rescue system needs a real root fs and can't just live in a subdir. I'll try this. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=937237 http://bugzilla.suse.com/show_bug.cgi?id=937237#c52 --- Comment #52 from Steffen Winterfeldt --- Nice idea. It gets you a / mountpoint; but --make-shared still fails. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=937237 http://bugzilla.suse.com/show_bug.cgi?id=937237#c54 --- Comment #54 from Steffen Winterfeldt --- Ok, rescue is now its own file system and the systemd error is gone. HOWEVER, it now mounts the root-fs ro. Any idea why and how to stop this? -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=937237 http://bugzilla.suse.com/show_bug.cgi?id=937237#c56 --- Comment #56 from Steffen Winterfeldt --- I thought so but there is an entry; but probably a wrong one. How would an entry for a tmpfs / look like? -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=937237 http://bugzilla.suse.com/show_bug.cgi?id=937237#c58 --- Comment #58 from Thomas Blume --- Ah, I guess we need this: https://github.com/systemd/systemd/commit/b0438462089d1e1460429a57718305de08... -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=937237 http://bugzilla.suse.com/show_bug.cgi?id=937237#c60 --- Comment #60 from Jan Engelhardt --- If /dev/hvc0 does not exist (because udevd did not launch), then starting the getty unit likely is not going to be successful either :-/ -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=937237 http://bugzilla.suse.com/show_bug.cgi?id=937237#c62 --- Comment #62 from Steffen Winterfeldt --- Hm, I just checked with qemu and sle12-sp1. I also saw the 'shared mount propagation error' in the journal. But /dev/hdc0 _does_ exist. Also a getty was running there and I could login there after fixing /etc/securetty. So why does that not work in openSUSE? -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=937237 http://bugzilla.suse.com/show_bug.cgi?id=937237#c64 --- Comment #64 from Thomas Blume --- (In reply to Thomas Blume from comment #63)

This is, because:

http://cgit.freedesktop.org/systemd/systemd/commit/ ?id=b3ac5f8cb98757416d8660023d6564a7c411f0a0

is not in systemd-210. Basically the same as if you apply the patch from comment#41.

Sorry, my fault, it is in systemd-210, but it is limited to containers: -->-- if (detect_container(NULL) <= 0) if (mount(NULL, "/", NULL, MS_REC|MS_SHARED, NULL) < 0) log_warning("Failed to set up the root directory for shared mount propagation: %m"); --<-- -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=937237 http://bugzilla.suse.com/show_bug.cgi?id=937237#c66 --- Comment #66 from Dinar Valeev --- (In reply to Steffen Winterfeldt from comment #62)

Hm, I just checked with qemu and sle12-sp1.

I also saw the 'shared mount propagation error' in the journal.

But /dev/hdc0 _does_ exist. Also a getty was running there and I could login there after fixing /etc/securetty.

So why does that not work in openSUSE?

Yes, it is only visible in openSUSE -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=937237 http://bugzilla.suse.com/show_bug.cgi?id=937237#c68 --- Comment #68 from Dinar Valeev --- Got reproduced on x86? -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=937237 http://bugzilla.suse.com/show_bug.cgi?id=937237#c70 --- Comment #70 from Thomas Blume --- (In reply to Steffen Winterfeldt from comment #65)

On tumbleweed I see comment 20; but /dev/hvc0 exists.

So, my question still is: why can systemd on sle12-sp1 cope with the situation but the one in tumbleweed can't? And, should systemd be fixed or the setup?

Checked the difference between SLES12SP1 and tumbleweed. /usr/lib/systemd/system/systemd-udevd.service on tumbleweed has this: MountFlags=slave and the manpage says: -->-- MountFlags= Takes a mount propagation flag: shared, slave or private, which control whether mounts in the file system namespace set up for this unit's processes will receive or propagate mounts or unmounts. --<-- I guess this makes systemd-udevd fail. The SLES12SP1 service file doesn't have this setting. The missing hvc0 device is most probably only a side effect of systemd-udevd.service failing to start. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=937237 http://bugzilla.suse.com/show_bug.cgi?id=937237#c72 --- Comment #72 from Thomas Blume --- Ok, disabling the mount propagation works. But I'm not sure wheter we should do this in general as it seems to break nspawn (see comment #43). Jan, Werner, Steffen, what do you think? -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=937237 http://bugzilla.suse.com/show_bug.cgi?id=937237#c74 --- Comment #74 from Steffen Winterfeldt --- You don't have to do it in the package; I can just change the setting for the rescue system. I guess systemd doesn't expect to be run chroot'ed where you don't have a mountpoint at the top dir... -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=937237 http://bugzilla.suse.com/show_bug.cgi?id=937237#c76 --- Comment #76 from Steffen Winterfeldt --- Tried that already; see comment 52. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=937237 http://bugzilla.suse.com/show_bug.cgi?id=937237#c78 --- Comment #78 from Steffen Winterfeldt --- Just modified the service file for the rescue system as in comment 71 and that seems to work. Looks like a good solution to me. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=937237 http://bugzilla.suse.com/show_bug.cgi?id=937237#c80 --- Comment #80 from Steffen Winterfeldt --- BTW, fix will be https://github.com/openSUSE/installation-images/pull/68 -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=937237 http://bugzilla.suse.com/show_bug.cgi?id=937237#c82 Steffen Winterfeldt changed: What |Removed |Added ---------------------------------------------------------------------------- Status|CONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #82 from Steffen Winterfeldt --- Thanks, Werner! as comment 80 is now on its way into tumbleweed, closing bug -- You are receiving this mail because: You are on the CC list for the bug.