Skip to content

Conversation

@bpradipt
Copy link
Member

Upgrading Fedora base to latest supported version till we have Ubuntu podvm image ready

@bpradipt
Copy link
Member Author

Depends on #2730
Once 2730 is merged, I'll update the commits to use the new base image

@bpradipt bpradipt marked this pull request as draft December 16, 2025 14:08
@bpradipt bpradipt marked this pull request as ready for review December 17, 2025 06:13
@bpradipt
Copy link
Member Author

Not sure why TestLibvirtCreateWithCpuAndMemRequestLimit is failing

@bpradipt
Copy link
Member Author

The important failure is the s390x mkosi job.

Failed to enable unit: Unit cloud-init.service does not exist

@bpradipt bpradipt requested a review from mkulke December 17, 2025 11:06
@stevenhorsman
Copy link
Member

Not sure why TestLibvirtCreateWithCpuAndMemRequestLimit is failing

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 DoTestPodWithCpuMemLimitsAndRequests(t, testEnv, assert, "100m", "100Mi", "200m", "1792Mi") to give us more headroom as we were close to the limit before.

@bpradipt
Copy link
Member Author

@stevenhorsman @mkulke and others, do we want to upgrade to 43 for the upcoming release ?

@stevenhorsman
Copy link
Member

@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?

@mkulke
Copy link
Collaborator

mkulke commented Jan 13, 2026

@stevenhorsman @mkulke and others, do we want to upgrade to 43 for the upcoming release ?

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]>
@bpradipt
Copy link
Member Author

I have split the kernel cli change to a separate commit

@mkulke
Copy link
Collaborator

mkulke commented Jan 21, 2026

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

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

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants