[ovirt-users] Re: Power Saving Schedule

2022-05-19 Thread Lucia Jelinkova
Hi, Could you please try to set the HostsInReserve parameter of the power_saving policy to 1? This should always keep 1 empty host (with no running vms) to be ready in case the others are over utilized. If there are more empty hosts, they should be put into maintenance or shut down, if there is

[ovirt-users] Re: Ignore CPU_TYPE_UNSUPPORTED_IN_THIS_CLUSTER_VERSION ?

2022-02-02 Thread Lucia Jelinkova
Hi, The list should contain more items. Could you please try to create a new cluster using UI, set the compatibility level to 4.6, architecture to x86_64 and check the CPU Type dropdown again? Please try to scroll down the dropdown and if there are no more values than you've already mentioned,

[ovirt-users] Re: Unable to install OVirt 4.4.6 on IvyBridge

2021-11-15 Thread Lucia Jelinkova
Hi, could you please run the following command on the non responsive host and post the output here? virsh domcapabilities Also, could you please go to the Webadmin UI and check the warning signs on the host list and host detail to see, what flags is the host missing? You can also check the CPU

[ovirt-users] Re: Change Cluster CPU type

2021-09-06 Thread Lucia Jelinkova
Please check the engine.log, there should be details of what went wrong with the HostedEngine update. Thanks, Lucia On Thu, Sep 2, 2021 at 9:02 PM Andrey Rusakov wrote: > Exact Error > > Error while executing action: Cannot update cluster because the update > triggered update of the

[ovirt-users] Re: Update to 4.4.8 leaves cluster in a circular error-state

2021-09-06 Thread Lucia Jelinkova
/archives/list/users@ovirt.org/thread/ZTOZO4DO6F6LKHEJLY4HI7GSSZ2T54ZL/#VQC7OCVHXEMRIUR26YXMZMKS5SKWURH7 Regards, Lucia On Fri, Sep 3, 2021 at 6:58 PM Paul-Erik Törrönen wrote: > On 9/2/21 9:16 AM, Lucia Jelinkova wrote: > > Could you please share more details about the CPU problem you'

[ovirt-users] Re: Update to 4.4.8 leaves cluster in a circular error-state

2021-09-02 Thread Lucia Jelinkova
Hi, Could you please share more details about the CPU problem you're facing? There shouldn't be any breaking change in that CPU definition in 4.4+ compatibility version. Regards, Lucia On Wed, Sep 1, 2021 at 7:15 PM Paul-Erik Törrönen wrote: > Having updated rpm-packages for a DC with a

[ovirt-users] Re: adding new host failed with error "CPU does not match the Cluster CPU Type"

2021-08-09 Thread Lucia Jelinkova
It might be that the host is not reporting the host capabilities correctly. You can see all host's supported CPUs in the host detail screen, just roll over the info icon next to the CPU Type. You can check if the data are in the database like this: select cpu_flags from vds where vds_name =

[ovirt-users] Re: CPU Compatibility Problem after Upgrading Centos 8 Stream Host

2021-07-28 Thread Lucia Jelinkova
Hi Christoph, The 20200602gitca407c7246bf-5.el8 is the "broken" one [1], try downgrading to the older version (I have 20200602gitca407c7246bf-4.el8_4.1). 1: https://bugzilla.redhat.com/show_bug.cgi?id=1961558#c6 Regards, Lucia On Wed, Jul 28, 2021 at 9:40 AM Michal Skrivanek <

[ovirt-users] Re: Q: Node host becomes non-operational after upgrade

2021-07-07 Thread Lucia Jelinkova
Hi, The issue has already been discussed in this thread [1]. Please check the version of edk2-ovmf package and downgrade to 20200602gitca407c7246bf-4.el8_4.1 if necessary. Lucia 1: https://lists.ovirt.org/archives/list/users@ovirt.org/thread/D47YYGMGJZIOM3QTDRVNBMRDEPK4ZMCQ/ On Tue, Jul 6,

[ovirt-users] Re: Bad CPU TYPE after Centos 8.3

