runtime: agent: use PCI segments 1+ for blk devices #183
Conversation
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
This reverts commit 627be9b, that was insufficient. Waiting for blk devices used just the PCI device/slot index, but not the PCI segment/domain index. Signed-off-by: Dan Mihai <[email protected]>
Initialize the CLH Platform a single time. Signed-off-by: Dan Mihai <[email protected]>
danmihai1
changed the title
Hotplug block devices on PCI segments >= 1. PCI segment 0 is used for the network interface, any disks present at Guest boot time, etc. Just bus 0 of each segment is used, and up to 31 devices can be hotplugged to each bus. Signed-off-by: Dan Mihai <[email protected]>
This pod starts successfully when using default AKS-CC settings, and a permissive policy. When the Kata debug options are enabled, this pod fails to start while trying to hotplug image layer index 41. This bug is being investigated. The genpolicy tool should also try to create a smaller policy for this pod, because otherwise "kubectl apply" rejects the policy annotation as being too large. Signed-off-by: Dan Mihai <[email protected]>
danmihai1
force-pushed
the
danmihai1/hotplug7
branch
from
8fe7f89 to
bbc7b97
Compare
manuelh-dev
reviewed
Apr 25, 2024
manuelh-dev
approved these changes
Apr 25, 2024
Redent0r
approved these changes
Apr 30, 2024
Redent0r
reviewed
Apr 30, 2024
|
Test run https://dev.azure.com/mariner-org/mariner/_build/results?buildId=560047&view=ms.vss-test-web.build-test-results-tab (2 failures (1 flake and one addressed by updating test sample)) |
Move pod-many-layers.yaml to needs_containerd_pull category Signed-off-by: Saul Paredes <[email protected]>
sprt
pushed a commit
that referenced
this pull request
Feb 10, 2025
runtime: agent: use PCI segments 1+ for blk devices
sprt
pushed a commit
that referenced
this pull request
Feb 27, 2025
runtime: agent: use PCI segments 1+ for blk devices
sprt
pushed a commit
that referenced
this pull request
Mar 3, 2025
runtime: agent: use PCI segments 1+ for blk devices
sprt
pushed a commit
that referenced
this pull request
Mar 4, 2025
runtime: agent: use PCI segments 1+ for blk devices
sprt
pushed a commit
that referenced
this pull request
Mar 4, 2025
runtime: agent: use PCI segments 1+ for blk devices
sprt
pushed a commit
that referenced
this pull request
Mar 4, 2025
runtime: agent: use PCI segments 1+ for blk devices
sprt
pushed a commit
that referenced
this pull request
Mar 4, 2025
runtime: agent: use PCI segments 1+ for blk devices
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Hotplug block devices on PCI segments >= 1. PCI segment 0 is used for the network interface, any disks present at Guest boot time, etc.
Just bus 0 of each segment is used, and up to 31 devices can be hotplugged to each bus.