-
Notifications
You must be signed in to change notification settings - Fork 120
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
Ensure support for x86-64-v2 when creating VMs for each node #253
Comments
Yes, this is also needed for ACS as qemu64 is not the right CPU for the job :-) |
You can overwrite the cpu in your cluster.yml via:
I will double check if it make sense to change the defaults because of newer os/qemu version |
I believe |
+1 for making it default and also the options should be documented outside of the container native virtualization usecase, since they are needed for usecases outside of nested virtualization. |
For testing purpose, I added |
Branch libvirt-xml-improvements merged into devel. |
Released in 2023-06-22 |
This is a small but I believe meaningful enhancement request.
I am using RHEL 9 as host. With several container images, I have encountered the following issue at runtime:
Based on this I checked that my CPU (Xeon E5-1650 v3) does actually satisfy the criteria for x86-64-v2:
The problem can actually be fixed by modifying the CPU settings of each VM to use the
host-model
. See e.g. here. With my compact setup (3 master/worker nodes), I used the following command:After restarting each VM, the issue no longer appears.
I believe it would make sense to set this automatically with the playbook already at cluster creation, when setting up the VMs of each node.
The text was updated successfully, but these errors were encountered: