On Mon, May 19, 2025 at 3:20 AM Alistair Francis <alistai...@gmail.com> wrote: > > On Tue, May 6, 2025 at 8:47 AM Daniel Henrique Barboza > <dbarb...@ventanamicro.com> wrote: > > > > Hi Alistair, > > > > > > I think we should push this upstream and see what happens. We'll have a > > full release cycle to undo the change in case we find unintended side > > effects. I'm fairly optimistic that this change will be a no-op for most > > users and will benefit us when we'll have to deal with RVA23 specific > > software. > > I worry it will cause us grief in the future. I think if we are > changing it we should just drop any default. > > With profiles now becoming popular it's easy for users to just pick a > profile CPU when starting the machine. >
Hi Alistair, FYI the next virt-manager release will default to maximum CPU on riscv if the guest type is QEMU. Basically if you are using libvirt/QEMU (non-KVM guests) and setup VMs with virt-install it will get maximum CPU. See PR: https://github.com/virt-manager/virt-manager/pull/784 Our current instructions in Fedora/RISCV set cpu to max too. This is done by passing --cpu mode=maximum to virt-install command. david
