Updated my rawhide VM today and now it refuses to boot: dracut: Switching root SELinux: initialized (dev tmpfs, type tmpfs), uses transition SIDs SELinux: initialized (dev cgroup, type cgroup), uses genfs_contexts SELinux: initialized (dev cgroup, type cgroup), uses genfs_contexts SELinux: initialized (dev cgroup, type cgroup), uses genfs_contexts SELinux: initialized (dev cgroup, type cgroup), uses genfs_contexts SELinux: initialized (dev cgroup, type cgroup), uses genfs_contexts SELinux: initialized (dev cgroup, type cgroup), uses genfs_contexts SELinux: initialized (dev cgroup, type cgroup), uses genfs_contexts SELinux: initialized (dev cgroup, type cgroup), uses genfs_contexts SELinux: initialized (dev cgroup, type cgroup), uses genfs_contexts SELinux: initialized (dev cgroup, type cgroup), uses genfs_contexts init[1]: Succesfully opened /dev/kmsg for logging. init[1]: systemd 4 running in system mode. init[1]: Your kernel apparently lacks built-in autofs4 support. Please fix that. We'll now try to work around this by calling '/sbin/modprobe autofs4'... init[1]: Your kernel apparently lacks built-in ipv6 support. Please fix that. We'll now try to work around this by calling '/sbin/modprobe ipv6'... NET: Registered protocol family 10 lo: Disabled Privacy Extensions init[1]: Set hostname to <rawhide.poochiereds.net>. init[1]: Failed to load configuration for distcache.service: No such file or directory init[1]: Failed to load configuration for openct.service: No such file or directory init[1]: Failed to load configuration for default.target: No such file or directory init[1]: Failed to start default target: Unit default.target failed to load. See logs for details. Was able to get the machine back up into some semblance of workingness by booting with init=/bin/bash: systemd-4-4.fc14.x86_64 For now, I've switched the /sbin/init symlink back to upstart.
Should mention that after the log messages above, the machine just hung -- presumably in userspace.
I think this a duplicate of bug #618315
Agreed. Closing as such. *** This bug has been marked as a duplicate of bug 618315 ***