-
Notifications
You must be signed in to change notification settings - Fork 123
Fedora 43 upgrade #2729
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
base: main
Are you sure you want to change the base?
Fedora 43 upgrade #2729
Conversation
|
Depends on #2730 |
|
Not sure why TestLibvirtCreateWithCpuAndMemRequestLimit is failing |
|
The important failure is the s390x mkosi job. |
I think this will be that with the new base image the memory requirements are slightly larger, so we probably need to bump them in |
|
@stevenhorsman @mkulke and others, do we want to upgrade to 43 for the upcoming release ? |
I was hoping that we could move to ubuntu instead, but I don't think there will be time for that to happen. I'm not sure we have a way to get the fedora 43 upgrade working though either? |
I'd go with bumping fedora for this release and then updating it in the next, I don't expect ubuntu to work without hickups. we can announce the plan in the release notes. |
Latest supported release Signed-off-by: Pradipta Banerjee <[email protected]>
Kernels after 6.14 are failing to boot on AWS SNP instances and blacklisting vmgenid was found as a workaround. A proper fix is posted upstream - https://www.spinics.net/lists/kernel/msg5976520.html Fixes - confidential-containers#2691 Signed-off-by: Pradipta Banerjee <[email protected]>
|
I have split the kernel cli change to a separate commit |
a PR would be better (if the fix is urgent), since there is probably more work required for s390x |
Upgrading Fedora base to latest supported version till we have Ubuntu podvm image ready