Skip to content
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

runtime: agent: use PCI segments 1+ for blk devices #183

Merged
merged 5 commits into from
Apr 30, 2024

Commits on Apr 24, 2024

  1. Revert "runtime: agent: use up to 10 PCI segments (#61)"

    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 <dmihai@microsoft.com>
    danmihai1 committed Apr 24, 2024
    Configuration menu
    Copy the full SHA
    823dcd2 View commit details
    Browse the repository at this point in the history
  2. runtime: clh: clean-up merge from main

    Initialize the CLH Platform a single time.
    
    Signed-off-by: Dan Mihai <dmihai@microsoft.com>
    danmihai1 committed Apr 24, 2024
    Configuration menu
    Copy the full SHA
    6a47c86 View commit details
    Browse the repository at this point in the history

Commits on Apr 25, 2024

  1. runtime: agent: use PCI segments 1+ for blk devices

    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 <dmihai@microsoft.com>
    danmihai1 committed Apr 25, 2024
    Configuration menu
    Copy the full SHA
    c905577 View commit details
    Browse the repository at this point in the history
  2. samples: pod with ~70 image layers

    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 <dmihai@microsoft.com>
    danmihai1 committed Apr 25, 2024
    Configuration menu
    Copy the full SHA
    bbc7b97 View commit details
    Browse the repository at this point in the history

Commits on Apr 30, 2024

  1. genpolicy: update sample location

    Move pod-many-layers.yaml to needs_containerd_pull category
    
    Signed-off-by: Saul Paredes <saulparedes@microsoft.com>
    Redent0r committed Apr 30, 2024
    Configuration menu
    Copy the full SHA
    cbb60ff View commit details
    Browse the repository at this point in the history