You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Deprecate the `cpu_template` field in the `/machine-config` API, which
is used to set static CPU templates. Users can use custom CPU templates
as an alternative.
To differentiate between explicitly specifying `None` and not specifying
anything, wrap the `cpu_template` of the `MachineConfig` with `Option`.
With this, it can notify the deprecation of only users using the field.
Signed-off-by: Takahiro Itazuri <itazur@amazon.com>
Copy file name to clipboardExpand all lines: docs/cpu_templates/cpu-templates.md
+6Lines changed: 6 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -34,6 +34,12 @@ Firecracker supports two types of CPU templates:
34
34
- Custom CPU templates - users can create their own CPU templates in json
35
35
format and pass them to Firecracker
36
36
37
+
> **Note**
38
+
Staitc CPU templates are deprecated starting with v1.5.0. It will be removed in
39
+
accordance with our policy. Even after dropping the support, users can use
40
+
custom CPU templates as an alternative. For more details, please refer here (
41
+
link to the GitHub discussion to be added).
42
+
37
43
> **Note**
38
44
CPU templates for ARM (both static and custom) require the following patch
39
45
to be available in the host kernel: [Support writable CPU ID registers from userspace](https://lore.kernel.org/kvm/20230212215830.2975485-1-jingzhangos@google.com/#t).
0 commit comments