On 2/3/26 3:18 PM, Barry wrote:


On 3 Feb 2026, at 16:38, Paolo Galtieri <[email protected]> wrote:

I even tried with systemd.unified_cgroup_hierarchy=1 with the same result.  
What do I need to do to resolve these failures?

I suggest you do not try to fix these things at all.
Some of the changes risk breaking systemd.

Try using virt lib manager to create a vm and test that what you need works.
This all works for me with no tuning of kernel command line.

Barry


What I find interesting is that there is a difference between F43 and Ubuntu 24.04. Here is the boot line on Ubuntu

BOOT_IMAGE=/boot/vmlinuz-6.14.0-1020-oem root=UUID=d86db02c-3292-4ddb-a29f-217181a50592 ro quiet splash intel_iommu=on cgroup_enable=devices systemd.unified_cgroup_hierarchy=0 vt.handoff=7

Here is the boot line on F43

BOOT_IMAGE=(hd8,gpt2)/vmlinuz-6.18.7-200.fc43.x86_64 root=UUID=0339e593-808e-4f94-9413-8b8302a5720c ro rootflags=subvol=root rhgb quiet intel_iommu=on cgroup_enable=devices systemd.unified_cgroup_hierarchy=0

They are almost identical. On Ubuntu I don't see the failures. Both are running cgroup2.

The Ubuntu system is only a few weeks old while the F43 system is several years old. I don't know if this plays a part.

I've only recently upgraded my system to F43. Under F42 I had a lot of problems creating a VM, mostly related to permission denied errors. I have created a VM on Ubuntu prior to making the kernel changes so I'm certain that these failures do not directly affect creating a VM. I'm also waiting for the update to bug 2277235 so that I can create an F43 VM.

Paolo
--
_______________________________________________
users mailing list -- [email protected]
To unsubscribe send an email to [email protected]
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/[email protected]
Do not reply to spam, report it: 
https://forge.fedoraproject.org/infra/tickets/issues/new

Reply via email to