On 29. 3. 2021, at 14:43, Roman Bednar <rbednar(a)redhat.com>
wrote:
Hi Andrei,
kvm64 is a legacy type, not recommended for use by qemu project [1]. I suppose that's
the reason it's been left out from the list you're looking at.
we only include ~10 years old CPUs, anything older is usually not useful these days
Not sure how this is implemented exactly, anyway it seems like you can type in any custom
value into the field for cpu type, instead of just picking one from the list provided. It
seems to have worked for me:
yes, you can use any CPU type supported by qemu. They may not work of course, depending on
your hw and other features we configure by default for a VM.
# virsh -r dumpxml vm1 | xpath -q -e "//domain/cpu/model"
<model fallback="forbid">kvm64</model>
# virsh -r list
Id Name State
----------------------
1 vm1 running
[1]
https://qemu-project.gitlab.io/qemu/system/qemu-cpu-models.html#other-non...
<
https://qemu-project.gitlab.io/qemu/system/qemu-cpu-models.html#other-non...
-Roman
On Mon, Mar 29, 2021 at 10:23 AM Andrei Verovski <andreil1(a)starlett.lv
<mailto:andreil1@starlett.lv>> wrote:
Hi,
OK, thanks, found this option.
But host CPU type “KVM64” is not available here, only Conroe, Penryn, Nehalem, Westmere.
Where I can add CPU type “KVM64” in this list?
> On 29 Mar 2021, at 11:00, Ritesh Chikatwar <rchikatw(a)redhat.com
<mailto:rchikatw@redhat.com>> wrote:
>
> Hello,
>
> Yes , There is an option but I have not tried.
> Log in to the portal and edit the vm properties.
> Steps:
>
> Select VM -> Edit -> Click System Tab -> then click Advanced Parameter ->
Custom CPU Type
>
> <Screenshot from 2021-03-29 13-29-40.png>
>
> On Mon, Mar 29, 2021 at 12:37 PM Andrei Verovski <andreil1(a)starlett.lv
<mailto:andreil1@starlett.lv>> wrote:
> Hi !
>
>
> Is it possible to set host CPU type to kvm64 for a single VM ?
>
>
> Thanks.
> Andrei
>
> _______________________________________________
> Users mailing list -- users(a)ovirt.org <mailto:users@ovirt.org>
> To unsubscribe send an email to users-leave(a)ovirt.org
<mailto:users-leave@ovirt.org>
> Privacy Statement:
https://www.ovirt.org/privacy-policy.html
<
https://www.ovirt.org/privacy-policy.html>
> oVirt Code of Conduct:
https://www.ovirt.org/community/about/community-guidelines/
<
https://www.ovirt.org/community/about/community-guidelines/>
> List Archives:
https://lists.ovirt.org/archives/list/users@ovirt.org/message/MFTVL6WIALN...
<
https://lists.ovirt.org/archives/list/users@ovirt.org/message/MFTVL6WIALN...
_______________________________________________
Users mailing list -- users(a)ovirt.org <mailto:users@ovirt.org>
To unsubscribe send an email to users-leave(a)ovirt.org
<mailto:users-leave@ovirt.org>
Privacy Statement:
https://www.ovirt.org/privacy-policy.html
<
https://www.ovirt.org/privacy-policy.html>
oVirt Code of Conduct:
https://www.ovirt.org/community/about/community-guidelines/
<
https://www.ovirt.org/community/about/community-guidelines/>
List Archives:
https://lists.ovirt.org/archives/list/users@ovirt.org/message/WNPVLRRAH7Z...
<
https://lists.ovirt.org/archives/list/users@ovirt.org/message/WNPVLRRAH7Z...
_______________________________________________
Users mailing list -- users(a)ovirt.org
To unsubscribe send an email to users-leave(a)ovirt.org
Privacy Statement:
https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct:
https://www.ovirt.org/community/about/community-guidelines/
List Archives:
https://lists.ovirt.org/archives/list/users@ovirt.org/message/X2NTGFKFHET...