[systemd-devel] Running a x86_64 kernel on Fedora 15 x86 userland
Thomas Meyer
thomas at m3y3r.de
Tue May 3 10:14:54 PDT 2011
Am 03.05.2011 um 15:14 schrieb Daniel J Walsh:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On 05/02/2011 03:49 PM, Thomas Meyer wrote:
>> Hi,
>>
>> I try to run a x86_64 kernel on x86 Fedora 15 userland. But systemd get's somehow stuck in the boot process. Any ideas how to debug the problem? What is systemd waiting for?
>>
>> I need to boot with selinux=0 as I get some selinux errors (file not found or something like this, strangley these lines doesn't show up in the netconsole log).
>>
>> Here is what I could catch via netconsole and systemd.log_level=debug:
>>
>
> Have you grabbed the latest SELinux policy out of koji for F15? What
> AVC messages are you seeing?
I don't get an AVC message, so maybe there is not problem with selinux, just with plymouth, that ABRTs.
But I see this:
[ 7.204437] type=1403 audit(1304471120.046:3): policy loaded auid=4294967295 ses=4294967295
Unable to fix label of /sys/fs/cgroup/systemd: No such file or directory
Unable to fix label of /sys/fs/cgroup/cpuset: No such file or directory
Unable to fix label of /sys/fs/cgroup/cpu: No such file or directory
Unable to fix label of /sys/fs/cgroup/cpuacct: No such file or directory
Unable to fix label of /sys/fs/cgroup/devices: No such file or directory
Unable to fix label of /sys/fs/cgroup/freezer: No such file or directory
Unable to fix label of /sys/fs/cgroup/net_cls: No such file or directory
Unable to fix label of /sys/fs/cgroup/blkio: No such file or directory
[ 7.828143] <31>systemd[1]: Successfully opened /dev/kmsg for logging.
[ 7.829998] <30>systemd[1]: systemd 25 running in system mode. (+PAM +LIBWRAP +AUDIT +SELINUX +SYSVINIT +LIBCRYPTSETUP; fedora)
I guess systemd tries to relabel these files, but fails somehow!?
More information about the systemd-devel
mailing list