2020-12-15 Thread Lucia Jelinkova
p and activated > except the 8.3 one). Maybe this is why the cluster table is not updated? > > What do you think, if y remove the 8.3 host, rerun "engine-setup" an > re-add the 8.3 host? > > > Lionel. > > -- > *De: *"Lucia Jelinkova&quo

[ovirt-users] Re: Bad CPU TYPE after Centos 8.3

2020-12-15 Thread Lucia Jelinkova
rl,+arch-capabilities > > > So in your link they said TSX is disabled by default, may i enable it? or > the best option is to change cluster cpu type to lower value? > > Sorry for all my question i'm quite lost > > > Regards, > Lionel. > --

[ovirt-users] Re: Bad CPU TYPE after Centos 8.3

2020-12-15 Thread Lucia Jelinkova
Hi Lionel, Thank you for the output from the virsh command. The interesting part is this: Cascadelake-Server-noTSX Cascadelake-Server The Cascadelake-Server is not usable any more in 8.3 [1] yet that is what the cluster is probably configured with. Could you please run the following query for

[ovirt-users] Re: Bad CPU TYPE after Centos 8.3

2020-12-14 Thread Lucia Jelinkova
Hi Lionel, could you please run the following command on the non responsive host? virsh domcapabilities Also, could you please go to the Webadmin UI and check the warning signs on the host list and host detail to see, what flags is the host missing? You can also check the CPU Type on the host's

[ovirt-users] Re: EPYC CPU not being detected correctly on cluster

2020-11-26 Thread Lucia Jelinkova
ommands I was able to have the CPU properly detected: > > > > # dnf module reset virt > > # dnf module enable virt:8.3 > > # dnf upgrade –nobest > > > > I think virt was in 8.2. > > > > Thank you! > > > > *From:* Lucia Jelinkova >

[ovirt-users] Re: Intel Cascade Lake Family supported

2020-11-23 Thread Lucia Jelinkova
Hi Ramon, yes, it is. However, you should know that if you disabled tsx in the system (or it simply would not be reported in /proc/cpuinfo) you'd need to use the secure variant of the CPU [1]. 1: https://gerrit.ovirt.org/#/c/111242/ Regards, Lucia On Mon, Nov 23, 2020 at 2:29 PM Gianluca

[ovirt-users] Re: EPYC CPU not being detected correctly on cluster

2020-11-23 Thread Lucia Jelinkova
> virtio > > none > > bochs > > ramfb > > > > > > > > > > subsystem > > > > > > default > > mandatory > > requisite > >

[ovirt-users] Re: Can't use ovirt web interface (500 error)

