On Wed, Mar 15, 2023 at 03:40:18PM +0100, Ján Tomko wrote:
On a Monday in 2023, Jim Fehlig wrote:
If an explicit machine type is not specified in the VM config, the qemu driver will select the first machine type in the list of machine types for the specified accelerator. See virQEMUCapsGetPreferredMachine
https://gitlab.com/libvirt/libvirt/-/blob/master/src/qemu/qemu_capabilities....
On my test machines, this works reasonably well for x86_64 where the first machine type is pc-i440fx-7.1. But for aarch64, the first machine is integratorcp, which is not very useful with maxCpus=1 and other limitations.
Is it possible to run such machine with libvirt?
If not, we could say our default is faulty and pick a new one.
Good point. If we can prove that it's not possible to define a working VM when using the default machine type (integratorcp for Arm and spike_v1.10 for RISC-V), I think we'd have a fairly solid argument in favor of changing our defaults. -- Andrea Bolognani / Red Hat / Virtualization