Hello,
To confirm, changing MaxNumOfCpusCoefficient solved my issue.
64
Thank you for the help.
Regards,
David
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement:
Hello,
Not sure about the feature part. I additionally tested this on oVirt
4.4.10.7-1.el8 and it works fine even if cluster compatibility there is set to
4.6.
Engine:
MaxNumOfVmSockets: 32 version: 4.2
MaxNumOfVmSockets: 32 version: 4.3
MaxNumOfVmSockets: 32 version: 4.4
MaxNumOfVmSockets: 32
Hello,
I recently upgraded our cluster from 4.3 to 4.5 (4.5.1.3-1.el8), I raised the
cluster compatibility afterwards to 4.7 as well. I noticed that the CPU hot
plugging does not work above 16 CPU's if cluster compatibility is set to 4.6 or
4.7.
Error I get is:
Failed to hot set number of
ou on VMs that might have this issues
> and let you know before you resume the upgrade.
>
>
> On Fri, Apr 22, 2022 at 8:04 PM David Sekne wrote:
>
>> Hello,
>>
>> I followed the documentation on updating the compatibility version. We
>> had no issues with NIC'
t and set the password based on the first 8 chars, i
> don't know from which version that happened but in 4.4.10 you won't be able
> to use VNC so i recommend to use SPICE (which is actually much better).
>
>
>
> On Fri, Apr 22, 2022 at 2:57 PM David Sekne wrote:
>
>>
gi?id=1774230
>
> On Fri, May 29, 2020 at 3:54 PM David Sekne wrote:
> >
> > Hello,
> >
> > I tried the live migrate as well and it didn't help (it failed).
> >
> > The VM disks were in a illegal state so I ended up restoring the VM from
> backup (It was lea
> >written to the current active layer, vdsm may have trouble finishing
> >the synchronization
> >
> >
> >On Wed, May 27, 2020 at 4:55 PM David Sekne
> >wrote:
> >>
> >> Hello,
> >>
> >> Yes, no problem. XML is attached (I ommit
efore the VM switches to use
> it as the active layer. So if there is constantly additional data
> written to the current active layer, vdsm may have trouble finishing
> the synchronization
>
>
> On Wed, May 27, 2020 at 4:55 PM David Sekne wrote:
> >
> > Hello,
> >
Hello,
Yes, no problem. XML is attached (I ommited the hostname and IP).
Server is quite big (8 CPU / 32 Gb RAM / 1 Tb disk) yet not overloaded. We
have multiple servers with the same specs with no issues.
Regards,
On Wed, May 27, 2020 at 2:28 PM Benny Zlotnik wrote:
> Can you share the VM's
Hello,
Running virsh blockjob sda --info a couple of times it shows 99 or 100
%. Looks like it is stuck / flapping for some reason.
Active Block Commit: [ 99 %]
Active Block Commit: [100 %]
What would be the best approach to resolve this?
I see taskcleaner.sh can be used in cases like these?
Hello,
Thank you for the reply.
Unfortunately I cant see the task on any on the hosts:
vdsm-client Task getInfo taskID=f694590a-1577-4dce-bf0c-3a8d74adf341
vdsm-client: Command Task.getInfo with args {'taskID':
'f694590a-1577-4dce-bf0c-3a8d74adf341'} failed:
(code=401, message=Task id unknown:
Hello,
I'm running oVirt version 4.3.9.4-1.el7.
After a failed live storage migration a VM got stuck with snapshot.
Checking the engine logs I can see that the snapshot removal task is
waiting for Merge to complete and vice versa.
2020-05-26 18:34:04,826+02 INFO
Hello,
I'm running oVirt version 4.3.9.4-1.el7. After a failed live storage migration
VM got stuck with snapshot. Checking the engine logs I can see that the
snapshot removal task is waiting for Merge to complete and vice versa.
2020-05-26 18:34:04,826+02 INFO
13 matches
Mail list logo