2020-11-20 Thread Lucia Jelinkova
Hi, it seems that the config values in your database are not correct or up to date - it might be worth trying to run the engine-setup again (it should insert the correct values). Lucia On Wed, Nov 18, 2020 at 10:07 AM wrote: > Hi, > After updating to the latest version of ovirt (standalone

[ovirt-users] Re: EPYC CPU not being detected correctly on cluster

2020-11-20 Thread Lucia Jelinkova
Hi, oVirt CPU detection depends on libvirt (and that depends on qemu) CPU models. Could you please run the following command to see what libvirt reports? virsh domcapabilities That should give you the list of CPUs known to libvirt with a usability flag for each CPU. If you find out that the

[ovirt-users] Re: which cpu type should I chose ??

2020-07-22 Thread Lucia Jelinkova
Hi, when you go to the Host details, General tab, there is a CPU Type field. The info icon should list all CPU types supported by the host. [image: Screenshot from 2020-07-22 14-25-36.png] Hope that helps. Lucia On Tue, Jul 21, 2020 at 11:05 AM tommy wrote: > Hi: > > > > 1.My server using as

[ovirt-users] Re: Change Hosted engine VM cluster compatibility version throws error

2020-06-23 Thread Lucia Jelinkova
Ritesh, is this error occurring on master? There was a similar issue some time ago and was fixed. As for the blank compatibility version combo box, are you talking about the field in edit VM or is it blank in edit cluster? Michal, I agree, the patch is awaiting your response to clarify what the

[ovirt-users] Re: Issues deploying 4.4 with HE on new EPYC hosts

2020-05-29 Thread Lucia Jelinkova
Hi, I think I found the problem - our definition of CPU types in the database is not correct. We do autodetection of the CPU type based on the CPU flags but they are not in sync with what we send to the VDSM.

[ovirt-users] Re: Issues deploying 4.4 with HE on new EPYC hosts

2020-05-29 Thread Lucia Jelinkova
When you look into the detail of external-HostedEngineLocal, Genral tab, what is its Origin? On Thu, May 28, 2020 at 11:53 PM Gianluca Cecchi wrote: > On Thu, May 28, 2020 at 3:09 PM Gianluca Cecchi > wrote: > > [snip] > >> >> >> for the cluster type in the mean time I was able to change it to

[ovirt-users] Re: Issues deploying 4.4 with HE on new EPYC hosts

2020-05-28 Thread Lucia Jelinkova
, cpu_flags, cpu_verb from cluster; Thanks, Lucia On Thu, May 28, 2020 at 12:10 PM Gianluca Cecchi wrote: > > Il Gio 28 Mag 2020, 11:59 Lucia Jelinkova ha > scritto: > > >> The cluster should be set to Intel Cascadelake Server Family. I am not >> familiar with the

[ovirt-users] Re: Issues deploying 4.4 with HE on new EPYC hosts

2020-05-28 Thread Lucia Jelinkova
I think you have the same problem as Mark - the cluster is set to use the secure variant of the CPU type but your host does not support all the necessary flags. Intel Cascadelake Server Family - the VM is run with Cascadelake-Server,-hle,-rtm,+arch-capabilities Secure Intel Cascadelake Server

[ovirt-users] Re: Issues deploying 4.4 with HE on new EPYC hosts

2020-05-28 Thread Lucia Jelinkova
This might help: https://lists.ovirt.org/pipermail/users/2017-January/079157.html On Thu, May 28, 2020 at 10:17 AM Gianluca Cecchi wrote: > > > On Wed, May 27, 2020 at 4:13 PM Mark R wrote: > >> Replying to my own post here, I've verified that it's currently not >> possible to do a greenfield

[ovirt-users] Re: Issues deploying 4.4 with HE on new EPYC hosts

2020-05-28 Thread Lucia Jelinkova
Hi, The cluster CPU type should be set to AMD EPYC, because your system does not support Secure AMD EPYC type (it requires the virt-ssbd). Did you by any chance specify the Secure variant during HE setup? Lucia On Wed, May 27, 2020 at 4:13 PM Mark R wrote: > Replying to my own post here, I've

[ovirt-users] Re: oVirt 4.4 pending VM changes on HostedEngine VM

2020-05-28 Thread Lucia Jelinkova
Hi, it is a bug and it is discussed here: https://bugzilla.redhat.com/show_bug.cgi?id=1830872 Note that it is a UI issue and it does not affect the system. Unfortunately, there is no workaround I know of. Lucia On Wed, May 27, 2020 at 2:45 PM Radoslav Milanov wrote: > Hello > > I'm not sure

[ovirt-users] Re: NUMA Pinning bug with Hugepages?

2020-04-15 Thread Lucia Jelinkova
Hi, I think you've hit similar issue as reported here: https://bugzilla.redhat.com/show_bug.cgi?id=1812316 You're right, the hugepages are considered as allocated memory and it is a bug. I am working on a fix right now. Regards, Lucia On Wed, Apr 15, 2020 at 1:21 PM Alan G wrote: > Hi, > >

[ovirt-users] Re: UI lockup

2020-04-08 Thread Lucia Jelinkova
Hi, NS_ERROR_STORAGE_BUSY is an error coming from Mozilla [1] so it is possible it is a problem with your Firefox. You could try steps suggested in [2] to check your local storage integrity (in short: navigate to about:support and click Verify integrity button). [1]