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

Windows buildkite agents need AMD/Intel dual configuration #40

Open
staticfloat opened this issue Jan 1, 2023 · 0 comments
Open

Windows buildkite agents need AMD/Intel dual configuration #40

staticfloat opened this issue Jan 1, 2023 · 0 comments

Comments

@staticfloat
Copy link
Member

When running on amdci6, our windows KVM configuration uses the following CPU block:

  <cpu mode='custom' match='exact' check='full'>
    <model fallback='forbid'>EPYC-IBPB</model>
    <feature policy='disable' name='monitor'/>
    <feature policy='require' name='x2apic'/>
    <feature policy='require' name='hypervisor'/>
    <feature policy='require' name='topoext'/>
    <feature policy='require' name='npt'/>
    <feature policy='require' name='nrip-save'/>
  </cpu>

This allows Hyper-V to run, and enables docker to run on the machines.

On the Intel-based AWS c5d.metal instances that we used during the amdci outage period in December 2022, we found that the following CPU block was necessary:

  <cpu mode="custom" match="exact" check="partial">
    <model fallback="allow">IvyBridge</model>
    <feature policy="require" name="hypervisor"/>
    <feature policy="require" name="vmx"/>
  </cpu>

We should parameterize this somehow, perhaps by having two XML templates, or by splicing in pieces together through a xml_template.d directory structure.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant