-
Notifications
You must be signed in to change notification settings - Fork 190
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
Option to disable CPU template in runtime config for non-Intel support #525
Comments
Let me take a look. I'm doing #531 for ARM, but I need to detect AMD as well... |
kzys
added a commit
to kzys/firecracker-containerd
that referenced
this issue
Aug 4, 2021
It doesn't work AMD's x86_64 processors sadly. Fixes firecracker-microvm#525. Signed-off-by: Kazuyoshi Kato <[email protected]>
kzys
added a commit
to kzys/firecracker-containerd
that referenced
this issue
Aug 4, 2021
It doesn't work AMD's x86_64 processors sadly. Fixes firecracker-microvm#525. Signed-off-by: Kazuyoshi Kato <[email protected]>
kzys
added a commit
to kzys/firecracker-containerd
that referenced
this issue
Aug 4, 2021
It doesn't work AMD's x86_64 processors sadly. Fixes firecracker-microvm#525. Signed-off-by: Kazuyoshi Kato <[email protected]>
Working perfectly, thanks! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi!
Currently firecracker-containerd is enforcing CPU template as a runtime config where default T2 template is pinned in the config
firecracker-containerd/config/config.go
Line 90 in 4f43968
Due to only the fact that only Intel flavored T2 and C3 instance types are supported, when I ran the quick start example on an AMD x86 machine firecracker threw
I believe this error is raised by:
https://github.com/firecracker-microvm/firecracker/blob/35829883994e69c807f52b9efea915c5ad42f45f/src/cpuid/src/template/intel/mod.rs#L14-L16
On the other hand it runs perfectly fine on the AMD machine when
CPUTemplate
is not passed intomodels.MachineConfiguration
with something looks like:This makes me wonder given non-Intel template isn't supported at the moment, will it be useful to provide an option in the config to enable/disable the CpuTemplate (maybe something called
disable_cpu_template
default to false), so thatfirecracker-containerd
can run on AMD/Arm.The text was updated successfully, but these errors were encountered: