Skip to content

Set q35 hw machine type as default #648

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

Merged
merged 3 commits into from
Sep 25, 2023

Conversation

darmach
Copy link
Member

@darmach darmach commented Sep 18, 2023

Changed nova.conf machine type to q35.

@darmach darmach requested a review from a team as a code owner September 18, 2023 11:13
@@ -0,0 +1,3 @@
[libvirt]
hw_machine_type = q35
num_pcie_ports = 16
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That's going to be backported upstream (right @bbezak ?) - so we probably could set only hw_machine_type?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

master got merged today. backports just started - https://review.opendev.org/c/openstack/kolla-ansible/+/895373

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

stable/yoga merged

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Probably we should have kept this since we can't assume kolla-ansible is up to date on client deployments.

@darmach darmach changed the title Jdarmach/yoga hw machine type Set q35 hw machine type as default Sep 22, 2023
@darmach darmach merged commit 1d39c76 into stackhpc/yoga Sep 25, 2023
@darmach darmach deleted the jdarmach/yoga-hw_machine_type branch September 25, 2023 15:50
upgrade:
- |
Configure Nova to use more modern 'q35' libvirt machine type rather than
'pc' which is considered legacy.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Will there be any impact on existing systems from changing this?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Most likely no - in yoga all instances should have type metadata already, during upgrade check will fail if not. When restarted new vms should use new type afaik.

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

Successfully merging this pull request may close these issues.

4 participants