Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

FCOS VM (Bhyve on TrueNAS) failing to boot after automatic update to Fedora 41 (“systemd[1]: Freezing execution”) #1833

Open
LeoSum8 opened this issue Nov 14, 2024 · 2 comments

Comments

@LeoSum8
Copy link

LeoSum8 commented Nov 14, 2024

Describe the bug

This morning my FCOS VM was down. I think zincati ran an update.

Upon manually rebooting it, I get the following output via VNC:
Pasted image 20241114095224
Pasted image 20241114095452
Pasted image 20241114095522

Those are the versions installed:
Pasted image 20241114202732

Reverting back to Fedora 40 and everything works again as before.

The FCOS VM is a bhyve guest on a FreeBSD (TrueNAS) Host. The guest filesystem resides in a Zvol.

Reproduction steps

Expected behavior

Boot F41 after update.

Actual behavior

Booting F41 fails, need to revert to F40

System details

FCOS as Bhyve-VM on a FreeBSD 13.1-RELEASE-p9 (TrueNAS) host.
FCOS version before update: 40.20241019.3.0 (working)
FCOS version after update: 41.20241027.3.0 (not working)

Butane or Ignition config

No response

Additional information

Initial discussion at https://discussion.fedoraproject.org/t/fcos-vm-bhyve-on-truenas-failing-to-boot-after-automatic-update-systemd-1-freezing-execution/136788/3

@dustymabe
Copy link
Member

dustymabe commented Nov 14, 2024

what kernel arguments do you have set for this system?

this looks vaguely like the issue where systemd won't boot with cgroups V1 but I don't see that message in your output you show.

@stackrainbow
Copy link

I can confirm also affected on a large amount of nodes, auto updates on, cgroups V1 enabled.
Was a little difficult to figure out what was going on apart from just rollbacking, there's no notice or information that cgroups V1 causes this apart from this issue being linked from OP's thread.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants