-
Notifications
You must be signed in to change notification settings - Fork 458
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
Default machine #1014
Default machine #1014
Conversation
Thanks. I am unsure if this is a good idea. The default for the setting would not longer be depending on the schema. Why is this default not improved in libvirt itself? |
The machine type set in libvirt is the one that was first implemented for this architecture. The argument for not changing it to a more capable machine type would break libvirt's backward compatibility guarantees see this email The fix avoids unpleasant surprises if the same terraform module that works on x86_64 fails horrifically on aarch64. |
This is a great change and would be in line with what most users expect. Also, /when/ they see the non-obvious default behaviour of libvirt, they tend to not know or find out about how to deal with this in a general way. +1. |
Ok. I am convinced, but please add a comment explaining what we are doing above the call to |
Done. Please check if it fits. |
If no machine is set, use default types depending on the arch. The selection is taken from https://github.com/virt-manager/virt-manager file virtinst/guest.py function get_recommended_machine(). Signed-off-by: Egbert Eich <eich@suse.com>
Signed-off-by: Egbert Eich <eich@suse.com>
Thanks 🥳 |
@dmacvicar - Thank you! |
…car#1014) * Improve 'machine' type selection If no machine is set, use default types depending on the arch. The selection is taken from https://github.com/virt-manager/virt-manager file virtinst/guest.py function get_recommended_machine(). Signed-off-by: Egbert Eich <eich@suse.com> * Test for getMachineTypeForArch() Signed-off-by: Egbert Eich <eich@suse.com> --------- Signed-off-by: Egbert Eich <eich@suse.com>
The default machine types picked by libvirt on non-x86* architectures are often quite limited and not very useful. For compatibility reasons libvirt picks the machine type that was the first one support for this architecture. virt-installer therefore maintains its own settings.
This patchset implements the same setting for libvirt if the user does not explicitly specify a machine type.
@dmacvicar - could you have a look?