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

Drop support for Linux host 4.14 #4689

Merged
merged 6 commits into from
Jul 18, 2024
Merged

Conversation

pb8o
Copy link
Contributor

@pb8o pb8o commented Jul 18, 2024

Changes

Drop support for running Firecracker on host Linux 4.14

Reason

Linux 4.14 has been EOL since January 2024.

License Acceptance

By submitting this pull request, I confirm that my contribution is made under
the terms of the Apache 2.0 license. For more information on following Developer
Certificate of Origin and signing off your commits, please check
CONTRIBUTING.md.

PR Checklist

  • If a specific issue led to this PR, this PR closes the issue.
  • The description of changes is clear and encompassing.
  • Any required documentation changes (code and docs) are included in this
    PR.
  • API changes follow the Runbook for Firecracker API changes.
  • User-facing changes are mentioned in CHANGELOG.md.
  • All added/changed functionality is tested.
  • New TODOs link to an issue.
  • Commits meet
    contribution quality standards.

  • This functionality cannot be added in rust-vmm.

@pb8o pb8o added Priority: Low Indicates that an issue or pull request should be resolved behind issues or pull requests labelled ` Type: Documentation Indicates a need for improvements or additions to documentation Status: Awaiting author Indicates that an issue or pull request requires author action labels Jul 18, 2024
@pb8o pb8o self-assigned this Jul 18, 2024
@pb8o pb8o requested review from xmarcalx and kalyazin as code owners July 18, 2024 09:26
pb8o added 6 commits July 18, 2024 11:32
Kernel 4.14 has reached End of Life and is not supported by upstream.

This should also reduce our CI costs by 1/3.

Signed-off-by: Pablo Barbáchano <pablob@amazon.com>
We are dropping support for Linux host 4.14, so we don't need a special
5.10 guest kernel anymore.

Signed-off-by: Pablo Barbáchano <pablob@amazon.com>
We are dropping support for Linux 4.14 so they are no longer needed.

Signed-off-by: Pablo Barbáchano <pablob@amazon.com>
We are dropping support for Linux 4.14 so reflect it in the docs.

Signed-off-by: Pablo Barbáchano <pablob@amazon.com>
Remove code to support Linux 4.14.

Firecracker/Jailer will only work with kernel 5.10 and above.

Signed-off-by: Pablo Barbáchano <pablob@amazon.com>
Fix typo in the documentation

Signed-off-by: Pablo Barbáchano <pablob@amazon.com>
Copy link

codecov bot commented Jul 18, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 81.92%. Comparing base (4cd47bd) to head (7f82141).

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #4689      +/-   ##
==========================================
- Coverage   82.16%   81.92%   -0.24%     
==========================================
  Files         255      253       -2     
  Lines       31361    31108     -253     
==========================================
- Hits        25768    25486     -282     
- Misses       5593     5622      +29     
Flag Coverage Δ
4.14-c5n.metal ?
4.14-m5n.metal ?
4.14-m6a.metal ?
4.14-m6g.metal ?
4.14-m6i.metal ?
4.14-m7g.metal ?
5.10-c5n.metal 82.16% <100.00%> (-0.02%) ⬇️
5.10-m5n.metal 82.14% <100.00%> (-0.02%) ⬇️
5.10-m6a.metal ?
5.10-m6g.metal 79.45% <100.00%> (-0.03%) ⬇️
5.10-m6i.metal 82.15% <100.00%> (-0.02%) ⬇️
5.10-m7g.metal ?
6.1-c5n.metal 82.16% <100.00%> (-0.02%) ⬇️
6.1-m5n.metal 82.14% <100.00%> (-0.03%) ⬇️
6.1-m6a.metal ?
6.1-m6g.metal 79.45% <100.00%> (-0.03%) ⬇️
6.1-m6i.metal 82.14% <100.00%> (-0.02%) ⬇️
6.1-m7g.metal 79.45% <100.00%> (-0.03%) ⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@pb8o pb8o added Status: Awaiting review Indicates that a pull request is ready to be reviewed and removed Status: Awaiting author Indicates that an issue or pull request requires author action labels Jul 18, 2024
Copy link
Contributor

@xmarcalx xmarcalx left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Doc changes looks good to me, thanks for the change

@ShadowCurse ShadowCurse merged commit 643349a into firecracker-microvm:main Jul 18, 2024
8 checks passed
@zulinx86 zulinx86 mentioned this pull request Jul 18, 2024
4 tasks
roypat added a commit to roypat/firecracker that referenced this pull request Jul 22, 2024
io_uring is not supported on 4.14 hosts. Since firecracker-microvm#4689 dropped
support for 4.14 hosts, and 5.10 does support io_uring, remove various
checks related to unsupported (4.14) host kernels.

Signed-off-by: Patrick Roy <roypat@amazon.co.uk>
roypat added a commit to roypat/firecracker that referenced this pull request Jul 23, 2024
io_uring is not supported on 4.14 hosts. Since firecracker-microvm#4689 dropped
support for 4.14 hosts, and 5.10 does support io_uring, remove various
checks related to unsupported (4.14) host kernels.

Also update some of our unittests to always test both the sync and async
block engines. Previously, we only tested the sync engine on 4.14 hosts,
and only the async engien on 5.10 hosts. With the removal of 4.14 hosts,
this meant that we were no longer unittesting the sync engine in these
tests at all. Thus, have all the tests unconditionally test both
engines.

Signed-off-by: Patrick Roy <roypat@amazon.co.uk>
zulinx86 pushed a commit that referenced this pull request Jul 23, 2024
io_uring is not supported on 4.14 hosts. Since #4689 dropped
support for 4.14 hosts, and 5.10 does support io_uring, remove various
checks related to unsupported (4.14) host kernels.

Also update some of our unittests to always test both the sync and async
block engines. Previously, we only tested the sync engine on 4.14 hosts,
and only the async engien on 5.10 hosts. With the removal of 4.14 hosts,
this meant that we were no longer unittesting the sync engine in these
tests at all. Thus, have all the tests unconditionally test both
engines.

Signed-off-by: Patrick Roy <roypat@amazon.co.uk>
ghost pushed a commit to JamesC1305/firecracker that referenced this pull request Aug 14, 2024
io_uring is not supported on 4.14 hosts. Since firecracker-microvm#4689 dropped
support for 4.14 hosts, and 5.10 does support io_uring, remove various
checks related to unsupported (4.14) host kernels.

Also update some of our unittests to always test both the sync and async
block engines. Previously, we only tested the sync engine on 4.14 hosts,
and only the async engien on 5.10 hosts. With the removal of 4.14 hosts,
this meant that we were no longer unittesting the sync engine in these
tests at all. Thus, have all the tests unconditionally test both
engines.

Signed-off-by: Patrick Roy <roypat@amazon.co.uk>
@pb8o pb8o deleted the eol-4-14 branch October 9, 2024 07:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Priority: Low Indicates that an issue or pull request should be resolved behind issues or pull requests labelled ` Status: Awaiting review Indicates that a pull request is ready to be reviewed Type: Documentation Indicates a need for improvements or additions to documentation
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants