https://bugzilla.novell.com/show_bug.cgi?id=733022 https://bugzilla.novell.com/show_bug.cgi?id=733022#c17 Andrew Daugherity <adaugherity@tamu.edu> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |adaugherity@tamu.edu --- Comment #17 from Andrew Daugherity <adaugherity@tamu.edu> 2012-02-02 01:43:52 UTC --- I am also affected by this bug -- I normally run SLES 11 on my VMs, but am testing out opensuse 12.1 and was frustrated by the slow logins. My standard Xen config is to disable graphics since most of my VMs are servers and it's easier to ssh into the host server and then "xm console foo" on the rare occasions I need a console than to deal with X forwarding, etc. Disabling graphics from the vm-install tool appends "xencons=tty" and that's worked well enough so far (aside from needing to disable the xvc0 console in inittab in the guests), so I haven't bothered trying other xencons options. I can confirm that both using sysvinit ("init=/sbin/sysvinit" on the "extra" line in the Xen VM config) and the updated systemd package from home:fcrozat fix the login delay problem. With fcrozat's package I see dmesg complaints from systemd on boot, and logging in from the Xen text console causes console-kit-daemon to go crazy, but logins are fast now; ssh logins appear to be working properly. It's still a huge improvement, as I'd previously see messages like in comment #1 and logins would experience a 25 second delay. dmesg systemd messages (systemd-37-3.142.1.x86_64): ==== [ 1.508291] systemd[1]: systemd 37 running in system mode. (+PAM +LIBWRAP +AUDIT +SELINUX +SYSVINIT +LIBCRYPTSETUP; suse) [ 1.539050] systemd[1]: Set hostname to <imsweb1.vpr.int>. [ 1.545953] systemd[1]: Failed to open /dev/tty0: No such file or directory [ 1.987489] systemd-readahead-replay[209]: Bumped block_nr parameter of 202:0 to 16384. This is a temporary hack and should be removed one day. [ 2.013751] udevd[212]: starting version 173 [ 2.430911] ifup[295]: Service network not started and mode 'auto' -> skipping [ 2.472245] systemd-vconsole-setup[285]: Failed to open /dev/tty0: No such file or directory [ 2.479039] boot.localnet[249]: Using boot-specified hostname 'imsweb1.vpr.int' [ 2.479164] boot.localnet[249]: Setting up hostname 'imsweb1'..done [ 2.479383] boot.localnet[249]: Setting up loopback interface RTNETLINK answers: File exists [ 2.479551] boot.localnet[249]: ..done [ 2.536855] systemd[1]: systemd-vconsole-setup.service: main process exited, code=exited, status=1 [ 2.544216] systemd[1]: Unit systemd-vconsole-setup.service entered failed state. ==== console-kit-daemon complaints in /var/log/messages (triggered by login from xen text console): ==== Feb 1 19:15:31 imsweb1 systemd-logind[352]: New user root logged in. Feb 1 19:15:31 imsweb1 systemd-logind[352]: New session 3 of user root. Feb 1 19:15:32 imsweb1 systemd-logind[352]: Failed to read current console: Unknown error -9 Feb 1 19:15:32 imsweb1 dbus[476]: [system] Activating via systemd: service name='org.freedesktop.ConsoleKit' unit='console-kit-daemon.service' Feb 1 19:15:32 imsweb1 dbus-daemon[476]: dbus[476]: [system] Activating via systemd: service name='org.freedesktop.ConsoleKit' unit='console-kit-daemon service' Feb 1 19:15:32 imsweb1 console-kit-daemon[1537]: ioctl VT_GETSTATE: Invalid argument Feb 1 19:15:32 imsweb1 console-kit-daemon[1537]: WARNING: Could not determine active console Feb 1 19:15:32 imsweb1 console-kit-daemon[1537]: console-kit-daemon[1537]: WARNING: Could not determine active console Feb 1 19:15:32 imsweb1 console-kit-daemon[1537]: WARNING: Error waiting for native console 3 activation: Invalid argument Feb 1 19:15:32 imsweb1 console-kit-daemon[1537]: console-kit-daemon[1537]: WARNING: Error waiting for native console 1 activation: Invalid argument [ repeat these last two messages for every console up to 63, in random order ] Feb 1 19:15:32 imsweb1 console-kit-daemon[1537]: missing action Feb 1 19:15:32 imsweb1 dbus[476]: [system] Activating service name='org.freedesktop.PolicyKit1' (using servicehelper) Feb 1 19:15:32 imsweb1 dbus-daemon[476]: dbus[476]: [system] Activating service name='org.freedesktop.PolicyKit1' (using servicehelper) Feb 1 19:15:32 imsweb1 polkitd[1605]: started daemon version 0.102 using authority implementation `local' version `0.102' Feb 1 19:15:32 imsweb1 dbus[476]: [system] Successfully activated service 'org.freedesktop.PolicyKit1' Feb 1 19:15:32 imsweb1 dbus-daemon[476]: dbus[476]: [system] Successfully activated service 'org.freedesktop.PolicyKit1' Feb 1 19:15:32 imsweb1 dbus[476]: [system] Successfully activated service 'org.freedesktop.ConsoleKit' Feb 1 19:15:32 imsweb1 dbus-daemon[476]: dbus[476]: [system] Successfully activated service 'org.freedesktop.ConsoleKit' ==== This also seems to be another bug in c-k-d where it's repeating each error, once normally, once with a doubled console-kit-daemon log header. -- 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.