Skip to content

Commit d4f917e

Browse files
committed
ci: don't apply VMGenID patches for guest ARM 6.1
AmazonLinux has backported the patches for 6.1 and we are now building from their tree, so we don't need to manually apply the patches when we re-create CI artifacts. Signed-off-by: Babis Chalios <bchalios@amazon.es>
1 parent 9157a0c commit d4f917e

File tree

5 files changed

+4
-463
lines changed

5 files changed

+4
-463
lines changed

docs/snapshotting/random-for-clones.md

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -137,8 +137,10 @@ Firecracker supports VMGenID on ARM systems using the DeviceTree binding that
137137
was added for the device in Linux 6.10. However, the latest Linux kernel that
138138
Firecracker supports is 6.1. As a result, in order to use VMGenID on ARM
139139
systems, users need to use a 6.1 kernel with the DeviceTree binding support
140-
backported from 6.10. We provide a set of patches that apply cleanly on mainline
141-
Linux 6.1 [here](../../resources/patches/vmgenid_dt).
140+
backported from 6.10. For our CI we backport the
141+
[relevant changes](https://github.com/torvalds/linux/commit/f0cd69b8cca6a5096463644d6dacc9f991bfa521)
142+
from 6.10 to 6.1. Consumers of Firecracker that want to use the feature on ARM
143+
need to ensure they backport these changes on their guest kernels.
142144

143145
Please note that, Firecracker will always enable VMGenID. In kernels where there
144146
is no VMGenID driver, the device will not have any effect in the guest.

resources/patches/vmgenid_dt/0001-virt-vmgenid-change-implementation-to-use-a-platform.patch

Lines changed: 0 additions & 174 deletions
This file was deleted.

resources/patches/vmgenid_dt/0002-dt-bindings-rng-Add-vmgenid-support.patch

Lines changed: 0 additions & 135 deletions
This file was deleted.

0 commit comments

Comments
 (0)