-
Notifications
You must be signed in to change notification settings - Fork 1.9k
[Platforms] AMD CPU support #651
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
Comments
@raduweiss looking forward to AMD and ARM support in 2019. https://aws.amazon.com/about-aws/whats-new/2018/11/firecracker-lightweight-virtualization-for-serverless-computing/ |
I was at least able to boot a VM on a Ryzen level CPU. So the basics at least work. I'll update if I run into any blockers (and maybe even try to fix them).
|
@iggy , out of curiosity, do all integration tests pass on that machine? |
Some, but not all of them. The output is quite long, so I'll link to a termbin. |
I'm running an AMD FX processor and it doesn't work for me. Here's the flags not present in my processor that are in @iggy 's
Of all these 🤷♂️ |
I recently switched to a Threadripper 1950X, however in contrast to @iggy vms do not fully start (they hang after rng init). |
Here's the cpuinfo from the actual host (vs the one above being inside the actual VM) https://gist.github.com/iggy/7c72e0d3de86e37cafd3ce9032352316 |
Here's the CPU flag diff between @iggy's CPU flags (Ryzen Zen microarchitecture) and mine (FX - Bulldozer family)
|
Odd. I also have a FX-series processor and the only tests that are failing are |
I'll close this tracking milestone and move all AMD issues to a milestone. |
Uh oh!
There was an error while loading. Please reload this page.
Ensure Firecracker and all it's features work on AMD. While most functionality should carry over without changes, the cpu masking feature is not implemented for AMD.
Task breakdown:
The text was updated successfully, but these errors were encountered: