Open
Conversation
r2k1
requested review from
AbelHu,
AlisonB319,
Devinwong,
UtheMan,
anujmaheshwari1,
cameronmeissner,
djsly,
ganeshkumarashok,
jason1028kr,
juan-lee,
junjiezhang1997,
lilypan26,
phealy,
timmy-wright and
zachary-bailey
as code owners
lilypan26
force-pushed
the
r2k1/amd-gpu5
branch
from
b4cf970 to
5523fcd
Compare
Contributor
|
No changes to cached containers or packages on Windows VHDs |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What type of PR is this?
/kind feature
What this PR does / why we need it:
Add support for AMD GPUs. Install AMD GPU Kernel drivers if user didn't specify
--skip-gpu-driverinstall.AMD Operates differently to NVidia. A kernel driver is required on the host VM. Additionally containers should have ROCm suite installed (which is blowing container size images to 60GB+, but it's on AMD).
With this change .deb packages are cached on the VM, but doesn't install until required (adds about 30MB overhead).
Once installed it takes about 600-1000MB of additional space.
We don't have a reliable quota for the VM SKUs in the test subscription. And VM allocation isn't reliable either.
So automatic testing is disabled until we manage to sort it out somehow.