Skip to content

METAL-1750: baremetal: use q35 machine type with EFI firmware for bootstrap VM#10349

Open
elfosardo wants to merge 1 commit intoopenshift:mainfrom
elfosardo:q35-efi-metal-support
Open

METAL-1750: baremetal: use q35 machine type with EFI firmware for bootstrap VM#10349
elfosardo wants to merge 1 commit intoopenshift:mainfrom
elfosardo:q35-efi-metal-support

Conversation

@elfosardo
Copy link
Contributor

The bootstrap VM domain definition did not set a machine type, causing libvirt to default to the deprecated pc-i440fx-rhel7.6.0 chipset on CentOS Stream 9 hosts. This has been correlated with intermittent bootstrap VM startup failures in CI where the VM becomes unreachable after QEMU starts.

Explicitly set the machine type to q35 with EFI firmware for x86_64, matching the pattern already used for aarch64 and aligning with how dev-scripts provisions master/worker VMs.

The arch-specific domain configuration is extracted into a separate configureDomainArch() function with unit tests.

Assisted-By: Claude 4.6 Opus High

@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Mar 3, 2026
@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented Mar 3, 2026

@elfosardo: This pull request references METAL-1750 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.22.0" version, but no target version was set.

Details

In response to this:

The bootstrap VM domain definition did not set a machine type, causing libvirt to default to the deprecated pc-i440fx-rhel7.6.0 chipset on CentOS Stream 9 hosts. This has been correlated with intermittent bootstrap VM startup failures in CI where the VM becomes unreachable after QEMU starts.

Explicitly set the machine type to q35 with EFI firmware for x86_64, matching the pattern already used for aarch64 and aligning with how dev-scripts provisions master/worker VMs.

The arch-specific domain configuration is extracted into a separate configureDomainArch() function with unit tests.

Assisted-By: Claude 4.6 Opus High

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci openshift-ci bot requested review from dtantsur and iurygregory March 3, 2026 14:28
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Mar 3, 2026

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign iurygregory for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@elfosardo
Copy link
Contributor Author

/retest

1 similar comment
@elfosardo
Copy link
Contributor Author

/retest

The bootstrap VM domain definition did not set a machine type,
causing libvirt to default to the deprecated pc-i440fx-rhel7.6.0
chipset on CentOS Stream 9 hosts. This has been correlated with
intermittent bootstrap VM startup failures in CI where the VM
becomes unreachable after QEMU starts.

Explicitly set the machine type to q35 with EFI firmware for
x86_64, matching the pattern already used for aarch64 and
aligning with how dev-scripts provisions master/worker VMs.

The arch-specific domain configuration is extracted into a
separate configureDomainArch() function with unit tests.

Assisted-By: Claude 4.6 Opus High
@elfosardo elfosardo force-pushed the q35-efi-metal-support branch from 53a7f2e to 2399c31 Compare March 4, 2026 08:44
@tdomnesc
Copy link
Contributor

tdomnesc commented Mar 4, 2026

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Mar 4, 2026
@dtantsur
Copy link
Member

dtantsur commented Mar 4, 2026

Looks good but conflicts with #9814 which should go in first. Sorry for the delay.

/approve
/hold

@elfosardo
Copy link
Contributor Author

@dtantsur I'm ok merging #9814 first, JFYI this is needed to fix some flaky jobs in CI

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Mar 4, 2026

@elfosardo: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
ci/prow/e2e-metal-ovn-two-node-fencing 2399c31 link false /test e2e-metal-ovn-two-node-fencing

Full PR test history. Your PR dashboard.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

@elfosardo
Copy link
Contributor Author

/hold

@openshift-ci openshift-ci bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Mar 6, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants