Hi,
Could you please create a bug for the oVirt project on
https://bugzilla.redhat.com and attach logs from your oVirt Engine using
sos logcollector?
https://www.ovirt.org/documentation/administration_guide/#sect-The_Log_Collector_Tool
Thanks,
Martin
On Thu, Mar 11, 2021 at 11:40 PM wrote:
>
I've re-installed oVirt 4.4.4 without capital letter, I continue to get the
same results. Do you have any idea of where to start looking for a solution?
What could the error message "Internal Server Error" be coming from, "oVirt",
"FireFox Browser" or "Apache Server". Where do I start lookin
Just move it away (to be on the safe side) and trigger a full heal.
Best Regards,
Strahil Nikolov
В сряда, 10 март 2021 г., 13:01:21 ч. Гринуич+2, Maria Souvalioti
написа:
Should I delete the file and restart glusterd on the ov-no1 server?
Thank you very much
On 3/10/21 10:2
It seems that the affected file can be moved away on ov-no1.ariadne-t.local, as
the other 2 bricks "blame" the entry on ov-no1.ariadne-t.local .
After that , you will need to "gluster volume heal full" to
trigger the heal.
Best Regards,
Strahil Nikolov
В сряда, 10 март 2021 г., 12:58:10
Hi Arik,
You are right. I tried this syntax and it worked:
olvm-vmcontrol -m -u api_cpu_pin@internal -v -c setvcpu -s
0-19,40-59 -e
(Pinning to 40 Physical cpus).
Will see how to convert a long list of digits to the shorten syntax...
Thanks,
Lavi
_
On Thu, Mar 11, 2021 at 5:20 PM lavi.buchnik--- via Users
wrote:
> Hi Arik,
>
> I'm using this tool to pin the VM cpu's:
> olvm-vmcontrol -m -u api_cpu_pin@internal -v -c setvcpu -s
> 0,1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,17,18,19,40,41,42,43,44,45,46,47,48,49,50,51,52,53,54,55
> -e
>
So th
Hi Arik,
I'm using this tool to pin the VM cpu's:
olvm-vmcontrol -m -u api_cpu_pin@internal -v -c setvcpu -s
0,1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,17,18,19,40,41,42,43,44,45,46,47,48,49,50,51,52,53,54,55
-e
Thanks,
Lavi
___
Users mailing list --
On Thu, Mar 11, 2021 at 4:27 PM lavi.buchnik--- via Users
wrote:
> Hi,
>
> When trying to pin a VM CPU's to Physical CPU's, I'm getting this error in
> case the number of physical CPU slots are > 35 (e.g. 40):
>
> Error attempting to pin CPUs.
> Full error: Fault reason is "Operation Failed". Fau
Hi,
When trying to pin a VM CPU's to Physical CPU's, I'm getting this error in case
the number of physical CPU slots are > 35 (e.g. 40):
Error attempting to pin CPUs.
Full error: Fault reason is "Operation Failed". Fault detail is "[size must be
between 0 and 4000, Attribute: vmStatic.cpuPinnin
9 matches
Mail list logo
